Problem: Shop Managers cannot translate taxonomies. Solution: We recommend checking the workaround provided in the WPML errata page. Before implementing any changes, ensure to back up your database. You can find the necessary steps and details here: https://wpml.org/errata/shop-managers-cannot-translate-taxonomies/.
If this solution does not apply to your case, or if it seems outdated, please do not hesitate to 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.
Problem: You are setting up multicurrency functionality on your WordPress site using WPML with Elementor, but the currencies do not convert correctly and the currency symbol does not change after switching.
Solution: First, ensure that WooCommerce and Elementor are updated to their latest versions as outdated plugins can cause conflicts.
The issue with incorrect currency conversion and pricing appears to be due to a lifting charge added in the Automatic Exchange Rates settings in WCML. This additional charge is applied to the exchange rate before conversion, making one currency appear costlier than the other. To resolve this, set the lifting charge to 0% and manually update the rates by clicking the "Update manually now" button.
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 problems persist, please open a new support ticket.
Problem: The client is trying to manage translated URLs in their sitemap XML and is unsure how to proceed using the WPML SEO addon plugin. Solution: First, ensure that you have provided the WPML support debug information from your site. You can do this by logging into your site, navigating to WPML → Support, and clicking on the 'debug information' link at the bottom of the page. Copy the entire content of the text box and paste it into the debug information box on our support forum. For more details, visit https://wpml.org/faq/provide-debug-information-faster-support/.
Next, verify that you are using the WPML SEO addon plugin. Also, check if the issue persists when using the WP Default theme with only WPML plugins and SEO enabled, and all other plugins disabled. It's recommended to test this on a staging site.
Additionally, follow these steps: 1. Go to WPML > Support > Troubleshooting. 2. Click on the following buttons: - Synchronize posts taxonomies (Select 'Pages' from the dropdown and then click the button) - Clear the cache in WPML - Assign translation status to duplicated content - Set language information - Fix post-type assignment for translations 3. Clear the caches from your site and browser. 4. Navigate to Rank Math > Sitemap Settings in your WordPress dashboard. 5. Ensure that the relevant post types (like Posts and Pages) are selected for inclusion in the sitemap. 6. Save the changes, and Rank Math will automatically regenerate the sitemap.
If the issue persists or if the solution provided here becomes 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 necessary, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is experiencing an issue with incorrect product counts on the taxonomy list page in a Product Category. Solution: If you're encountering a similar issue, we recommend following these steps: 1. Navigate to WPML > Support > Troubleshooting. 2. Perform the following actions: - Synchronize posts taxonomies - Clear the cache in WPML - Remove ghost entries from the translation tables - Set language information - Fix terms count - Fix post type assignment for translations IMPORTANT: Please ensure to backup your database and website before proceeding.
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: The client is experiencing issues with custom fields not transferring correctly for variation products in a translating plugin and CDX feed plugin for Google Shopping, affecting pricing measures. Solution: If you're encountering similar issues, we recommend navigating to WPML -> Settings -> Custom Field Translation and setting those fields to 'Copy' as required. This process is detailed in our documentation, which you can find here: Translating Custom Fields. If you don't see those custom fields, try clicking 'Show System Fields' below the 'Custom Field Translation' heading. Then, search for 'Unit Price Measure' and 'GTIN' to ensure they are set to copy. Please remember to backup your database before making these changes.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: The client needed to translate a custom tab added to the WooCommerce product data, which was not appearing in the WPML String Translation interface.
Solution: 1. We advised the client to ensure that the strings are wrapped in the gettext function. For example, replace:
'Refund and Returns Policy'
with:
__('Refund and Returns Policy', 'themedomain')
2. We instructed the client to go to WPML >> String Translation and enable the 'Look for strings while pages are rendered' option in the Auto register strings for translation section. 3. The client should then visit the page on the front end where the string appears. 4. After that, revisit the WPML >> String Translation page and search for the string. 5. Translate the string as needed. 6. Finally, uncheck the auto-registration option to maintain site speed.
If this solution does not apply to your case, or if it seems outdated, 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. Should you need further assistance, please do not hesitate to open a new support ticket. You can do so by visiting the WPML support forum.
Problem: The client reported that translated pages were not appearing in their sitemap.
Solution: We recommended checking if the WPML SEO plugin was installed and active, which helps with sitemap generation. If the issue persisted, we asked for an example of a missing translated page/post and the Debug Information from WPML > Support. After the client updated the pages using the Gutenberg editor, the sitemap refreshed and included the previously missing pages. This suggests that a caching mechanism might have been holding an outdated version of the sitemap. We also checked the settings by toggling the no-index and no-follow options for the pages, which confirmed that the sitemap was updating correctly.
If you're experiencing a similar issue, we recommend: 1. Ensuring the WPML SEO plugin is installed and active. 2. Updating the pages using the Gutenberg editor to refresh the sitemap entries. 3. Checking for any caching mechanisms that might be affecting the sitemap. 4. Providing Debug Information by following the instructions here.
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 necessary, please open a new support ticket here.
Problem: The client is using a staging site and has encountered two notifications after setting it up. The first notification is about mapping the default language for automatic translation, and the second is about WPML detecting a new address for the site.
Solution: For the first notification regarding the default language, the client should ensure that the default language (English) is correctly mapped to a supported language in WPML -> Languages settings.
For the second notification about the site address change, on the staging site, the client should select "Yes, this is a copy" to indicate that the original site is still running. In the subsequent step, the client can decide whether to share credits for automatic translation with the staging site.
If these steps do not resolve the issue, we recommend 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. If the problem persists, the client should open a new support ticket for further assistance at our support forum.
Problem: The client needed to change the value of the Tagline and Blog Title strings for their website using the Hello theme, which is compatible with WPML. They also had issues with translating Rank Math's %Sitename% placeholder, as it was not reflecting on the live site despite being translated in WPML's String Translation.
Solution: 1. To change the Tagline and Blog Title strings, go to WPML > String Translation. Check the boxes for these strings, scroll down, and switch the language to one that is not yet set up on the site. This will allow you to change the strings for English, adding a new column with a '+' for the EN flag.
2. For Rank Math SEO integration with WPML, refer to the following documentation:
. If the hosting provider limits these settings, contact them to request an increase.
If the provided solution does not apply to your case, or if it seems outdated, we 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 the issue persists, please open a new support ticket. We highly recommend creating a backup of your site before making any changes.
Problem: The client reported that their WPML Automatic Translation credits were showing as zero on their site, despite previously having about 70,000 credits. Solution: 1. We checked if the credits might have been stuck due to a reinstallation or reset of WPML or WordPress. 2. We moved the 79,912 credits back to the client's current website. 3. We instructed the client to check WPML > Translation Management > Automatic Translation to see the credits. 4. We asked for the Automatic Translation account ID from WPML > Support > Troubleshooting to verify the correct assignment of credits. 5. Upon receiving the ID, we confirmed that the credits were mistakenly assigned to a staging site and moved them to the correct live site.
If you're experiencing a similar issue with your WPML Automatic Translation credits, we recommend checking WPML > Translation Management > Automatic Translation to see if your credits are displayed. If they are not, please go to WPML > Support > Troubleshooting and share your Automatic Translation account ID with us. However, keep in mind that this solution might be irrelevant if it's outdated or not applicable to your case. We highly recommend checking related 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 is using Hostinger for hosting and wants to enable the staging feature to make changes on a subdomain (e.g., stage.turkmenexporter.com) without affecting the live site. The client is concerned about whether the WPML plugin will remain active and functional on the staging subdomain.
Solution: 1. We informed the client that WPML should work fine on the staging site, but issues might arise with registering WPML if the correct URL is not used when generating the WPML key. 2. We advised the client to create a full website backup and ensure that the domain shown in the WordPress General Settings is the one used when creating a new WPML key on the WPML account sites page. 3. We provided a screenshot from the WPML purchase page to clarify the number of available keys for production/live and dev/staging sites based on the client's subscription. 4. We created custom Google search URLs to help the client find existing tickets with solutions for similar issues:
5. We mentioned that the disappearance of notifications in the WordPress backend could be due to automatic cache clearing.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, 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 you need further assistance, please open a new support ticket in the WPML support forum.
