-
Notifications
You must be signed in to change notification settings - Fork 70
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
Version 1.1.0 of WP Redis causes the page list on sites running WordPress 5.5 to timeout #291
Comments
Thanks for the report, @lukecav. I'm not able to recreate the problem. Could you share more details about the site (plugins, amount of data), or steps I can follow to reproduce? |
wp plugin list --status=active |
Hi @lukecav, This isn't quite enough information to go on. I'll need enough information to reproduce the issue, or you'll need to do a bit of debugging to identify the root cause. |
None of the other active plugins were causing the issue on the page list not loading in wp-admin. Posts and postmeta data levels were not even that high on the site. The same issue happened on another site as well. |
|
Did you try leaving WP Redis active, deactivating all other plugins, and then activating each plugin one by one to see which introduced the slowness? |
Yep, I did and none of the plugins being activated one by one resolved the issue for the page list in wp-admin not loading. |
Ok.
|
|
Waiting to be able to enable the WP Redis plugin again and enable debugging on the customer's site to get the info. |
Please try to use 1.1.1 version, there were some fixes (today, after your last comment) about multiple keys caching, not sure if they fix your problem, but i think it's worth to try. |
@stavultras |
@lukecav good to know, thanks :) |
@stavultras Double props to you — thanks again! |
The fix was to roll back to version 1.0.1 of WP Redis using WP-CLI.
wp plugin update wp-redis --version=1.0.1
The page list in wp-admin would timeout and would not load with WP Redis version 1.1.0 active on the site.
Not sure if the issue is being caused by?
#287
The text was updated successfully, but these errors were encountered: