Problem: You are trying to set the default Woocommerce endpoint language to Dutch on your website, but despite the default language being set to Dutch, the Woocommerce endpoints default to English. This causes the English version of the website to show the wrong URL slug. Solution: 1. To change the default language of the endpoint strings, you should follow the steps described in this guide: How to Change the Source Language of Strings. 2. If you can't find the strings in String Translation, then follow these steps: Finding Strings that Don't Appear on the String Translation Page. 3. Please increase the WP memory limit to at least 128Mb. You can add the following code to your wp-config.php file:
- Add it above the line /* That's all, stop editing! Happy blogging. */ You can double-check the WordPress memory limit in WPML -> Support.
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 the problem persists, please open a new support ticket.
Problem: The client is experiencing issues with shipping costs not being calculated correctly on the .de and .com domains of their WooCommerce site. While the shipping costs are displayed correctly on the main .nl domain, switching to German or English translations results in incorrect or missing shipping costs. Solution: 1. We recommend putting the site into maintenance mode and disabling all plugins. 2. Reactivate the plugins one by one to identify if any specific plugin is causing the conflict. 3. If the issue persists, clear the Object Cache. 4. If the problem still occurs, it might not be related to WPML. We suggest consulting with WooCommerce Support for further assistance.
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 persists, please open a new support ticket at WPML support forum.
Problem: The client is trying to use prepaid credits for their main website, but the credits are currently on their build website. The main website is using a pay-as-you-go subscription instead of prepaid credits. Despite following the tutorial for transferring credits, the client cannot see any option to add or remove credits on their 'My Account' page, and the credits previously assigned to the development website are no longer visible. Solution: 1. We clarified that you cannot assign prepaid credits to a website using a pay-as-you-go subscription. For more details, please see our documentation here. 2. To switch back to using prepaid credits, you might find this support ticket helpful: this ticket. 3. We manually assigned the 90k credits to the site ID provided by the client. You should now be able to see the assigned credits in your site's backend under WPML > Translation Management > Tools.
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 WPML support forum.
