Problem: The client is experiencing issues with translating custom strings on their WordPress/WooCommerce site in German, which appeared after updating to Astra ver. 4.13.2 and the latest versions of WPML CMS and WPML String. The affected strings, mostly from functions.php in the child theme, are not appearing translated on the frontend despite being translated in WPML's String Translation.
Solution: We recommend the following steps to address the issue: 1. Temporarily disable all plugins except for WPML, WooCommerce Multilingual (WCML), and WooCommerce to rule out conflicts with third-party plugins. 2. Navigate to WPML → Support → Troubleshooting and run the option: “Show custom MO Files Pre-generation dialog box”. 3. Proceed to WPML → Theme and plugins localization. A popup should appear indicating that WPML needs to generate .mo files. Follow the instructions to generate these files. 4. Ensure that your custom strings are correctly wrapped in gettext calls such as __() and _e(), specifying your text domain. For more details on adding gettext calls, visit Adding GetText Calls to PHP Code. 5. Scan your child theme for new strings via WPML → Theme and plugins localization to register them for translation. 6. Confirm that the text domain 'structurababy' is properly loaded in your theme. For guidance, refer to load_theme_textdomain and Text Domain. Remember to back up your database before making any changes.
If these steps do not resolve the issue or if the solution becomes outdated, 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 problem persists, please open a new support ticket.
Problem: The client has a page originally in Bulgarian with translations in English and Greek. The Greek version has a different structure, and the client wants to edit it in Elementor while keeping it as a translation of the Bulgarian version. In newer versions of WPML, the option to 'Translate Independently' under Language is no longer available. Solution: We advised the client that the 'Translate Independently' option is still available when editing a duplicated page using the WordPress Editor. However, this option does not appear when using different translation editors, such as the WPML editor for manual translations. To resolve this, the client should ensure they are using the WordPress Editor from the default language screen. For more details, we recommended checking the documentation on using different translation editors: Using Different Translation Editors for Different Pages.
If this solution does not apply to your case, or if it seems outdated, we highly recommend opening a new support ticket. Additionally, please 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, you can contact us through the WPML support forum.
Problem: The client is experiencing issues where they are initially taken to the Translation Queue instead of directly to the translation editor when starting a new translation for products. Additionally, they encounter errors such as 'WPML couldn't translate this page' and 'The website is under heavy load' when attempting to translate certain templates. Solution: We have identified that the issue occurs specifically with a certain template and not with other pages or posts. The problem persists even when exporting and importing this template into a different custom post type and attempting to translate it. Since the root cause is unclear, we have escalated the matter to our second-tier support for further investigation. We will provide updates as soon as we have more information.
If this solution does not resolve your issue, or if it seems outdated or irrelevant to your case, 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. Should you need further assistance, please open a new support ticket.
Problem: The client was unable to translate all content on a custom products post type created using Elementor and an ACF gallery field. Only specific sections were available for translation in the WPML Translation Editor, despite trying various troubleshooting steps such as resaving permalinks, updating software, and disabling advanced translation editors.
Solution: 1) Ensure that all Elementor Widgets used are supported by WPML. WPML supports widgets from Elementor and Elementor Pro by default. If using widgets from other sources like 'Ultimate Addons for Elementor Pro', ensure they have an XML configuration for translation. More details can be found here: https://wpml.org/documentation/support/language-configuration-files/how-to-register-page-builder-widgets-for-translation/ 2) Check the translation preference settings for the ACF Field Group. If set to 'Expert', adjust the settings accordingly. 3) Update all WPML plugins to their latest versions. 4) Disable any potentially conflicting plugins temporarily to check if they interfere with the translation process. 5) If issues persist, consider sending the page for translation again through WPML > Translation Management, and then take and translate the job.
If this solution does not resolve your issue or seems outdated, 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 further assistance is needed, please open a new support ticket at https://wpml.org/forums/forum/english-support/.
Problem: You are trying to apply template conditions in the Bricks Theme to display only for specific terms, such as a particular category, but the condition does not apply correctly in the translated templates. This issue occurs with a template for a custom post type post. Solution: If you're experiencing this issue, we recommend you try the following steps: 1. Go to WPML-> Settings-> Custom Fields Translation section 2. Click "Show System Fields" 3. Search for the "_bricks_template_settings" field 4. Set as Copy Once and save 5. Edit the template in the default language 6. Make a minor edit and update it 7. Switch the language using the top admin bar 8. Edit the translated template using Bricks 9. Edit the translated template display conditions 10. Select the translated term and save it We tried these steps on the Asia template, which resolved the issue in this language. Please try the steps from Step 7 in other languages and let us know if that fixes the issue.
Please note that 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.
