You are right, removing some of the default skins does not always work.

In what version of DNN do you have this issue?

---

OK, I have found a workaround, but you need to changes something in the database.
Also there's a good chance that DNN will reinstall these skins on upgrade..

It seems these Skins are not uninstalled because they are marked as System packages.

In the database there's a table named SkinPackages, this contains all the installed skins.
(the ones that where installed via the installer)

You will find a Packageid for every skin / container skins and containers and a corrosponding record in the Packages table.
There the packages of the default skins have IsSystemPackage=True.
When you change this to False and restart DNN, you can uninstall the default skin packages.

Do not uninstall the default package, and make sure you change the fallback skin I mentioned in a previous post to a skin that is still installed or don't uninstall the gravity skin.

 

---

IMHO, whenever DNN provides a new default skin, it should remove system flag from previous default skin and delete should only be prevented
- skin being used in Host Setting
- skin being used in Site Settings (PortalSettings)
- skin being used in TabSettings
- skin is current Default Skin
- same for containers, in addition it should not be used for individual modules (i.e. in TabModules).

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN