Problem: The client inquired if WPML can fully support Papiamentu as a custom language for page translations, integrate with automatic translation services, and if there are any limitations or best practices to consider. Solution: We informed the client that Papiamentu can be added as a custom language in WPML for manual translations across the site. However, for automatic translations, there are limitations since not all custom languages are supported by WPML's integrated translation engines. Although Google Translate supports Papiamentu, it is not supported directly by WPML's engines. We recommended checking the supported languages on https://ate.wpml.org/mt_langs. As a workaround, the client can map Papiamentu to a supported language for automatic translations.
If this solution does not apply to your case, or if it seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is implementing WPML with Advanced Custom Fields (ACF) Multilingual and seeks confirmation on best practices for field translation settings, ensuring layout elements sync across languages, and maintaining a scalable multilingual structure. Solution: We recommend setting ACF Field Groups to 'Not translatable' and choosing the appropriate translation preferences for fields: use 'Copy' for layout/structure fields (like repeaters, icons, CTAs) to maintain synchronization across languages, and 'Translate' for user-facing text fields to allow proper content translation. It's important not to manage ACF fields from the WPML → Settings → Custom Fields Translation screen but directly from the ACF Field Group edit screen. The fields listed there, including dynamically created ones, are normal for ACF-based sites and should remain as configured without manual adjustments. For detailed guidelines, refer to ACF Field Groups translation settings and recommended custom fields translation preferences for ACF and WPML.
If this solution does not fully address your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
