Problem: You are using WPML to auto-translate content and want internal links to automatically update to the translated URLs. However, some links are not correctly updated to the Spanish URL after auto-translation. Solution: 1. Ensure that the content type (e.g., 'case type') is set to 'Translatable' in WPML > Settings > Post Type Translation. This setting allows WPML to handle the translation of links associated with these content types. 2. Create a test post with internal links to the content types and publish it to see if the links correctly point to the translated versions. 3. If links are still not translating correctly, you can manually adjust the links by following the instructions here: https://wpml.org/faq/how-to-translate-links/
If this solution does not resolve your issue or seems outdated, we 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 at https://wpml.org/forums/.
Problem: If you're experiencing issues where internal links are not automatically translating to the correct URL on the translated page, this might be due to the links not being translated in the Translation Editor. Solution: We recommend following these steps: 1. Create a full site backup. 2. Navigate to WPML -> Settings -> Translate links section, and click on the button to start the translation process. Wait for the process to finish. 3. Flush any cache memory that might exist on your site. 4. Double-check if the issue has been resolved by updating the translation of the page, searching for the links, translating them, saving the changes, and confirming that the issue is solved.
If this solution does not resolve your issue or seems irrelevant due to being 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.
Problem: You have set the WPML Page URL to translate, but when creating a new page, the Spanish page slug isn't translated automatically. For example, instead of the expected URL 'https://tilstaging.wpengine.com/es/nueva-pagina-de-prueba', you see 'https://tilstaging.wpengine.com/es/new-test-page/'. Solution: By default, WPML translates URL slugs using the page title when you use the automatic translation setting 'Auto-generate from title (default)'. If you choose the option 'Translate', which includes the slug in the translation, you must manually translate the URL slug using the Advanced Translation Editor. This option does not automatically translate the slug if the page is sent for automatic translation. To ensure URL slugs are translated as expected, you might need to manually adjust them in the Advanced Translation Editor. For more details on how to translate page and post URL slugs, please visit Translate Page and Post URL Slugs.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also highly suggest 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.
Problem: You are encountering an issue where both the original and updated permalinks for a translated page are functioning, leading to unexpected redirections. This occurs after changing the slug to resolve a 404 error on the translated page. Solution: The issue stems from custom code that modifies the URL structure. Specifically, the code segment handling 'locations' might be causing the redirection behavior. To address this, you can modify the code by commenting out the following line:
This change should ensure that only the desired URL remains active, preventing the original URL from redirecting to the updated one.
If this solution does not resolve your issue or seems outdated, please check the related known issues and confirm that you have the latest versions of themes and plugins installed. If the problem persists, we recommend opening a new support ticket at WPML support forum.
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.
