-
Notifications
You must be signed in to change notification settings - Fork 17
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
Updating plugin via WP-CLI yields ZenCache Pro errors #563
Comments
@MarioKnight Thanks so much for the additional information! @jaswsinc I noticed |
Yeah. I suspect this is a bug. ZenCache needs to consider that it might run as part of a CLI process where |
Next Actions
|
Should also resolve: #560 |
I tested this on a site, and the behavior is back to normal. I'm looking forward to seeing this in the next release, though since it's just a one line change, I will likely roll out that change to all our client sites in the meantime. Thank you! |
@MarioKnight Thanks so much for the confirmation that @jaswsinc's fix works. :-) I'll make sure this fix makes it into the next Pro release. |
Next Pro Release Changelog:
|
ZenCache v151114 has been released and includes changes from this GitHub Issue. See the v151114 announcement for further details. This issue will now be locked to further updates. If you have something to add related to this GitHub Issue, please open a new GitHub Issue and reference this one (#563). |
While I know that ZenCache (Pro) has yet to support WP-CLI directly, an issue has come up that I believe started after updating sites to the latest ZenCache Pro version. When I run plugin updates, sites with ZenCache Pro activated output the following errors:
The plugins still update and the cache still appears to clear and work normally afterward, so thankfully this is currently just an inconvenience. I just wanted to let you know in case something can be done, and in hopes that this could potentially help with #464 . Please let me know if you need anything else on my end. Thank you!
The text was updated successfully, but these errors were encountered: