Strange behaviour!

Rate this topic:

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.

Author

Messages

Declan Ward
<20 Posts

Posts:3

09/08/2004 4:58 AM
Last night I purchased and installed CSSSkins. I have a site on my local mahine with many tabs setup for showing different shins and modules developed. For example using skins from the skinning competition I added a tab for DNNMachine, DNN Africa, DNNVivo etc. Each tab had the appropriate skin assigned in the Tab Management tab. After installing your sample skins my settings have been lost. What has happened is that your sample Aqua Blue has become the default and all my tabs show this. However they show the containers from the skin that was originally set on the tab. If I look at tab management the "Tab Skin" setting has been reset to "Not Specified". If I try to change this the change is not saved. My Host Settings have "Not Specified" for each: Host Skin and Admin Skin The only thing I did was use the CSS Editor to change the width of the CURRENTDATE as it was going to 2 lines. I then clicked Save Combined Stylesheet. Has this caused my problem? I have deleted the combined css file to no avail. This suggests saving a combined sheet was not the cause of my problem. Can I uninstall CSSSkins to try and get back to where I was, and no I did not copy C:\DotnetNuke before installation - Doh!!! I am using DNN 2.1.2 Any help appreciated. Declan

John Mitchell
<500Posts

Posts:355

09/08/2004 11:12 AM
Hi Declan, As you said, that sure is strange behaviour! I haven't heard of this problem before but I'll try to recreate. It sounds like you had all the individual skins assigned at the Tab level. Were they all skins that were uploaded to the Host portal using the File Manager under the Host menu? CSS Skins doesn't do anything in the Database and only “rides on top of” the core skin engine in DNN 2.1.2 so I'm at a loss as to how the settings could have been changed. Same with the CSS Editor, as you discovered the Combined Stylesheet is the only difference there. How did you install the sample Aqua Blue skin, and where/how did you apply it? Do you see all the skins still available under Admin>Site Settings in the Portal Skin & Admin Skin dropdowns?

John Mitchell
<500Posts

Posts:355

09/08/2004 11:15 AM
Oh, to answer the main question: The only thing you need to do to stop using the CSS Skins engine is apply a skin that is not using it. If you can't change the skin settings, then just delete the offending skin and let DNN go back to using the “default” skin, then you should be able to update again if it was a CSS Skin that was causing the problem.

Declan Ward
<20 Posts

Posts:3

09/08/2004 2:32 PM
OK, so I don't know what caused the problem! What I have done is deleted all skins using Skins on the Admin tab. I then deleted all entried in the DNN Skins table referring to these skins. I then loaded the skins that came with CSSSkins again. It seems to be working fine now. -dw

Please Register to post a reply. Another benefit of registration is the ability to subscribe to and recieve notifications of new posts.