-
Notifications
You must be signed in to change notification settings - Fork 466
fix: update appsero/client to v2.0.4 to prevent conflicts with WP6.7
#3245
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
Conversation
|
Code Climate has analyzed commit 29cfbf4 and detected 0 issues on this pull request. View more on Code Climate. |
The merge-base changed after approval.
|
@justlevine I got some error on updating over composer wp-graphql-smart-cach Mabye, also need some composer update? I can't install the new wp-graphql/wp-graphql version. |
|
@Messa1 can you be more specific about what "over composer" means? Are you using WPackagist or something else? |
|
composer.json |
|
Yup as expected, you're installing the source (from (Iirc smart-cache is on .org too so you might want to use |
|
|
@Messa1 it's At some point WordPress.org stopped allowing plugins that started with |
What does this implement/fix? Explain your changes.
This PR updates
appsero/clientto v2.0.4, which contains the compatibility fix for WP 6.7To prevent 3rd party conflicts (and a repeat of #2599), use of
Appsero\Clienthas been wrapped in a try/catch block.Important
This PR is based on #3242 which should be merged first.
Does this close any currently open issues?
Fixes #3239
Any relevant logs, error output, GraphiQL screenshots, etc?
Any other comments?
Alternatively tried namespacing the dependency (which is the code-ideal solution), however Strauss is not compatible with PHP 7.3 (what Composer uses to compile on).
Where has this been tested?
Operating System: Ubuntu 24.04 (WSL + ddev + PHP 8.2.24 )
WordPress Version: 6.7.1