Here's a fresh new install of DNN 7.2.0. More issues with the Getting Started screen. 

Does anyone at DNN actually use it?

https://www.youtube.com/watch?v=4of_C...

Great question. The actual developers should cover a bulk of that...but that's the beauty of the open source community, relying on others to test and help out (thus I reported the bug here: https://dnntracker.atlassian.net/brow...). Unfortunately, many of the major bugs I run into are some of the more simple errors you'd think would be caught in development. Development on a project this big is a large endeavour, understandable, I just wish DNN would hold a higher standard on quality over quantity of features.


On the problem:

Added runAllManagedModulesForAllRequests="true" to the modules node in the web.config and that fixed the error. Apparently, you need to be a genius to install this stuff.

Also had an error message with FriendlyUrls breaking the Login popup. Solved again by runAllManagedModulesForAllRequests="true". This is the magic that runs DNN.

FWIW if you are needing to set  runAllManagedModulesForAllRequests="true" - its a likely indication that the computer you are running the iis server on may not be fully updated and patched - http://support.microsoft.com/kb/980368.   Its not the only reason this may happen but one worth looking at.

 where possible you should NOT run with the true setting - since it adds a considerable overhead to each page request - that is really not needed.  In particular - with the value set to true - there are handlers getting fired every time a image element is downloaded for example - same for any media - even though in reality there is not point - but the switch is forcing the handlers to fire on each request regardless.

Westa