Problem: If you're experiencing issues with translating content that starts with numbers followed by dots (e.g., '1.1.') using WPML's Advanced Translation Editor, where such text remains untranslated in other languages, this might be due to a formatting issue recognized by the editor. Solution: We recommend removing the last dot after the number sequence. For example, change '1.1.' to '1.1' without a dot after the second number. This adjustment should make the sentences appear for translation in the Advanced Translation Editor. You can also use the search field in the editor to locate these specific sentences by searching for the dot (.). Please note that this issue is fixed with the latest versions of the 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.
Problem: You are working on a site under development and trying to change the source language of a Gravity Form using WPML. When selecting all string translations for the form, you receive a message: 'You have selected strings belonging to a package. Please select all strings from the affected package or unselect these strings.' The message does not specify which package, preventing you from changing the language of the form. Solution: To resolve this issue, follow these steps: 1. Go to the WPML > String Translation page. 2. Use the search filter to find strings related to your Gravity Form. 3. Check the 'Belongs to a package' column to identify the package name associated with the strings. 4. Once identified, either select all strings from that package or deselect the strings as needed. 5. After adjusting your selections, try changing the source language again.
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 verify that you have installed the latest versions of themes and plugins. For further assistance, please visit our support forum.
Problem: The client is experiencing an infinite redirection loop when visiting the English version of their site with the WPML SEO plugin activated. This issue arises after changing their setup to have each language in its own directory, with an HTML page at the root URL that redirects based on browser language.
Solution: 1) Ensure you are following the steps in our documentation to set up the Language Directory for the default language: Redirect the root domain to the default language Language setup for directory default language 2) Upgrade to the latest version of WPML plugins (4.8.1 series). 3) Go to WPML >> Languages >> Languages URL format, and resave the settings. 4) Visit Settings >> Permalinks, and resave the settings. 5) Clear all types of caches. 6) Check for unexpected redirects set inside the "Redirection" plugin or other SEO plugins like Yoast SEO Premium, as these might conflict with WPML's settings.
If these steps do not resolve the issue, it might be due to specific configurations or conflicts within your site. 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.
Problem: You are translating your website from Swedish to English using WPML and facing an issue where internal links are not being translated automatically in the WPML translation editor. This occurs even though English is set as 'hidden' in the settings, and you are using the WPML translation editor for Elementor pages, posts, custom post types, and templates. Solution: 1. Ensure that your WordPress Settings for the site URL include 'https' to match the frontend URLs. Go to WP Dashboard >> Settings >> General and replace both URLs to start with
https://
and then press 'Save Changes'. 2. Update the links in your Elementor Template to start with 'https' and then attempt to translate the links again. You might need to remove the old links and re-add them to ensure they are automatically translated. 3. Clear all types of caches (site, server, CDN) and then verify if the issue is resolved. Alternatively, try adding links on a new page and check if the automatic link translation works with the Advanced Translation Editor (ATE).
If this solution does not resolve your issue or seems irrelevant due to updates or different circumstances, 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: You are trying to build a custom PHP language switcher for your site using WPML but are unable to find the example code or documentation previously available. Solution: We recommend ensuring that you are using the latest version of the WPML plugins, specifically version 4.8.1, which includes the latest bug fixes and improvements that might address your issue. You can check and download the latest versions from My Account -> Downloads on the WPML site. If updates are not visible, you may need to click the 'Check for updates' button in the Plugins → Add New Plugin → Commercial tab. Always remember to back up your database before updating.
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 experiencing issues with WP All Import where products are being imported into a different language than the one you set during the import process. Solution: We are aware of this issue and it will be resolved in the next release of the WPML Export & Import plugin. Please keep an eye out for the upcoming release. We will announce it through a blog post and provide detailed documentation on how to implement this. 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 this solution becomes outdated or does not apply to your case, please open a new support ticket. We highly recommend visiting our support forum for further assistance at WPML Support Forum.
Problem: You are experiencing issues with WP All Import where products are being imported into a different language than the one you set during the import process. Solution: We are aware of this issue and it will be resolved in the next release of the WPML Export & Import plugin. Please keep an eye out for the upcoming release. We will announce it through a blog post and provide detailed documentation on how to implement this. 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 this solution becomes outdated or does not apply to your case, please open a new support ticket. We highly recommend visiting our support forum for further assistance at WPML Support Forum.
Problem: The client is unable to assign purchased credits to the correct account and implement the activation key 4d57569036 within WordPress. They have two accounts and are confused about how to manage credits and activation keys between them. Solution: 1. We advised the client to remove the old domain from their account by visiting https://wpml.org/account/ and then generate a new sitekey for the new domain. 2. Replace the sitekey in WordPress by navigating to WP > Plugins > Add New > Commercial Tab. 3. We returned the 12126 credits from the old domain to the client's account. 4. The client should deactivate PAYG if they wish to use their credits first. Once the credits are fully utilized, they can activate PAYG again.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where the cursor jumps to the beginning of the text field in the Advanced Translation Editor after 5 seconds of idle time, making it difficult to use. Solution: We have resolved this issue in the latest versions of WPML and the Advanced Translation Editor. We recommend ensuring that you are using the most recent versions to benefit from the latest bug fixes and improvements.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and verify the version of the permanent fix. Also, confirm that you have installed the latest versions of your themes and plugins. If the problem persists, we highly recommend opening a new support ticket for further assistance. You can do so at WPML support forum.
Problem: You are unable to save the translated slug for a custom post type in French. Despite changing the settings in WPML, the page reloads without saving the changes. Solution: We recommend adjusting the priority with which you register the custom post type. Instead of using a priority of 999, set it to priority 0. This change should resolve the issue with saving the translated slug.
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 here.
Problem: You are unable to translate the custom description of your product categories anymore, and it does not appear on the Advanced Translation Editor (ATE). Solution: First, ensure you have backed up your entire site. Then, we recommend updating your WPML plugin and all related add-ons to the latest versions available. You can find these updates in your WPML account under My Account > Downloads. If the updates are not visible, click the "Check for updates" button in Plugins > Add New Plugin > Commercial on your WordPress dashboard. After updating, if the problem still exists, please use the workaround suggested in this forum post.
Please note that this solution might be outdated or not applicable to your specific case. If the issue persists, 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, do not hesitate to open a new support ticket for further assistance at WPML support forum.
Problem: You are trying to ensure that the frontend and backend of your WordPress site are synchronized, with the language switcher visible and translations properly displayed. You noticed an issue under 'Reading' stating: 'Your home page does not exist or its translation is not published in NL, FR.' However, the home page and its translations are accessible when clicked on. The language switcher is missing, translations are not visible, and posts are not synchronized between languages. Solution: We suspect that the translations of your homepage might still be in Draft status, which could explain why you don’t see the page when logged out. Please try the following steps: 1. Go to Pages → All Pages. 2. Switch the language to Dutch. 3. Edit the homepage using the WordPress editor. 4. Click the Publish button.
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 at WPML support forum for further assistance.
Problem: You are experiencing issues with the WPML CMS Nav plugin on your website after updating to PHP 8.2. The specific problem involves deprecated property creation warnings in the plugin's code, which could affect compatibility with PHP 8.2 and future versions. Solution: We are planning to address this issue in future updates of the WPML CMS Nav plugin. Although these warnings are harmless to your site, you can continue using the workaround previously suggested.
Please note that 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: You are encountering PHP errors related to the WPML CMS Nav plugin and the sitepress-multilingual-cms after updating to the latest version. Solution: We are planning to address these issues in future updates of the WPML CMS Nav plugin. Although these PHP warnings are harmless to your site, you can use a temporary workaround.
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: If you're receiving deprecation warnings like 'Creation of dynamic property wpml_cms_nav_cache::$cache_to_option is deprecated' in your WordPress site using WPML CMS Nav plugin, this might be due to a conflict with PHP versions 8.3 and 8.2. Solution: We recommend setting the debug mode to false to temporarily resolve this issue. You can do this by adding or modifying the following line in your wp-config.php file:
define('WP_DEBUG', false);
Please ensure to back up your site before making this change. This workaround will suppress the warnings until a permanent fix is released in future updates of the WPML CMS Nav plugin.
If this solution does not apply to your case, or if it becomes 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 open a new support ticket at WPML support forum.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
