-
Notifications
You must be signed in to change notification settings - Fork 882
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
PHP8 compatibility and installation via Composer #16881
Comments
Hi @sboerrigter . The plugins themselves are compatible with PHP 8.0. However, the composer process isn't and still needs to be ran with PHP 7.x. I believe it's something that's still being worked on and I'm not really sure anymore what the reason(s) are/were. But they were substantial enough that we couldn't just change the requirements in the json file. |
Any update on this? |
Are there any updates on this? |
Any update on this?
|
The plugin still needs to be build on 7.x. There are no updates on PHP 8.0 progression. And just to clarify for others; the plugin does work on PHP8. It's the composer building that needs to be done on 7.x. |
Thanks. That's a big odd....build on 7.x for use on 8.x? FWIW, that creates a LOT of work when doing auto-deployments. It would be great if you could get on with testing and building via standard methods. PHP 8.x has officially been out for a year now... |
As an addition for anyone that this is affecting, there's a workaround in composer that I was not privy to. Given that @Djennez said that Yoast is PHP 8.0 compatible, I felt comfortable doing a platform override. Adding this to my composer worked perfectly.
|
Hi There! 👋
Are the "WordPress SEO" and "WordPress SEO Premium" plugins compatible with PHP 8?
I see that the version constraints in
composer.json
are set to"^5.6.20||^7.0"
, so I cannot install these plugins via Composer. Can you please update these version constraints if the plugins are compatible with PHP 8? And if they are not, is there an expected date when they will be?Thanks in advance!
Used versions
The text was updated successfully, but these errors were encountered: