Problem: The client wants their URL to include language codes in uppercase (e.g., domain.com/fr-FR/) during the initial setup of the WPML plugin. However, they encounter an error stating that only lowercase letters and '-' are allowed, which prevents them from setting uppercase language codes initially. Solution: We explained that all language codes should be in lowercase due to international standards and WordPress conventions. ISO 639 language codes must appear in lowercase, while country codes can be capitalized. The ability to add uppercase letters later in the 'edit language' section is identified as a bug and is scheduled for a fix. We recommend using lowercase language codes to avoid issues with translation files from other plugins and search engines.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also advise 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 at WPML support forum.
Problem: The client created translations for a header and footer template in different languages, but when changing the language on the site, the translations do not appear and continue to display the English version. Solution: We recommend editing the template by making a small change to the content, saving it, and then updating the translation template to see if the text becomes available in the Advanced Translation Editor. If the issue persists, it may be due to the use of custom Elementor widgets that are not registered for translation. In this case, follow the steps to create custom XML configuration code to register these widgets for translation: How to Register Page Builder Widgets for Translation WPML Compatibility Test Tools Plugin
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 needed, please open a new support ticket for further assistance.
Problem: If you're experiencing issues with double slashes (//) in your URLs for custom post types, which are being flagged as hreflang issues in your site crawls, this might be related to WPML's redirection functionality. Solution: First, verify if the double slashes appear when WPML is deactivated. This will help determine if the issue is directly caused by WPML or if it exists independently of it. If the double slashes still appear with WPML deactivated, the problem does not originate from WPML. It's also important to note that WPML correctly adds hreflang tags, and the issue of double slashes should not be confused with hreflang problems. If you need further clarification on why double slashes are flagged as hreflang issues by specific tools, you should contact the tool provider directly.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your specific case, we recommend opening a new support ticket. We also 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 at WPML support forum.
Problem: You are trying to display a page in German, but despite translations being present in the translation editor, they do not appear on the page. Instead, texts are still in French. Solution: If you're experiencing this issue, we recommend checking if you have installed the String Translation addon, which is essential for translating page content with Elementor. You can install this addon by going to Plugins > Add new > Commercial. After installation, re-translate your page. Additionally, it's a good practice to make a backup before installing new plugins.
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.
Problem: You are unable to update the WPML Multilingual CMS due to a critical error occurring when removing and adding the site key. The error message indicates that the update failed because the undefined site key does not match. Solution: First, ensure that you are using the correct site key for your WPML Multilingual CMS. We have removed the incorrect key and replaced it with the correct one, which resolved the update issue. Additionally, there is a notification about WPML String Translation attempting to write .mo files to a folder. You should check with your hosting provider to ensure that these folders are writable to prevent future issues.
If this solution does not resolve your issue or seems irrelevant due to it being outdated or not applicable to your case, we highly recommend opening a new support ticket. Also, check the related 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, please visit our support forum.
Problem: The client is experiencing issues where category pages are not connected with their translated equivalents, and hreflang tags are missing on paginated category pages. Additionally, the language switcher redirects to the root category page instead of the corresponding translated category page. Solution: We recommended inserting custom PHP code into the theme's functions.php file to address the URL issues with the language switcher on paginated category pages. Here is the code you should add:
For the hreflang tags issue, it was determined by our 2nd Tier Support that this is a default behavior and indexing paginated archive pages is not recommended. If you still require hreflang tags on paginated pages, it would require custom programming, which is outside our support scope. We recommend consulting with one of our certified partners: http://wpml.org/documentation/support/wpml-contractors/
If this solution does not resolve your issue or seems irrelevant, 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 needed, please open a new support ticket at WPML support forum.
Problem: The client wants to skip translations for brand names and product names in WPML. Solution: If you're experiencing the same issue, we recommend the following steps: 1) To avoid translating brands and products entirely, navigate to WPML-> Settings-> Post Type Translation and Taxonomies Translation sections, and set the products/brands to "Not Translatable". 2) If you wish to translate other elements but keep the product and brand names the same, proceed with the normal translation process and simply copy the title in the translation editor.
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.
Problem: You are experiencing issues where pages are not translated in DIVI after using auto translation. Solution: If you're facing this issue, we recommend you try the following steps: 1- Edit the page in the default language. 2- Add 'V2' to the title and update it. 3- Delete the 'V2' and update it again. 4- Update the page's translation.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client has created a field with ACF called Tags, which is a taxonomy for tags matched to images attached to posts. Although these tags are translated, they are not displayed in the Italian version of the site.
Solution: We found that due to some custom coding the issue arises because when media is added in the default language and tagged, the tags are stored in the postmeta table. However, when switching to the secondary language and editing the media, the translated tags do not have a corresponding entry in the postmeta table. To resolve this, the client should edit the media in the secondary language, remove any pre-filled tags, and add them again to ensure the postmeta table is updated correctly for the secondary language.
If this solution does not resolve your issue, 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 at WPML Support Forum.
Problem: You are using Beaver Builder on a development site and have encountered an issue where the saved global rows are not translating, despite increasing the memory limit in wp-config. Solution: We recommend you navigate to WPML > Settings > Post Types Translation and set the post type
Templates (fl-builder-template)
preference to Translatable - Only show translated items and then save your changes. Next, go to Beaver Builder > Saved rows or WPML > Translation Management to translate the saved row template into the second language. For further guidance, you can refer to our 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. Should you need further assistance, please do not hesitate to open a new support ticket or visit our support forum.
Problem: The client is unable to find documentation on how to change the translation switcher abbreviations in WPML to display 'EN' for English and 'ES' for Spanish. Solution: If you're experiencing this issue, we recommend you follow the steps outlined in the forum post to set the language name to show the abbreviated version. You can find the detailed instructions here: https://wpml.org/forums/topic/abbreviate-languages-on-the-switcher/
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: The client needed to change the linked site from /development to /staging in their WPML account, but was unable to do so because the development site had been removed. Solution: 1. We recommended that the client go to their WPML.org account profile and remove the key generated for the old/deleted site. 2. Next, navigate to Plugins->Add new->Commercial tab in the WordPress dashboard. 3. Choose to Unregister WPML or Register WPML and click on "Get a key for this site". This action will automatically generate a new key code for the staging site. 4. After registering, go back to Plugins->Add new->Commercial tab and click on "check for updates" to ensure everything is functioning without errors.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are seeing four PHP errors related to WPML on your website. Solution: The errors you are encountering are 'deprecated' warnings in PHP. This means that the functions causing these warnings are outdated and discouraged for use, as they may be removed in future PHP versions. To resolve these warnings, we recommend updating to a PHP version that is fully compatible with WordPress, such as PHP 7.4 or 8.0. This update should eliminate the deprecated warnings.
If this solution does not apply to your situation, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket with us for further assistance. You can do so at our support forum.
Problem: The translation service translated some jobs but the translation can't be retrieved to the website
Solution: the upload translated XLIFF file was having some issues in the format, I told the client to remove the extra tags that causes the issues and it solved the problem
Problem: The client is experiencing issues where changes made to a calculator plugin and media translations are not displayed on the Italian and English translations of the homepage, despite working on a subpage. Solution: We recommend the following steps to resolve the issue: 1. Navigate to WPML > Settings > Custom XML Configuration. 2. Add the following code and save:
3. Make a small change on the page that contains the image and save. This should allow you to translate the URL of the image directly in the translation editor.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
