Hi Lee,

Having a few problems that I hope you can help with, but first want to say that I am really enjoying your website, and it's excellent, useful tutorials. I appreciate the effort that you have put in.

As a developer, I have been working extremely hard trying to learn as much as I can from your website about DDN so that I can build some new portals for clients.

My problem is that I just messed up my main portal (0) while attempting to install the red leaf container. I am sure that it is something I did, and not your container.

First my site showed an error. Now my default page comes up, but will not let me log back in so that I can change back to the prior container. I just learned the value of a back-up! Fortunately, my other 6 portals are fine. I just don't want to have to start over, as I have the FCK editor and house menu installed already. Plus, I debugged http://www.rightontop.net (the site giving me trouble) down to 2 validation errors (down from 38) just last night.

I do have an original backup of the initial installation. Could you tell me which files would have been affected. I installed the container while logged in as admin. I am hoping that I can over-write the corrupted file.

Thank you very much

George Hummer
george@rightontop.com

Hello,

Glad to hear you have found the tutorials useful, that's always good to hear.  The simple red leaf container should not cause any errors within your portal so I am unsure what has happened here.  However, you may be able to fix this by navigating to your DotNetNuke installation files using FTP and going to the folder where you installed the simple red leaf containers in your portal.  If you delete that folder DotNetNuke will no longer be able to find the container file and will use the default DNN blue container.  You will then need to go into your portals site settings and select a container to use.

(This works for skins, but I have not tested it with containers)

A tip when testing a new skin or container is to just apply the skin or container to one page, this way if an error occurs you can just deleted the page without causing problems across your entire portal.

Hope this helps, thanks,

Just had a thought, are you using DNN 4.4?

Have installed the missing DLL files for this version of DotNetNuke? Have a read of this article: How to fix the [DROPDOWNACTIONS] token bug in DotNetNuke 4.4.1

If this is the problem you will not need to delete the container files, you just need to upload the missing DLL files.

Thanks,