Vai al contenuto Vai alla barra laterale

Questo è il forum di assistenza tecnica di WPML, il plug-in multilingue di WordPress.

La sua lettura è permessa a tutti, ma la pubblicazione è riservata esclusivamente ai clienti di WPML. Il team di WPML risponde sul forum 6 giorni su 7, 22 ore su 24.

Sun Mon Tue Wed Thu Fri Sat
- 8:00 – 14:00 8:00 – 14:00 8:00 – 14:00 8:00 – 14:00 8:00 – 14:00 -
- 15:00 – 17:00 15:00 – 17:00 15:00 – 17:00 15:00 – 17:00 15:00 – 17:00 -

Fuso orario del supporto: Europe/Madrid (GMT+02:00)

Etichettato: 

Questo ticket contiene 8 risposte, ha 0 voci.

Ultimo aggiornamento da Paola Mendiburu 6 mese fa.

Assistito da: Paola Mendiburu.

Autore Post
Novembre 3, 2025 alle 20:44 #17543420

alessandroD-74

Contesto del problema:
I am experiencing a severe slowdown when saving or updating posts in the WordPress admin after the recent WPML update (4.8.4). The issue occurs on all posts, and each save or update request (post.php?...&_locale=user) takes more than 60 seconds and results in a 302 redirect. Using the browser DevTools, I see a call to wpml-proxy-interceptor.js which delays the response significantly. After cleaning up old string domains from a previous theme, Soledad, and optimizing the database (reduced from ~9,000 strings to 200), the problem persists. The site I need help with is link nascosto.

Sintomi:
Saving or updating posts takes over 1 minute after the latest WPML update, with a significant delay caused by wpml-proxy-interceptor.js.

Domande:
Why does saving or updating posts take over 1 minute after the latest WPML update?
How can I resolve the delay caused by wpml-proxy-interceptor.js?

Novembre 4, 2025 alle 6:39 #17543916

Paola Mendiburu
Sostenitore di WPML dal 11/2020

Lingue: Inglese (English ) Spagnolo (Español ) Italiano (Italiano )

Fuso orario: Europe/Madrid (GMT+02:00)

Hi there,

I’m Paola from WPML Support — thanks for your detailed explanation.

This kind of delay during post updates (with wpml-proxy-interceptor.js) usually happens when the REST requests used by WPML to synchronize translation data take too long to respond — often due to a conflict or excessive data loading in the background.

To narrow it down, could you please try the following steps?
- Create a staging copy of your site (if possible).
- Deactivate all plugins except WPML and its add-ons, and switch to a default theme (like Twenty Twenty-Five).
- Try editing a post again and check if the delay persists.

If it works fine, reactivate the plugins one by one to find which one causes the slowdown.

Also, please enable the WordPress debug log so we can see if any PHP warnings appear during the save process:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

Then, try saving a post again and share the log file from /wp-content/debug.log.

Once we have that information, we’ll be able to determine whether the delay comes from WPML itself or an interaction with another plugin or script.

Novembre 4, 2025 alle 16:18 #17546968

alessandroD-74

Thanks!

Where can i send the logs?

I have disabled all the plugins, the issue persist.

Novembre 5, 2025 alle 12:24 #17549818

Paola Mendiburu
Sostenitore di WPML dal 11/2020

Lingue: Inglese (English ) Spagnolo (Español ) Italiano (Italiano )

Fuso orario: Europe/Madrid (GMT+02:00)

Hi there,

You can copy the error logs from your debug.log file, paste them on https://pastebin.com/ , and then send me the link here.

Thank you.

Novembre 9, 2025 alle 16:24 #17560113

alessandroD-74

https://pastebin.com/HgsXctSa

I’ve run a complete performance diagnostic from the server side using WP-CLI, disabling plugins selectively to isolate the cause.

Here are the tests I ran on the same post using WP-CLI:

Baseline (no plugins or themes):
wp --skip-plugins --skip-themes post update 111734 → 3.6 seconds

All plugins active (production):
wp post update 111734 → 2 minutes 38 seconds

WPML core disabled only:
wp --skip-plugins=sitepress-multilingual-cms post update 111734 → 6.0 seconds

Rank Math disabled only:
wp --skip-plugins=seo-by-rank-math,seo-by-rank-math-pro post update 111734 → around 2 minutes

WPML and all its add-ons disabled (acfml, string translation, etc.):
wp --skip-plugins=sitepress-multilingual-cms,acfml,wpml-graphql,wpml-media-translation,wpml-string-translation,wp-seo-multilingual → 5–6 seconds

WPML fully enabled again:
wp post update 111734 → more than 2 minutes

So the slowdown occurs only when sitepress-multilingual-cms (WPML core) is active.
All other combinations are fast.

This problem is causing major damage to our editorial workflow, as we manage a high-volume news site and editors cannot efficiently publish or update articles.
We would really need to resolve this urgently or find a temporary workaround to restore normal post-saving speed.

Thanks!

Novembre 10, 2025 alle 10:17 #17561307

Paola Mendiburu
Sostenitore di WPML dal 11/2020

Lingue: Inglese (English ) Spagnolo (Español ) Italiano (Italiano )

Fuso orario: Europe/Madrid (GMT+02:00)

Hi!

Thank you for the detailed report and for running all those WP-CLI tests — that really helps narrow things down.

Please try these quick steps so we can confirm where the bottleneck is:

1. Go to WPML → Support → Troubleshooting and click on:
Clear WPML cache, Remove ghost entries from translation tables, and Fix element_type collation.

3. In WPML → Settings, make sure only the fields you actually need are set to “Translate”.

3. Check with your hosting that outgoing requests to WPML domains (like api.wpml.org, ate.wpml.org, wpml.org) are not blocked by a firewall or proxy.

If the problem persists, I would like to request temporary access (wp-admin and FTP) to your site to take a better look at the issue. You will find the needed fields for this below the comment area when you log in to leave your next reply. The information you will enter is private which means only you and I can see and have access to it.

Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see:
https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/

**IMPORTANT**
- Please make a backup of the site files and database before providing us access.
- If you do not see the wp-admin/FTP fields this means your post & website login details will be made PUBLIC. DO NOT post your website details unless you see the required wp-admin/FTP fields. If you do not, please ask me to enable the private box.
The private box looks like this: link nascosto

Novembre 11, 2025 alle 6:51 #17564731

Paola Mendiburu
Sostenitore di WPML dal 11/2020

Lingue: Inglese (English ) Spagnolo (Español ) Italiano (Italiano )

Fuso orario: Europe/Madrid (GMT+02:00)

Hi!

Could you please allow me to install the Query Monitor plugin? It will help me check what’s happening in the background.

Also, please let me know if you see any errors or warnings appearing in the Debug Log. Per conoscere i dettagli dell’errore che stai riscontrando, potresti fare quanto segue?- Accedi al file wp-config.php (situato nella root di WordPress).
- Inserisci queste righe subito prima di /* That's all, stop editing! Happy blogging. */

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

Riproduci il problema, quindi accedi al registro di debug qui: /wp-content/debug.log e copia e incolla le informazioni nella tua prossima risposta.
Maggiori info: https://wordpress.org/support/article/debugging-in-wordpress/

Questo rapporto ci aiuterà a individuare la radice del problema.

Novembre 11, 2025 alle 7:13 #17564774

alessandroD-74

Yes you can install it.

https://pastebin.com/Xhdp9KCP

Thanks!

Novembre 11, 2025 alle 17:56 #17567998

Paola Mendiburu
Sostenitore di WPML dal 11/2020

Lingue: Inglese (English ) Spagnolo (Español ) Italiano (Italiano )

Fuso orario: Europe/Madrid (GMT+02:00)

Ho controllato il debug log e non vedo nessun errore collegato a WPML.

Hai per caso un sito staging dove possiamo fare delle prove senza influenzare il sito in produzione?

L'argomento '[Chiuso] Saving or updating posts takes over 1 minute after latest WPML update (proxy_interceptor.js delay)' è chiuso a nuove risposte.