If Litespeed ESI is enabled we are unable to access Tools section of Translation Managment

This is the technical support forum for WPML - the multilingual WordPress plugin.

Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.

Our next available supporter will start replying to tickets in about 3.51 hours from now. Thank you for your understanding.

Sun	Mon	Tue	Wed	Thu	Fri	Sat
-	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	8:00 – 12:00	-
-	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	13:00 – 17:00	-

Supporter timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Tagged: Compatibility

This topic contains 21 replies, has 3 voices.

Last updated by Long Nguyen 3 days, 20 hours ago.

Assisted by: Long Nguyen.

Author	Posts
June 10, 2024 at 8:10 am
Steven Jackson	If Litespeed ESI is enabled we are unable to access Tools section of Translation Managment. Also the Glossary shows blank so cannot edit exisiting definitions when adding new Languages
June 10, 2024 at 8:53 am
June 10, 2024 at 10:09 am #15721239
Long Nguyen Supporter Languages: English (English ) Timezone: Asia/Ho_Chi_Minh (GMT+07:00)	Hi, Here is the forum ticket. I'm discussing this issue with our 2nd tier support and I will update you here when I have something to share. Meanwhile, please contact Litespeed support if they are aware of this issue. Thanks.
June 13, 2024 at 11:24 am #15735795
Steven Jackson	Hi ling Please upgrade this to a general compatibilty issue when Litespeed ESI is enabled, as in addition to the Tools setcion, The string translations do not work see ticket https://wpml.org/forums/topic/translation-issues-with-litespeed-esi-enabled/?ref=w. Please also make sure the issue of the glossary not showing any existing definitions be looked at as this is the primary reason for trying to access the tools section.
June 14, 2024 at 1:42 am #15738031
Long Nguyen Supporter Languages: English (English ) Timezone: Asia/Ho_Chi_Minh (GMT+07:00)	Hi, Our 2nd tier support is still investigating the issue, I will let you know once I have any information. We will check the issue with the Tools tab first and the Glossary later. Thanks for your patience.
June 17, 2024 at 3:41 am #15743159
Long Nguyen Supporter Languages: English (English ) Timezone: Asia/Ho_Chi_Minh (GMT+07:00)	Hi, Our 2nd tier support sees that the feature ESI of Litespeed seems to corrupt one of our scripts and it is recommended to not use it until we find a way to address the case. This issue has been escalated to the development team, I will let you know when I have more information. Thanks.
July 15, 2024 at 2:38 pm #15955020
Alejandro Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	An update on this. For now, the only workaround is to disable this feature (ESI) which i know is definitely not the best way to go. Our devs found the root problem but they will need time to apply it and it's likely it won't make it to the next few releases. I'll try to push things a bit, but we still don't have a proper solution for it.
September 16, 2024 at 1:00 pm #16184010
Alejandro Supporter Languages: English (English ) Spanish (Español ) Italian (Italiano ) Timezone: Europe/Rome (GMT+02:00)	I'll answer here about the Litespeed issue: Updating Litespeed Cache plugin from version to 6.3.0.1 or above fixed the issue on our end. There was a line in the changelog that seemed related: Cloud Display error message when communicating with QUIC.cloud causes a token error. Our dev had managed to test it on one of your staging servers as well. Regards.
September 17, 2024 at 8:15 am #16186750
Steven Jackson	Hi Sorry this is not fixed, I have just quickly checked "dev" and it is still causing the issues. I have only tested viewing the tools section of translation management this is with Litespeed 6.4.1. Screenshot attached. I also updates LS to 6.5.0.2 and the issue is still present.
September 18, 2024 at 1:36 am #16190942
Long Nguyen Supporter Languages: English (English ) Timezone: Asia/Ho_Chi_Minh (GMT+07:00)	Hi Steven, Can you please share your dev site (or a staging site) credentials? I will share it with our development team to check the issue on your site. Your next reply is set to private to share the info. ❌ IMPORTANT: Please backup your database and website before proceeding ❌ Looking forward to your reply. Thanks
September 18, 2024 at 7:25 am
September 18, 2024 at 8:02 am #16191496
Long Nguyen Supporter Languages: English (English ) Timezone: Asia/Ho_Chi_Minh (GMT+07:00)	I'm asking our development team to check the issue on your dev site. I will update you here when I have more information. Thanks.
September 19, 2024 at 1:39 am #16195700
Long Nguyen Supporter Languages: English (English ) Timezone: Asia/Ho_Chi_Minh (GMT+07:00)	Hi, Our development team has identified the issue and fixed it on your site. In the file wp-content/plugins/litespeed-cache/src/core.cls.php around line 720, we change the code from $this->_footer_comment .= "\n<!-- " . $data . ' -->'; to $this->_footer_comment .= "<!-- " . $data . ' -->'; can you please confirm it works on your end? Then please help us report this issue to the Litespeed Cache plugin author so they can take a look at the workaround and include it in future updates. Looking forward to your reply. Thanks
September 19, 2024 at 7:11 am #16196261
Steven Jackson	Hi Long Thank you for this. I can confirm it appears to work and very quick test seems to resolve the string translation issue too. With regards to Litespeed support, do you not have communication with them already? If not I found this option to report a bug hidden link
September 20, 2024 at 1:14 am #16201009
Long Nguyen Supporter Languages: English (English ) Timezone: Asia/Ho_Chi_Minh (GMT+07:00)	Thanks for your confirmation. Our compatibility team will get in touch with the plugin author and report this issue. You can keep using the workaround on your site until they include the fix in an update. Thanks and have a good day.