Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Ray package to prevent conflicts with other plugins #7

Open
rosswintle opened this issue Nov 16, 2021 · 0 comments · May be fixed by #8
Open

Update Ray package to prevent conflicts with other plugins #7

rosswintle opened this issue Nov 16, 2021 · 0 comments · May be fixed by #8

Comments

@rosswintle
Copy link

rosswintle commented Nov 16, 2021

I have wp-debug-helpers installed alongside Yoast SEO v17.5.

I get:

[16-Nov-2021 08:44:34 UTC] PHP Fatal error:  Uncaught OutOfBoundsException: Package "spatie/ray" is not installed in <PATH>/public_html/content/plugins/wordpress-seo/vendor/composer/InstalledVersions.php:167
Stack trace:
#0 <PATH>/public_html/content/mu-plugins/wp-debug-helpers/vendor/spatie/ray/src/Ray.php(324): Composer\InstalledVersions::getVersion('spatie/ray')
#1 <PATH>/public_html/content/mu-plugins/wp-debug-helpers/vendor/spatie/ray/src/Ray.php(293): Spatie\Ray\Ray->sendRequest(Array)
#2 <PATH>/public_html/content/mu-plugins/wp-debug-helpers/vendor/spatie/ray/src/helpers.php(28): Spatie\Ray\Ray->send(true)
#3 <PATH>/public_html/content/themes/<sometheme>/functions.php(2): ray(true)
#4 <PATH>/public_html/wp/wp-settings.php(546): include('/Users/rosswint...')
#5 <PATH>/public_html/wp-config.php(43): require_once('/Users/rosswint...')
#6 / in <PATH>/public_html/content/plugins/wordpress-seo/vendor/composer/InstalledVersions.php on line 167

WordPress compatibility seems to have been addressed in more recent versions of spatie/ray (see changelog)

So can you please do a composer update spatie/ray and update this plugin?

My update took it to v1.19.5 which fixes this conflict.

I would PR the change myself, but GitHub gets VERY confused about the fact that I want to make a fork of something that is a fork of something that I forked.

ALSO: I don't know if this is part of what's confusing GitHub, but could you update the name in the composer.json? I'm honestly not sure what the impact of doing this would be to existing installs, don't worry if you think it might mess things up.

THANK YOU!!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant