Problem: You are trying to auto-translate posts with custom post types and ACF Fields to other languages, but some ACF field data is not copied, resulting in a broken page in the translated language. Solution: If you're experiencing issues with ACF fields not being translated during automatic translation, we recommend you follow these steps: 1. Go to WPML > Settings > Post type translation and set the post type acf-field-group as "do not translate". 2. Navigate to Plugins > Add New > Commercial tab, and install the ACF Multilingual plugin. 3. Read our ACF documentation and configure the fields according to your needs. 4. If necessary, send the post to translation again.
Please note that this solution might be irrelevant if it’s outdated or not applicable to your 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.
Problem: If you're experiencing issues where editing an original link field from '/contact/' to '/shop/' causes the translated link field to change to '/shop/' instead of 'en/shop/' because it is set to 'Copy', we have a solution for you. Solution: We recommend setting the field configuration to 'translate' instead of 'copy' or 'copy once'. This adjustment will make the field value available in the WPML Translation Editor, allowing you to manually translate the link. Additionally, for automatic adjustment of internal links, you might want to test using the
wpml_permalink
hook when calling the links inside your theme's template files. You can find more details on this workaround here. However, if you are using a page builder to display the fields on the frontend, this workaround might not be applicable. It would also be very helpful if you could send us the WPML debugging information to better assist you. More information on how to provide this can be found here.
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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.
Problem: The client wanted to change the language code of the Burmese language from /my-mm to /mm and faced issues when adding a custom language with the desired code in WPML. Solution: We informed the client that it is not possible to change the language code of existing languages in WPML. However, we recommended adding a new language with the desired language code by following the documentation:
We also suggested resetting the languages if the issue persists by navigating to WPML >> Support > Troubleshooting page and pressing the Reset languages button, then trying to add the language again.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your 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 problem continues, please open a new support ticket at WPML support forum for further assistance.
Problem: The client updated their website in various places over time but did not run WPML, suspecting that there is content that remains untranslated in various unknown places on their site. Solution: If WPML was active on the site while the client changed the original contents, WPML will keep track of any changes and know which segments need to be updated. The Advanced Translation Editor includes a translation memory, ensuring that identical segments previously translated will not incur double charges due to auto-completion. For more details, visit how WPML keeps track of your translations. To translate new content, go to WPML > Translation Management > Dashboard, select the post type from the dropdown on the top left, mark what you would like to translate, and at the bottom section choose "Translate automatically".
Please note that this solution might be outdated or not applicable to your specific case. We highly recommend checking related known issues at WPML known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If this does not resolve your issue, please open a new support ticket.
Problem: When clicking on "Languages", nothing happens on the client's site. Solution: If you're experiencing issues with your language switcher not responding, we recommend ensuring that you are using a WPML Language Switcher, as the switcher on this site appeared to be from Polylang. For guidance on setting up and translating menus, please refer to our documentation:
Please note that this solution might be irrelevant if it's outdated or not applicable to your 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.
Problem: The client has installed the WPML plugin and wants to use it only on specific pages like blogs and downloads for automatic translation to Polish and Swedish, but is unable to find documentation on how to apply the plugin selectively. Solution: We recommend setting the translation mode to 'Translate What You Choose' instead of 'Translate Everything Automatically'. This can be done by navigating to WPML > Settings > Translation Mode. After setting this, you can manage how each page is translated by going to WPML > Translation Management > Dashboard. Here, you can either send pages for automatic translation or assign them to translators or yourself using the Advanced Translation Editor. For more detailed guidance, please refer to our documentation on WPML Translation Management.
Please note that this solution might be outdated or not applicable to your specific case. If this does not resolve your issue, 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 you still need assistance, please open a new support ticket at WPML support forum.
