4. Change something on the page with this shortcode and press the Update button. This will also trigger a change to the translation. (The pencil icon will change to a circled arrow icon).
5. Edit the page with the Advanced Translation Editor and see if you can translate the content of this shortcode.
Problem: The client wants to automatically translate their website's pages, including the search bar, into Urdu when clicking on the Pakistan flag, using the Houzez theme. Solution: We recommend checking the following guides to understand how to set up automatic translation and translate different content types such as menus and search bars:
Problem:
The original language of a global product attribute is still English language even though the site's default language is Turkish and delete the attribute and recreate it with the same name. Solution:
It is possible that the site's default language was English and the attribute name was translated. You can go to WPML > String Translation > Delete the translated attribute name and recreate it in the Turkish language. Relevant Documentation: https://wpml.org/documentation/getting-started-guide/string-translation/#deleting-strings
Problem: If you're experiencing the error 'WPML could not load configuration files, which your site needs' on your dashboard, accompanied by a 'cURL error 7' in your error log, this indicates an issue with the curl PHP library on your server. Solution: We recommend checking the curl version on your server. It should be enabled and updated to at least version 7.34.0. You can refer to our errata page for more information: WPML could not load configuration files. Please contact your hosting support to ensure that curl support is enabled and up to date. If this solution doesn't seem relevant to your issue, feel free to open a new support ticket with us for further assistance.
Problem:
I'm receiving a warning that the WPML plugin can't connect to WPML.org, and I need this checked in my logs.
Solution:
There's a significant chance that what you are seeing is a false positive that has been cached on the server. This notification will likely be automatically removed when the cache clears on its own.
To verify if it's a false positive, follow these steps:
1. Go to your WordPress dashboard.
2. Navigate to "Plugins" > "Add New" > "Commercial."
3. Click the "check for updates" button.
If the page refreshes and WPML is still showing as registered, then it is indeed a false positive, and you don't need to worry about it.
Problem: The client is experiencing duplicate entries of existing glossary items in WPML's Translation Management Tools Glossary. Solution: 1. Ensure that all WPML plugins are updated to the latest version. For example, update to WPML 4.6.6 and WPML String Translation 3.2.8. Before updating, make sure to save a backup of the site and database. 2. If updating does not resolve the issue, we are ready to investigate further and would require temporary access to the client's test site's wp-admin and FTP. The client should ensure that a backup is in place before providing access. 3. Our development team is aware of the Glossary Duplicate Entries issue and is planning to implement a fix in the next version of our Automatic Translation Editor. This update is expected to be released in a couple of days, and we will confirm back once it is done.
Problem: The client is experiencing issues with WPML string translation when importing strings. Specifically, strings with escaped characters do not match during import, and translations do not appear on the site. Additionally, deleted strings are not re-added after rescanning, and strings containing links are not displayed as translated on the frontend.
Solution: We have identified the issue as being related to the use of the
stripcslashes()
PHP function, which removes slashes that are not needed, causing a mismatch in JSON. We have escalated this to our developers. Meanwhile, we suggest two workarounds:
1. Do not scan strings with quotes and delete all previously scanned strings. Then, navigate to WPML > String Translation and enable "Look for strings while pages are rendered". Visit the page where the strings are displayed, and once the page is loaded, disable this option. This will add all strings with slashes to the String Translation, allowing for smooth import/export of the PO file.
Problem: The client wants the review banner that appears at the top of a translated page to remain in the original language (English) instead of being translated into the review language.
Solution: We have consulted with our second-tier support team and confirmed that the box is designed to appear in the review language, which is the language the page has been translated into. Unfortunately, there is no setting or workaround available to display this box in the default language (English) instead of the review language.
Problem:
Is it possible to change the original translation language now that the job has been started?
If not, can the ongoing job be deleted?
Solution:
It is not possible to change the source language of this job.
You should be able to cancel the job at WPML > Translation Management > Jobs if you choose the translation option "Translate what you choose" inside WPML > Settings > Translation mode.
Problem: The client was experiencing an issue where after activating their website, content such as menus, categories, and comments were not set to the default language, even though posts and pages were correctly assigned after using the 'Set language information' and 'Fix post type assignment' troubleshooting options. Solution: 1. We recommended creating a minimal environment by deactivating all non-WPML plugins and switching to a standard WordPress theme. It's crucial to back up the database and website before proceeding. 2. We advised increasing the WordPress memory limit to at least 128M, preferably 256M, as the client's site was set to 40M. Afterward, the client should confirm the memory change via WPML > Support > WordPress > Memory limit. 3. We suggested running the 'Set language information' button again. If the issue persisted, we provided a link to documentation for resetting WPML: WPML reset documentation, reminding the client to back up their site before attempting the reset. After these steps, the categories and tags were successfully set to the default language.
Problem: The client is trying to translate the header template using Divi Builder with WPML, but the URLs in the DonDivi DiviMenus Flex modules are not being translated and still point to the original language pages.
Solution: 1. Navigate to WPML-> Settings-> Custom XML Configuration tab. 2. Insert the following custom XML configuration:
3. Click "Save". 4. Edit the page/template in the default language and add the page's full URL. 5. Update the page/template. 6. Update the translation and search for the URL to ensure it's translated.
Problem: The client is experiencing an issue where the attribute filters on the shop page are not working correctly in the English version of the site. When applying an attribute filter, the results are displayed in the default language, and the language selection in the URL is lost during the filter action.
Solution: We recommend trying to switch the language URL format to the directory method. This can be done by going to WPML > Languages and selecting the 'Different languages in directories' option. This change might help the widget handle the language parameter correctly.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
