Problem: The client was unable to see the 'Woo Filter by Price' element on the English and German pages of their Avada theme, preventing duplication and translation. Solution: We identified that the 'Woo Filter by Price' element might not automatically duplicate or translate due to its dependency on WooCommerce widget areas or filter logic. Here are the steps we recommend: 1. Ensure the element exists in the original layout and check if it's set to appear based on widget areas or dynamic conditions that might differ on translated pages. 2. If the element is added via a widget, go to Appearance > Widgets and verify if it's present in the language-specific widget areas. 3. If necessary, manually recreate the filter for each translated language. 4. Ensure that all products and categories you wish to filter by are translated into the respective languages. 5. Navigate to the backend of the German version of the Shop template, select 'Edit anyway', and manually add the missing price filter. 6. Use the WordPress editor as recommended by Avada developers for translating layout sections. More details can be found here: Translating Avada Layout Sections.
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 WPML support forum.
Problem: The client was trying to translate the word 'height' to German 'Höhe' under Taxonomy Translation in Label translation. However, the special character 'ö' was not translated correctly and was saved as an HTML entity.
Solution: We initially suggested that the issue might be caused by a third-party plugin or a database collation issue, which should be utf8mb4_unicode_ci. We requested temporary access to the site to investigate further. However, the client managed to resolve the issue by themselves. They found the word under String Translation and changed the translation to a different word to test if it would reflect the change. After confirming the change, they reverted it back to the correct translation 'Höhe'.
If you're experiencing a similar issue, we recommend checking your database collation and ensuring it is set to utf8mb4_unicode_ci. Additionally, try modifying the translation in String Translation to see if changes are reflected correctly.
Please note that this solution might be 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.
