Hello, I attempted to update our test enviornment from 10.02.02 to 10.02.05. After the upgrade, we now get display issues which I'm going to attribute to CSS. When I compare our production and test sites, the CSS stylsheet that "wins" for a common markup tag no longer is our xcillion skin.css document. Rather what I'm seeing happen is either a reset.scss or bootstrap.css gets selected. Even the Persona bar has been visually corrupted. so much so that the "feet" icon do not show up on the upgrade page anymore (so I can't use that page to upgrade to 10.03.03).
This issue should be fixed by 10.2.5 (it was one of the reasons for doing that release). You have have a cache issue, try to "hard reload and clear cache" or if the site is behind something that may cache resources (like cloudflare), you may want to also clear cache there.
Thanks for the pointer. After doing the hard refresh the visual problem with the upgrade page went away, so I was able to initiate the upgrade to 10.03.03. After the upgrade was complete, the issue I was describing with my skin.css getting overriden also seems to be fixed. So my portal is looking normal again.
Should I approach my upgrade in the production environment any differently? Or is it just a matter of doing the hard refresh. I'm still confused by 10.02.05 having display issues above and beyond just the persona bar.
Well, you should not have needed to clear the cache so it is hard to really tell you if you will need to do that or not on other hosting instances. But if you see the styles broke right after an upgrade, very often it is because of some level of caching.
These Forums are for the discussion of the open source CMS DNN platform and ecosystem.
For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:
Awesome! Simply post in the forums using the link below and we'll get you started.