Hi!

I really appreciate DNN's ability to easily create skin/container packages by navigating to:

Host > Extensions > Manage > Create New Extension

and particularly DNN's ability to find and configure the build if the directory containing the skin/container is the same as the proposed skin/container name. Really neat feature! However, it seems this functionality only exists when the skin/container package is located in /Portals/_default and not the individual portal (e.g. /Portals/7/Skins/MySkinName).

Is it really the case that I can only build skin/container packages in this way if they are available host wide?

Many thanks in advance.

Tony

Assigning a skin to a single portal by placing its folder inside the portal folder is a legacy solution, which should be replaced by a database table PortalSkins in a future version.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN

Bruno,

I have a similar issue but in this case, had to apply Chris Hammond's scripts to remove page-level skins by a certain provider.  I don't want to mention names but a site I'm working on has their very good 5.x era skins applied to a 6.x site.  Chris' work at  http://www.chrishammond.com/blog/itemid/2614/how-to-clear-all-page-level-skins-in-dotnetnuke.aspx very much saved loads of time.  With this I'm able to take back over setting host/site level skins. 

However, one of the old skins can't be removed, nor the containers associated with it. No red X appears to uninstall these.

If I try to repair the install, an duplicate Index exception is thrown.

I have to mention the name of a very good company in this context to give more info and I won't do that.  The fault isn't theirs, the fault is not having uninstalled an incompatible version of their product prior to the site having been updated before.

OK, to the question -- short of extending Chris' work and getting into other DNN skin settings in the database, is there an easy way to fully uninstall a skin extension after such an upgrade oversight?

I can give sensitive details in email, again, prefer not to mention product specific stuff in a public post.