Problem: The client was unable to translate the URL attribute of the Avada Title element in WPML's Advanced Translation Editor (ATE) due to a missing or incorrect attribute name in the XML configuration.
Solution: 1. We advised the client to add or update the XML configuration for the
fusion_title
shortcode in WPML settings to include the URL attribute. The correct XML block should look like this:
2. After saving the XML configuration, the client needed to make a minor edit to the original page and update it to trigger the changes. 3. Reopen the page in ATE and use the Search Source bar to locate the URL field. 4. If the URL field still does not appear, check the page source to confirm the exact attribute name used in the shortcode.
If this solution does not resolve the 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: After translating ACG post taxonomies in Avada, the layouts no longer apply to the pages. Solution: First, ensure you have followed the steps outlined in the Avada documentation for translating layout sections, which can be found here: Translating Avada Layout Sections. It's important to note that conditional layouts should not be translated directly. Instead, create a separate layout for each language and set up the conditions for each one. After setting up these layouts, you can proceed to translate the individual sections within each layout as needed.
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 problems persist, please open a new support ticket.
Problem: The client experienced an issue where installing WPML reset the Avada global settings, linking them to a secondary language instead of the default language. Despite attempts to reset and reconfigure, the settings continued to default to the wrong language, causing frustration and repeated site recoveries. Solution: We advised the client to follow the steps outlined in the Avada documentation on setting different global options with WPML, which can be found here: https://avada.com/documentation/how-to-set-different-global-options-with-wpml/. Additionally, we suggested creating a staging site to safely test and configure the settings without affecting the live site. This approach allows for adjustments and troubleshooting in a controlled environment. If issues persist, importing the configuration as initially done by the client is a quick method to revert settings to the desired state.
Please note that this solution might be outdated or not applicable 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 the problem persists, please do not hesitate to open a new support ticket at WPML support forum for further assistance.
Problem: If you're experiencing issues where the alert element in an Avada form does not inherit the properties of Avada global settings after a successful form submission, it might be due to the theme options not being configured for each language. Solution: We recommend checking your Avada theme options to ensure they are either configured per language or shared across all languages. This is crucial as the Alert element styles likely use Avada Global Options which might not be configured for the English language, causing the form success message to revert to default styling. Please make sure to create a full backup before making any changes. For detailed guidance, visit the following documentation: How to Set Theme Options for Languages in Avada.
If this solution does not apply to your case, or if it 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. Should you need further assistance, please do not hesitate to open a new support ticket at WPML support forum.
