Problem: The client's bilingual Greek/English website was displaying Greek translations on English pages unexpectedly. Solution: We resolved the issue by translating the strings using the WPML String Translation. If you're experiencing similar problems, we recommend you try the following steps: 1. Navigate to the WPML String Translation page on your site. 2. Translate the strings that are displaying incorrectly.
Problem: The client was facing an issue where internal links on their page were not being translated automatically on their live site, despite the SQL code working on their stage site. Solution: We investigated the issue and initially updated the Site URL and WordPress URL in the database to include HTTPS, which did not resolve the problem. Further analysis indicated that a specific script in the header file was causing the issue. We recommend the following steps: 1. Temporarily disable the problematic script. 2. Make a small change to the page or products where the issue was occurring and save the changes. 3. Complete the translation update. 4. Re-enable the script. This process should trigger a refresh of backend processes and result in the correct translation of links. If the links are still not being translated correctly, please open a new support ticket with us.
Problem: If you're experiencing issues with a translated header appearing incorrectly on your .com/de pages, or if you're facing a 404 error after translating your main pages, we have some recommendations.
Solution: For the header translation issue: 1. Switch to the secondary language of your site from the WordPress admin. 2. Navigate to Template > Saved Templates and locate the translated header template. 3. Open the template in the WordPress editor and note the ID in the Browser URL bar. 4. Go to "WPML > String Translation" and click on "Translate texts in admin screens »" at the bottom. 5. Search for "wpda" and find "wpda-builder-settings". Add it to string translation. 6. In the String Translation section, click on the "+" icon under the German flag. 7. Copy the English configuration content and paste it into the German translation field, replacing the "current_header" value with the ID of the translated header.
For the 404 error on translated pages: 1. Go to "Rank Math > Redirections". 2. Remove any redirections set for the link that is causing the 404 error.
Problem: The client reported that the language switcher was missing on both English and French search URLs, despite having added location translation and post translation.
Solution: We noticed that the search URLs were using a different template from the homepage. The homepage had a breadcrumb coming from an Elementor shortcode with a news-filter, whereas the search pages had a WooCommerce Breadcrumb. Since the client is using Elementor PRO, we advised ensuring that the same shortcode used on the homepage is also applied to the search/archive template.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us.
Problem: If you're trying to translate the label of a Custom Post Type (CPT) created with the JetEngine plugin for a multilanguage site and can't find where to do it. Solution: 1. Go to WPML > Settings and under 'Post Type Translation', set the translation preference for your Post Type to "Translatable". 2. Navigate to WPML > Theme and Plugins Localization. 3. Select the JetEngine plugin and scan for strings within the plugin. 4. Once the scan is complete, move to WPML > String Translation. 5. Search for the name of your CPT. 6. If the name appears, click on the "+" icon next to it to add a translation.
If the name doesn't appear in the String Translation, it might be registered as an Admin string. In this case, you need to register the string for translation by following the instructions in our guide:
Problem: The client needed to update the header with custom mobile numbers for each language.
Solution: We provided a step-by-step guide to find and translate the strings for the header: 1. Navigate to WPML-> Theme and plugins localization, select the theme/plugin, and scan. 2. Go to WPML-> String Translation. 3. Click on the "Translate texts in admin screens »" link. 4. Search for the needed strings. 5. Select the strings. 6. Click on the "Add to String Translation" button. 7. Click on the "« Return to String Translation" link. 8. Translate the strings, clear the cache, and check the front end.
Problem: The client is manually translating their website from English to Spanish and is encountering an issue where the Services pages are not being translated correctly. When updating the Spanish content on these pages, the English pages are also being updated with the Spanish content. Solution: 1) We recommend backing up the site first. 2) Navigate to WPML >> Settings >> Post Types Translation. 3) Set the 'Services(pxl-service)' to Translatable - only show translated items. 4) Save the changes. 5) Go to Our Services >> All Our Services and translate the posts. For more detailed guidance, refer to our documentation on translating custom posts.
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us here.
Problem: The client's website was experiencing an issue where the translation update service was running continuously, displaying the message: 'Updating affected posts for changes in translatable fields...'. Solution: We recommended checking our errata page for a known issue that might be related to this problem. The client should follow the workaround suggested there after ensuring a full site backup. The specific steps taken by the client to resolve the issue by truncate the
wp_icl_background_task
table in the database, which successfully fixed the error.
Problem: The client is unable to get translations from English to Swedish for pages automatically created by a plugin on their Swedish site. The pages are marked as Swedish even though they are in English, and the client needs to change the source language from Swedish to English to enable automatic translation. Solution: We recommend following the steps outlined in our documentation to link already translated pages: https://wpml.org/faq/how-to-link-already-translated-pages/. 1. Go to the page you want to change the source language for. 2. Select "none" in the 'This is a translation of...' field. Here is an image for reference: https://snipboard.io/bHPCAq.jpg. 3. Click the 'connect with translations' button. 4. Choose the Swedish page and set English as the new original language when prompted. We have also created a video tutorial to help you through these steps: https://www.loom.com/share/d2879ba4cba244398bc9f977fcae1a66. If you follow these steps and still experience issues, or if this solution doesn't seem relevant to your situation, please open a new support ticket with us.
Problem: The client is experiencing an issue where the same footer is showing in both English and Hebrew on their Elementor-based website, despite following the documentation.
Solution: We resolved the issue by taking the following steps: 1. We activated the WPML String Translation plugin. 2. We opened the default language Footer template in Edit mode and noticed that the English footer was set as a Duplicate. 3. We then opened the secondary language footer in Edit mode and clicked the
Translate Independently
button. 4. We made a minor change in the default language footer title, opened the translated footer in the WPML Translation Editor, and translated a few strings.
We recommend that the client translates the complete footer into the English language to resolve the issue.
Problem: The client is having an issue related to ACF where he uses ACF Shortcodes to display ACF Fields in Elementor and the fields were not translated.
As the shortcodes also included raw text this raw text was showing on the translated content.
Solution:
We were not able to identify an issue on this ticket, apart from expected behavior, as the affected ACF Fields and their shortcodes were not yet translated.
If you're experiencing similar issues with Dynamic Visibility and ACF Fields not behaving as expected in translated content, here are the steps you can take: - Ensure that ACF Fields are filled out, as empty fields can cause visibility issues. - If changes do not reflect immediately, allow some time as it might take a while for the system to update. - Check the page URL settings and ensure they are set to 'copy from the primary language' if issues persist.
If this solution doesn't seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
Problem:
The client is making a change to the default language widget and is confused why he has to update/add translation each time.
Solution:
Each time you make a change to the default language widget it is expected that you also need to add/update the translation of the widget via WPML String translation to keep the content in sync.
Otherwise, you can manually create different widgets per language.
Problem: The client's website isn't loading translated Elementor loops after updating to the latest versions. The 'load more' button does not work, and the console shows a 'TypeError: Cannot read properties of null (reading 'getAttribute')' error.
Solution: We noticed that the pagination page number is appending after the language parameter in the URL, which should ideally appear before the language parameter. This is likely causing the pagination malfunction in different languages.
1. We recommend changing the "Language URL format" by navigating to "WPML > Languages" in the WordPress dashboard and selecting "Different languages in directories".
2. If using the Yoast SEO plugin, ensure it is updated to the latest version, specifically later than 20.3, to avoid similar issues. For more information, please refer to the Errata page.
If this solution doesn't seem relevant or if you continue to experience issues, please open a new support ticket with us for further assistance.
Problem: The client is unable to confirm some translations after automatically translating Elementor templates. Solution: We recommend increasing the WordPress Memory Limit to 256M, as the current setting is below the minimum required by WPML. To do this, add the following code to the
wp-config.php
file:
define('WP_MEMORY_LIMIT', '256M');
Place it just before the line:
/* That's all, stop editing! Happy blogging. */
After making this change, check the current settings at WPML > Support > WordPress and attempt the translation again. If the hosting provider has set limitations, contact them to request an increase in the memory limit. For optimal performance, higher values than 256M are beneficial. For more information on WPML's minimum requirements, please visit the documentation: WPML Minimum Requirements. If the issue persists after following these steps, please open a new support ticket with us.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
