Since I received the message saying that the latest update has applied a minimise CSS option any site I export and publish refuses to call the CSS at all. It publishes fine via the publish option but refuses to work when exporting the site.
Please could this be looked into asap as I have sites I need to upload to my server and this has completely halted my whole workflow.
I have opened up a site file and in the stylesheet on the index page it seems to be misreading the css in as much is it not calling the .webflow command it is just calling the sitename.
*this is happening whether you have minimise css ticked or not.
Hi alexvs, in the short term, rename your css file that normally has the .webflow prefix to the same structure as the currently broken one…so for example where it should be
sitename.webflow.css
change to
sitename.css
Then upload to server and it will display properly. This will get you out of trouble until the fix is issued.
I have issues since this morning too. Not only the exported site isn’t linked to the css anymore, but numerous classes have been altered along the site, such as links losing their ‘no underline’ properties. It shows in the designer and on published site.
For the moment there is the CSS file rename workaround, which is a quick one, and it seems I’m the only one reporting the issue with styles affected. It’s an important thing and I’m sure it will be fixed withing the next hours.
I understand the frustration, I’m a bit scared too. Luckyly I have no client on my back today. I understand the stress if you do. I’m sure they tested it. Since last april, I’ve seen only a couple of bugs after the light redesign of the UI, fixed within a day, and this one today, that I’m sure will be fixed within the day also.
Yeah, I’m sure it will be fixed aswell. Webflow is utterly fantastic as is their service but it sure gives me palpitations when something like this is pushed out live!
If you’re like me, a freelance with many clients, it makes you realize that we’re relying on an online service. It can break. There must be a way to inform our client that sometimes it can break and we can eventually face a short delay in our work. This should be part of our contracts. We can do amazing things with WF but there are some aspects we will never have leverage on.
So was this only on sites being exported not ones hosted with Webflow? Golden29 and vincent, I’m also a free lancer with a decent client base and growing all the time. I’m curious if either of you host many client sites on WF.
Small company here with a few webflow customers, the export bug scared me this morning but I had an email from Webflow support in less than an hour about the workaround.
