Problem: The client is using the RankMath Plugin on their site and is facing issues with the front-end not displaying the correct RankMath meta for product sub-categories. The front-end also fails to show the correct product category IDs for editing, resulting in incorrect RankMath meta. Solution: If you're experiencing similar issues, we recommend navigating to WPML > Languages and enabling the option "Adjust IDs for multilingual functionality". This adjustment should resolve the issue with incorrect meta display and category IDs on the front-end.
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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: Your site cannot communicate with https://api.wpml.org/ anymore, showing a Code 403 error. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Log in to your WPML.org account and navigate to the Sites page. 2. Delete the existing site key. 3. Log in to your site, go to the Dashboard >> Plugins >> Add new >> Commercial tab and click the Unregister WPML from this site link if it exists. 4. Click the Register WPML link. 5. Click the Get a key for this site link to generate a new key. 6. Copy the new key, paste it into the input box, and press the Register button. If this solution does not resolve the issue or seems irrelevant due to being outdated or not applicable to your case, please open a new support ticket. 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, you can also contact us directly through the WPML support forum.
If this solution does not resolve your issue or 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 at WPML support forum.
Problem: The client experienced an issue where the content/description tab disappeared from the WPML Translation Editor. This caused the text to disappear from the front end when these products were updated. Solution: We identified that the issue was due to the translation method settings. Each product has a setting in the right sidebar of the WordPress Editor where you can choose between the WPML Translation Editor or the WordPress Editor. It's important to use the same translation method consistently for each product. We resolved the issue by opening all the translated products in the WordPress Editor and saving them, ensuring that the WordPress Editor opens as expected for future updates.
If you're experiencing similar issues, we recommend checking the translation method settings for each product in the WordPress Editor and ensuring consistency in the method used. If the problem persists, please visit our support forum at WPML Support Forum for further assistance. 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. If this solution does not apply to your case, please open a new support ticket.
Problem: The client was unsure if the tables wp_2, wp_3, wp_4, and wp_5 in their database were remnants of an old language plugin or were created by WPML for managing additional languages in a WordPress Multisite setup. They needed to know if these tables could be safely removed if they were not needed. Solution: We confirmed that the client's site is a WordPress Multisite installation, where each child site has its own set of tables, including those for WPML. The tables with prefixes like wp_2, wp_3, etc., correspond to different child sites within the Multisite network. Therefore, these tables are necessary for the operation of each site and should not be removed. For further details on WordPress Multisite database structure, we recommended checking the following documentation:
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Also, 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. For further assistance, you can contact us directly through our support forum.
Problem: The client was experiencing issues with modifying text on the frontend. Some product options were displayed correctly, but the translated text did not appear, possibly due to not being added to the translation fields. Additionally, for some products, the additional options did not show up on the product page, and the product reviews data was missing. Solution: We reviewed the translation management and noticed that the post type was set to "Translatable" but was not appearing in the translation management dashboard. When attempting to translate forms by clicking the + icon, it redirected to the WordPress editor instead of the translation editor. We recommended checking the plugin's translation guide here to follow the correct translation steps.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, we highly recommend opening a new support ticket. Additionally, 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. For further assistance, you can also contact our support forum at WPML support forum.
Problem: If you're experiencing issues where your custom post-type template is not being applied or translated for secondary languages on your WPML site, it might be due to a known issue. Solution: We recommend checking the workaround provided in this documentation. Please ensure to backup your database before making any changes. If the problem persists after applying the workaround, update us with screenshots and detailed steps of the issue.
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 continues, please open a new support ticket.
Problem: The client reported that the German version of the menu was displaying correctly, but the layout was confusing. Additionally, manual text updates were not appearing correctly on the front end, even after force refreshing the page. Solution: We reviewed the translated menu and discovered that the size values were missing. We corrected these values and updated the translated menu. We recommend the client to check if the translated menu now works as expected. If the issue persists or if this solution becomes outdated, we advise checking related known issues at https://wpml.org/known-issues/, verifying the version of the permanent fix, and confirming that the latest versions of themes and plugins are installed. For further assistance, please open a new support ticket or visit our support forum at https://wpml.org/forums/forum/english-support/.
Problem: The client is trying to make the black text on the second slide of a slideshow translatable using WPML on their Elementor-based website. Despite following the documentation for registering custom Elementor widgets for translation, the custom XML does not appear in the 'Edit page' menu, and the text is not available for translation. Solution: 1) Ensure that the Multilingual Tools plugin is installed and activated. After installation, revisit the edit screen to check if the XML configuration appears. 2) Although unrelated to the translation issue, it's recommended to increase the WordPress memory limit to meet WPML's minimum requirements. This can be done by adding the following lines to the wp-config.php file:
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 further assistance is needed, please open a new support ticket at WPML support forum.
Problem: If you're experiencing issues with Toolset relationships getting mixed up or disappearing after reactivating WPML on your WordPress site, it might be due to a potential database corruption. This problem typically occurs when WPML is deactivated during development and then reactivated. Solution: We recommend running a custom SQL query to correct the mismatch in the database entries for the relationships. Here is the SQL query you should execute:
You can run this query on your staging server first to ensure it resolves the issue without affecting your live site. If successful, apply the same query to your production site.
Please note that this solution might be irrelevant if it's 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 problem persists, please open a new support ticket.
Problem: The client is experiencing a connection error when trying to register WPML, despite having a valid license. The error message displayed is 'cURL error 28: Failed to connect to api.wpml.org port 443 after 9377 ms: Couldn't connect to server.' This issue persists even after confirming with the hosting provider, GoDaddy, that they are not blocking WPML domains. Solution: We recommend contacting your hosting provider again and insisting that they check for any blocks on the following domains: - wpml.org - cdn.wpml.org - api.wpml.org - api.toolset.com - cloudfront.net It is crucial to request that they escalate the issue to a higher level of support if necessary, as similar issues have been resolved by other clients after persistent requests. Additionally, you can refer to our documentation on this error at https://wpml.org/faq/wpml-plugin-cannot-connect-to-wpml-org/.
If this solution does not resolve your issue, or if it seems outdated or irrelevant 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing a compatibility issue between the EA Duplicator plugin and WPML, where the duplicator does not function when WPML is activated. This issue has occurred previously on another site. Solution: We recommend the following steps to isolate and potentially resolve the issue: 1. Back up your site for security reasons before making any changes. 2. Flush any existing cache memory. 3. Update all outdated plugins and themes. 4. Deactivate all plugins not related to WPML. 5. Temporarily switch to a default WordPress theme, such as Twenty Seventeen. 6. Activate the Essential Addons for Elementor plugin. 7. If the issue resolves, reactivate your original theme and then the plugins one by one to identify the specific cause of the conflict.
If these steps do not resolve the issue, or if the solution seems outdated or irrelevant 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 problem persists, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to translate the 'read more' text on their website using WPML, and the strings are not appearing in the WPML String Translation. Solution: We recommend trying two methods to resolve this issue: Method 1: Navigate to WPML > String Translation. At the bottom of the page, there is a checkbox labeled "Look for strings while pages are rendered". Enable this option, visit the front end of a page where the string appears, then return to WPML > String Translation and search for the string. Method 2: If the string is not found in WPML > String Translation, it might be categorized as an admin text string. You can find and translate admin text strings by following the guide here: Translate Admin and Settings Strings Related documentation can be found here:
If these solutions do not resolve your issue or seem outdated, we highly recommend checking related known issues at WPML 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: The client was experiencing issues with payment methods not working for non-Sweden currencies and errors from PayPal during the checkout process. The WPML showed a message about taxonomies being forced to be untranslatable, and both Klarna and PayPal reported receiving the wrong currency. Solution: We identified that the issue was due to a conflict between WCML and the EU Tax Plugin. To resolve the currency handling issue, we recommended adding a specific hook to the functions.php file of the theme to enable the query string argument on currency change. Here is the code you should add:
/**
* Enable the query string argument on currency change.
*/
add_filter( 'wcml_is_cache_enabled_for_switching_currency', '__return_true' );
If this solution does not resolve your issue, or if it seems outdated or not applicable to your case, we highly recommend checking the related 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.
Problem: The client was experiencing a CORS error because WPML did not update the URL returned by
plugins_url()
. This issue occurred when trying to load JavaScript files across different mapped domains, resulting in files being loaded from an incorrect domain. Solution: The client resolved the CORS error by resetting WPML and re-entering the domains, which corrected the URL mapping for JavaScript files. If you're experiencing this issue, we recommend trying the same steps: reset WPML and ensure your domains are correctly entered.
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 problem 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