..it happens. When you get 404 errors for all pages on fresh installation, just change <modules> in web.config to <modules runAllManagedModulesForAllRequests="true">. Thats it.
This blog is about life of true developer. Projects, coding, testing, ideas, interesting customers from around the world - all these events make life of developer interesting and active. In this blog i will try to describe my experience. Hope it helps someone :)
Thursday, 11 September 2014
Friday, 17 January 2014
DotNetNuke 7.2.0: Prevent "Getting Started Page" for SuperUsers
In DNN 7.2.0 has been added "Getting Started Page" for Super Users. It looks like this:
So, "Getting Started Page" appears on the next conditions:
- Current User is SuperUser.
- Current TabID is equal to the param "GettingStartedTabId" (for current Portal) from the "PortalSettings" table.
- Setting "EnableGettingStartedPage" from the "HostSettings" table should be equal "True".
You can hide this message in few ways:
- Just tick a checkbox "Don't show this again" at the bottom left corner. But this will hide "Getting Started Page" for current SuperUser only, and will show it for other SuperUsers.
- Change "EnableGettingStartedPage" setting from the "HostSettings" table to "false". After this change, "Getting Started Page" will not be displayed for all SuperUsers.
- If you like to change it for all future installations you plan to do, then you can edit "Install/DotNetNuke.install.config.resources" file in your installation package. In this file you can find "<EnableGettingStartedPage>True</EnableGettingStartedPage>", what is very easy to change to "False".
BTW: I have not found a way on how to change "EnableGettingStartedPage" setting from the "HostSettings" at the FrontEnd.
Subscribe to:
Posts (Atom)