Are there any downsides to just deleting the Portal.css in a Portals root directory when it's not needed?

We generally create custom skins for most of the sites we build and put all the css in the skin.css so I rarely have any use for the Portal.css. But recently, when running the SEO Toolkit, I noticed that for new installs of DNN, the Portal.css was a 4.92kb file that had a bunch of styles used for styling the default template home page.

It looks like if I delete the Portal.css file from each of the Portal directories where it's not needed, it no longer is added to the rendered HTML for a page (which is ideal). I just want to make sure that won't cause any unexpected problems.

---

David O'Leary
Efficion Consulting

Because the portal.css will just be replaced on upgrade, I use the 40FINGERS StyleHelper Skin Object. It allows you to remove .css files from loading (among other nice features.)

HTH

---

Chris AFAIK upgrades only replaces portal.css under Portals/_default directory. I use portal.css to style module templates where needed. For example. Changing skin may require you to update new skin's css file to handle module template css. However portal css is static.

---

Or-Rouge Team Or-Rouge
Personally recommend Hostgator for hosting single or multiple DotNetNuke Websites.
DotNetNuke Tips and Tutorials
Install DotNetNuke to Godaddy root
DotNetNuke Türkçe Hakkinda Hersey