I just dont know how to fix it. I uploaded a new skin and container under HOST , I changed my site to that skin, I had done the same on a localhost version of the site as a trial of the (commercial download)skin and all worked well. I had done some edits to elements of the skin which on my localhost version is in default portal/skins/newskin so on FTP I went to the same place on the livesite and although the skin was working ( without the changes) I could not find the files for it anywhere on the server , no sign of them in any of the portals directories. I did not want to leave the new skin as the choice without the amends so on the HOST _SKINS page I selected "REstore Default Skin" and subsequently, although I can log in and use the site whenever I choose HOST or ADMIN and any associated choice from the menu I get the message below. I am guessing I have pointed the cotainer to be something that isn't there..?? Pretty sure it means editing the SQL _But I dont know where to look ( which table) or know how to fix it or even if I should be allowed to go near the site again! ( I was doing SO well on the localhost version...!!!- Honest) THE FOLLOWING POPS UP at any HOST or ADMIN menu choice ><><><><><><><><><>< An error has occurred. DotNetNuke.Services.Exceptions.PageLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Framework.DefaultPage.Page_Init(Object sender, EventArgs e) in C:\Inetpub\vhosts\xxxxx.xxxxxxxxx.xxx\httpdocs\www\Default.aspx.vb:line 554 at System.Web.UI.Control.OnInit(EventArgs e) at System.Web.UI.Page.OnInit(EventArgs e) at DotNetNuke.Framework.PageBase.OnInit(EventArgs e) at System.Web.UI.Control.InitRecursive(Control namingContainer) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) --- End of inner exception stack trace --- <><><><><><><><><><> ANYTHING YOU CAN DO TO HELP? ps i xxx.xxx'd out the full url just in case..( of what I am not sure!) Rob

With FTP, delete the folder of the uploaded skin. DotNetNuke will then revert to the default skin.

hi Joe
Thanks for the speedy reply..
part of my problem, and why I asked it to revert to the default, is that although I could apply the new skin I had uploaded, I could not find the folder for it ,so that I could do the amends I had practiced on my localhost copy.
I even copied ALL the files from the server and searched for the new skin files to no avail.
frustrating cos they must be there as the site was using them!

the site was working ok before I clicked to revert to default skin, it still works fine now except if I try to choose Host or Admin after I have logged in..
 I cant see the folder on FTP so I cant delete it...

any other thoughts?

Thank you

If you can't see the folder via FTP, then either:

• The folder doesn't exist.
• There folder is somewhere else.
• There are some permissions that hide the folder from FTP.

(of course, there could be something even stranger, but I have no idea what that might me.)

I reverted to a backup of the database and can now access the site, so I went to the HOST>SITE tab and selected restore default skin again. same issue. no access to host or admin but rest of site working ok. and in this case no previous skin changes etc. I am worried about using a piece of software that can be broken by selecting a choice on the screen.. any ideas as to why this might be happening?

I assume that you went to the Host, Skins page from where you clicked the "Restore Default Skin" link?

Which version of DotNetNuke?

Which skin are you using as the default skin?

Are you able to view the Control Panel?

Is it that you don't see either the Admin or Host menu entries?


This situation can occur if the default skin to which you are reverting chooses to NOT display the Admin or Host menus.  This is not a fault of DotNetNuke, but it is a conscious choice of the skin designer -- assuming that it's a skin problem.

If you can see the control panel, click on the Site link in the upper right hand corner.  That should get you to the Admin, Site Settings page.  If your admin skin is also set to a DotNetNuke skin, you should also see the Host and Admin menus.

I think that it is best to always keep the Admin skins set to a DotNetNuke skin for safety ... at least while you are in an experimental mode with skins.

If I have misinterpreted, give some more details or even some screen shots so that we can see what you are facing.

hi Joe, thanks fo rthe reply DNN 04.08.04 yes I did click the link default is as far as I can see "noskin" I can not say if selecting site from the top menu would let me see the admin screen but I doubt it as I assume it is simply directing to the same place choosing admin from the normal menu would.( and when the site screen comes up now it seems to be the same skin as if I choose from the normal menu moot point at the moment tho, I reverted to a backup database and went from there, I will never press the revert to default skin again! Still don't see any of the dnn files on FTp but seems that might be an issue with my host not letting me in high enough up the tree. Using the file manager is DNN is frustrating one file at a time but I got the thing up and running and uploaded the changes I had done on my localhost successfully . nice to have friends in high places , thanks for the responses also good to know I learned a bit on the way.. thanks PS in the edit window this looks all nicely formatted.. when it comes out on the forum its all flattened together.. not quite wysiwyg Rob