You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using Redis Sentinel for caching via predis. I am running PHP 8.0.30. I am using version 2.5.2 of Redis Object Cache. I am using Yoast SEO version 22.8. I can flush the cache using the admin toolbar or wp-cli.
Expected Behavior
The post to save without error
Actual Behavior
Every second attempt at updating I get an error at the top of the editor that says Updating failed. The response is not a value JSON response.
Possible Fix
Maybe related to the discussion happening in GH-528
Steps to Reproduce
Have both plugins mentioned in description active
Edit a page, update. Update again. Error message typically happens every second update. PHP log error displayed with each update attempt.
Additional context
Unable to turn cache on in our production environment
Environment
Plugin version: latest redis cache and yoast seo
PHP version: 8.0.30
WordPress version: 6.5.4
The text was updated successfully, but these errors were encountered:
@yatsukhnenko Can you try running a group_flush() using Redis Sentinel when using Predis as the client. We may have missed that when we refactored it in 2.5.0.
Description
I am getting the following error in my server logs when I save any page. I am using WP 6.5.3 in a Gutenberg environment.
I am using Redis Sentinel for caching via predis. I am running PHP 8.0.30. I am using version 2.5.2 of Redis Object Cache. I am using Yoast SEO version 22.8. I can flush the cache using the admin toolbar or wp-cli.
Expected Behavior
The post to save without error
Actual Behavior
Every second attempt at updating I get an error at the top of the editor that says
Updating failed. The response is not a value JSON response.
Possible Fix
Maybe related to the discussion happening in GH-528
Steps to Reproduce
Additional context
Unable to turn cache on in our production environment
Environment
The text was updated successfully, but these errors were encountered: