Problem: You are trying to translate pages on your site using WPML, but one specific page is not translating while others are. Solution: First, ensure that the post type 'Pages' in WPML > Settings > Post Type Translation is not set to display the original content if a translation does not exist. Next, check if the translation for this page is completed to 100% in the WPML Translation Editor and confirm that the translated page has been published. You can verify the status of the page by going to Pages > All Pages and selecting the language filter for English. Additionally, you can use the language switcher in the top admin bar to switch the admin language.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, 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. For further assistance, please visit our support forum at https://wpml.org/forums/forum/english-support/.
Please note that this solution might be 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 contact our support team for further assistance.
Problem: You are experiencing issues with translations not appearing correctly on the Home page of your website, although they appear correct in the backend and in the Advanced Translation Editor. Solution: If you're facing this issue, we recommend you try the following steps: 1. Edit the Home page in the default language. 2. Add "V2" to the page's title. 3. Click the update button. 4. Remove the "V2" and update the page again. 5. Click the "Spinning Arrows" icon to open the editor. 6. Complete the translation. 7. Clear the cache and check the translated page on the front end.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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. For further assistance, you can also visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: You are trying to translate text from a custom JavaScript on your website, but you're unable to do so because the strings are added through JavaScript and not localized. Solution: To make the text in your JavaScript translatable, you should use the
wp_localize_script
function. This function allows you to pass PHP variables to JavaScript. For more details on how to implement this, please refer to the WordPress developer resource: wp_localize_script Additionally, you can find a practical example discussed in our forum here: WPML support forum topic If you need further customization, we recommend contacting one of our third-party contractors who specialize in custom work with WPML: WPML Contractors
Please note that this solution might be irrelevant if it's 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 this does not resolve your issue, please open a new support ticket at WPML Support Forum.
Problem: The client wants to maintain Dutch as the default language for backend operations and translations, while setting English as the primary language on the front end of the website. The client also wants the original URL to direct to the English version, with Dutch available in the language menu. Solution: We recommend two features to achieve this setup: 1. Change the display language of the Back End: You can change the display language in the backend by navigating to Users > Profile in your WordPress dashboard. This change will only affect the user interface and not the content language. 2. Create content in any language with WPML: By using the flag option in the top-bar on the website's backend, you can switch and create content in any language, such as Dutch. This allows content creation in Dutch while keeping the website's default language as English. Currently, there is no feature to permanently set a different default language for the backend, but setting it to Dutch will remain until changed again.
If this solution does not resolve your issue or 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 problem persists, please open a new support ticket.
Problem: You are using the advanced translation editor in WPML and cannot save a translation due to an error stating that 'the original sentence includes formatting markers. However, not all markers are applied to the translation.' You need to know how to add formatting markers correctly to resolve this issue. Solution: We have identified that the issue arises because there must be an equal number of newline markers in both the original and translated content. For instance, if there are 7
wpml_linebreak
instances in the original text, you should ensure there are also 7 line breaks in the translation. It's important to note that one of these line breaks might be inside an HTML tag, so you should add one there as well. If you encounter difficulties in applying this solution, please provide us with the exact name of the page or post, and we can assist further.
Please be aware that this solution might be 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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are using the Divi Events Module plugin from Pee Aye Creative and are unable to translate some modules. Solution: Usually you translate the strings for each Divi Module together with your content using the WPML Translation Editor. This was an edge case, as these strings are not coming directly from the module, but instead from the plugin directly. First, scan the plugin for new strings by navigating to WPML > Theme & Plugin Localization. After scanning, you can translate the strings using the WPML String Translation module. For guidance on how to translate strings, visit the WPML String Translation guide.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Additionally, please 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, you can also visit our support forum.
Problem: The client was experiencing issues with the translation queue not loading and errors when editing translations. The theme used was not compatible with the site editor, and there were layout problems on the English homepage. Additionally, the client could not translate certain parts of the site using the Divi Events Calendar module. Solution: We recommended increasing the WP MEMORY LIMIT to at least 256M, as the existing setting was too low and could cause issues. We updated the WPML String Translation to the latest version and adjusted the database entries that were 'stuck'. We also cleared old translation packages and re-sent the Gravity Forms for translation. For the issue with the Divi Events Calendar module, we suggested opening a new support ticket as it required further investigation. We also recommended checking related known issues at https://wpml.org/known-issues/ and verifying the version of the permanent fix, confirming that the latest versions of themes and plugins are installed.
If this solution does not resolve your issue or seems irrelevant, we highly recommend opening a new support ticket for personalized assistance. Please visit our support forum at WPML Support Forum.
