This thread is resolved. Here is a description of the problem and solution.
Problem: The client is experiencing issues with global element updates not being imported correctly, such as background colors, and has questions about the 'post types translation' settings for global styles in the Avada theme. They are also concerned about notifications for updates to strings. Solution: We recommend ensuring that the settings are consistent across all languages. If the settings are set differently for each language, WPML will maintain these differences. To synchronize the settings, you can import your settings from one language to another, such as from EN to FR. This process will overwrite all old options with the imported settings. For detailed steps on how to import theme options from one language to another, please visit https://wpml.org/documentation/theme-compatibility/using-wpml-with-the-avada-theme/how-to-set-theme-options-for-languages-in-avada/#how-to-import-theme-options-from-one-language-to-another. Moving forward, we suggest changing the settings for 'All Languages' to avoid similar issues.
If this solution does not resolve your issue or seems irrelevant due to being 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 issues persist, please open a new support ticket at WPML support forum for further assistance.
This is the technical support forum for WPML - the multilingual WordPress plugin.
Everyone can read, but only WPML clients can post here. WPML team is replying on the forum 6 days per week, 22 hours per day.
Hi Lucas, I don't think it's caching, I had issues with the translation in all sorts of ways prior to the latest update: showing the dots to the translation - which now shows as a yellow line (this was so a couple of updates earlier). Also the screen was jumping around (I have a screencast of this if you want to see it) so something has been awry for a while. I use Firefox if that is of any relevance. All of this seems to have resolved with this latest update thank goodness.
I am still having issues with global element updates (background colours not being imported being a major one). There is a setting in the fields for: 'post types translation' > global styles' which is currently set to translatable. Should this be set to untranslatable, which would bring in the latest changes I make to the global styles for Avada on the backend?
Finally, I also have had notification for updates to strings being needed - do I need to just do this every now and then to update... would this have an influence?
Regarding the global styles. Please make sure to have a full website backup and follow these steps:
1. Go to WPML > Settings and mark the option you mentioned (global styles) as Not translatable;
2. Make a small change to a global element and save;
3. Update its translation;
Let me know how it goes. When options like this are set to Not translate, it's expected that the values stay consistent across languages.
If it works for the element, please follow steps 2 and 3 for other elements that show the behavior as well.
No it is still not updating in either the Avada 'library' or the 'options' or global elements, I'm attaching screengrabs to show where these are in the Avada breakdown, but what does seem to be universal is when it is global aspects of elements.
Thanks for sharing the results. I checked your settings in Avada and noticed that they are inconsistent between languages. Check the images attached.
Please make sure, when changing the language between EN and FR inside the Avada options, that they're consistent.
If that still doesn't solve the issue, please give me a concrete example of how I can check the error and test it myself on the Front End. Thanks in advance.
Hi Lucas,
Thanks very much, yes they are inconsistent because I have changed them on the english side, but it is not automatically updating on the French side.
This is exactly the problem. I'm sure I shouldn't have to make those changes twice - shouldn't there be somewhere in the WPML settings that says this is not translatable (like the CSS) thus it will be brought into the french side from the UK side.
The problem is that I don't know where to find this in the WPML settings. Given that WPML is the 'go to' translator and these settings are regularly updated by an Avada user, it must be somewhere - I'm hoping you can find out as I believe this will solve all the issues.
So, the settings must be the same across the different languages. Since you have set them differently, WPML "understands" that this is what you want to have as a final result. It's expected that when you change the settings for one language, it only changes it for that language.
By importing the settings, all old options will be overwritten by the importation. That's a quick and simple way to achieve what you want. In the future, I recommend that you only change the settings for All Languages, as it's also explained in the link I sent.
Thank you so much for this helpful advice. I have taken the steps you said and understand the process. Now that the settings are the same on both languages (effectivey re-set) if I need to update the global settings can I do this on the English side and it will update on the french side automatically - or do I need to always update the global settings whilst in the 'all languages' mode.
