Problem: The client was experiencing layout inconsistencies across different language versions of their site. Specifically, the language and currency pickers differed, the margin under the breadcrumb was larger, and the search element had a border on the Dutch version of the page, which did not match the English version. Solution: We identified that the issue was due to different page padding settings for each language within the Avada theme options. To resolve this, we instructed the client to: 1. Go to the Avada > Options > Layout settings. 2. Use the language switcher at the top bar to select 'All languages'. 3. Save the changes to synchronize the settings across all languages, with English as the default. We also provided a link to our documentation for further guidance: Using WPML with the Avada Theme.
Please note that the solution provided might be irrelevant if it's 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, please open a new support ticket in our forum: WPML support forum.
Problem: The client is experiencing an issue where custom colors added in the 'Global Layout' for the 'Global Footer' in one language are not appearing when editing the 'Global Footer' in another language. The client is concerned that custom colors might be language-specific, requiring separate maintenance for each language.
Solution: We recommend checking the documentation on Using WPML with the Avada Theme to ensure that the theme options are set correctly for all languages.
If the solution provided here is not relevant to your case, either because it's outdated or not applicable, we encourage you to open a new support ticket. We also 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 contact us in the WPML support forum.
Problem: The client needed to update the WPML registration key after moving their website from one domain to another. Solution: 1. We instructed the client to add the new domain as a new site in their WPML account and generate a new key at https://wpml.org/account/sites/. 2. We then guided the client to copy the new WPML key. 3. Next, we advised the client to navigate to their WordPress backend, go to Plugins > Add New > Commercial. 4. We instructed the client to unregister WPML from the old key and then re-register WPML with the new key.
Please note that this solution might be outdated or not applicable to your case. If this doesn't resolve your issue, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please don't hesitate to open a new support ticket with us.
Problem: The client wanted to display a custom text when an item is available for backorder and also wanted to change the text displayed when an item is in stock, without showing the quantity available.
Solution: 1. For the custom backorder message not appearing in String Translation: - Navigate to WPML > Theme and plugins localization. - Select the theme and click on Scan selected themes for strings. - Then, return to WPML > String Translation and search for the string again.
2. For changing the 'in stock' text: - Add a new IF statement in the custom function for products that are in stock:
if ( $product->is_in_stock() ) { ... }
- For an example of how to change the 'in stock' text, refer to this Stack Overflow thread.
Please note that the solution provided might be outdated or not applicable to your case. If the issue persists, we highly recommend checking the related known issues, verifying the version of the permanent fix, and confirming that you have installed the latest versions of themes and plugins. If you still need assistance, please open a new support ticket. For further assistance, you can reach out to us on the WPML support forum.
Problem: The client is concerned about the convoluted HTML structure generated by WPML, specifically the excessive classes within the language switcher elements, and is seeking a simpler structure.
Solution: We acknowledge the client's concern and explain that the current structure is maintained for backward compatibility. However, we are open to considering this as a feature request and will register it in our system for potential review and implementation in the future. In the meantime, we recommend creating a custom language switcher by following the instructions in our documentation: Custom Language Switcher.
Please note that the solution provided might be irrelevant if it's outdated or not applicable to your case. If the issue persists, we encourage you to open a new support ticket. We also 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 contact us through the WPML support forum.
