Problem: The client needs to filter posts in the WPML Translation Dashboard to show only those that are not translated and not duplicated, excluding posts where the translation process has started. Additionally, the client wants to duplicate all published posts of a particular type that do not have any duplicated pages for other languages or where the translation is not started. Solution: To filter posts as required: 1. Go to WPML → Translation Dashboard. 2. In the filter options at the top, locate the Translation status dropdown. 3. Select Not translated from the options. This will display only the posts that are completely untranslated and not duplicated.
To duplicate posts: 1. In the Translation Dashboard, select the Type of post you want to duplicate (e.g., 'Post', 'Page', or a specific Custom Post Type). 2. For the Status filter, choose Published. 3. For the Translation status filter, select Not translated. 4. Select all the posts you wish to duplicate by checking the box next to the Title column header. 5. Scroll down and use the Translate selected content section to duplicate the selected posts.
For automation via a custom script, WPML's Coding API provides hooks such as
apply_filters('wpml_post_duplicates', $post_id)
and
do_action('wpml_make_post_duplicates', $post_id)
to detect and create duplicates programmatically. However, this requires custom development outside the standard support services. More details and examples are available at WPML Coding API documentation.
If this solution does not resolve your issue or seems outdated, 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. If further assistance is needed, we recommend opening a new support ticket or contacting one of our recommended contractors at WPML contractors.
Problem:
The website's admin was showing an "Expired account" message, even though the account was active; Solution:
In these cases, it's best to reach out directly to hello@wpml.org
Problem: The client is experiencing an issue where an unwanted language code prefix (e.g., 'DE', 'FR') is automatically added before the 'FREE SHIPPING OVER' text in the announcement bar on non-English pages of their multilingual website. The English version displays correctly without any prefix. Solution: 1. We recommended inspecting the Elementor templates by navigating to Templates → Theme Builder/Saved Templates to locate and edit the announcement bar widget. 2. Check the widget’s 'Advanced' settings, specifically the 'Before'/'After' fields, for any dynamic tags or shortcodes that might be adding the language codes, and remove any found prefixes. 3. Update the template after making these changes. 4. Search for related strings in WPML → String Translation and make necessary edits if the prefix is present in the translations. 5. If dynamic tags or custom PHP hooks in the child theme are conditionally generating the prefix, these should be reviewed and adjusted as needed.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: After upgrading to Divi5, the client experienced issues with their multilingual e-commerce site. Specifically, the English version of the homepage and product page were not displaying correctly, showing only the header and footer. Additionally, any changes made to already translated pages caused them to stop displaying, and the translated footer was not visible across all pages. Solution: We recommended the following steps to address the translation issues: 1. Edit the page in the default language. 2. Make a minor edit and update it. 3. Check the translated page on the front end. We also set the
_et_pb_divi5
custom field to be copied, ensuring that the modules are copied to the English version of the pages.
Please note that this solution might be outdated or not applicable to your specific case. We 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 the issue persists, please open a new support ticket.
Problem: If you're experiencing issues with not finding the template part or footer template on your multilingual site, Solution: We recommend checking if an empty footer has been set for the entire site. In a recent case, we found that removing the empty footer setting resolved the issue, and the correct footer appeared in all languages. Please verify on your site if this solution applies.
Keep in mind 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 problem persists, please open a new support ticket.
Problem: The client was experiencing issues with forms created in Bricks Builder on pages translated with WPML. While forms worked correctly in the original language, submissions from translated versions were not being sent, and emails did not arrive at the specified address. Additionally, translated pages displayed a 404 error or redirected to the homepage. Solution: The issue was resolved by updating the GUIDs in the database after a site migration. The client updated the GUID fields correctly, which fixed the form functionality and email delivery on the translated pages. Regarding the WPML Troubleshooting message indicating 'Alias domains to https://bws-windows.com domain: * https://bws-windows.com', it is not a concern if the forms are functioning properly and can be ignored.
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. Should you need further assistance, please open a new support ticket at WPML support forum.
Problem: The client is unable to use their password for their WPML account and is unsure why their old password is missing. Solution: If you're experiencing issues with your WPML account password, we recommend the following steps: 1. Disconnect the social media account from your WPML profile. 2. Log out of your WPML account. 3. Visit https://wpml.org/account and click the Login button. 4. Use the 'Forgot password' option to generate a new password. After completing these steps, you should be able to log in with your email and password and change the password later without any issues. If you prefer to continue using social media login, you can dismiss the warning message; it will not affect your access or account usage.
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.
Problem: The client is experiencing issues with media translation not working within the Unlimited Element Carousel Widget using the WPML plugin. They are seeking a way to manage media names for different languages and ensure that the media translates correctly across different language versions of the site.
Solution: 1. Install and Activate WPML Media Translation: Ensure that the WPML Media Translation add-on is installed and activated. 2. Enable Automatic Media Text Translation: Go to WPML → Settings, scroll to the Media Translation section, and turn on 'Automatically detect best options for translating image texts'. 3. Translate the Page with the Carousel: Use the WPML Translation Dashboard to send the page containing the carousel for translation. 4. Replace Media in WPML Media Translation: Assign different images for each language by using the WPML Media Translation tool. 5. Re-save Your Elementor Page: After updating media translations, re-save the original page in Elementor to refresh content and apply new translation settings.
If these steps do not resolve the issue, or if the solution seems 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: The client reported issues with the language switcher on their website, where they often had to click twice on the French (FR) icon for it to switch languages, and sometimes it would revert back to English (EN) when navigating to another page. Solution: We recommended enabling the footer language switcher as a potential solution to improve the responsiveness and accuracy of language switching. Detailed guidance on setting up the language switcher can be found here: Language Switcher Options. Additionally, we suggested testing the language switcher functionality in different browsers to determine if the issue might be browser-related.
If this solution does not resolve the 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. Should further assistance be needed, please open a new support ticket at WPML Support Forum.
Problem:
When saving Automatic Translation settings in WPML (and other plugin settings like Hostinger Tools), client received a "Some error occurred" message. The settings were not being saved.
Solution:
During the investigation, I found that .htaccess file contained a custom "Trailing Slash Redirect" rule that was interfering with WordPress REST API requests.
This rule was forcing all URLs to end with a trailing slash (/), which caused:
- REST API POST requests (e.g., /wp-json/wpml/v1/save-automatic-translation-settings) to be redirected with a 301 status to the same URL with a trailing slash
- The browser converted the POST request to a GET request during the redirect (standard HTTP behavior)
- The REST API endpoint returned a 404 error because it doesn't accept GET requests at that URL
This affected all plugins using the WordPress REST API, not just WPML.
I modified the existing trailing slash redirect rule in .htaccess file to exclude REST API paths (/wp-json/).
Problem: After setting up WPML on the production site, the client encountered a 404 error on the homepage and could not access any pages, whether draft or published. The pages section showed the correct number of pages but did not display them. Solution: We installed a local copy of the client's site and noticed that all pages were in the same language. We recommended re-importing the pages and translations following the guide on WPML export and import. After applying troubleshooting steps, we were able to retrieve the pages, posts, and products on the client's site.
If this solution does not resolve your issue or seems outdated, 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. If the problem persists, we highly recommend opening a new support ticket at WPML support forum.
Problem: The client reported a critical error on their site, experiencing a PHP 8.3 infinite recursion issue leading to a 503 error. This was traced back to a potential bug in the WPML plugin with the newer WordPress version. Solution: 1. We asked the client to check if the issue persists after following the steps described on the erratum page for PHP 8.3.x errors, which can be found here: PHP 8.3.x Fatal Error. 2. We requested a detailed description of the issue, including steps to reproduce it and any error messages, to better understand the problem. 3. We asked for access credentials to the site to investigate the configuration and reproduce the issue. 4. We inquired if the client would prefer to continue troubleshooting the issue or remain on the older WordPress version (v6.8.9) that did not exhibit the problem.
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 WPML 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 experiencing an issue where the notification 'Your default language, Italian, must be mapped to a supported language in order to use automatic translation' kept reappearing even after mapping the language and saving the settings. This issue persisted despite the WP memory limit being set to 512MB and clearing the WPML cache. Solution: We recommended the following steps to resolve the issue: 1. Navigate to WPML → Settings → Translation Engines settings and ensure at least one translation engine is activated. 2. Save the changes and check if the error persists. If the problem continues, it might be due to outdated information or a unique case not covered by this solution. 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 remains unresolved, please open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing an issue where your WPML account shows a message that your email does not have a usable password and your account might have been reset, even though you did not initiate any reset, follow the steps below for a solution. Solution: 1. Disconnect any social media accounts linked to your WPML profile. 2. Log out of your WPML account. 3. Visit https://wpml.org/account and click the Login button. 4. Use the 'Forgot password' option to generate a new password. After completing these steps, you should be able to log in with your email and new password, and you can change the password later if needed.
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 problem persists, please open a new support ticket.
Problem: 1) The client receives an error indicating that WPML has detected a change in the site's URL after moving from a development subdomain to a new domain, despite updating the WPML license key. 2) Errors in Language settings prevent automatic translation because languages are not mapped to supported languages. Solution: 1) To resolve the URL change issue, navigate to WPML → Translation Dashboard and select the appropriate action on the migration banner. For more details, visit Using Advanced Translation Editor when you move or use a copy of your site. 2) After addressing the first issue, if language setting errors persist, go to WPML → Settings and ensure that a translation engine is selected.
If these solutions do not apply to your situation or seem 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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
