Problem: The client reported an issue with the Croatian version of a WooCommerce product page showing an ERR_TOO_MANY_REDIRECTS error and having a URL with double slashes. Additionally, the featured image and attribute images were not displaying on the translated product page.
Solution: We advised the client to first take a full backup of their site and database. The steps included: 1) Checking in String Translation for the problematic URL and correcting it for the Croatian translation. We also suggested running the process to scan and auto-adjust links under WPML -> Settings -> Translate link targets. 2) Deactivating all plugins except for WPML, String Translation, WooCommerce, and WCML to check if the issue persists. 3) Switching to a standard theme like 2024 or 2021 to rule out theme-related issues. 4) Re-activating plugins one by one to identify any conflicts, and then switching back to the original theme to check for issues.
Alternatively, client found that plugin SEO press was causing the url to look like this, resetting the plugin fixed the issue.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant, 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is unable to translate the WooCommerce integration on the checkout page, even though it appears translated in WPML's String Translation. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Edit the
// Ensure translation here 3. Save the file. 4. Navigate to WPML -> String Translation. 5. Enable the "Auto register strings for translation" option. 6. Visit the checkout page in the default language. 7. Disable the option. 8. Search for the string in String Translation. 9. You should see it twice, please translate both strings. 10. Clear the cache and check the translated checkout page.
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 issue persists, please open a new support ticket at WPML support forum.
Problem: In the Spanish version of a multilingual webshop, the client is unable to set display conditions in Elementor for the Spanish category 'JUEGO TABLAS'. Despite the taxonomy hierarchy being synchronized, only Slovenian categories are available for selection. Solution: We discovered that the issue was due to the use of an outdated 'Products' widget in Elementor, which was deprecated since version 4.1.3. We recommended switching to the 'Products Grid' widget. After making this change, the client should verify if the translated archive displays correctly by checking the front end.
If this solution does not resolve the issue or seems outdated, 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 problems persist, please open a new support ticket.
Problem: The client is unable to see the URL ACF field for translation on their website. Solution: We identified that the URL type field was set to 'Copy' under the 'Same fields across languages' option in the ACF groups. To enable translation for this field, the client needs to switch the translation option of the 'Dodatno mize' field group to 'Expert' mode. For more details on default settings and how to switch to Expert mode, please refer to the following documentation links:
If this solution does not resolve your issue or 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 is trying to set different prices for the same product in different languages on their WooCommerce site without using a multi-currency setup. They are unsure if the WPML Custom Fields Translation settings are sufficient for this purpose.
Solution: We advised the client to check if any other plugins might be affecting the pricing since WPML typically does not support different prices for the same product in different languages without a multi-currency setup. We suggested reviewing the settings and possibly disabling other plugins that might interfere with WPML's functionality. For further assistance, we requested temporary access to the site to investigate the issue more thoroughly.
If this solution does not resolve your issue or seems irrelevant due to being outdated or not applicable to your case, we recommend opening 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. For further assistance, please visit our support forum at https://wpml.org/forums/.
Problem: The client is using Revolution Slider with shortcodes on a homepage and is facing issues with translating the carousel shortcode using WPML. The client finds that after editing the page and updating the translation, the shortcode updates incorrectly. Solution: 1. Ensure that the Revolution Slider shortcodes are added to the page and make a small change to the page title, then save the page. 2. Update the translation and check if the shortcodes are visible in "WPML > String Translation". 3. If using the WPML Advanced Translation Editor (ATE), avoid mixing translation methods as manual changes will be overwritten. Instead, follow the guide on creating multilingual sliders with Revolution Slider and WPML: https://wpml.org/documentation/plugins-compatibility/creating-multilingual-sliders-with-revolution-slider-and-wpml/ 4. If the shortcode is still not appearing, ensure it is registered for translation as per the guide on translating custom shortcodes with WPML: https://wpml.org/documentation/support/language-configuration-files/translate-custom-shortcodes-with-wpml/#making-shortcodes-translatable 5. After registering, make a small edit to the page containing the shortcode and save the changes, then update the translation.
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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: You want to translate bank account details in WooCommerce to Croatian using WPML, but you only have one bank account and need to disable the second one. Solution: Since WooCommerce Multilingual translates content on a 1:1 basis, here are a few approaches you can consider: 1) Implement custom code to handle different bank accounts based on the language. 2) Translate all content, using placeholders (e.g., empty spaces) for fields that should remain empty. 3) Use CSS to hide specific sections for a particular language. Note that WooCommerce might use the same class names for both sets of bank details, which may require additional customization to target them properly. Alternatively, you can use a regular space or an ASCII whitespace character to make the second bank account details "invisible". You can find various ASCII whitespace symbols here.
If these solutions do not apply to your case, or if they seem outdated, we recommend opening a new support ticket. Also, 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, please visit our support forum.
