Problem: The client has successfully loaded and activated the WPML plugin on their site but cannot find the translator option. The site still uses a previous free translator plugin. Solution: We recommend checking if WPML is properly working and accessing the translator options by following these steps: 1. Review the WPML Getting Started Guide 2. Understand how WPML Automatic Translation works 3. Explore the WPML Translation Editor options
If these resources do not resolve your issue or if the information 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 problem persists, please open a new support ticket.
Problem: The client is experiencing issues with translations not working properly on their site using WPML. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Open the
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: After updating to WPML plugin version 4.6.12, the staging site broke due to a PHP Warning error. The error indicated a missing file, specifically
autoload_real.php
, in the plugin's directory. Solution: 1. Verify if the
directory. 2. If the file is missing, manually upload this file or the entire plugin. Follow the guide on how to update WPML manually: https://wpml.org/faq/updating-wpml-manually/ 3. After uploading, the PHP Warning should resolve.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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, please visit our support forum: https://wpml.org/forums/forum/english-support/
Problem: The client is experiencing an issue where the URL parameter '?lang=en' remains in the URL after setting up redirections using Rank Math on a site under development. The expected URL was 'https://www.bassetti-group.com/en/', but the actual result is 'https://www.bassetti-group.com/en/?lang=en'. Solution: We analyzed the situation and found that the redirection to 'https://www.bassetti-group.com/en/?lang=en' is handled by Rank Math, and this behavior is not related to WPML. Visiting 'https://www.bassetti-group.com/en/' does not redirect further, which aligns with WPML's expected behavior. We also noticed that the client does not have WPML SEO installed. We recommend installing WPML SEO to enhance compatibility with Rank Math by helping it recognize the language settings more accurately. Since this issue is related to Rank Math's functionality, we advise contacting Rank Math's support for further assistance.
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 with us.
Problem: The client wants to set a specific product with a different currency and have other currencies converted from this set currency on a multi-vendor platform using Dokan. The client also inquires if it's possible to set a different main currency for each vendor. Solution: We informed the client that currently, WooCommerce Multilingual or WooCommerce does not support setting a specific currency for a vendor, user, or country. However, a future version of WooCommerce Multilingual (5.5) will include a feature to set prices based on the country, but it is still in the early development stage. For now, a custom plugin might be necessary. We suggested checking out the WooCommerce Product Price Based on Countries plugin, although we have not tested this ourselves. For custom development, we recommended contacting certified developers through this link. Additionally, we provided a code snippet using the
wcml_raw_price_amount
hook to convert from the WooCommerce default currency price to another currency, and pointed to the function that auto-updates product prices in other currencies:
The update_exchange_rates function is defined in the *wp-content/plugins/woocommerce-multilingual/classes/multi-currency/class-wcml-exchange-rates.php* file (line 151).
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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: The client reported that images available in the Dutch (NL) and English (EN) media libraries were not appearing in the French (FR) media library. Solution: We suggested checking if the French language was added later, which might have caused the synchronization issue. We recommended verifying specific WPML media settings. Specifically, we advised selecting the first three options under the media settings and clicking "Start" to synchronize existing media. For future uploads, we suggested enabling the option "When uploading media to the Media library, make it available in all languages" to ensure all media is automatically available in all languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page and check for any related issues. Also, ensure you have the latest versions of themes and plugins installed. If the problem persists, we highly recommend opening a new support ticket here.
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 further assistance is needed, please open a new support ticket at our support forum.
Problem: The client is experiencing issues with URLs not being translated correctly in WPML due to custom code that removes the base slug for Custom Post Types (CPT), causing WPML to misinterpret these URLs. Solution: 1. Modify or Remove Custom Code: Access your theme's
functions.php
file and comment out or remove the code responsible for removing the base slug. Here is the code snippet:
2. Update Permalinks: After modifying the code, navigate to Settings > Permalinks in your WordPress dashboard and click Save Changes to refresh the rewrite rules.
If this solution does not resolve your issue or seems outdated, 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 problem persists, please open a new support ticket at WPML support forum.
Problem:
PHP Fatal error: Uncaught TypeError: str_contains(): Argument #1 ($haystack) must be of type string, array given in ...m/wp-includes/blocks.php:1409 When enabling "Scellius for WooCommerce" plugin with PHP 8
Solution:
The error was happening due to the settings being corrupted.
To fix this, We went to the site database wp_options table and searched for the option name "woocommerce_scelliusstd_settings" and renamed it to "woocommerce_scelliusstd_settings_old", this stored the plugin settings.
Problem: If you're experiencing an issue where your shop page is displaying products from all languages, this might be due to the translation settings applied to your products. This issue typically arises when products are not set as translations of each other and the translation preference is set to 'Translatable - use translation if available or fallback to default language', which displays products in the default language if translations are not available. Solution: We recommend you follow these steps to resolve the issue: 1. Change the translation preference for the post type Products to 'Translatable - only show translated items' in the WPML > Settings > Post types translation. 2. Ensure that each product in your shop is connected as a translation to its counterparts in other languages. You can find guidance on how to link translated products here.
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. Should you need further assistance, please do not hesitate to open a new support ticket here.
Problem: You are trying to translate the 'Book your session!' button in TR, RUS, and DE languages, but the translations are not appearing on the front-end of your site. Solution: We recommend translating the Elementor template post where the button is located. This approach often resolves issues with missing translations in the front-end. For detailed guidance on how to proceed, please refer to the ElementsKit plugin documentation at https://wpmet.com/doc/translate-elementskit-header-footer-and-advanced-widgets-with-wpml/.
If this solution does not resolve your issue or seems irrelevant due to updates or differences in 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
Problem: You are experiencing issues with 301 link redirection in Yoast SEO for Arabic directions, while English ones work fine. Solution: 1. Add the redirection URL in the encoded format:
If this solution does not resolve your issue or seems irrelevant due to updates or differences in your case, we recommend opening a new support ticket. Additionally, 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. For further assistance, please contact our support team at WPML support forum.
Problem: The client is using JavaScripts to display pricing tables in different languages (English, Portuguese, Spanish) via shortcodes managed by the WPCode plugin. Despite following the documentation on making shortcodes translatable, the Advanced Translation Editor (ATE) does not recognize these shortcodes for translation. Solution: We recommend creating separate snippets for each language and adding the ID of the English snippet to the original page. Then, use the ATE search bar to find the ID of the original shortcode. Once located, you can translate the pages by searching for the ID of the English snippet and adding the ID of each translated snippet in their respective language. This method should allow the ATE to properly load data from the specific snippets. For further details, you can refer to this video demonstration: https://www.loom.com/share/14acd0e747a5449caff7d84915c86344.
If this solution does not resolve your issue or seems outdated, please 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. If the problem persists, we highly recommend opening a new support ticket for personalized assistance.
Problem: You have a custom block built using ACF with a Link Field that is not translating the URL automatically, despite setting 'wpml_cf_preferences' => 2 for translation. The link label translates correctly, but the URL does not, showing inconsistency across different pages. Solution: We have identified this as a known issue with Custom ACF Blocks where LINK fields do not adjust automatically. This problem is scheduled for a fix in the upcoming version of Advanced Custom Fields Multilingual 2.2.0. For now, you should keep the LINK field in your block set to "Translate". As a workaround, you can modify the code in your project. Here’s what you need to do:
Edit the file
acfml/classes/class-wpml-acf-blocks.php
On line 191, replace the existing
get_text_type
function with the updated code that includes a condition to handle 'LINK' types. Complete solution.
Ensure you use absolute links and set the link field to translate. After making these changes, update and re-translate the page.
If this solution does not apply to your case, or if it seems outdated, we recommend opening a new support ticket. We also advise 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, please visit our support forum at WPML Support Forum.
Problem: The client translated an email title into Japanese using WPML's String Translation, but the email was still received with an English title. The client found multiple identical strings in the Admin Texts Translation section and was unsure which one to translate. Solution: We recommended that the client include numbers behind the translations to identify which specific string needs translation and then remove the translations for the strings that are not required. This method helps in distinguishing between multiple identical strings.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page to check for related issues. Ensure you have the latest versions of themes and plugins installed. If further assistance is needed, we highly recommend opening a new support ticket at our 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
