Problem: You are trying to manually translate a string using WPML, which translates correctly in all languages except Spanish. The translation only appears when 'Look for strings while pages are rendered' is enabled, reverting to the default when disabled. Solution: We suspect the issue might be due to two reasons: 1) The text domain might not be used or loaded correctly. Ensure your code includes the text domain like this:
__( 'Text to translate', 'your-text-domain' )
For more details on internationalization, visit WordPress Developer Internationalization. 2) The .mo files may need regeneration. You can regenerate these files by navigating to WPML → Support → Troubleshooting and clicking on "Show custom MO Files Pre-generation dialog box".
If this solution does not resolve your issue, or if it 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 persists, please open a new support ticket with us for further assistance.
Problem: The client is using the Divi theme builder and has translated strings related to the Divi template builder. Despite being visible in WPML > string translation, these translated strings are not showing on the frontend. Solution: 1. Ensure that the Divi template itself is translated, as strings found in the String Translation might belong to the template. If the template is not translated, the strings will not appear translated on the frontend. Detailed steps for translating Divi templates can be found here: Translating Divi Templates Documentation. 2. Use the Advanced Translation Editor (ATE) which includes Translation Memory. This feature helps in avoiding repetitive translation of the same content across different layouts. More information on ATE and Translation Memory can be found here: Translation Memory Documentation.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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: WPML Support Forum.
Problem: You are unable to install WPML on your localhost due to an error: 'Unable to parse data from service response'. This issue might be occurring because your localhost is not able to connect to the WPML servers. Solution: We recommend checking if your localhost environment is properly configured to connect to the internet. Additionally, ensure that it is not being blocked by any antivirus software or firewall. Specifically, your localhost should be able to connect to the following addresses:
wpml.org
cdn.wpml.org
api.wpml.org
api.toolset.com
cloudfront.net
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific 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 persists, please open a new support ticket for further assistance at WPML support forum.
Problem: The client was inquiring about different methods of translating layouts in Divi Builder using WPML, the possibility of using the Divi visual builder for layout translations, translating taxonomy slugs to keep the same slug across languages, and forcing the default language to include the language code in the URL.
Solution: 1) We recommend not mixing different translation methods for the same item. If you're using the WPML translation editor, directly editing the translation can lead to problems. More details can be found here: Using different translation editors for different pages.
2) It is expected behavior that the Divi visual builder cannot be triggered while translating layouts because the "edit with the Divi builder" button does not appear in this case.
3) To keep the same slug for translated taxonomy, you need to enable the slug option in the WPML settings. Please refer to this documentation: Translating taxonomy slugs with WPML.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, 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 you still need assistance, please open a new support ticket at WPML support forum.
Problem: The client is using the WordPress editor for post translations and is unsure how to translate the title, alt text, and other attributes of the featured image, as well as seeking advice on handling image translations efficiently. Solution: If you're experiencing difficulties translating the title, alt text, and other attributes of the featured image using the WordPress editor, we recommend the following steps: 1. Use the 'text' tab in the WordPress editor to edit the HTML code of the content, similar to how you would with the default language. 2. Navigate to WPML->Media Translation to add translations for your images. Remember that after adding translations here, you must update the translation of the page or post for the changes to take effect.
Please note that this solution might not be applicable to your situation if it's outdated or not relevant to your specific case. We 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. If the issue persists, please open a new support ticket with us.
