Problem: The client was unable to translate the WooCommerce Extras section that can be added to single product listings. Solution: We recommended adding the following code to the Custom XML Configuration in WPML-> Settings-> Custom XML tab:
After adding the code, we instructed the client to: 1. Go to the String Translation page. 2. Search for "single-product". 3. Delete the four strings related to the section. 4. Search again for "single-product". 5. Translate the strings. 6. Clear the site's cache. 7. Check if the strings are translated correctly. 8. Add a new test product and translate it to check the issue. We also provided a guide for further information on registering admin strings: https://wpml.org/documentation/support/language-configuration-files/translate-strings-in-wp-options-table/
Please note that the solution might be irrelevant due to being 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 necessary, do not hesitate to open a new support ticket for further assistance: WPML support forum.
Problem: If you're experiencing issues with Astra Pro Custom Layouts not showing on translated pages, it might be due to the fact that a Hook template in Astra can only be active in one specific location at a time. This means that when you translate a Hook template, it will not function in both languages simultaneously.
Solution: To resolve this, you can either create a new hook template in the translated language with the correct content and display conditions, or disconnect the translated hook from the default one and reconfigure its display conditions. Here are the steps to disconnect and reconfigure the translated hook: 1. Open the Translated Hook in the Editor. 2. Disconnect the translated Hook from the default one by following this guide: https://wpml.org/faq/how-to-disconnect-translations-from-the-default-language-page-or-post/ 3. Once the Translated Hook is disconnected, reconfigure the display condition for it, and then update the changes.
It's important to note that this issue is specific to Hooks. For other elements like Headers/Footers or custom layouts, the translated layout should display correctly without the need for separate templates. If this solution doesn't seem relevant or if you need further assistance, please open a new support ticket with us.
