Problem: The client needed to translate the SEO title, meta description, and author bio of the author archive page on their website using WPML. Solution: 1. Navigate to WPML > String Translation. 2. In the bottom section, enable "Edit user roles" within the "Translate user properties" section. 3. Use the text search field at the top or select specific text domains to find the strings you want to translate. 4. Optionally, create a translation job for these strings at WPML > Translation Management > Dashboard > Other texts. 5. If the author's text is not available for translation, go to the user profile, edit and save the text again, and ensure it is registered new in WPML > String Translation. Adjust the source language of the string if necessary. For detailed guidance, refer to the following documentation:
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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.
Problem: The client is experiencing an issue where the translation of a Gutenberg "Details" block text is not reflecting on the frontend, despite being correctly displayed in the Advanced Translator.
Solution: We have resolved this issue in WPML version 4.6.10. We recommend updating to the latest versions of WPML plugins and WordPress. Before proceeding with the update, please ensure to take a full backup of your website and database.
After updating, check if the translation issue is resolved on the frontend.
If the problem persists or if this solution is not relevant to your case, perhaps because it's outdated or not applicable, we suggest opening a new support ticket. We also highly recommend checking the related 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.
Problem: The client has created a map with MapPress, which is typically compatible with WPML, and inserted into a page edited with Elementor. When trying to find the text strings to translate following the plugin's instructions, only the system strings appear and not those that the client has entered when creating their map. Solution: If you are experiencing this, we recommend that you try the following: 1. Go to WPML → String Translation. 2. Activate the option "Search for text strings while pages are rendered". 3. Navigate to the page where untranslated text strings are displayed. 4. Go back to WPML → String Translation and check if the given string has been registered. 5. Translate the string. https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/
This solution may be irrelevant, either because it is outdated or because it does not apply to your case. If so, we suggest you open a new support ticket. We also strongly recommend reviewing related known issues at https://wpml.org/known-issues/, check the version of the permanent solution and confirm that you have installed the latest versions of themes and plugins. If you need additional assistance, please contact us on the WPML support forum.
Problem: The client inquired about which comparison table plugin is compatible with WPML, specifically asking about Ninja Tables or any other plugin. Solution: We informed the client that Ninja Forms is compatible with WPML and provided a documentation link: Creating multilingual forms using Ninja Forms and WPML. While Ninja Tables is not officially compatible, we suggested a forum topic that might help: Translation of the content of tables created with Ninja Tables. Additionally, we recommended searching for other plugins through the WPML compatibility page: WPML compatible plugins. We also clarified that a lack of official compatibility does not necessarily mean that a plugin will not work with WPML; it simply has not undergone our comprehensive testing process.
If this solution does not seem relevant, please feel free to open a new support ticket in our support forum.
Problem: The client needed to know if they could create a Pattern (reusable block) that can be edited with the WP editor to display differently in various languages and be used on pages translated using the Advanced Translation Editor (ATE) without causing conflicts. Solution: We reassured the client that creating and using reusable blocks should not cause conflicts with WPML. We provided steps for translating reusable blocks and mentioned that they might need to translate the page without ATE to display the block differently in various languages. For detailed guidance, we shared documentation links:
