Hi,
I can’t see any reason why this issue happens. The plugin is mostly using core functions and do not interact on the caching side.
Can you tell me if you’re using the classic editor or no ? If you have any javascript error in the console ? If there is XHR issues ?
Cheers,
Brice
Thread Starter
Greys
(@jgreys)
Hi @brikou,
Totally agree, when I was troubleshooting this issue, I did not think your plugin could be the cause.
You can reproduce the exact same issue with a fresh install with WooCommerce and Redis Object Cache installed and activated. Nothing more. The theme used doesn’t matter.
On the other hand, I do not have any javascript or PHP errors.
Cheers,
John Greys
-
This reply was modified 5 years, 8 months ago by
Greys.
-
This reply was modified 5 years, 8 months ago by Greys.
Hmmm…
I thinks I was wrong !
I totally forgot that I did a fix for W3 Total Cache a few years ago because of object caching issues…
Fortunatly you can disable the related filters with the following hooks.
remove_action( 'set_transient_wpsrd_settings_errors', 'wpsrd_enable_linked_in_cached' );
remove_action( 'transient_wpsrd_settings_errors', 'wpsrd_enable_linked_in_cached' );
remove_action( 'deleted_transient_wpsrd_settings_errors', 'wpsrd_enable_linked_in_cached' );
remove_action( 'pre_set_transient_wpsrd_settings_errors', 'wpsrd_disable_linked_in_cached' );
remove_action( 'pre_transient_wpsrd_settings_errors', 'wpsrd_disable_linked_in_cached' );
remove_action( 'delete_transient_wpsrd_settings_errors', 'wpsrd_disable_linked_in_cached' );
Let me know if it works 😉
Best,
Thread Starter
Greys
(@jgreys)
Thanks, the hooks fixed the issue. 🙂
Do you plan to integrate this fix when the plugin Redis Object Cache is activated?
Glad to hear that.
No I think I will only apply the above filters if W3 Total Cache is activated (don’t why I didn’t do that at first…)
Glad to hear that.
No I think I will only apply the above filters if W3 Total Cache is activated (don’t know why I didn’t do that at first…)
If this is broken by default with any object caching solution, doesn’t it make sense to fix this?
I said “apply”, not “remove” filters 😉
Ah maybe I misunderstood. I was referring to:
Do you plan to integrate this fix when the plugin Redis Object Cache is activated?
The plugin is used by 60,000 sites.
The fix is to apply the above filters only when W3 Total Cache is activated (if still needed). That mean there will no need to remove them with other caching solutions.
Update done.
I’ve completely remove the W3 Total Cache filters previously added since it does not since to be required anymore.
You can remove the the above filters.
Best,
Thread Starter
Greys
(@jgreys)
I confirm the issue is now fixed with the 1.5.1 update.
Thanks for the support! 🙂
