Hello There I am not sure if I posted this in a different thread but I am having a lot of difficulty tyring to tweak a skin that I purchased from a third party vendor. When I was working with DNN 6 and DNN7 I could install the skin or simply save the skin in dnn's file system portals/_default/sins and tweak an ascx file as needed so I can further customize the skin beyond what the third party vendor had done.

Since DNN 7 I have jumped over DNN 8 and installed DNN 9.1.1 and purchased a skin file from dnn store figuring I could use their skin as a template and just tweak some ascx files as needed. When I installed Doris theme via DNN 9.1.1 extensions it worked as the vendor intended however the files that were packaged in the zip file never showed up in DNN's file system when I used my ftp client to browse to portals/_default/sins or portals/_default/containers. It just didn't exist. DNN 9.1.1 default skin showed up in the skins and container folders but not the premium skin I purchased and installed.



I also deleted the default skin folder that came with DNN 9.1.1 which was Xcelion I think was the name of that skin and did this in both the container and skins folder but the graphic of the default skin still was there and when I clicked to use that skin it appeared to still be usable though the actual folder containing all these ascx files were now gone.



I guess the question I have than is this. Is there anyway by which I can tweak ascx files found in the skin packaged in the .zip file and have DNN recognize it and show those changes. Can I simply copy the premium skin files via ftp into the portals/_devault/skins area and be able to play with the ascx files and have it be reflected in DNN 9.1.1 or is it that once you install the skin into the extensions area that it only reads the skin within the database instead of the old way of doing things with the file system.



If DNN now only reads the database to find out if skins exist instead of the actual folders and files you get when you install DNN than can you point me to a tutorial or info as to how I could take a premium skin and or container that goes with that skin, tweak it by editing the ascx file in visual studio and then put it back into DNN 9.1.1 with my customizations and have DNN 9.1.1 accept the change and see it refelcted on my site as I would like to not have to contact the vendor for customizations outside their out of the box capabilities.



For example I would like to take the skin object logos and move it to a different part of the skin so it is over a colored background area that the menu system sits in opposed to having the logo above the menu bar as it happens to be out of the box. Changing logo positioning is not something the skin developer gave me control over but this is the reason I would like to be able to tweak premium skins so I can rearrange skin objects that are found in the ascx files a bit here and there so I can maybe have the log in skin object at the footer of the skin and the header instead of the header alone.



Anyway these are just a couple examples on what I would like to be able to do with skins installed in DNN 9.1.1 so if you have any idea of any information of how I can play with the skin file and reupload it, re-register it, etc... so that modules that are lying on the skin doesn't get messed up because of the re-registration that would be great. Ideally tweaking the file and pushing it up ftp would be the most efficient way for me like I did in DNN 6 or DNN7 but it seems to me like those days maybe over however if I can get my hands on the new way of revising skins that is what I need for my client.



Bo

Nothing has changed in terms of skin location on DNN 9.1.1