Problem: You are trying to translate your custom theme (child of Neve theme) to different languages using .po/.mo files. After adding _e() functions to your strings in the child theme for detection, you now want to use your .po/.mo files to translate in bulk without using the WPML interface on wp-admin. Solution: We recommend using the import feature of WPML for translating your custom theme in bulk. Here are the steps you should follow: 1. Go to your WordPress Dashboard > WPML > String Translation. 2. Scroll down and expand the Import/Export .PO option. 3. Choose your .po file. 4. Select which language it is intended for. 5. Select the proper text domain that you used in your child theme within the
_e()
function. 6. Import the strings.
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 this does not resolve your issue, please open a new support ticket at WPML support forum.
Problem: The client is using WPML with Elementor Pro on a WordPress site and needs to synchronize an updated Elementor structure from the original language (PT-PT) to all existing translations in six languages, without losing the translated text content. The client has 92 locations (custom post type) already translated into six languages. The 'Duplicate' option is not viable as the translated pages already exist, and the Advanced Translation Editor only syncs text strings, not the Elementor container structure. Solution: Initially, the WPML support team suggested that the layout/structure synchronization from the default language should work automatically while the translated texts are handled via the Advanced Translation Editor. However, the client decided to switch to the Classic version of WPML, which resolved the issue. The client is now manually checking each location page to ensure everything is properly set up.
If you're experiencing similar issues, 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 the solution provided here is irrelevant or outdated for your case, please open a new support ticket at WPML support forum.
Problem: The client's website includes "www" in the URL, but the link displayed in the backend does not include "www". Solution: If you're experiencing this issue, we recommend re-registering your website with the correct URL. Here are the steps to follow: 1. Visit https://wpml.org/account/sites and remove your website from the list. 2. Add it again, ensuring to include 'www' in the URL, and copy the newly generated key. 3. In your website's admin panel, navigate to Plugins > Add New > Commercial Tab and click on "Unregister WPML from this site". 4. Register the website again using the key you copied in step #2.
This should resolve the discrepancy in the URL displayed in the backend. Regarding the "Translate Everything Automatically" option, it will automatically translate all translatable content on your website. If you prefer more control over what gets translated, it's best not to activate this option.
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.
Problem: The client is experiencing issues where the SEO meta description is not updating correctly across translated pages using WPML's Advanced Translation Editor (ATE). The client has tried using both ATE and manual 'Edit Page' methods, which has led to inconsistencies and outdated translations in the SEO fields managed by Yoast SEO. Solution: We recommend choosing one consistent method for translations to avoid conflicts and ensure accurate updates: 1. Use only the WPML Translation Editor (ATE) for all translations, or 2. Disable the WPML editor for the affected pages and manage translations manually through the 'Edit Page' option for each language. Additionally, running a reindex from Yoast SEO tools might help, as it can rebuild indexables to reflect the correct metadata. If the issue persists after choosing one method and reindexing, further investigation might be necessary.
Please note that WPML will not automatically update existing translations when changes are made to the default language SEO title or meta description. After making such changes, you need to manually open ATE and update the translations for these fields.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your specific case, we highly recommend opening a new support ticket. Also, 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. For further assistance, please visit our support forum at WPML support forum.
Problem: If you're experiencing issues where not all strings are appearing in the Strings Translation, and specific elements like the hamburger menu in the main navigation remain untranslated, this might be due to the header template not being translated. Solution: First, ensure that the header template is translated. You can do this by accessing the header template in your admin panel and translating it. Here is a general guide on how to translate templates: Translating Your Contents.
If the issue persists, we have implemented a custom code workaround. Add the following code to your functions.php file:
After adding the code, open the translated header template in Elementor and set the correct off-canvas (sidebar) template. This adjustment is necessary for each translated template.
Please note that this solution might become irrelevant due to updates or may not apply 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: If you're experiencing 404 errors on translated pages of your WooCommerce shop built with Elementor and using a rental product plugin, and issues with translated buttons and widgets not functioning correctly, this summary might help. Solution: Firstly, for the 'Rent a bike' button in the header that works in English but not in Dutch or Spanish, ensure that the header was created and translated using Elementor's dynamic links rather than manually adding URLs in the button settings. Manually added links can remain connected to the original language, leading to 404 errors on translated pages. For more information on using dynamic links in Elementor, visit Elementor Dynamic Links.
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 with us for further assistance.
Problem: You are experiencing issues with embedded URLs in your bilingual site's posts being overwritten when saved, despite being manually added to point to the same post in a different language. This issue occurs even though the URLs preview correctly before saving. Solution: To prevent WPML from automatically adjusting and overwriting your manually inserted links, you can exclude specific links from being rewritten by blacklisting certain slugs. This involves adding custom code to your theme's functions.php file to specifically exclude URLs that contain certain patterns, such as those associated with events. Here is an example of how you can implement this:
For more details on linking to pages in a different language and using sticky links, you can visit WPML Sticky Links documentation.
If this solution does not apply to your case, or if it 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. If further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client was unable to use the 'Unregister WPML from this site' option. Solution: We discovered that the client had an outdated version of the WPML String Translation plugin installed. We updated the plugin to the latest version, which automatically unregistered the site. We recommend the client to try registering WPML again.
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 reported issues with their site, including an error related to the 'String Translation table' which interfered with other plugins, notably affecting the display of slides on the homepage and causing abnormalities in the translations area. Solution: We advised the client to update their WPML plugin and its add-ons to resolve the issue. Here are the steps we recommended: 1. Create a backup of the website, preferably testing on a staging version to avoid disruptions. 2. Ensure you are signed in at wpml.org. 3. Visit https://wpml.org/account/downloads/ and click on the Download WPML manually link. 4. Download the latest versions of WPML and its add-ons. 5. Follow the manual installation guide at https://wpml.org/faq/updating-wpml-manually/.
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 issues persist, please open a new support ticket at WPML support forum.
Problem: The client is experiencing 404 errors for translated URLs of a custom post type named 'tdc-review' in Portuguese (pt-br). The original English content exists and is accessible, but the Portuguese translations appear to be missing or disconnected. Solution: 1. Verify if the translated content for the 'tdc-review' custom post type exists in Portuguese. If not, recreate or retranslate the missing reviews. 2. Restore the Portuguese versions of these review posts to ensure the URLs become valid again. 3. Update the sitemap to exclude non-existent translated URLs and reflect only available translations via WPML. 4. Request reindexing in Google Search Console for the affected URLs. Additionally, we recommend checking the guide on translating custom post types with WPML: https://wpml.org/documentation/getting-started-guide/translating-custom-posts/
If this solution does not resolve your issue or 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, visit our support forum: https://wpml.org/forums/forum/english-support/
Problem: You are using WPML with JetEngine custom post types and have several Media/File custom fields such as file, file_2, and r_file. These fields do not appear in the Advanced Translation Editor (ATE) when creating a new translation. They only become visible after manually editing the English translation or after an existing translation job is created. Solution: We recommend using the search option inside the ATE editor to look for those URLs. For guidance on how to translate links, please visit https://wpml.org/faq/how-to-translate-links/. If the fields still do not appear even when searching, it might be necessary for us to further investigate the issue. In such a case, please provide admin access, preferably to a staging site.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client is experiencing an issue with an unaccounted additional draft post that does not appear even after performing several troubleshooting steps including clearing WPML cache, checking the translation queue, and attempting to locate the draft via the "All Languages" view. Solution: We recommended temporarily deactivating WPML to check if the draft post becomes visible. If the draft appears, the client should edit it, then reactivate WPML and resave the content. This step helps in determining if WPML is interfering with the visibility of the draft post.
If this solution does not resolve the issue or seems irrelevant due to updates or different circumstances, 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 with us for further assistance.
Problem: You are experiencing an issue where WPML is overriding the Yoast SEO fields for translated taxonomies, replacing Arabic SEO content with the default English content. This behavior is affecting the Focus keyphrase, Custom SEO title, and Meta description fields, causing a drop in rankings for Arabic pages. You need a solution that allows manual per-language editing of these fields without using WPML String Translation. Solution: This is a know issues which will be solved in a future update for WPML SEO. For now, we recommend downgrading WPML SEO to version 2.1.1 to restore the ability to manually set SEO content per language directly within each taxonomy page. This version does not force the default language values and allows for independent SEO strategies per language. You can find more details and the downgrade guide here: https://wpml.org/errata/wordpress-seo-issues-translating-yoast-seo-term-meta/.
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: If you're experiencing issues with link arrays not showing in the Advanced Translation Screen, particularly with ACF blocks where the same label is used for multiple links or internal URLs are not visible, this summary might help. Solution: 1. When the same label, such as "Learn more", is used across several links in ACF blocks, they might share the same path attribute. WPML cannot register a string with the same path more than once, which results in only the last occurrence being shown in the translation editor. However, the translation will still apply correctly to all occurrences. 2. Internal URLs in blocks are hidden by default as WPML is designed to automatically translate these. If you need to see these URLs, you might be able to find them by searching within the translation editor. 3. For ACF link array fields, we recommend setting them to "translate" rather than "copy". This setting allows for manual editing of the URL if necessary, although WPML can automatically convert internal links.
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.
Problem: You are experiencing an issue where adding or editing content in a secondary language using WPML and the Avada Builder overwrites the content in the default language, and vice versa. Solution: We have identified that the issue arises from using both the WPML Advanced Translation Editor (ATE) and the WordPress/Avada editor simultaneously for translations. To resolve this, you should use only one method for translations. If you choose to continue with the WordPress/Avada editor, you need to disable the Advanced Translation Editor for the specific page or post. You can find instructions on how to do this here: Using Different Translation Editors for Different Pages. To ensure the solution works, please follow these steps: 1. Add the German text to the original (German) page. 2. Update the page. 3. Translate the content using WPML’s Advanced Translation Editor. 4. Check if the issue still occurs.
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 the issue persists, please open 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
