[Chiuso] Translation Editor not saving ACF fields on consecutive saves (WPML 4.8.2)
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 – 13:00
9:00 – 13:00
9:00 – 13:00
8:00 – 12:00
8:00 – 12:00
-
-
14:00 – 17:00
14:00 – 18:00
14:00 – 18:00
13:00 – 17:00
13:00 – 17:00
-
Fuso orario del supporto: Europe/Zagreb (GMT+01:00)
Contesto del problema:
I am trying to use the WPML Translation Editor for WooCommerce products with ACF fields. I encountered an issue after updating to WPML 4.8.2 where the Translation Editor does not save changes to ACF fields on consecutive saves. This issue blocks my translation workflow.
Sintomi:
When I modify an ACF custom field and click Save, it works the first time. However, if I modify the same field again without closing the editor and click Save, the changes are not saved. Refreshing the page does not help, and the issue persists unless I open the Translation Editor in a new browser tab, but this only works once. Standard WordPress fields save correctly on multiple attempts. All ACF field types are affected, and the issue started after updating to WPML 4.8.2.
Domande:
Why are ACF fields not saving on consecutive saves in the WPML Translation Editor?
Is there a fix or patch available for this issue?
Give each field a unique name. Reusing the same Field Name in multiple field groups can cause some values to be missing in the editor.
What if you try to use a different name for these custom fields? Because I see "name" and "description" in your custom fields, it is possible that this interferes with some of the built in WooCommerce field names.
Please try this on the test site with a product where the translation has not started yet.
If that doesn't change anything, I will prepare a sandbox where we can test his behavior and escalate to our developers for further checks.
Lingue: Inglese (English )Tedesco (Deutsch )Francese (Français )
Fuso orario: Europe/Zagreb (GMT+01:00)
This case is currently being reviewed by our developers (it’s a confirmed bug). At the moment, there are no available workarounds other than using the Advanced Translation Editor.
We’ll try to find at least a temporary workaround before the official patch is released (though I can’t provide a specific date yet). Would using the Advanced Translation Editor be an option for you?
Lingue: Inglese (English )Tedesco (Deutsch )Francese (Français )
Fuso orario: Europe/Zagreb (GMT+01:00)
Thank you for the update. I’ll continue checking this further and will keep you informed here regarding any progress on the bug resolutions or if any alternative workarounds become available in the meantime.
