Problem: The client has a multilingual site with English and Dutch languages. They noticed that while the content was translated by WPML, the URLs in the static HTML custom "menu" were not updated to point to the corresponding translated pages. The client wanted to know if there is a setting in WPML that automatically redirects users to the translated version of a page when they are on the Dutch homepage and click a link that has a Dutch translation available.
Solution: We informed the client that static HTML cannot be translated by WPML. Only PHP code that includes proper GetText calls can be translated within WordPress. Therefore, to achieve the desired functionality, the client would need to update the static HTML links manually to point to the correct translated pages. We also provided a guide on how to translate themes created by the client, which can be found here:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also 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 contact us in the WPML support forum.
Problem: The client is experiencing issues when copying their Production environment to the Development environment on a multisite network hosted on WPEngine. After the copy, WPML detects a new address for the site and prompts a migration process. Despite completing the process, the client encounters the same message again, and the Production environment's connected site list grows with each attempt.
Solution: 1. If you're experiencing a similar issue after copying your Production environment to your Development environment, it's important to ensure that you're not forcing HTTPS or a specific domain in your wp-config or elsewhere in your installation. This could cause the site to be accessed with two domains, leading to the repeated migration banner. 2. Follow the instructions in our guide on Using Advanced Translation Editor when you move or use a copy of your site to resolve the issue. 3. Make sure to be using our latest WPML version (4.6.9 at the time of writing this summary).
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related known issues on the WPML Known Issues page, 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 with us.
Problem:
The client has a custom post type called "Transaction" with an Advanced Custom Field of type Radio Button with options Yes and No. When using automatic translation, if the radio button is not selected in the original item, WPML incorrectly selects "Yes" in the translated version, allowing it to bypass required fields. This causes issues as the site relies on the Yes/No selection to determine if further fields should be present.
Solution:
We recommend setting all your groups to "Same fields across languages" in "ACF > Field Groups" to use the default configuration for each field type. This usually meets most clients' needs, with text fields being translatable and checkbox fields being copied.
If you need to fine-tune the translation preferences, switch to "Expert" mode for a particular group. You can then see and change the translation preference for each field.
You can find the recommended preferences for each field type here: Recommended Custom Fields Translation Preferences for ACF and WPML
