Problem: Pages built with the Cornerstone page builder and translated are visible in the backend, but the front-end still displays the original content instead of the translation. Solution: If you're experiencing this issue, we recommend you review our documentation on how to translate Cornerstone with WPML. You can find it here: https://wpml.org/documentation/theme-compatibility/xtheme/ Additionally, at the bottom of the documentation, we list all known open issues between Cornerstone and WPML. Please pay special attention to this one: https://wpml.org/errata/cornerstone-translation-is-not-displayed-on-front-end-when-using-ate-or-cte/ We suggest trying the workaround provided and letting us know your results.
If this solution doesn't look relevant to your situation, please open a new support ticket with us for further assistance: WPML Support Forum
Problem: The client was experiencing issues with their theme not applying correctly to the English version of their website when using Elementor. Additionally, there was a problem with the URL slugs of translated archive pages and posts not matching the expected structure.
Solution: Firstly, we suggested increasing the memory limit and ensuring all translations were complete, which resolved the theme application issue. For the URL slug issue, we identified that the client might be using a custom permalink structure like
/actualites/%post_name%
. We advised that WPML cannot translate custom permalink structures and recommended using the "Post Name" structure for posts. If the client uses a static page for posts, WPML will use the page title as the slug for translations.
Problem: The client reported that their website became significantly slower on both the frontend and backend after installing WPML plugins. The issue was confirmed to be resolved by removing specific custom code from the
login.php
page in their custom theme. Solution: We recommend reviewing the custom theme for compatibility with WPML. If you are the theme author or have the ability to modify the theme, please consult our documentation on achieving WPML compatibility for themes and plugins. You can find the best practices and guidelines here:
If this solution does not seem relevant to your situation, or if you need further assistance, please open a new support ticket in our WPML support forum.
Problem: The client needs information on why WPML does not translate their custom post types (CPTs), as they noticed the language flags and status icons are missing. Solution: We recommend configuring the CPT "Services" to be translatable. This can be done by following the steps in our documentation on translating custom posts. After configuring the CPT to be translatable, the client should be able to translate them and add them to the menu.
If this solution does not seem relevant, please open a new support ticket with us for further assistance.
Problem:
The client was trying to translate permalinks slugs for the custom taxonomies set from the Houzez theme but encountered issues where the expected translated slugs were not appearing, and instead, the original language slug was still being used. Additionally, the client faced 404 errors on the translated pages.
Solution:
Note: While using the theme Houzez, make sure that you translate the custom taxonomies that come with the theme only from the page: WPML -> Settings -> Taxonomies Translation section (all the taxonomies that come with the theme are set here). You shouldn't add the strings that end in "_rewrite_base" for translation in the WPML -> String Translation, as it will give error 404 on the translation pages.
For the strings that show on the property page (ex: "Garage size" or "Description"), you should check on WPML -> String Translation and translate those strings from there.
1. We recommended flushing the website's cache and then navigating to WP Admin -> Settings -> Permalinks to click the "Save" button, which flushes the permalinks.
2. We advised checking the documentation for using the Houzez theme with WPML, specifically for translating taxonomies:
3. We instructed the client to add strings for translation from WPML -> String Translations -> Translate texts in admin screens, and to change the string language to "BG" as they are set to English by default.
4. We clarified that the string "features" from the domain "houzez_settings]property_feature_rewrite_base" should not be translated in WPML -> String Translation, as it is should be translated in WPML -> Settings -> Taxonomies Translation section.
5. For the author page translation, we explained that the bio/description found on the author's page in the backend is translatable using WPML -> String Translation -> More options. Also, the theme Houzez has a custom post type "Agents" and offers the possibility to translate it as any other default post type.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
2. This change allows us to scan the theme and register the shortcode call in the String Translation. 3. Change the language of the string to Dutch and create a new pager facet named: resultaat-en, or as the shortcode appears: resultaat_en. 4. Translate the registered string so the English version displays resultaat_en. 5. Apply the same method for other languages by creating a new facet and adding the shortcode of each language under String Translation to the string 'resultaat' of the domain 'harmless-child'.
We ask the client to test this solution and inform us of the results.
Problem: The client has installed the frontnotification bar plugin, but the text in and next to the button (meer info and vacature) is not translated into English. Additionally, clicking on the button does not redirect to the English page. Solution: We translated the URL in the "wpfront-notification-bar" text domain. We recommend checking if the translation works correctly now. If you're experiencing this issue, you can translate the URL by following these steps: 1. Go to the WPML String Translation page. 2. Search for the URL you want to translate. 3. Translate the URL to the desired language. If this solution doesn't look relevant, please open a new support ticket.
Problem: If you're experiencing a broken layout on your translated homepage and a missing footer on all translated pages, it might be due to incorrect taxonomy settings and post slug modifications in the database. Solution: We found that the footer template post slug was incorrectly modified in the database and the taxonomies 'wp_template_part_area' and 'wp_theme' were unlocked, which should not be the case. Here's what we recommend you try: 1. Remove the incorrect terms from the 'icl_translations' table. 2. Re-translate the front-page and footer template parts. 3. Correct the post slug in the 'wp_posts' table by changing it from 'footer-2' back to 'footer'. After these steps, please check your website again to see if the issue is resolved. If this solution doesn't look relevant to your problem, please open a new support ticket with us.
Problem: The client is unable to translate functioning buttons/tabs in the AffiliateWP plugin into Arabic. Solution: We recommend performing a full backup before proceeding with the following steps: 1. Open the file
Problem:
The client wants to place the English language switcher below the search option in the 3rd column of the header on every page of their Divi-themed website.
Solution:
We recommend adding the language switcher to a specific location by using a shortcode. Here are the steps to follow: 1. Enable a custom language switcher and customize it according to your needs. 2. Place the shortcode
Problem: The client changed the footer in the German(default) version, but the changes did not appear correctly in the English translation. Solution: We checked the HTML structure in the translated string from the WPML >> String Translation page and found it was incorrect. We corrected the string and added 'EN' to verify it worked properly. We recommend the client to update the translation from the WPML >> String Translation page by following these steps: 1. Navigate to the WPML >> String Translation page. 2. Use the search function to find the specific string that needs updating. 3. Update the translation accordingly.
Problem: The client is trying to add media images in Dutch for a product, but after saving, the original German media image remains in the gallery instead of the new Dutch one. Solution: 1. Edit the product in the original language. 2. In the right column, locate the Languages block. 3. Uncheck the options to duplicate the media elements. 4. Ensure the custom field for the product gallery is set to NOT be 'Copy'. You can find more information on translating custom fields here. 5. Save the changes. 6. Update the translation. If you plan to use the same number of images for the products in different languages, you can translate the images, which should resolve the issue. For guidance on how to do this correctly, please refer to our documentation on media translation here.
If this solution doesn't look relevant, please open a new support ticket here.
Problem:
The client installed the WPML plugin and noticed that some elements in the header and other sections were not fully translated.
Solution:
Those texts were created in English while the default language of the site is French.
Please try these steps to translate the following elements:
1. The custom links in menu items:
- Go to Appearance > Menus
- Switch the language to English from the top admin bar
- Select the Main menu
- Create a French translation
- Add new custom links for the French pages
2. Any text added to the page with WPbakery builder:
- Edit the French homepage with the page editor
- Edit the English text and replace it with French
- Update the page
- Update the English translation from the back end
Problem: How to translate a static page with projects that is not displayed in the list of all pages. Solution: If you're experiencing issues translating a static page created with the Divi Theme Builder, we recommend translating it as outlined in our documentation on Translating Divi Theme Builder Templates. After updating the content from the front end, make sure to update the translations accordingly. If this solution doesn't seem relevant to your situation, please open a new support ticket with us 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
