Problem: The client is experiencing an issue where the translated 'last_name' string of user meta in WPML is not visible on the frontend; only the default translation is shown. Solution: If you're facing a similar issue, first confirm how the user field was created. If it was created via ACF, check the translation settings of this field. Follow the guide on translating custom user fields with WPML, which can be found here: Translating Custom User Fields.
Add the following code to your functions.php to make the field translatable:
Then, use the shortcode [author_text] in your Elementor template to display the translated string.
If this solution does not apply to your case, or if it seems outdated, 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 issues persist, please open a new support ticket.
Problem: The client was unable to view a post in a new language after using an automatic translator. The translated post was not visible when switching languages, and the client was unsure whether to delete existing translations and add new ones. Additionally, there was confusion about whether the issue was related to object cache settings. Solution: We recommended the following steps: 1) Disable the object cache temporarily as it can sometimes cause issues with translations. This setting can be re-enabled after completing the translations. 2) Check if the translated posts are in the trash. If they are, either permanently delete them or restore them. Having translations in the trash can prevent them from being visible even if they are translated anew. 3) Manually edit the post in the desired language, set it to publish, and adjust the page slug if necessary. 4) Make a small change to the title in the default language and save it. Then, re-translate the page. This may trigger a new translation job and avoid using an old one. You can revert the title change and re-translate if needed.
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 problems persist, please open a new support ticket.
Problem: The client is experiencing an issue where WPML's translations are overriding the translations made with Loco Translate for the default language, Norwegian, on their WooCommerce site. Solution: We recommend not using WPML and Loco Translate simultaneously as they perform similar functions and can conflict. To resolve the issue, you can import the .po files created with Loco Translate into WPML. Here's how you can do it: 1. Navigate to WPML > String Translation > Utilities > Import/export .po. 2. Ensure you select the correct original language for the import. 3. If necessary, specify which languages you want to create translations for before proceeding with the import.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
