Problem: The client is experiencing issues translating Avada Fusion Elements into Chinese using WPML, encountering alerts about encoded fields. Additionally, there are concerns about the correct method to translate content and manage layouts across different languages.
Solution: 1. For translating menus, especially with advanced options like Avada's mega menu, it's recommended to translate the menus manually to ensure correct settings in each language. Alternatively, WPML > WP Menus Sync can be tested, but manual adjustments might still be necessary. 2. In the Avada Library, ensure that the admin language is set to English to view the original content settings. If using WPML > Translation Dashboard, set each content's specific translation method accordingly. 3. To switch to the WPML Translation Editor, access it via the right sidebar in the WordPress Editor while editing the original content. This allows for text-only translations, maintaining layout and design across languages. 4. If using the WordPress Editor for translations, ensure to set Avada Theme Options manually for each layout in each language. Use the 'Translate independently' option if duplicating content to prevent overwriting. 5. For issues like excerpt length, which might not be directly related to WPML but to Avada's handling of Chinese characters, consider testing on an Avada setup without WPML to confirm.
If these steps do not resolve the issue or if the solution seems outdated or irrelevant to your specific 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 problems persist, please open a new support ticket at WPML support forum for further assistance.
Problem: The client is working on translating a site into traditional and simplified Chinese and plans to use Google Fonts Noto Sans TC and Noto Sans SC. However, Google Fonts do not load reliably in mainland China due to most of the fonts.googleapis.com and fonts.gstatic.com domains being blocked, resulting in slow loading or broken text rendering. Solution: We confirmed that Google Fonts indeed do not work reliably in China. To ensure fonts load properly for a Chinese audience, we recommend self-hosting the fonts. The client has already downloaded local .ttf versions of Noto Sans TC and Noto Sans SC, converted them to .woff2 format using Google Webfonts helper - A Hassle-Free Way to Self-Host Google Fonts, and uploaded these as custom fonts in the Avada theme. This approach is suitable for audiences in China.
If this solution does not resolve your issue or seems outdated, we 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, feel free to contact us through the WPML support forum.
Problem: The client installed WPML CMS on a staging site and migrated it to a live site, resulting in a WPML alert about the URL change. The client was unsure about the correct steps in the migration wizard, specifically whether to start with 'Yes' or 'No' and how to handle the site key registration and unregistering process. Solution: 1. In the WPML > Translation Management, select "Yes/This is only a copy - original site is still running" for the first prompt. 2. For the second prompt, choose "No/You will need to assign credits or set up a pay-as-you-go plan for this site to use automatic translation". 3. Continue using the staging site's WPML site key for translations until you are ready to deploy to the live site. 4. Upon deploying the staging to the live site, expect a "site key mismatch" warning. Then, perform the following steps: - Log in to WPML.org > My Account > Register WPML on your sites - Delete the staging site key if no longer in use. - On the live site, navigate to WP > Plugins > Add new > Commercial Tab. - Click "Unregister WPML from this site" and then "Register WPML" again using the production site key. This process ensures the live site is correctly registered with WPML, and future translations will utilize the correct site key.
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 at WPML support forum.
Problem: You are trying to translate the user notification of an Avada form and encountering a critical error when translating the 'Register Course' Avada Form. Solution: We recommend the following steps to address the issue: 1) Ensure you back up your site. 2) Add the following code to the functions.php file of your theme:
add_action('init', function () {<br /> if (!is_admin()) {<br /> return;<br /> }<br /><br /> $option_name = 'icl_sitepress_settings';<br /> $settings = get_option($option_name);<br /> if (isset($settings['translation-management']['custom_fields_attributes_whitelist'])) {<br /> $settings['translation-management']['custom_fields_attributes_whitelist'] = null;<br /> update_option($option_name, $settings);<br /> error_log("Successfully nullified custom_fields_attributes_whitelist.");<br /> } else {<br /> error_log("custom_fields_attributes_whitelist not found in settings.");<br /> }<br />});
3) After adding the code, visit the backend of your site to ensure the code executes.
If this solution does not resolve your issue or seems irrelevant due to updates or specific circumstances, 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 problems persist, please open a new support ticket at WPML support forum.
Problem: You are managing translations in WPML > Translation Management for Pages and Avada Layout Sections. You noticed that the homepage status has not changed for a few days and are unsure whether to send it for translation again and which option to select. Additionally, you are seeing items in the WPML > Translations Queue. Solution: The status you observed for the homepage indicates that the page is not fully translated. We recommend you go to WPML > Translations and complete the translation by translating all segments and saving. Alternatively, you can send the page to automatic translation and select the option to overwrite existing translations. This should resolve the issue of seeing items in the WPML > Translations Queue as well.
If this solution does not apply to your case, or if it seems outdated, please check the related known issues and confirm that you have installed the latest versions of themes and plugins. We highly recommend opening a new support ticket if the problem persists. You can do so at the WPML support forum.
Problem: The client is using WPML with the Avada theme to translate the main menu on their WordPress site. The translated menus are displaying on two lines on desktop, indicating a potential padding adjustment issue. Solution: We recommend trying the following steps: 1. Shorten the translated menu items: - Navigate to Appearance >> Menus - Select the translated (secondary language) menu - Edit the "Navigation Label" to make it shorter if possible - Click Save Menu
2. Adjust padding/styling per language using Avada theme options: - Take a backup of your site theme options first for safety reasons. - Set the language switcher (in the admin top bar) to the secondary language. - Go to Avada >> Options. - Adjust padding or CSS under Custom CSS or relevant menu settings. - Click Save Changes. - Repeat for each language as needed
If these steps do not resolve your issue, or if the solution seems outdated or irrelevant to your specific 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 further assistance is needed, please open a new support ticket at WPML support forum.
