Problem:
A client is trying to use WPML to make template files in a theme multilingual. When they tried to translate text using __(), they ran into an issue where the auto-translate button was not showing up. Solution:
1. We suggested the client to contact their hosting or webmaster to see if external connections or XLIFF file creation is blocked.
2. We suggested them to test on different servers and see if that solves the issue.
3. We recommended that they set their WordPress address (URL) and site address (URL) to be the same in their WordPress settings.
It's possible that this solution is outdated or doesn't apply to your case. If so, please open a new support ticket. We also strongly recommend that you check for related known issues, check the version of the permanent fix, and make sure that you have the latest version of your theme and/or plugins installed. Check for known issues
If you need further assistance, please visit the WPML support forum.
Problem: You have updated the header button text in mobile using Elementor and also updated WPML and WordPress to the latest versions. However, the updated text is not showing in the WPML strings.
Solution: We found that the issue was due to the missing translation of the header template. We added the translation, and now it is working correctly. If you're experiencing this issue, we recommend checking if all templates used in your pages are fully translated in WPML.
Please note that this solution 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 problem persists, please open a new support ticket at our support forum.
Problem: You are unable to use the autotranslate feature on your website despite having added 70000 credits to your WPML account, as it shows that the credits are zero.
If the credits are assigned but not reflecting in the Translation Management dashboard, follow these steps: 1. Go to Plugins -> Add New -> Commercial on your website. 2. Unregister WPML by clicking the unregister link. 3. Visit WPML Account Sites. 4. Delete the existing site key. 5. Create a new site key and remember to assign the credits. 6. Return to Plugins -> Add New -> Commercial on your website. 7. Click the register link and use the new site key to register.
If these steps do not resolve the issue, we 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 the problem persists, please open a new support ticket.
Problem: In Classic Editor, when entering a tag name, the AJAX request (ajax-tag-search) does not return some tags in Ukrainian, even though they exist in the database and are correctly translated in WPML. This issue does not occur in Gutenberg. Solution: If you're experiencing this issue, we recommend you go to WPML -> Languages and check the box for
Adjust IDs for multilingual functionality
. This adjustment should resolve the issue by ensuring that the AJAX requests in Classic Editor correctly recognize the language settings.
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 open a new support ticket at WPML support forum for further assistance.
