Problem: The client needs to display different decimal separators for invoices in English and German on a WooCommerce site, both using the Euro currency. The client found the necessary string for the decimal separator but it was registered and locked, preventing changes. Solution: 1. Set the default decimal separator in WooCommerce to a period (.) for English, which is the site's default language. Navigate to WooCommerce → Settings → General → Currency Options and set the Decimal Separator to a period (`.`). 2. To adjust the decimal separator for German, use WPML's String Translation. Go to WPML → String Translation and click on the Admin Texts Translation link here. Search for `woocommerce_price_decimal_sep`, check the box, and click "Add to String Translation". 3. In WPML → String Translation, search again for `woocommerce_price_decimal_sep`. For German, set the translation value to a comma (`,`), and leave the English version as is.
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 here.
Problem: The client is trying to translate a text widget in Elementor using the Classic Translation Editor (CTE) and is concerned about the support and compatibility of CTE with the Advanced Translation Editor (ATE). The client noticed that translating with CTE adds an HTML paragraph to the text and is unsure if this behavior is expected. Solution: We confirmed that when translating with CTE, it is expected behavior for an HTML paragraph tag to be added by Elementor, as this tag usually already exists on the original content. We have confirmed this on a test site running only Elementor. We also clarified that CTE and ATE are not fully compatible because they function differently. Translations done in CTE cannot be migrated to ATE due to different system architectures, including translation memory. However, clients can switch back from ATE to CTE and continue using their translations. If switching from CTE to ATE, translations need to be redone because ATE has its own translation memory. For more details, visit how WPML keeps track of your translations and switching from classic to advanced translation editor.
If this solution does not resolve your issue or seems outdated, we recommend opening a new support ticket. We also highly suggest 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 created a WordPress Archive using Toolset and translated various elements using WPML. However, the page layout appears different between the English and German versions, despite identical settings in Astra for both languages. Solution: We recommended the client to clear all caches, especially the CSS cache managed by WP Rocket, to ensure that all styles load correctly. This approach helped align the layouts in both languages.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, please visit our known issues page, verify the version of the permanent fix, and ensure you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists.
Problem: If you're experiencing an issue where clicking the "Save & Close" button while translating a page results in endless loading and doesn't return you to the Pages list, even though the translations are saved correctly, you might notice errors in the console log related to React or a 500 Internal Server Error for admin-ajax.php. Solution: We recommend you try the following steps: 1. Edit the page in the default language. 2. Copy the page ID from the URL browser bar. 3. Navigate to WPML -> Packages. 4. Search for the ID. 5. Delete the package. 6. Update the page in the default language. 7. Re-translate the page.
Please ensure to back up your database before performing these steps.
