Problem: The client is unable to see the 'Edit translation / Publish this translation' bar in the WPML plugin while using Kubio Builder Pro, preventing them from completing or publishing translations. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML-> Translations 2. Filter the status by 'Pending Review' 3. Select the templates 4. Scroll down to the 'Bulk Action' dropdown menu 5. Select 'Approve' and apply After completing these steps, the templates should be published.
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 wants to set up a subdomain per language for their site and is following the WPML documentation on how to use WPML with different domains per language. However, they are facing issues with the DNS settings not working correctly even after setting them up as per the documentation. Solution: We recommend checking the setup of the subdomains to ensure they correctly display the content from the main site. Once this is verified, you should add these subdomains in the WPML settings area. If the subdomains are still not showing the content correctly, it might be a configuration issue on the hosting or domain panel side. In this case, we advise contacting your hosting/domain provider for further assistance and sharing the WPML documentation with them: https://wpml.org/documentation/getting-started-guide/language-setup/language-url-options/how-to-use-wpml-with-different-domains-per-language/.
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 for personalized assistance at WPML support forum.
Problem: User is experiencing a 404 error when creating a new product in a secondary language on their WordPress site, it might be due to an issue with WPML settings or permalink configuration. Solution: We recommend you follow these steps after backing up your site: 1) Go to WPML>>Settings>>Slug translations. 2) Disable the
Translate custom post and taxonomy base slugs (via WPML String Translation)
option and save the changes. 3) Clear all types of caches. 4) Navigate to Settings>>Permalinks. 5) Resave the settings.
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 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 using WP All Import to upload listings directly to the second language on your site, but the translated listings are going into the English listing section. Solution: It is not possible to directly import translated listings into the second language in WPML using a single import. To properly import listings into multiple languages, including already translated ones, you will need to perform two separate imports: 1. First Import: Import the listings in the default language (English, in this case). 2. Second Import: Import the listings in the second language. For this to work, you must add a unique identifier to your spreadsheet. This identifier will allow WPML and WP All Import to correctly link the translated listings to the original ones. For more details, please refer to the following documentation:
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. If you still need assistance, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues where slider images are partly missing only in the French language on your translated pages, and you've noticed an unknown widget in the WPML Translation Management, here's what we recommend. Solution: For the missing images in the French translation: 1. Edit the page in the English language and make a small change to the content. 2. Ensure the following options are enabled in the WPML settings: - Duplicate uploaded media to translations - Duplicate featured image to translations 3. Save the changes and update the translation. 4. If the issue persists, go to WPML > Settings > Media Translation section, run the set language information and duplication steps, then send the page and all attached images to translation from Translation Management.
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: The client was experiencing an issue where the English version of a page was displaying content in French, despite being fully translated. This problem was linked to the use of emojis in the content, which is a known issue with WPML and page builders.
If these solutions do not resolve your issue, or if they become outdated, we highly recommend checking related known issues (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.
Problem: The client is experiencing issues with WPML that prevent posting new blog articles or editing existing content. The WPML Translation Manager is not working properly, not saving entries, losing input, messing up links, and showing multiple inconsistencies. The translation editor does not display all the original language content, and saved content is disappearing.
Solution: We recommend switching to the previous version of the Advanced Translation Editor (ATE Gen2). Here are the steps to do this: - Open a page or post for translation in ATE. - Click the gear/settings icon in the top right corner of the editor. - From the settings popup, select "Use the previous version of Advanced Translation Editor". - Fill in the feedback box with any text and submit. This will reload the editor with the previous interface and should display the incomplete content that wasn't visible in the new interface, allowing you to complete the translation.
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 problems persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue where search results in their website's header, powered by Buddyboss, are not displayed in the main language (English), but work fine in French. The issue is linked to the 'smart-opengraph' plugin, which affects the display of search results in the translated language. Solution: If the 'smart-opengraph' plugin is essential for the website, we recommend modifying its function to correctly handle search queries in different languages. Here's how you can adjust the code:
static function compileOpenGraphTags() {<br /> if ( ! $_GET['s'] ) { //added check condition<br /> global $post;<br /> // Your logic here<br /> return $aVal;<br /> }<br />} //added end bracket
Please note that the plugin might have hardcoded values that could lead to further issues, and it uses a logic that incorrectly retrieves page IDs, causing it to fail in translated versions. We also suggest contacting the plugin developers to consider joining the Go Global Program for better multilingual support.
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 for further assistance.
Problem: The client was unable to see the translated Divi footer in Dutch and English on their website, despite translating it via WPML's String Translation. The footer remained in French, and the content appeared empty under WPML → Translation Management. Solution: We advised the client to increase the WP_MEMORY_LIMIT to at least 256M, as the initial setting was too low (40M). Instructions for increasing this limit can be found here: https://wpml.org/faq/checklist-before-opening-a-ticket-in-wpml-support/#how-to-increase-your-sites-memory-limit. Additionally, we located the specific footer template and directed the client to use the translation editor accessible via the plus sign in the WPML Translation Management dashboard. This allowed the client to manually translate the footer into Dutch and English.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we recommend opening a new support ticket. We also highly suggest 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 https://wpml.org/forums/forum/english-support/.
Problem: You are using WPML to translate content from German to French, and some images are not displaying on the translated pages. The issue is due to broken image links where the 'uploads' folder is missing from the URL. Solution: We recommend checking the format of your image links to ensure they include the 'uploads' folder. This problem might be related to a known issue with SVG support when WPML Media is activated, which strips the 'uploads' folder from the SVG image URL. For a workaround, please visit the following documentation: WPML Errata on SVG Support.
If this solution does not apply because it is 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 issues persist, please open a new support ticket at WPML Support Forum.
Problem: You are experiencing a persistent staging website notice after pushing changes from development to live. Solution: If you're facing this issue, we recommend following these steps: 1) Ensure you back up your database. 2) Navigate to WPML → Support and click on the Troubleshooting link. 3) On the WPML Troubleshooting page, click the Force-enable WPML’s Advanced Translation Editor button.
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: When you make changes to a page in Elementor, these changes are not synchronized with the translated page. Newly added text appears in the WPML Editor for translation, but does not show up on the frontend. The only workaround is to switch to the WordPress Editor, change the language, and then edit the page with Elementor. Even though the element is present when opening the translation in Elementor, you must resave the page for the changes to take effect on the frontend. Solution: We have identified that the issue is due to the "Element Caching" beta feature in Elementor. This feature is currently not supported by WPML. To resolve this issue, we recommend you deactivate the "Element Caching" option temporarily in Elementor → Settings → Features.
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 problem persists, please open a new support ticket.
Problem: The client reported an issue where a translated media photo was not appearing in the English version of their website. The photo was assigned in media translation, but it did not display on the frontend.
Solution: We resolved the issue through several steps: 1. We recommended registering custom Elementor Widgets for translation using an XML file. You can read our tutorial here: https://wpml.org/documentation/support/multilingual-tools/registering-custom-elementor-widgets-for-translation/ 2. The issue of the image not appearing was because it was added as a background but the slide had no content. Moving the image inside the content resolved the issue. 3. When translating the page, it is necessary to search for "http" to find and manually translate links such as image links.
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 experiencing issues with a site built using Kadence and Beaver Builder, where the translation lost text formatting, resulting in a block of text instead of paragraphs. Additionally, the mobile CTA button from Kadence Conversions is displayed on all screen sizes, not just on mobile, and editing the French Conversion version causes a 500 Internal Server error. Solution: For the issue of lost text formatting, we recommend disabling the option "I prefer bigger segments" in the Advanced Translation Editor as it might be causing the line breaks to be ignored. You can find more details and workarounds on this issue at https://wpml.org/errata/line-breaks-are-ignored-when-using-the-advanced-translation-edior/. Regarding the mobile CTA button displaying on all screen sizes, please ensure that Kadence Conversions is compatible with WPML and check any specific settings within Kadence Conversions that might be affecting visibility across different devices.
If these solutions do not resolve your issues or if the information provided 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 do not hesitate to open a new support ticket at WPML support forum.
Problem: The client is trying to translate a page from French to English using both automatic translation and human reviewing, but the English page is not visible after translation. Instead, the page remains in French. Additionally, the 'automatic translation' button on individual segments is not functioning. Solution: Ensure you have selected the 'Translate What You Choose' option in WPML>>Settings>>Translation Mode. Follow these steps: 1) Open the Page for editing in the default language. 2) Make a minor change and update it. 3) Go to WPML>>Translation Management Dashboard. 4) Choose the Page you want to translate or update the existing translations. 5) Send it to the Translation Basket. 6) Go to WPML>>Translation Management>>Translation Basket. 7) Send it for translation, selecting yourself as the translator. 8) Go to WPML>>Translations queue and click the 'Translate' button. For more detailed instructions, refer to this documentation. If the issue persists, please provide screenshots for a better understanding, especially regarding why the 'automatic translation' button is not working on individual segments.
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 needed, please open a new support ticket for further assistance.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
