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
12:00 – 20:00 12:00 – 20:00 12:00 – 20:00 12:00 – 20:00 12:00 – 20:00 - -
- - - - - - -

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

Questo ticket contiene 1 risposta, ha 2 voci.

Ultimo aggiornamento da Noman 1 anno, 4 mese fa.

Assistito da: Noman.

Autore Post
Settembre 7, 2024 alle 2:43 pm #16151412

emilio-luigiB

Contesto del problema:
I created my first options page on my site using ACF, WPML for translations, and AVADA as the theme. I added a price list that should be the same across all languages and installed the ACFML extension, setting the field groups as 'same field across languages'.

Sintomi:
In the primary language, the fields on the options page load correctly in both my custom shortcode and AVADA's dynamic fields feature.
However in secondary languages, my shortcode did not fetch any data and Avada did not display the ACF fields from the Options page.
When I changed the ACF field group configuration to "different fields per languages", both my shortcode and the Avada functionality worked immediately.
After returning to the "same field in all languages" and changing a price, the new price was displayed correctly in the primary language, but the old price was still displayed in the secondary languages.

Domande:
Why doesn't the "same field in all languages" setting work correctly for ACF fields in secondary languages?
How can I ensure that the same field values ​​are displayed in all languages?
How can I configure my custom code to always point to the primary language?

Settembre 8, 2024 alle 9:23 am #16152314

Noman
Sostenitore di WPML dal 06/2016

Lingue: Inglese (English )

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

Hi,

Thank you for contacting WPML Support. It sounds like the issue is with how the ACF options page fields are being saved across different languages. When using the "same field in all languages" setting, changes made in the default language don’t automatically update the secondary languages. To ensure the changes reflect correctly, you'll need to re-save the options page in the secondary languages as well. Here’s what you can try:

1. Open the options page in the default language, make your changes, and click the Save button
2. Switch to the secondary language using the admin language switcher.
3. If needed, make any adjustments (this step is optional).
4. Click the Save/Update button.

These steps should help keep the field values consistent across all languages. For more details, you can check out this guide:
https://wpml.org/documentation/related-projects/translate-sites-built-with-acf/translating-the-acf-options-page-custom-fields-with-wpml/

Please let me know the results,
Thank you

L'argomento '[Chiuso] ACF OptionPage: Same field across languages does not work correctly' è chiuso a nuove risposte.