Problem: The client is experiencing issues with currency not changing when users are not logged in, despite trying to switch currency by user location and by language. The client is using WP Rocket for caching, and the server is hosted with Kinsta. Additionally, a client using a Starlink setup could not switch currency, possibly due to an unrecognized IP. Solution: If you're experiencing issues with currency switching on your site, especially when caching plugins like WP Rocket are enabled, we recommend adding the following cookies to the cache exclusion list under the Advanced Rules of WP Rocket:
wcml_client_currency
_wcml_booking_currency
wcml_client_country
wcml_client_currency_language
wcml_client_currency_switched
These cookies should also be excluded from Kinsta's caching. Keep in mind that changes may take some time to take effect. If you've configured the currency to change based on the user's location, try using a VPN to simulate accessing the site from a different location and check if the currency updates. If this solution doesn't seem relevant to your issue, please open a new support ticket with us.
Problem: The client is experiencing a blank page when viewing the "Jobs" and "Employers" pages in languages other than English. The pages were created with the Superio theme and the WP Job Board Pro plugin.
Solution: We found that the issue is related to the translation preferences of custom fields. To resolve this, please follow these steps: 1. Navigate to WPML > Settings > Custom Fields Translation. 2. Enable the option "Show 'Multilingual Content Setup' meta box on post edit screen". 3. Save the settings. 4. Edit the Jobs page in the default language. 5. In the 'Multilingual Content Setup' section, set the apus_page_ fields to 'Copy'. 6. Click 'Apply'. 7. Make a minor change to the page and update it. 8. Send the page for translation using the WPML editor.
For the 'Employers' page, please: 1. Go to WPML > Settings > Custom Fields Translation. 2. Set the following fields to 'Copy':
apus_page_employers_display_mode
apus_page_employers_inner_list_style
apus_page_employers_inner_grid_style
apus_page_employers_columns
3. Save the changes. 4. Make a small change to the 'Employers' page and save it. 5. Send the page for translation with the WPML editor.
We also suggest contacting the theme authors to address this issue and set the correct default preferences for these fields.
Problem: The client wants to offer an English version of their website for both the Belgian and Dutch markets while using 'a different domain per language' setup. They are inquiring if it's possible to have a setup like this: NL: pearlcapital.nl NL-EN: pearlcapital.nl/en/ BE: pearlcapital.be BE-EN: pearlcapital.be/en/
Solution: We recommend not mixing 'a different domain per language' with 'Different languages in directories'. Instead, you should use subdomains for the English versions. The setup would look like this: NL: pearlcapital.nl NL-EN:
en.pearlcapital.nl
BE: pearlcapital.be BE-EN:
en.pearlcapital.be
Please refer to our documentation for more details:
Problem: The client is trying to set up WPML on a server with a domain that already has an old website running on it. The client is modifying their Hosts files to work around this. Solution: We registered the domain
http://www.racemotos.com
on the WPML account sites and added it to the client's site. We recommend following the documentation for installing WPML, which can be found here: https://wpml.org/faq/install-wpml/. It's important to ensure that the domain registered is correct, as sometimes the key may not be valid if there is a discrepancy.
If this solution doesn't look relevant, please open a new support ticket in our WPML support forum.
Problem: The client was experiencing an issue where product categories appeared correctly in the English interface on desktop and tablet but not in the mobile view. Solution: If you're experiencing a similar issue with product categories not displaying correctly on mobile devices, we recommend checking the 'Order By' settings. Here's how you can do it: 1. Navigate to 'Appearance' > 'Theme Options' > 'Product Global Options'. 2. Modify the 'Order By' settings to 'Name'. This adjustment should resolve the issue with the product category display on mobile devices. Please note that the options for the Mobile category might not be adjustable through 'Appearance' > 'Widgets'. If this solution doesn't look relevant to your issue, feel free to open a new support ticket with us.
Problem: The client wants the page URL to include special characters, similar to how it was displayed when using Weglot, but is now using WPML and the URLs do not retain the special characters.
Solution: We recommend the following steps to include special characters in the slugs: 1. Consider using custom code to allow accents in permalinks. You can refer to this discussion on WordPress Stack Exchange. However, we cannot guarantee compatibility with WPML. 2. Use a third-party plugin like Permalink Manager Pro, which allows special characters in permalinks. More information can be found here: Permalink Manager Pro Documentation. 3. Manually encode the slug using a service like URL Encoder. After encoding, paste the encoded slug in the Quick Edit post section in the admin area for the Portuguese language version of the post. For more details on how WordPress handles slugs, you can refer to the WordPress Developer Documentation.
Problem: The client is experiencing an issue where product attributes translated into Russian using the WooCommerce Multilingual & Multicurrency module are displaying in English on the front end, despite being correctly translated on the backend. Solution: We discovered that the problem was related to a form within a popup that was not translated. This form was created with the "Contact Form 7" plugin. To resolve the issue, we recommended translating the form by following these steps: 1. Go to the Contact Form 7 plugin. 2. Translate the form into the required language. 3. Check the front end to ensure that the attributes are now displaying correctly in Russian. For detailed instructions on how to translate forms using Contact Form 7 with WPML, please refer to our guide:
If this solution does not seem relevant to your issue, please do not hesitate to open a new support ticket with us for further assistance: WPML Support Forum.
Problem: The client is trying to connect multiple websites using WPML and manage a single invoice/payment for automatic translation services. They are concerned about losing translated data when following the steps to merge sites with active accounts.
Solution: 1. We recommend checking our guide on managing Automatic Translation Subscription for Multiple Sites for detailed instructions. 2. To merge sites, follow these steps: - Cancel the automatic translation account on one of the sites through WPML -> Translation Management -> Tools. - Wait approximately one hour for the charge to be triggered for the canceled account. - Pay the final invoice for the canceled account. - Obtain the migration code from the site with the canceled account and enter it into the site with the active account. 3. Cancelling an account will not result in the loss of completed translations or Translation Memory. 4. However, it will set the account status to cancelled, prevent future charges, disable automatic translations, and cancel ongoing translation jobs.
Problem: The client needs to ensure that all settings for a product set up in Dutch are transferred to other languages, with the exception of the description, which should remain editable and not be automatically translated. They are experiencing issues with having to manually add all content, such as pictures, prices, and variations, for translations, which was not the case previously.
If you are manually adding translations and want to duplicate the product while only changing the description, you can refer to the guide on duplicating posts with WPML. This guide explains how to duplicate content, perform bulk duplication, and convert a translation to a duplicate. It also includes an option to overwrite the duplicated post with the original language content, thus copying everything to the translation and allowing you to manually edit only the description.
If this solution does not seem relevant to your situation, please open a new support ticket and we will be happy to assist you further.
Problem: The client is trying to translate their store page to Dutch and expects to see the same version as in English. However, they are encountering an issue where the translated page has a different view with incorrect margins, making the site look unprofessional. Solution: If you're experiencing a similar issue with incorrect margins on your translated store page, we recommend checking if there is custom CSS set within your site or theme options that controls the margins and width of your shop page. In the client's case, the English version had specific CSS that set the max-width to 1240px for screens wider than 922px:
Applying this CSS to the translated page should resolve the issue. If the translated page is currently set to 100% max-width, it needs to be adjusted to match the original language's styling.
If this solution doesn't seem relevant to your situation, please open a new support ticket with us, and we'll be happy to assist you further.
Problem: The client needs to downgrade the WooCommerce Multilingual & Multicurrency plugin from version 5.3.2 to 5.2.0 but is unsure how to proceed. Solution: If you're looking to downgrade the WooCommerce Multilingual & Multicurrency plugin, we recommend the following steps: 1. Make sure to make a full backup of your site as a precaution. 2. Navigate to your WordPress admin panel, go to Plugins, find WooCommerce Multilingual, and deactivate it. Then, delete the plugin. 3. Download the version you want to downgrade to from our official repository here: WooCommerce Multilingual & Multicurrency changelog. 4. Return to the plugins page in your admin panel, click on Add New, and install the version you've just downloaded.
If this solution doesn't seem relevant to your situation, please don't hesitate to open a new support ticket with us here.
Problem: The client is trying to translate a specific message on the WooCommerce My Account page in French and wants to change the text for "Mot de passe". Solution: We recommend searching for the string to translate under WPML > String Translation. We have comprehensive documentation on how to do this: https://wpml.org/documentation/getting-started-guide/string-translation/
Problem: The client was trying to fix the layout of translated pages to match the English layouts and was unsure if the issue would persist when adding new pages. They also needed assistance with the Spanish page layout.
Solution: We assisted the client by correcting options that were not being saved on the translated page. We asked the client to check if the issue was resolved. For the Spanish page, we provided a specific solution by sharing a video tutorial (https://screenpal.com/watch/cZVfIgVHpzi) that demonstrated the steps we took to fix the layout.
If this solution doesn't look relevant or if you encounter further issues, please don't hesitate to open a new support ticket by visiting our support forum.
Problem: The client has completed translations on every page, but they are not visible when switching languages, although the menu does change. This suggests there might be a URL issue. Solution: We found that the translations were not marked as 100% complete. We have created a video tutorial to explain why this is important and how to resolve the issue: Video Tutorial. We have already applied the solution to your homepage, which is why it is now working correctly: Homepage.
If this solution does not seem relevant to your issue, please feel free to open a new support ticket with us here.
Problem: The client needs to know if there is a way to automatically translate updates to blog posts after editing the default language, without having to manually click the "refresh" button and update the translation each time. Solution: We recommend enabling the 'Translate Everything Automatically' mode on your site. This feature allows for automatic translation of all content, including updates to existing posts. To use this feature, it must be active at all times. For more information on how to enable and use this mode, please visit our documentation: Translating Your Whole Site Automatically.
If this solution doesn't look relevant to your issue, please open a new support ticket in 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
