Salta la navigazione

Questo thread è stato risolto. Ecco una descrizione del problema e della soluzione.

Problem:
You are trying to save data on an ACF option page in various languages using ACFML, with fields set as 'copy' to maintain the same values across all languages. While the backend shows values correctly copied and locked, the frontend still displays values from the main language (Italian). Even after updating the value in the main language, you need to manually update it in each secondary language to reflect changes on the frontend.
Solution:
The behavior you're experiencing is expected when using ACF fields with the copy translation preference. To apply these values to the secondary languages on the frontend, you must re-save the options page in those languages. This process is necessary to ensure consistency across languages as currently implemented by WPML and ACFML. For more details, you can refer to our documentation here: Translating the ACF Options Page Custom Fields with WPML.
If this manual update process is cumbersome, we can submit a feature request to explore the possibility of automatically copying the options page values into the secondary languages upon saving the default language options page. Please let us know if you would like us to proceed with this request.

Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If the issue persists, please open a new support ticket at WPML support forum.

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.

Etichettato: 

Questo ticket contiene 1 risposta, ha 0 voci.

Ultimo aggiornamento da Noman 2 settimane, 1 giorno fa.

Assistito da: Noman.

Autore Messaggi
Dicembre 5, 2024 a 2:40 pm #16481860

Paolo Sax

Background of the issue:
I'm trying to save data on an ACF option page in various languages using ACFML. The option page includes various ACF fields set as 'copy' to maintain the same values across all languages.

Symptoms:
In the backend, everything appears to work fine with values copied in the relevant locked fields. However, in the frontend, I still see the value from the main language (Italian). If I update the value in the option page with the main language selected, I also have to update it in the secondary language.

Questions:
Is this correct as procedure? Shouldn't I expect to get always updated values WITHOUT having to access the option page in each secondary languages in order to update the data in the frontend?

Dicembre 5, 2024 a 2:58 pm #16482458

Noman
Supporter

Lingue: Inglese (English )

Fuso orario: Asia/Karachi (GMT+05:00)

Hi,

Thank you for contacting WPML Support. The behavior you're experiencing is expected when using ACF fields with the "copy" translation preference. While the values appear correctly copied and locked in the backend, applying them to the secondary languages on the frontend requires re-saving the options page in those languages. This is outlined in our documentation: https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-the-acf-options-page-custom-fields-with-wpml/#applying-copy-translation-preference

Currently, WPML and ACFML work this way to ensure consistency across languages. However, I understand that having to update the options page in each language manually may not be ideal. If you'd like, I can submit a feature request to explore the possibility of copying the options page values automatically into the secondary languages upon saving the default language options page.

Let me know if you'd like me to proceed with that or if you have any additional questions!

Thank you