Background of the issue:
I have been doing some updates to both the global elements and custom CSS sheet for this site and can see that these are not being imported to the translated pages. The best example I have is after doing some CSS changes to a search form it is not showing on the translated page (NB I am not wanting to translate the fields of the form, just show the formatting from the CSS). This search is for a chalet and is on the home page - the search feature sits at the bottom of the header image.
Symptoms:
CSS changes are not being imported to the translated pages.
Questions:
Why are the CSS changes not being imported to the translated pages?
How can I ensure that the global elements and custom CSS are applied to the translated pages?
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?
Many thanks for your help.
Kind regards
H
New threads created by Lucas Vidal de Andrade and linked to this one are listed below:
Hi Lucas, thanks so much for all your help so far.
I can now see that we have managed to get the custom CSS stylesheet to pull in... however, it is still not pulling in the details from the Avada 'Options' menu under which there is a 'forms' styling, but I guess you want that to be reviewed separately under the additional tickets, even though it has an influence on this.
Yes, it seems they have a common cause. Let's check how it goes with the other ticket. It seems to me that the issue is that the settings are inconsistent across languages.
