Developer forum

Hi Nuno

I have experienced somerhing similar and it was caused by editing themes. 

After editing a theme, remember to click "preview", otherwise the css isn't rendered. 

I dont know if this will solve your issues, but give you can give it a try 😊

/Suzi

Hi Suzi,

Thanks. That is our workaround, but we have to do it regularly/every day because it gets broken without anybody touching it.

Does it keep happening for you?

Nuno Aguiar

Depends how the server setup is in terms of disk.

I could imagine that 2 or more nodes are trying to write the same file to the same disk - locking the file and causing something to break.

I think something around here is the cause:

Hi Nicolai,

I don't think that's the case. Only files from node1 are copied over to the other nodes when they change; in other words, we don't share the same files across all nodes.

Any other thoughts?

Nuno Aguiar

Complicated setups, complicated lives :-).

I have no clue - you have to trawl through eventviewe and logs etc.

Runtime Dynamicweb does not touch these files and Swift only tries to write them if they are note there of if things changed...

"Complicated setups, complicated lives :-)"

I hear you... and this project in particular threw us a very interesting curve ball...

"Runtime Dynamicweb does not touch these files and Swift only tries to write them if they are note there of if things changed..."

Perfect, that's exaclty what I was expecting to hear. We will try to find some other leads then

Thanks,

Nuno Aguiar

We just ran into the same issue on a single server without a web farm configured. I regenerated the Themes page (making a change, saving, undoing and then previewing the page) which caused a new CSS file to be written. The old one was only 13k,. the new one 63k so a lot of styles were missing. 

Did you ever figure this one out Nuno?

Hi Imar,

I think I did.  We found inconsistencies in the page templates and reported them to DK (below). A quick look tells me that hasn't been fixed yet.

What I found was that the Design pages, which are unique among themselves

Here's what I told them at the time:

• The Branding, Ecommerce Badges, Font collection, Themes and CSS Decorations page templates update the css files

• Consider
  • Branding – lines 340 - 354
    https://dev.azure.com/dynamicwebsoftware/Dynamicweb/_git/Swift?path=/Swift/Files/Templates/Designs/Swift/Swift_Branding.cshtml
  • Ecommerce Badges – lines 24 – 38
    https://dev.azure.com/dynamicwebsoftware/Dynamicweb/_git/Swift?path=/Swift/Files/Templates/Designs/Swift/Swift_EcommerceBadgesCollection.cshtml
  • Font Collection – lines 28 – 43
    https://dev.azure.com/dynamicwebsoftware/Dynamicweb/_git/Swift?path=/Swift/Files/Templates/Designs/Swift/Swift_Fonts_Collection.cshtml
  • Themes Collection – lines 69 - 84
    https://dev.azure.com/dynamicwebsoftware/Dynamicweb/_git/Swift?path=/Swift/Files/Templates/Designs/Swift/Swift_Themes_Collection.cshtml
  • CSS Decorations - lines 18 - 29
    https://dev.azure.com/dynamicwebsoftware/Dynamicweb/_git/Swift?path=/Swift/Files/Templates/Designs/Swift/Swift_Css_Collection.cshtml

• Notice how
  • Ecommerce Badges does not have cssFontPath as all others do (should be after cssPathTheme)
  • Font Collection does not combine the csss in the same order. Not sure if it would matter, but for consistency it should be
    • cssPathEcommerceBadges
    • cssPathTheme
    • cssPathFont
    • cssPathBranding
  • I was not thorough. Other inconsistencies may happen across all 5 page templates

So depending on what page you render after making changes (i.e. Ecommerce Badges), it may "break" your css.

Hope this solve it for you. For us, apparently got mitigated for now, but I can't say it was the silver bullet.

Nuno