Skip to content Skip to sidebar

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.

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: 

This topic contains 21 replies, has 3 voices.

Last updated by Long Nguyen 1 year, 7 months ago.

Assisted by: Long Nguyen.

Author Posts
September 23, 2024 at 8:37 am #16207935

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English ) Vietnamese (Vietnamese )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Please try this again hidden link

Thanks.

September 23, 2024 at 11:22 am #16209201

Steven Jackson

Hi

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.

September 24, 2024 at 2:05 am #16212171

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English ) Vietnamese (Vietnamese )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Hi,

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.

Thanks.

October 1, 2024 at 7:56 am #16238758

Steven Jackson

Hi

I have just received a notification about the ticket being closed, please ensure it stays open until resolved.

October 2, 2024 at 2:01 am #16243234

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English ) Vietnamese (Vietnamese )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

Hi,

The ticket will be closed in 2 weeks. Please update me here in the time or you can post a follow-up reply to open it and so on.

Thanks.

October 2, 2024 at 7:49 am #16243719

Steven Jackson

So basically you are closing the ticket regardless of whether it is resolved or not.

October 3, 2024 at 1:12 am #16247724

Long Nguyen
WPML Supporter since 02/2022

Languages: English (English ) Vietnamese (Vietnamese )

Timezone: Asia/Ho_Chi_Minh (GMT+07:00)

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.

Thanks.