This is a problem that has shown up in a multi-portal DNN installation.  The host settings under, Host Settings, Advanced Settings, Other settings are set with the Skin Upload permissions set to Portal.  This should allow the admin of each portal to upload their own skin.  These settings are done on a deployment server.  For development I have the started kits and source installs available.  When these Host settings are applied to the development server, the admin users can view the folders that are created from uploading a skin (i.e. Skins, Containers, Skins.css, etc.).  The problem is that on the Deployed server the admin users cannot view these same folders.  I haven't been able to find a way to allow the admin users to view the folders.  The need for this is small corrections to files that could be uploaded by reuploading the skin, but would be easier to just change the uploaded files.  The example here is, if the skin contains a javascript file for changing an image on mouse over, but the image needs to be changed or the type of effect needs to be changed, it would be easier to upload an updated javascript file then a skin.  The problem is, if the admin users can't view the skin folders then they can't upload the updated file to the correct folder.  This requires a host user to do the work for them.  i don't think this is a problem with Dot Net nuke, I think it is a problem related to the install on the  Deployed server.  I am hoping someone has ran into this and knows of a setting that isn't correct or some other small thing that I have missed.  If I can change this it will save me, the host user, a fair amount of work.  Thanks in advance for any help. 

just a tipp: I use a DotNetnuke system installed locally on my PC to develop skins, where I can easy access all files.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN