Problem: The client is experiencing issues with the header and footer not updating across all languages after making edits. The edits are made directly via Editor → Patterns → Header, which causes synchronization issues with WPML. Solution: We recommend the following steps to ensure proper synchronization of translations across all languages: 1. Create and edit the header pattern in the default language only, using the top bar language selection. 2. Ensure everything looks correct in the default language. 3. Navigate to WPML → Translation Management 4. Send the header/pattern for translation. 5. Translate it using the WPML editor. This process helps WPML to properly track and synchronize the translations across all languages. Additionally, when updates are made to texts, patterns, etc., you only need to re-translate the specific items that were changed in the default language.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 issues persist, please open a new support ticket.
Problem: The client was experiencing issues with translating Forminator fields and custom plugins using WPML. They also encountered problems with translating patterns due to a disabled option. Solution: We recommended setting the Forminator post type as translatable in WPML > Settings and disabling the WPML Translation Editor for this post type. The client should create separate forms manually for each language. When editing pages where the forms are displayed, they should insert the correct form shortcode for each language. We advised against using automatic translation on these pages as it might overwrite manually added changes. For patterns, the client discovered that the option to edit them was disabled and enabled it themselves.
Please note that this solution might be outdated or not applicable to your case. If you encounter further issues, 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 problem persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing issues with the WPML plugin on a website, specifically with translating ACF (Advanced Custom Fields) option fields and field values, despite having credits for automatic translation. Additionally, other languages appear to be running on an older version of the page, and there is confusion on how to translate Forminator labels and placeholders. Solution: 1. Ensure that ACF Multilingual is installed and configured correctly. If issues persist, check the setup and configuration. 2. For translating ACF fields, use the WPML Advanced Translation Editor accessible by clicking the plus icon next to each language. Note that translations need to be done one language at a time as there is no feature to translate into all languages simultaneously. 3. For issues with outdated content in other languages, ensure that all posts, including custom posts like FAQ or Opdrachten, are translated and exist in the respective languages. 4. Regarding Forminator and custom plugins, these may require specific integration efforts for translation if they are not natively supported by WPML.
If these steps do not resolve the issues or if the solution seems outdated or irrelevant to your specific case, we recommend opening a new support ticket. We also advise 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. For further assistance, please visit our support forum at WPML Support Forum.
