Hello All

We are still designing skins without the manifest as we have not become proficient at the manifest thing.  DNN Creative even recommended that it was OK to use Legacy designing if you are not using the skins for publication on the SnowCovered site.   All skins we design are for our own or client consumption.  This all being said.....

When we create a skin and upload it, everything works fine in DNN 6.  We have to jump through the normal hoops... meaning we need to choose skin or container on the host install as opposed to if we had a manifest.  That stuff aside we are able to install our skins and they work well.  However, if we try to uninstall a skin we have installed it does not fully uninstall.  It will uninstall the files but for some reason in DNN 6 it leaves the skin name in the dropdown list of available skins in the Page Settings area.  Does anyone know why this is happening and how we can fix it, short of learning the manifest process?

This being said, let me also ask some more about the manifest process.  In the past we could get DNN to create a Package after we uploaded a skin and it would output the skin with the manifest.  Our legacy skins do not have the button that shows create package.  I am not sure if this is an issue with DNN?  Any thoughts???


Thanks for all the help and cheers,
D. Kyle

the skinning page is also a good read - http://www.dotnetnuke.com/Resources/Wiki/Page/Skins.aspx ,, in the tutorial part 4 covers packaging.

---

Buy the new Professional DNN7: Open Source .NET CMS Platform book Amazon US