Problem: The client is unable to translate multiple slugs on their website despite having the correct settings enabled. They are experiencing an issue where only one slug is available for translation instead of five, as seen on the original English page. Solution: We confirmed that the slug translation is functioning correctly for the page the client mentioned. If the client wishes to change the translated slug, they can simply click on it to modify it. Additionally, if the client uses absolute URLs, WPML should automatically recognize and translate these URLs. However, for relative URLs, WPML might not detect them as internal URLs. In such cases, the client needs to manually search for these URLs or they will appear in the Advanced Translation Editor for translation. For more details on how to search for a URL, please visit: https://wpml.org/faq/how-to-translate-urls-shortcodes-and-html-attributes-using-the-advanced-translation-editor/
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, 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 contact us through the WPML support forum.
Problem: If you're experiencing issues with copying and pasting translated text, where the right-click doesn't work after entering a word, this be due to our spellchecker/dictionary not being applied yet. Solution: We have identified that this issue occurs because the browser context menu is replaced with our spellchecker/dictionary. To work around this, you can enter a space after the word, which should make the browser mark the word with an underlined red color and load our own context menu. Alternatively, we recommend using keyboard shortcuts for copying and pasting.
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 issue persists, please open a new support ticket at WPML support forum for further assistance.
Problem: You are unable to see and translate the image ALT, Name, and Description from within the WPML advanced editor, despite having addressed this issue previously. Solution: This issue arises because the search function in the WPML advanced editor only locates content within the included text, not based on attributes like ALT, Name, or Description of images. To resolve this, we recommend checking our documentation on how to properly configure and use the advanced editor for translating image metadata. Additionally, ensure that you have the latest versions of WPML and other related plugins installed.
If this solution does not apply to your case, or if it seems outdated, please visit our known issues page and verify the version of the permanent fix. If issues persist, we highly recommend opening a new support ticket with us for further assistance. You can do so at our support forum.
Problem: The client was experiencing issues with translating image texts using WPML. The texts on the left side to be translated appeared in the same language as the target language, making translation from French to French impossible. Solution: We recommended checking if the WPML SEO add-on is installed by following the documentation at https://wpml.org/documentation/plugins-compatibility/using-wordpress-seo-with-wpml/. Additionally, we suggested troubleshooting steps that involved: 1. Ensuring the translation was marked as 'in progress' and then duplicating the content. 2. Navigating to WPML->Support->Troubleshooting. 3. Running several actions:
Clear WPML cache
synchronize local job ids with ATE ids
Synchronize translators and translation managers with ATE
Set language information
Cleanup and optimize string tables
These steps resolved the issue of incorrect language display in the Advanced Translation Editor (ATE).
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 at WPML support forum.
Problem: The client was experiencing issues with duplicate texts and texts that did not exist on the original page or any of the images while trying to translate a page using WPML. Additionally, remnants of the uninstalled RankMath SEO plugin were still visible in WPML settings, potentially affecting the translation process. Solution: We recommended the following steps to address the translation issues: 1. Navigate to WPML > Support > Troubleshooting and click on the buttons to clear the WPML cache, remove ghost entries from translation tables, fix element_type collation, synchronize local job ids with ATE jobs, synchronize translators and translation managers with ATE, assign translation status to duplicated content, set language information, and fix post-type assignment for translations. 2. Open the default page in the WordPress editor, make a small change in the page title, save the changes, and update the translation. For the RankMath remnants, we instructed the client to remove the custom fields from the database that were left behind after uninstalling the plugin. This involved using a database plugin to identify and delete the specific meta fields from the wp_jfsjb2cm3k_postmeta table.
If the solution provided 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was able to translate image texts (ALT, name, and description) on the first page but encountered issues on the second page where none of the translations were working. Solution: We recommended checking the WPML -> Settings -> Media Translation and ensuring that the option "Translate media library texts with posts" is enabled. This setting allows the translation of media meta information when using the WPML Translation Editor. Additionally, the client can edit the meta information for any attachment in the Media Library by switching the language in the top admin bar or using the WPML Media Translation add-on. For more detailed guidance, visit WPML Media Translation documentation.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are trying to remove all remnants of the RankMath plugin from your WPML translations after switching to Yoast, but despite deleting the plugin, its remnants still appear in WPML translations. Solution: The remnants of RankMath are still present in your database, which is why WPML continues to offer these fields for translation. To completely remove these remnants, follow the steps similar to those used for removing old custom fields from Yoast, which can be found in our forum discussion: https://wpml.org/forums/topic/split-how-can-i-remove-old-unused-custom-fields/ and https://wpml.org/forums/topic/delete-used-fields/. Make sure to search for 'Rank Math' fields specifically when prompted for the field name. It is crucial to create a backup of your database before proceeding with the removal.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Additionally, 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, please visit our support forum: https://wpml.org/forums/forum/english-support/.
Problem:
I am working on a site under development and trying to translate internal link of the button using WPML, but the internal links do not show up in the Advanced Translation page.
If you need to translate the slug of the page itself, use these steps: 1) Activate the option "Translate (this will include the slug in the translation and not create it automatically from the title)" in WPML → Settings → Translated documents options. 2) Then, edit the page. Make a minor modification to the page, save it, and navigate to the WPML translation editor. The slug will be added to the translation. Translate or change it and save it.
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 this does not resolve your issue, please open a new support ticket.
Problem: You are working on a site under development and trying to ensure that the Rank_Math plugin and its database entries are completely removed. However, strings related to the Rank_Math plugin are still showing up even after the plugin has been eradicated. Solution: If you're experiencing this issue, we recommend you try removing strings from a specific domain in WPML > String Translation. Please follow the instructions in the second part of the section "How to Delete a String" to remove strings by domain. You can find the detailed steps in our documentation here: WPML String Translation Documentation.
If this solution does not apply to your case, or if it seems outdated, 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.
Problem: The client is trying to translate existing pages and remove obsolete content from a previous page builder (WPBakery) that is still appearing in the Translation Management filter options, even after deleting all references from the server database.
Solution: 1. To remove a specific string, search for and delete it from the String Translation page. For detailed instructions, see How to delete a string. 2. If there are any unwanted translation jobs, cancel them from the Translation Jobs page. For more information, visit How to cancel translation jobs. 3. To delete templates from WPBakery: - Reinstall WPBakery and locate the stored templates. - Delete the templates in the default language and their translations, ensuring to also remove them from the trash. 4. It is advised not to delete template posts directly from the database to avoid orphan records. Instead, consider reinstalling WPBakery or contacting their support for assistance.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need help, please open a new support ticket. For further assistance, visit the WPML support forum.
Problem: The client was experiencing an issue where both the top and bottom language switchers were only showing the original language available, instead of all the languages.
Solution: We advised the client to ensure that the home page is completely translated. The language switcher by default only displays languages/flags for which translations are available. If the home page is not translated, the language switcher will not show the other languages.
If the solution provided here does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we encourage you to open a new support ticket. We also highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If further assistance is needed, please contact us on the WPML support forum.
Problem: The client needed confirmation on whether changing the hreflang attribute from "fr" to "fr-ca" was correct for their site targeting French-Canadian users, and whether using American English as the primary website language instead of British English would pose an issue for targeting Canada. Solution: 1. We confirmed that using "fr-ca" is appropriate if the client wants to target the Canadian French-speaking audience. If the client does not wish to target specifically Canadian users, they can use "fr". 2. To change the hreflang value, we advised the client to navigate to WPML > Languages > Edit Languages. 3. We also mentioned that the client could switch to "en-gb" if they feel it is more accurate for their target audience, but if they do not target "en-gb" users, no change is necessary at this time. 4. We provided a custom search URL for the client to explore existing tickets regarding similar hreflang changes: here.
Please note that the solution provided might be irrelevant due to being outdated or not applicable to your case. If the solution does not resolve your issue, 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 you still need assistance, please open a new support ticket here.
