Our compatibility contacted the plugin author and they setup a clean site with WPML and Litespeed Cache plugin, enable the option ESI and the Tools tab works properly without applying the workaround above.
If you want to access the test site, please visit this link hidden link
It looks like a specific issue on your site, so I suggest you contact the plugin author and ask them to investigate it further.
Well in my opinion there is still a conflict. 2 of our sites have the exact same issue. And as demonstrated by our ongoing support with Aljandro that this is not a fair test in a like fore like scenario as there is no Woo, ACF etc.
In the recent example that has now been accepted it was only when meta data was added the REST update request time dramatically increased.
I dont have time to waste proving if this is the case. Between this and all the other ongoing issues with WPML which Aljandro is dealing with.
If however you have a known resolution for the issue then please work on this basis.
Below is my findings:
- There is a JS error "Uncaught SyntaxError: "" string literal contains an unescaped line break" 5:2039 wpml-app=ate-widget&ver=4.6.13
- Which looks to me to be caused by a link break in the JS with the caching comment by Litespeed at the restNonce value.
"ui_language":"en","restNonce":"
<!-- Block cached by LiteSpeed Cache 6.5.0.2 on 2024-09-23 11:50:44 -->"
Please either supply the exact Nonces so that I can add it as an exception in Litespeed ESI section. Or get Litespeed to add it to their list or have the code updated.
Otherwise it is not worth the wasted time, given the length of time it takes for tickets to be resolved and my time. To actually bother getting this issue resolved. We are only trying to use ESI as a method of speeding up or incredible slow site that is caused by the use of WPML.
The nonce name when opening the Tools tab is "wp_rest" and it is located in the file wp-content/plugins/sitepress-multilingual-cms/classes/menu/ams-ate-console/class-wpml-tm-ams-ate-console-section.php line 250.
Our compatibility team already tried to add it to the option ESI Nonces on your staging site and also added the URL "?wpml-app=ate-widget" to the cache excludes but it didn't have any effects.
We have contacted the plugin author and they are going to check the issue on your site further. Meanwhile, you can use the workaround to use WPML and Litespeed ESI on the site.
Please update us here when you have more information from the Litespeed Cache support regarding this issue. In the meantime, we already have a workaround to fix it.
