Problem: The client is experiencing 404 errors on the order confirmation page and the endpoint 'order-paid' in translations. The issue temporarily resolves by saving the permalinks but reoccurs the next day. Deactivating the WPML String Translation plugin stops the error. Solution: If you're experiencing this issue, we recommend you follow these steps: 1. Navigate to WPML → String Translation and ensure that the endpoints are set to their original English values (not translated). 2. Save the permalinks again to resolve the current 404 errors. 3. Return to WPML → String Translation and translate the endpoints as needed. Important: After translating the endpoints, please do not save the permalinks again. We are aware of this issue and are actively working on a permanent solution.
We already have a development ticket for this problem and are actively working on a permanent solution in future releases.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. If the problem persists, we highly recommend opening a new support ticket here.
Problem: The client is experiencing issues with the automatic translation of new WooCommerce products from Dutch to English or German using WPML. Despite updating the credit card information for the pay-as-you-go service, some parts of the products are only partially translated, requiring manual intervention to complete translations.
Solution: We recommend the following steps to resolve the issue: 1. Reconnect to WPML.org: Navigate to WPML → Support and re-authenticate or re-login to ensure your site is properly linked to your WPML account and credits. 2. Check Translation Credits: In WPML → Translation Management → Automatic Translation, verify that you have available credits and there are no warning messages about your pay-as-you-go plan. 3. Clear Caches: Clear all caches if your site uses caching plugins or server-side cache, as old cache can interfere with translation jobs. 4. Translation Jobs Review: In WPML → Translations, check if jobs are assigned to local translators (not automatic) and reassign them for automatic translation. 5. Test Automatic Translation: In WPML → Translation Management, select a few new products and send them for automatic translation. After a few minutes, verify if all fields are fully translated. 6. Ensure all custom fields and product attributes are set to be translatable in WPML → Settings → Custom Fields Translation.
If these steps do not resolve the issue, it may be necessary to manually inspect product translation jobs for inconsistencies, especially focusing on which specific product fields remain untranslated and whether they are configured for translation in WPML settings. Additionally, ensure that the site is correctly registered and showing a connection with the correct WPML.org account.
If the problem 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. Should these steps not provide a resolution, please open a new support ticket for further assistance at WPML support forum.
