Problem: The client needed to translate text within the WPML plugin but was unable to find where to add these translations. Solution: 1. Navigate to WPML->String Translations. 2. At the bottom of the String Translation table, click on "Translate text in admin screens". 3. Search for the strings there and if found, select them and add them using the "Add to string translation" button. 4. Click on "Return to String Translations" and proceed to translate the text. For more detailed guidance, visit WPML String Translation documentation. Additionally, if the above steps do not resolve the issue, adding a custom XML configuration might be necessary.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check related known issues at https://wpml.org/known-issues/, verify the version of the permanent fix, and confirm that you have installed the latest versions of themes and plugins. For further assistance, please visit WPML support forum.
Problem: The client is unable to change the translation option of their ACF text fields under WPML > Settings > translation customFields because there is a lock symbol next to the fields. Solution: We explained that when the ACF field group translation settings are set to either "Simple fields across languages" or "Different fields across languages" from the ACF >> Field Groups page, it automatically sets the text field translation preference to "Translate" and locks the setting. To change the translation preference of field group fields, follow these steps: 1. Navigate to ACF >> Field Groups. 2. Edit the field group where you want to change the settings. 3. Click on the "Change option" and select the "Expert" option. 4. Individually edit each field and set the translation preferences as needed. 5. Make a minor change in the default language page, then edit the secondary language page to see if the issue resolves. For more details on the Expert mode, visit Expert translation option.
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 the issue persists, please open a new support ticket.
Problem: The client was experiencing an issue where the Elementor template title was not displaying correctly in the second language for an alternate loop item. The first loop item was translated correctly, but the alternate loop item was not showing the translated version automatically. Solution: We recommended the following steps: 1. Edit the template in the original language (German). 2. Make some changes and save the template. 3. Update the translation template using the WPML Translation Editor. It is important not to edit the translation template directly, as changes will be lost after updating the translation with WPML Translation Editor. We also provided a link to our documentation for further guidance: https://wpml.org/faq/why-arent-my-translations-showing/
If you're experiencing this issue, we recommend you try the steps outlined above. However, please note that the solution might be irrelevant due to it being outdated or not applicable to your case. If these steps do 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. Should you need further assistance, please do not hesitate to open a new support ticket with us.
Problem: The client wants to synchronize content between the Italian and German versions of their website, where some content is translated and some is not.
Solution: 1. We recommend using the WPML 'Duplicate' feature to copy content from the Italian site to the German site where translations are missing. This will ensure that changes in the Italian content are automatically applied to the German version. For detailed instructions, please visit Displaying Untranslated Content on Pages in Secondary Languages.
2. If your site uses custom fields, you can decide which custom fields should be translated and which should be copied (synchronized) between languages. This allows you to keep some fields synchronized across languages while translating others. For guidance on this process, please refer to Translating Custom Fields.
By following these steps, you can ensure that specific content remains synchronized between the Italian and German versions of your site, while still allowing for translations where needed.
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 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 at WPML support forum.
