Problem: The client is using the Divi theme along with a plugin called "Divi contact form helper" to add more options to the contact form module. However, when the "multilingual languages" option is enabled in the plugin, the contents of the contact form, specifically the "choose files/upload files" button, are not being translated into French.
Solution: Firstly, we recommend increasing the WordPress Memory Limit as the current limit is below the WPML minimum requirements. You can do this by adding the following code to your wp-config.php file, just before the /* That’s all, stop editing! Happy publishing. */ line:
Next, follow these steps: 1. Disable the Multilingual language option in the "Divi contact form" plugin settings. 2. Navigate to WPML-> Theme and plugins localization, select the plugin, and scan it. 3. Go to WPML-> String Translation. 4. Click on the "Translate texts in admin screens »" link. 5. Search for the needed strings. 6. Select the strings and 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.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket: WPML support forum.
Problem: The client is receiving notifications from Wordfence about obsolete WPML plugins that have not been updated for 3-4 years and is wondering if they can disable these plugins without affecting site functionality or if there are plans to update them for compatibility with the latest version of WordPress. Solution: We assure the client that the plugins in question are still safe to use despite not being updated, as there have been no changes to their code. If the client is using the features provided by these plugins with their current theme, we recommend keeping them. For more information, we provide documentation links:
Problem: The client is using WPML's auto-translation feature with a site built using Advanced Custom Fields (ACF) and flexible content. They have encountered an issue where internal links within an ACF WYSIWYG field inside a flexible content field are not being translated to the target language (French) even after using the 'Translate Link Targets' feature in WPML.
Solution: We recommend ensuring that the custom fields are set with the correct translation settings under WPML > Settings > Custom Fields Translation.
For the links that are not automatically translated, you will need to manually search for and translate them within the page or post itself, as they do not appear by default in the translation editor. For a more detailed explanation on how to translate links manually, please refer to our documentation:
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.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
