Hi;
Just wondering if anyone can help here. I recently installed DotNetNuke 4.9.2 and I wanted to localise the date format. I installed additional language packs (Australia, UK and German).

When I choose any of the languages and try to access my portal I receive following error message:

An error has occurred.
DotNetNuke.Services.Exceptions.PageLoadException: String was not recognized as a valid DateTime.

This happens on every page. I have installed the modules Events and also DNNArticles (not sure if that has to do with it?)

Any help is greatly appreciated.

Thanks
Thomas

Are you using a skin that is not a standard DotNetNuke skin? I would start by switching to a standard skin to see if that solves the problem.

Next, I would check to make sure that the language packs that you installed are valid for version 4.9.2.

You could remove the three additional language packs and see if that solves the problem. If it does, install the language packs one at a time, and see if one of them breaks the site.

Thanks good way of troubleshooting. Yes changing the skin elimited the error. I then looked at my skin to see what the problem might be. I narrowed it down to the snapsis menu that I am using. When I replace the snapsis menu with the default [MENU] token the page loads fine in all languages.

This is how the snapsis menu looks in my html page:

<Snapsis:NavMenu id="nav" DisplayIcon="False" Level="0-2" Type="Hover" runat="server" CacheTabs="False" />

Any ideas how I can overcome the problem? Or any other menu recommendations. I like the fact the the menu uses unordered lists and that the hover displays the submenu vertically.

Thanks
Thomas

Can you post a link to the site, or can you attach your skin file to this thread?

I don't understand how the menu could change something else, but I suppose that's not out of the question.

I would also suggest that you go to the Snapsis forums and ask for help there. 

Solved, I contacted Snapsis directly and there was an error in the evaluation version that have on their website. The error was when checking for the expiry date and has since been fixed.

Thanks again for the quick response