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 through our support forum.
Problem: If you're unable to translate the slugs of pages that were already translated before activating the slug translation option in WPML, this summary is for you. Solution: We recommend updating the translation of the page to include the slug in the WPML translation editor. Here's how you can do it: 1. Slightly modify the original page and save it. 2. Navigate to the WPML translation editor. 3. Look for the slug field and update it accordingly. Please ensure to backup your database before proceeding with these steps.
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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing an issue where after editing the formatting of a translated post, the translation disappears and cannot be added back. The translation saves in the advanced editor, but does not appear in the dashboard. Solution: We recommend the following steps: 1. Go to the top right corner of the translation editor. 2. Click the gear icon. 3. Enable the option "Use the previous version of the Advanced Translation Editor." 4. Refresh the page. Next, follow these steps: 1. Navigate to your Dashboard > Pages. 2. Open the edit screen of the original page. Look for a pencil/circle/gear icon in the sidebar options under the "Languages" section. 3. Make a small change, such as adding an extra blank space at the end of a sentence or paragraph. 4. Save it. You should now see a circular arrow beside the second language's links, indicating that an update is required. 5. Edit the translation again and ensure it is saved up to 100% translated. If this solution does not resolve your issue or seems irrelevant due to being 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: You are trying to configure language-specific sitemaps using All-in-One SEO for your site, but the current sitemap includes links to pages for both English and French languages, and you want to create separate sitemaps for each language. Solution: Currently, it is not possible to separate the generated sitemap file as this is how the All-in-One SEO plugin operates. We recommend using WPML's hreflang tags to inform search engines about the default language of the page’s content and the translations available in different languages.
If this solution does not apply to your case because it might be outdated or not suitable for your specific situation, 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.
Problem: When using the Broadcast plugin to copy menus from one site to another, the copied menu is not visible on the child site, likely because the menu and its items do not have an assigned language. Solution: Currently, there is no available hook in WPML to programmatically set the language for menus and menu items copied using the Broadcast plugin. We recommend contacting the developers of the Broadcast plugin to discuss making their plugin compatible with WPML. They can also join our Go Global program where we assist developers in making their plugins compatible with WPML.
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.
Problem: You are unable to complete the home page translation using the WPML Translation Editor. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the page in the default language and make a small change, then update it. 2. Access the translation again in the WPML Translation Editor and try to save it to 100%.
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 is experiencing an issue where a SQL query sorts posts by a custom meta field 'trainings_display_date_start' on the homepage. This works correctly on the non-translated (English) page, but not on the translated page, resulting in no posts being returned. Solution: 1. Ensure that the 'trainings_display_date_start' is copied over to the translated posts so there is meta data to sort by. 2. Include a meta query that returns only posts with a start date and then sort by that start date. 3. Verify that the posts are translated and published in the second language. 4. Test the issue with the WP default theme and only WPML plugins enabled to see if the issue is caused by something else.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your 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 contact our support forum at WPML support forum.
Problem: The client is experiencing issues with WPML on their production site where only English URLs are opening correctly, and the language switcher only displays the default English language. Solution: We recommended checking if the content on the pages has been translated and published. In the WordPress backend under 'Pages', the client should look for translation status icons next to the default language pages: - A pencil icon indicates that the translation is published. - An eye icon suggests the translation needs review and acceptance before publishing. - A gear icon shows the translation is not saved, and the client should ensure it's 100% complete at the bottom and then try to resave. - A circled arrows sync icon means the main language content has been updated, and the translation needs resaving.
If these steps do not resolve the issue, or if the solution seems outdated or irrelevant to your specific case, please visit our known issues page, verify you have the latest versions of themes and plugins, and consider opening a new support ticket for further assistance.
Problem: You are unable to transfer credits because the original site does not exist. Solution: If you're experiencing this issue, we recommend logging into your WPML.org account. Once logged in, check if the old site URL is listed. If it is, you should see a blue button to add or remove credits from that site. Please try this and let us know how it goes.
If this solution does not apply because it might be outdated or not relevant 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 you still need assistance, please open a new support ticket.
Problem: You are trying to register your site as a production site with WPML, but encounter an error stating 'Unable to register: Site key not matching'. You have already tried deleting the old key and adding a new one, but the issue persists. Solution: The issue might be due to the URL used during the registration not matching the exact URL of your site. Please ensure that you include 'www' in your site's URL if it is part of the correct address. Follow these steps: 1. Visit https://wpml.org/account/sites 2. Remove the current key. 3. Generate a new key for the exact URL, including 'www'.
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 problems persist, please open a new support ticket with us for further assistance.
Problem: The client has a WordPress site with Dutch as the default language and English as a secondary language. They want to display the Dutch menu on English pages or add Dutch pages to the English menu in Appearance -> Menus. However, when switching to English, the system seeks the translation of the menu, and the client struggles with adding Dutch pages to the English menu.
Solution: We recommend setting your pages and posts to "Translatable - use translation if available or fallback to default language". Here are the steps to achieve this: 1. Go to WPML -> Settings and set pages and posts to "Translatable - use translation if available or fallback to default language". 2. Navigate to Appearance -> Menus, switch to the translated menu, and delete it. 3. Ensure that the default language menu is assigned as the main menu. 4. Check the front end to see if it displays correctly in the translations. If this does not resolve the issue, consider duplicating the pages in bulk. You can do this by going to WPML -> Translation Management, selecting the pages you need, and clicking on "Duplicate".
If these solutions do not apply to your situation, or if they become 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 needed to delete the Spanish and Danish translations of a page originally created in English. Solution: We recommended the following steps to delete the translations: 1. Make a backup of the site as a precaution. 2. Navigate to the pages listing screen and switch to either Spanish or Danish using the admin top bar. 3. Locate the translated page and send it to the trash. 4. Ensure to permanently delete the page from the trash to completely remove the translation. Alternatively, you can edit the page in the main language and switch to the secondary language directly on that screen to send it to the trash. Remember, it is crucial to delete the page from the trash as well.
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client is noticing an extra URL parameter (?_gl=) appended to your domain name on the home page and is wondering if it can be changed or removed. Solution: We have identified that the parameter (?_gl=1%2A4osfvv%2A_ga**) originates from Google Analytics and does not affect your site's functionality. For more information, please refer to the following Google documentation: Google Analytics Documentation. Additionally, you can check related issues and solutions on our forum:
If this solution is outdated or does not apply 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. Should you need further assistance, please open a new support ticket at WPML Support Forum.
Problem: The client is using Stripe to accept payments and has their store set up in USD. They need to use EUR to activate payment methods like Klarna. Although customers can switch to EUR, the client cannot accept payments using EUR with Stripe and Klarna because Klarna requires the store to be listed in EUR. Solution: We recommend setting the default currency of the store to EUR and the secondary currency to USD. This adjustment is necessary because Klarna requires EUR as the default currency to function properly. If you're experiencing this issue, we suggest making this change to enable Klarna payments through Stripe.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If further assistance is needed, we highly recommend opening a new support ticket with us here.
Problem: The client was setting up different domains for each language on their site using WPML but encountered issues where the different domain per language setup was not working. Solution: First, we recommended resaving the WPML>>Languages>>Language URL format settings and the Settings>>Permalinks. The client was also advised to clear all types of caches to see if the issue was resolved. Additionally, to verify the DNS settings, we suggested uploading a text file named WPMLTest.txt to the main domain's root directory and checking its accessibility from all the intended domains.WPML_LS_Menu_ItemUpon further investigation, it was discovered that the subdomain was not set to the actual document root (/public_html). Correcting this setting resolved the issue.
If this solution does not apply to your case, 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 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
