Hello,

We have problems in installing new 5.1.2 site. The problems are:

1. Default Language missing

2. Site Setting page looks strange. Some labels, help texts, options are rendered as blank. This error will remain even after adding English (United States) without setting fallback language as the default language.

The problems exist in every new 5.1.2 sites installed in our Windows XP/Vista/2003 test environments. The virtual directory name for these installations we used are "Portal".

This morning one of our team members installed a new 5.1.2 sites on the same Windows 2003 test environment. And he used Portal2 as virtual directory name rather than Portal. All of a sudden, the problems were gone. Site Setting works perfectly as it should be. Later, he install a new 5.1.2 instance in Windows XP with the "Portal2" virtual directory name. The problems disappeared too.

Does this show that some virtual directory names will result in faulty 5.1.2 installations? Is there any limitation on choosing a DNN virtual directory name?

BR/shortie

I ran into #2 (but not #1) and it turns out it was because the site was running on a server with ASP.NET 3.  It worked fine on ASP.NET 3.5 server.  Upgraded to ASP.NET 3.5 on the first server and the site settings labels and help text showed back up.  I filed a bug in Gemini but it was labeled as won't fix because starting in DNN 5.2 ASP.NET 3.5 sp1 will be the minimum requirement.

Cliff,

unfortunately, identifying the cause of your issue is not trivial. you can validate whether it is caused by the Skin / menu by renaming skin and container folder. the system will fall back to default skin.

Also, please validate upgrade logs inside /providers/dataproviders/sqldataprovider folder for errors reported.

if the admin modules are present, you might adjust publish permission (in admin:: extensions) and add it to appropriate pages again.