I am working with a powerPC Mac and dreamweaver. My client has set me up with a child site so I can learn DNN skinning. Using your videos things have gone fairly smooth. I use Dreamweaver for my xml, css, and html files. I use the Mac Finder to package the files and I use DNN to upload the package. When I test it all is cool. Here is the rub. I want to change the CSS file. Now I want to replace the file. I go to the File Manager and the skin files are no where to be found, not in the skins folder or the default folder of the child portal. So I assume I cannot upload the indivual file. My solution is to re-package it and reload. When I try to delete the current package it is not allowed - supposedly in use somewhere. I reset all my Admin and Host site settings and delete all the pages except home and it still says it is in use. My logic tells me to package the files and reload them and the will overwrite the current. Not true - Now there two skins with the same name and different configurations. I don't get it.

My only conclusion is that these files are loaded to parent portal but I don't know why. I am trying to uderstand where these files are and why are they tagged as in use. I want to modify the skins and I don't think it is or should be this hard. I suspect I will have the same issues when I start trying to modify or build containers.

I would love some help.

Thanks,

Larry

There is a skins file under _default if you uploaded the skins as "host" skins.

There is a skins file under each Portal/x directory if you uploaded as "site" skins.

I appreciate the answer and I understand where they are if I had access to the server and was using that file manager. I'm using the DNN file manager and the only _default folders are those in the skins folder and the the containers folder. Neither of these contain any files. The skins and containers I have uploaded are displayed as in use and unable to delte in the skins window. I have been through every folder available to me in the DNN file manager and they simple are not there.

Thanks,

Larry

My personal opinion is that you really need to have free and open access to both your web directory and to your database in order to be able to manage you site effectively.

Typically, you should be able to access your web directory using some sort of file access program, remote connection or ftp. For you database, you should be able to use SQL Server Management Studio (or Express Edition).

If you don't have BOTH of those sorts of access, shope around for a different hosting provider. Otherwise, you'll be constantly frustrated.

I agree with Joe, but if it is not an option, I would suggest installing DNN on a local computer and then when the skin is complete all you have to do is upload it once to your live website, you will find it's much quicker to work on a local computer rather than the live website when creating a DotNetNuke skin.

These tutorials walk you through how to install DotNetNuke with a barebones installation of Windows:

• How to install DotNetNuke to Vista
• How to install DotNetNuke 4.5 to Windows XP Pro with IIS
• How to install DotNetNuke 4.5 to Windows XP Home (Using VWD)

I agree with Lee, too!