Problem: The client was unable to confirm the installation of WPML on a new website using the provided installation guide. Solution: We resolved the issue by manually reinstalling WPML with the following steps: 1. Navigate to wp-admin -> Plugins, disable and delete all WPML plugins listed. 2. Download a fresh version of the WPML plugins from the downloads page. 3. Go to Plugins -> Add New -> Upload. 4. Choose the previously downloaded plugins, install, and activate them. This process is necessary as something might have been corrupted during the automatic installation.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client has a redirect URL on their site that is hidden from the sitemap.xml, but the hreflang is still referencing this redirect URL on a translated page. This causes an "incorrect hreflang link" error in SEMRush because it references a redirect URL. Solution: We do not provide functionality to directly change hreflang links for redirect URLs. We recommend contacting the support team of the SEO plugin in use to see if they can offer a solution for this specific need. Additionally, for custom solutions, we suggest reaching out to our specialized contractors at https://wpml.org/contractors/.
If this solution does not seem relevant to your situation, please open a new support ticket with us for further assistance at our support forum.
Problem: The client is experiencing an issue where an unwanted section with the page title is being added to pages when translating from English to Portuguese-Brazil. Solution: This section is added by the theme option "Page intro" which is disabled on the default language. We recommend the following steps to remove the unwanted section from the translated pages: 1. Navigate to WPML > Settings > Custom Fields Translation. 2. Look for the field
pix-hide-top-area
. 3. Set this field to Copy and save the changes. 4. Make a minor edit to the original page and update it. 5. Update the translation accordingly.
Problem: If you're experiencing issues where buttons on your multilingual website still redirect to the default language version after translation, the problem may be related to how the internal URLs are added to the buttons in the default language. Solution: We recommend checking how the URLs are added to the default language page. In a specific case, the issue was with the slider button URLs. We resolved this by editing the page with Elementor and using only the slug instead of the full URL for the buttons. After making this change, update the page and its translation to ensure that the buttons in the translated version correctly redirect to the corresponding language. If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us.
Problem: The client is setting up a bilingual website with different domains for each language. They followed the WPML guide for using different domains per language but encountered an issue where the secondary domain (.hr) was not validating in WPML and redirected to the primary domain (.eu) when trying to access translated pages.
Solution: 1. We activated the auto-login between domains. 2. We edited our profile to view hidden languages. 3. We added ourselves as a translator to troubleshoot. 4. We discovered that when the language is not hidden, the secondary domain is accessible. 5. We found that changes in translations were not visible on the frontend unless a fake URL parameter was added to bypass the cache. - We recommend purging all caches, including server-side caches, to resolve the issue with the cache.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client has set up the ACF fields programmatically and he was unable to translate them using the WPML Translation Editor. It is not possible to translate the ACF Fields if they are not existing in WP Admin.
If you're experiencing issues with custom ACF fields not working correctly after following WPML instructions, it's likely due to translation preferences not being set properly. Solution: First, ensure that the ACF Multilingual add-on is installed, as it adds custom fields to each ACF Field to manage translation preferences. These fields are not registered within WP Admin, so they need to be configured in WPML settings. For a guide on how to translate sites built with ACF, visit our documentation.
Next, navigate to WPML > Settings > Custom Field Translation. Here, you should set the fields that require translation to "Translate". Additionally, the ACF Field Groups should be set to the translation preference "Expert". For more detailed instructions, refer to this guide.
If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket with us for further assistance.
Problem: The client is experiencing an issue where a notice appears stating that a message must be translated manually because the field groups associated with it use different translation options. As a result, the translation editor cannot be used. Solution: We recommend checking the Advanced Custom Fields (ACF) field groups by navigating to the ACF field groups section in the WordPress admin. Look for the field group named "Productinformatie" and switch it to "Expert" mode. Before making this change, ensure to create a backup of your site. This action may resolve the issue with the translation editor.
If this solution does not seem relevant to your situation, please feel free to open a new support ticket with us.
Problem: If you're experiencing an issue where your shopping cart works fine when WPML is deactivated, but you encounter an error with WooCommerce Multilingual activated, it might be due to a compatibility problem with the OnSale Page for WooCommerce plugin.
Solution: The error occurs in the
pre_get_posts
method within the OnSale Page for WooCommerce plugin. The plugin is passing a NULL value because it expects a non-NULL return which WPML does not provide. To fix this, you can modify the plugin's code as follows:
public function pre_get_posts( $q ) {<br />if(!$q->query)<br />return;<br />$onsale_page_id = $this->get_main_wpml_id(wc_get_page_id( 'onsale' ));<br />if($onsale_page_id != -1 && $onsale_page_id != NULL){
This is a temporary workaround. Since the plugin is not compatible with WPML, you can suggest that the plugin's authors join our Go Global Program to achieve compatibility. Alternatively, you can contact the plugin's support for a permanent solution.
If this solution doesn't seem relevant to your issue, please open a new support ticket in our support forum.
Problem: The client is experiencing an issue where all categories are synchronized, but a notice indicating that some taxonomy terms are out of sync between languages persists. Solution: Ultimately the customer reported that this was likely a migration issue, he was able to fix the issue by returning to the old location.
Problem: The client inquired about setting a new translation as the default language for the website.
Solution: We asked the client to clarify which translations they wanted to set as the default language. We recommended checking our documentation on how to manage archive listings and change the default language, which can be found here: Manage Archive Listings & Default Language Change.
We also emphasized the importance of taking a full backup of the website and database before making any changes.
If this solution does not seem relevant, we encourage the client to open a new support ticket for further assistance at WPML Support Forum.
Problem: The client reported that a translation was not displaying on the frontend of their website, despite having successfully translated everything else.
Solution: We provided a workaround for the issue. Here are the steps we took: 1. Open the
Problem: The client was unable to find the string "Title: A - Z" using WPML's String Translation. Solution: 1. Navigate to WPML String Translation. 2. Scroll down to the "Auto register strings for translation" section and enable that option. 3. Visit the page where the string appears on the front end. 4. Return to String Translation and disable the "Auto register" option. 5. Search for the string again and proceed with the translation.
Problem: The client is unable to use the WPML multilingual CMS plugin on their site. Solution: We installed the latest version of the WPML plugin, which resolved the issue. We recommend the client to verify by checking their plugins page.
Problem: The client wants to style the language selector in the main menu as shown in the provided screenshot. Solution: If you're looking to style your language selector in the main menu, we recommend checking out the following documentation:
These resources should guide you through the process of customizing the language selector to fit your desired style. If this solution doesn't seem relevant to your issue, please don't hesitate to open a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client was experiencing an issue where the navigation links in the Divi Builder blog layout were not translating correctly. Despite translating the Dutch words for 'next' and 'previous' into English using String Translation and translating the module, the English blogs still displayed the Dutch words 'Vorige' and 'Volgende'. Solution: The navigation link texts were coming from a custom body template created for posts in Divi > Theme Builder. The template can be translated by going to WPML > Translation Management and using the search filter to find the 'Body Template' post type then translating the correct template. After translating the template, the issue was resolved.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
