Problem: The client was experiencing issues with hreflang tags not pointing to the correct URLs on their multilingual website using the WPML plugin. The hreflang tag for Spanish was incorrect on the English page, and the hreflang tags for English and x-default included the /es/ subdirectory on the Spanish page. Solution: We recommended the following steps to troubleshoot and potentially resolve the hreflang tag issues: 1. Edit the page in English (original language). 2. Make a small change to the content (such as adding or removing a point). 3. Save the changes. 4. Update the translation. 5. Go to Settings -> Permalinks and re-save the permalinks. 6. Flush any cache memory that might exist. 7. Double-check if the issue disappeared. Additionally, we asked the client to temporarily remove the custom rewrite rules for custom post types to see if that resolves the issue. After disabling the custom rewrite, the hreflang tags were generated correctly.
If this solution does not apply to your case, or if it 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 issues persist, please open a new support ticket.
Problem: The client is using the gettext function in their theme's footer.php to translate strings into Spanish, but the translations are not appearing when the page is refreshed. Solution: We recommended the client to enable the Auto-register strings feature in WPML → String Translation. This should be temporarily activated. After activation, the client should visit the front end, scroll to the footer, and reload the site once. For more information about this feature, please review the documentation: https://wpml.org/documentation/getting-started-guide/string-translation/finding-strings-that-dont-appear-on-the-string-translation-page/#enable-auto-register-strings After completing these steps, the client should check the WPML String Translation dashboard again to see if the strings are now being picked up or if they appear translated when tested with an incognito window. If this does not resolve the issue, we suggested changing the gettext call from
_e()
to
__()
and testing again.
If these steps do not resolve the issue or if the information provided here is 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 WPML support forum.
Problem: You are trying to use the automatic translation feature in WPML for your website, but it fails to continue after initially working. Additionally, the 'fix it' pop-up disappears quickly without resolving the issue. Solution: The issue with the automatic translation not continuing might be due to the first invoice's safety feature that limits your credits. To resolve this, go to Pages and click the title of the page you want to translate as if to edit it. Then, click the cog icon next to the language you are translating to, for example, Spanish. At the top of this page, you should see a message about not having enough translation credits. Click this message, and it will direct you to a page where you can pay the $100 safety limit. After this payment, you should be able to continue translating with more credits. If this solution does not resolve your issue, we 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.
