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: The client is unable to approve translation reviews on the translations queue page due to a console error: TypeError: Failed to construct 'URL': Invalid URL. Additionally, there were issues with the WordPress memory limit settings. Solution: We recommended the client to perform a conflict test by: 1. Setting a default WordPress theme. 2. Keeping only WPML Plugins and essential plugins active. 3. Disabling all other plugins. This step helps in identifying if there's any theme or plugin conflict. We also advised ensuring a full backup before making any changes. Furthermore, we noticed that the WordPress Memory Limit was below the minimum requirement for WPML. We suggested increasing the memory limit by adding the following code in the wp-config.php file:
If these steps do not resolve the issue or if the solution seems outdated or 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client needed to change links in a translated page and was unsure whether to use the WordPress editor or another method. They also inquired about the potential issues of editing the translated page with the WordPress editor and how to set the advanced editor after using automatic translation. Solution: We advised the client to manually translate the links using the Advanced Translation Editor. To do this, they should first switch off "Automatic Translation" and select "Translate what you choose" mode. Then, navigate to the primary language page and initiate the translation. In the Advanced Translation Editor, they should type "HTTP" into the search box to locate the links that need translation. For further guidance, we provided a link to a video tutorial on how to translate links: Translating Links with Advanced 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 at WPML support forum.
Problem: The client is experiencing an issue where some customized fields are not appearing in the WPML editor for translation. This problem is possibly related to the field size limitation in the database. Solution: We recommend increasing the field size in the database to accommodate larger data. You can do this by executing the following SQL command:
ALTER TABLE `wp_icl_translate`<br />CHANGE `field_type` `field_type` varchar(264) COLLATE 'utf8mb4_unicode_520_ci' NOT NULL AFTER `timestamp`;
Please ensure to replace `wp_icl_translate` with your actual table prefix and make a backup before applying this change. After updating the database, make a minor edit to the main language page to resynchronize the content.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your setup, 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: The client was unable to see the CTA button on the Chinese version of their website even after adding String Translations in WPML. Solution: We recommended checking the Chinese Language navigation menu to ensure the menu item with the button was appearing, following the 'Fully Custom' method described in this documentation. We then proceeded to translate the menu ID, the button URL, and the button text via the WPML String Translation interface.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly 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 WPML support forum.
Problem: You are trying to change the default locale, hreflang, and language mapping to Portuguese-Brazil on your website but encountered an error stating 'The default locale already exists.' You were able to change the mapping but not the locale or hreflang. Solution: To resolve this issue, follow these steps: 1) Activate the pre-defined Portuguese (Brazil) language on your site. 2) Go to the language settings and click to edit the languages. Initially, change the default locale for the Portuguese (Brazil) language to a temporary one, such as
pt_BRtt
, and save the changes. 3) After this, you can set the new language data with default-locale:
pt_BR
.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. Also, check the related known issues and ensure you have the latest versions of themes and plugins installed. For further assistance, please visit our support forum.
Problem: The client is experiencing issues with translations on their homepage not appearing as single sentences but as individual words, despite being translated previously. Additionally, the homepage needs to be updated in all languages without losing existing translations. Solution: 1. Edit the homepage using the Elementor editor in the default language. Ensure that text sections are correctly formatted, specifically checking and adjusting tags as necessary. 2. Update the homepage. This should trigger updates across all translations. 3. If the issue persists, switch to the translation language on the homepage, click 'Edit translation', and check if the text appears as individual words. 4. If so, edit the problematic section in Elementor, remove any unnecessary HTML tags, and ensure the entire text is wrapped in a paragraph tag. 5. Save the changes and verify by revisiting the homepage and selecting 'Edit translation' again.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific case, 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, visit our support forum at WPML Support Forum.
Problem: The client is working on a site under development and needs to register the WPML key to the website. Additionally, the WPML plugin cannot connect to wpml.org, which is necessary for checking new releases and security updates. Solution: To register the WPML key: 1. Ensure you are logged into wpml.org. 2. Navigate to WordPress Dashboard > Plugins > Add New > Commercial (Tab). 3. Click on "Register WPML" at the right section of the screen. 4. Click on "Get a key for this site". A new page will open, and the auto-generated key will appear. 5. Copy the key and paste it into the "Site Key" input box. 6. Click the "OK" button. For more information, visit https://wpml.org/faq/install-wpml/#register
For the connection issue: 1. Contact your hosting service provider and request them to whitelist the following URLs: - wpml.org - cdn.wpml.org - api.wpml.org - api.toolset.com - cloudfront.net For more details, visit https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/
Regarding plugin installation, the client does not need to install all plugins shown. Essential ones include WPML String Translation and WPML Multilingual CMS.
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 at WPML support forum for further assistance.
Problem: The client was encountering a fatal error when trying to open the WPML/Languages menu item in their WordPress site. The error message indicated a call to an undefined function 'wpml_tm_load_tp_networking()'. Solution: We recommended the client to manually download and reinstall the 'WPML Multilingual CMS' plugin from the WPML account downloads section. Despite reinstallation and cache clearing, the issue persisted. We then accessed the site with the client's permission to investigate further. After troubleshooting, we added a function to recreate any missing WPML tables in the database, which resolved the issue on the live site. We advised the client to apply the same workaround on the staging site and to deactivate and reactivate all plugins to ensure the cache was flushed.
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 problems persist, please open a new support ticket.
Problem: The client has multiple branches with the same page titles (e.g., 'Dining') under different URLs (e.g., /london/dining, /berlin/dining) within their website. In WPML's Translation Management, these pages appear with the same title without showing their full URL or hierarchy, making it difficult to identify and translate the correct page for a specific branch. Solution: 1. If the pages are not set as child pages but follow a hierarchical structure like destination pages (London, Spain, etc.), you can assign a translation priority when editing the page. This allows you to filter pages by priority in WPML's Translation Management. 2. Another method is to hover over the 'Edit' button for the page in the Translation Management dashboard. This action will display the URL in the browser's status bar or tooltip, showing the post ID. You can use this ID to identify the correct 'Dining' page to translate.
If these solutions do not apply to your case, or if they seem outdated, we recommend opening a new support ticket. We also highly 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: You are trying to display individual elements with translation on the frontend of your site, but some elements, like a PowerPack Card Slider, are always displayed in German on the translated English page. Solution: First, ensure that the card slider content is available in the Advanced Translation Editor. Try making a small change to the page title or content, save it, and then update the translation to see if this resolves the issue. If the problem persists, the card slider content might not be registered for translation. We recommend you create a custom XML configuration code to register the card slider content for translation. You can follow our documentation here: How to Register Page Builder Widgets for Translation.
If this solution does not apply to your case, or if it seems outdated, please open 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, you can contact us directly at the WPML support forum.
Problem: The client is experiencing an issue where the language switcher is not visible on mobile devices, and only the default language appears without any dropdown menu for selecting other languages. Solution: We recommend checking if the translated pages are still in the review phase or saved as drafts, as this could be why the language switcher does not display other languages. Here are the steps to resolve the issue: 1. Ensure that the Translation review is completed by following this guide: How to review automatic translations on your site. 2. From the WordPress dashboard, switch to a secondary language using the language switcher in the top bar of the admin area. 3. Navigate to "Pages > All Pages." 4. Check if the status of the pages is set to 'Published'. If they are in 'Draft' status, publish them by clicking on the "Quick Edit" button below the page name and changing the status to Published.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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, please visit our support forum at WPML Support Forum.
Problem: The client is developing a site and wants to add the Danish language. They encountered issues where 'Validate on save' shows 'Not valid', and the backend won't open after attempting to deactivate WPML. Solution: First, ensure that the subdomain for the Danish language points correctly to the root folder. This involves configuring the DNS settings. You can find detailed instructions on how to do this here: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/#2-configure-the-dns-settings. Once the DNS settings are correctly configured, try to validate the site again. If the problem persists or the solution provided here is not applicable due to being outdated or not matching your case, 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 contact our support team directly at the WPML support forum.
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.
Cette Page comprend les tickets d’assistance qui sont résolus et documentés. Tu cherches des billets qui sont « en cours » ? Visitez l’archive complète des tickets d’assistance
