Problem: If you're unable to register the WPML plugin because your URL has changed, Solution: First, check if the issue is a false positive due to server caching. Navigate to Plugins > Add New > Commercial and click the "check for updates" button. If WPML still shows as registered after the page refreshes, it's likely a false positive. The notice you're seeing is about WPML's connection to its servers, not about the registration itself. To change the WPML key, go to your site's backend, under Plugins > Add New > Commercial, where you can unregister WPML from the old key and re-register with a new key. Generate a new key at http://wpml.org/account/sites. If this solution doesn't resolve your issue, please open a new support ticket.
Problem: The client was experiencing an issue with WooCommerce products not displaying the correct 'out of stock' status in the English version of their site. Solution: We resolved the issue by applying a workaround detailed in our documentation. If you're experiencing a similar problem where your product stock status is not updating correctly in a second language, we recommend trying the steps outlined in the following documentation: WooCommerce Multilingual variable product stock status is not updated when it gets out of stock in the second language. After applying the workaround, the stock management should be functioning correctly. Please verify on your site.
If this solution doesn't look relevant to your issue, please don't hesitate to open a new support ticket with us here.
Problem: The client was experiencing issues with taxonomies clashing with Custom Post Type (CPT) slugs, which was resolved. However, they then encountered a new problem where classic widgets disappeared. Solution: We resolved the initial issue by removing some taxonomy that was clashing with the CPT slugs. If you're experiencing similar problems with taxonomies and CPT slugs, we recommend checking for any conflicts and removing the problematic taxonomy. Regarding the disappearance of classic widgets, if this solution doesn't seem relevant to your situation, please open a new support ticket with us so we can assist you further.
Problem: The client reported that all items on their multilingual website were being displayed in all languages, rather than only in the corresponding language. Solution: We resolved the issue by setting the taxonomy to 'translatable'. It appears that the client had previously altered this setting, which may have caused the problem. To fix similar issues: 1. Go to the WPML > Taxonomy Translation page. 2. Choose the taxonomy you want to translate. 3. Set the taxonomy to 'translatable'.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client was experiencing a white screen when trying to open two specific product pages in a language other than English, while the English versions were working fine.
Solution: 1. We asked the client if the issue was occurring only with the two mentioned products or with others as well. 2. We suggested making a small change in the product title in the default language (such as adding a '+' sign) and then updating the product to see if it resolved the issue.
The client managed to resolve the issue by creating their own template for the Product Page.
If this solution doesn't look relevant to your situation, please don't hesitate to open a new support ticket with us.
Problem: The client needed assistance translating a specific string: "I would like to receive exclusive emails with discounts and product information", but was unable to find it in the string translation interface. Solution:You should be able to translate that MailPoet plugin string by following the suggested steps from this thread: https://wpml.org/forums/topic/translate-mailpoet-to-enable-customers-sentence/#post-7448773
Problem: The client is trying to add multiple languages to their site and use the dropdown language switcher in the footer, but they are encountering an issue with its display. Solution: We recommend adding the following custom CSS to the theme's custom CSS section to control the height of the WPML Language Switcher dropdown:
Problem: The client's product gallery styles were not correctly applied to the English translation of their website. The images were appearing below the main photo instead of in their correct positions as defined by the 'Kadence shop kit' PRO plugin.
Solution: We identified that the issue was related to a string named
kt_woo_extras
that needed translation via WPML String Translation. We added the correct translation settings for this string, and after applying them, the product gallery displayed correctly in the English translation of the product pages.
If you're experiencing a similar issue, we recommend checking the WPML String Translation for the string related to your gallery display settings and ensuring that the correct translation is applied.
Problem: The client is unable to disconnect a translated post from its original post using the 'This is a translation of' dropdown by selecting 'none' and saving the post. Solution: We recommend updating WPML Multilingual CMS to version 4.6.8, as this issue has been resolved in that update. Before updating, ensure to create a full backup of the website. For more details on the issue and the update process, please refer to the errata page:
Problem: The client is experiencing issues with footer content not translating or reverting back to default values despite clearing cache engines and trying different browsers. Solution: If you're experiencing issues with your footer content not translating or reverting to default values, we recommend the following steps: 1. Navigate to WPML -> Theme and plugins localization, select your theme/plugin, and scan for strings. 2. Go to WPML -> String Translation. 3. Click on the "Translate texts in admin screens »" link. 4. Search for the strings you need to translate. 5. Select the strings you want to translate. 6. Click on the "Add to String Translation" button. 7. Return to the String Translation page by clicking on the "« Return to String Translation" link. 8. Translate the strings, clear the cache, and then check the front end to see if the changes are reflected. For more detailed guidance, please refer to our documentation on translating texts in the admin texts screen.
If this solution doesn't look relevant to your issue, please open a new support ticket in our support forum.
Problem: The client is unable to translate pages using WPML; clicking the "+" icon to translate a page does not trigger any action. Solution: 1. We changed the translation mode to "Translate what you choose". 2. We then attempted to translate the mentioned page, and the translation editor opened correctly. 3. We recommend the client to verify if the translation editor opens for them now. 4. If further adjustments are needed, the client should go to WPML -> Settings -> Translation Mode to ensure the correct settings are applied.
Problem: The client is experiencing an issue where changing the language on their homepage (and other pages) results in the browser tab showing a blank label or one with hyphens, percent signs, etc. This issue is also affecting the 'og:title' meta property, which is crucial for SEO and displaying titles in browser tabs. Solution: 1. We recommend deactivating the WPML String Translation plugin to see if this resolves the issue. 2. If deactivating the plugin fixes the problem, it indicates that there is a translated string that should not be translated. 3. If the issue persists after deactivating the plugin, it may be related to the settings in the Yoast SEO plugin.
If this solution does not seem relevant to your situation, please open a new support ticket with us for further assistance.
Problem: The client is experiencing issues with the styles of the product pages not displaying correctly on their translated pages. Solution: We noticed a PHP Fatal error in the debug.log file that might be causing the style issues on the product pages. The error is related to the ACF Repeater for Elementor plugin. We recommend deactivating the ACF Repeater for Elementor plugin to check if this resolves the issue.
If this solution does not seem relevant to your situation, please open a new support ticket with us.
Problem: The client wants the author bio link in the recipe card to redirect to the appropriate language version of the 'about-me' page, depending on the language the visitor is viewing the recipe card in. The current setup only redirects to the English version, even when the site is switched to Dutch.
Solution: 1. We recommend enabling the translation of the author by navigating to WPML > String Translation > More Options and checking the option to translate users. 2. If the author link is not a standard WordPress author page and is instead implemented using a custom template or page, we suggest using the wpml_object_id hook to adjust the URL based on the current language. This hook allows for the translation of post IDs, ensuring the correct page is served for each language.
3. Alternatively, you can register the URL as a string and translate it using the wpml_register_single_string hook, or create a conditional statement that checks the current language and returns the appropriate URL.
Please note that we do not provide fixes for custom code as per our support policy. If you require custom assistance beyond the scope of our support, we recommend contacting one of our certified partners from this link.
If this solution does not seem relevant to your issue, please open a new support ticket here.
Problem: The client is experiencing 404 error pages for the Arabic versions of the 'Terms of service' and 'Return Policy' pages after translation. Solution: We have identified that the pages in question are still drafts and not published. To resolve this issue, we recommend the following steps: 1- Navigate to Pages -> All Pages in the WordPress dashboard. 2- Switch the language to Arabic from the top admin bar. 3- Locate and edit the 'شروط الخدمة' and 'سياسة الاسترجاع' pages. 4- Publish the pages to make them live.
This page includes support tickets that are resolved and documented. Looking for tickets that are “in progress”? Visit the complete support tickets archive
