Problem: The client was experiencing an issue where the link to the request basket was not working correctly after adding an item to the cart. The link was redirecting to the German cart instead of the English cart. Solution: First, we suggested that the client should ensure that the request basket page is fully translated into English. If the problem persists, we recommended the following steps: 1. Go to WPML > Support > Troubleshooting and click on "Cancel in-progress automatic jobs" to cancel any stuck translation jobs. 2. Duplicate the request basket page into the English language to ensure the link to the English basket page works correctly. Additionally, we noted that the "Request a Quote for WooCommerce" plugin is not listed in our compatibility list, and we advised the client to contact the plugin's support for further assistance. We also provided a link to our documentation on using different translation editors for different pages: https://wpml.org/documentation/translating-your-contents/using-different-translation-editors-for-different-pages/
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, 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 you still need assistance, please open a new support ticket with us.
Problem: The client was experiencing issues with automatic translation not working on their development website after changing the theme and some page content and design.
Solution: We identified that the client was using the Marblex theme, which is not officially compatible with WPML. We suggested the following steps: 1. Contact the theme author to report the issue and inquire if they have a solution, as they claim compatibility with WPML. 2. Invite the theme author to join our Go Global program so we can collaborate on making their product compatible with WPML. 3. As an alternative, use the manual translation method provided in our documentation: Using Different Translation Editors for Different Pages.
We understand the inconvenience this may cause and are willing to assist further, but we cannot adjust the theme code without the author's collaboration.
If this solution is not relevant to your case, either because it's outdated or not applicable, 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 is unable to find an option to translate selected text within a widget.
Solution: We recommend adding different widgets for each language. Alternatively, to translate the widget text, follow these steps: 1. Navigate to WPML → String Translation. 2. Scroll to the bottom of the page and click on the Translate texts in admin screens link. 3. This will direct you to a searchable list of admin strings. Search for the string you want to translate and click Add to String Translation. 4. Return to WPML > String Translation to perform the translation.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we encourage you 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. If further assistance is needed, please contact us on the WPML support forum.
Problem: If you're experiencing issues with buttons on your homepage not redirecting to the correct language after a language change, and your site uses custom blocks from the Kubio plugin, the URL field of the block may not be registered for translation. Solution: First, try searching for the URL in the Advanced Translation Editor (ATE). If it's not available, you'll need to register the URL field for translation. You can do this by creating a custom XML configuration code. Here are the steps: 1. Edit the homepage with the default editor and switch to the Code editor to view the block structure. 2. Use the following XML code to register the button text and URL for translation:
3. Add this code to WPML > Settings > Custom XML Configuration. 4. Make a small change to the page content, save it, and update the translation. The button URL should now be adjusted automatically. For more detailed guidance, please refer to our documentation:
If this solution does not apply to your case because it might be outdated or not relevant, 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 you still need assistance, please open a new support ticket.
Problem: The client is experiencing issues with translation and RTL layout, the Language Switcher not functioning correctly, incomplete product translations, and translated products not appearing on the Arabic version of the site. The client's theme, 'El Greco,' is not on the WPML list of compatible themes, which may be causing these issues.
Solution: 1. We verified that the Language Switcher is functioning correctly and displaying the translated product URLs. 2. For translating the product tab content 'Shipping and Returns,' we directed the client to use WPML > String Translation, accessible through Customization > Single Product > Product Tabs Settings. 3. The 'Item Specifics' tab content, which is stored in a custom table by the theme, requires custom code for translation. We recommended that the client contact the theme author to join our Go Global program, where our Compatibility developers can assist in making the theme compatible with WPML. Alternatively, the client can manually translate the product using the WordPress editor and add the 'Item Specifics' data for the translated product.
Refer to the following documentation for further guidance:
Please note that this solution might be irrelevant if it's outdated or not applicable to your case. If these steps do not resolve your issue, 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 you still need assistance, please open a new support ticket.
