Different things when setting up translations for CPT's, ACF and archive pages

Etichettato: Documentation request

Questo ticket contiene 0 risposta, ha 0 voices.

Ultimo aggiornamento da mortenV-3 10 mese, 1 settimana fa.

Assistito da: Bruno Kos.

Autore	Post
Dicembre 4, 2024 alle 6:43 am
mortenV-3	Background of the issue: I am trying to set up translations for custom post types (CPTs), ACF fields, and archive pages on my site link nascosto. I recorded a video with detailed information: link nascosto. I am using Divi. Symptoms: There are extra fields for only one CPT post when I use the WPML translation editor. Questions: What are the best practices for translating CPTs with ACF fields, especially when adding different content in some fields but not all? Should I use the WPML translation editor given the extra fields issue? How can I ensure that ACF fields added in the future will be translatable? How do I translate the title, buttons, and breadcrumbs on the archive page?

Autore

Post

Dicembre 4, 2024 alle 6:43 am

mortenV-3

Background of the issue:
I am trying to set up translations for custom post types (CPTs), ACF fields, and archive pages on my site link nascosto. I recorded a video with detailed information: link nascosto. I am using Divi.

Symptoms:
There are extra fields for only one CPT post when I use the WPML translation editor.

Questions:
What are the best practices for translating CPTs with ACF fields, especially when adding different content in some fields but not all?
Should I use the WPML translation editor given the extra fields issue?
How can I ensure that ACF fields added in the future will be translatable?
How do I translate the title, buttons, and breadcrumbs on the archive page?