Localised styling not reflected on published site?

I’m encountering an issue where my localized styles display correctly in the Designer but aren’t applied on the live site post-publish. Does anyone have the same issue?

E.g. I was trying to hide certain elements on my danish site, but they are still visible on the published site.


Hi Eva, I had a quick look since I have access to your site-

The problem appears to be that the browser is confused on which language the page is in since the <html> element shows lang=en, and therefore it’s not applying your da-specific CSS.

If I change that, you can see it works;

I’ve seen this happen if you have localization switched on and also have site-level locale set in site settings. since the site-level language setting will override.

Check your site settings general tab when you can** and if you see an en there, remove and republish your staging site. Localized styling should work better.

** Currently this is bugging out for me, and the general tab gives me an infinite loading loop, looks like Webflow is working on something related to the /members endpoint. Hopefully you’ll be able to access it.

2 Likes

Ahhh, that was it :sweat_smile:
Thanks for looking into it!

1 Like

This IS a huge Bug. Thanks for your help. We have to report that to Webflow. How is someone supposed to find this issue?

1 Like

Hey @ianm Webflow knows about it, and it’s mentioned in the field notes.
It would certainly be nice if it put up a big red alert ( or even disabled ) when you’re using localization and did the same in the designer localization settings.

1 Like

This is really a “UI” bug (The feild under webflow setting must be empty when localization = true hh).

Why? For localization webflow auto set lang attribute.

Hope webflow team will fix this with better UI.

2 Likes

It would be great if when Localization is turned on for a project, the overarching language code in the site settings is turned off. Otherwise, this edge case of the site’s language blocking locale changes occurs without a clear way of fixing it.

P.S. Thanks @Siton_Systems for the fix!

1 Like