Brian, i dont see why. It is a logical result of removing the concept of admin pages. Technically t is not a breaking change

anyhow, check this blog I just wrote, as an example how you can easily make your admin menu accesible to non admins: http://www.erikvanballegoij.com/tabid/36/itemid/22/DotNetNuke-5-Tip-give-non-admins-access-to-any-ad.aspx

DNN Blog | Twitter: @erikvb | LinkedIn:

I agree with John,  it should either be removed or "fixed".

I personally don't see a problem in fixing it since because it would support DNN 4 modules and skin objects.

I would agree with Erik if the admin modules would respect the userroles in  their behavior, but they don't.

An admin module is an admin module and gives any user that can access it Admin rights for that module, so the discusion about other users accessing the admin pages is theorectical IMO (sorry Erik ;-)

If you giva a "normal" user access to one of the exisitng admin pages this user in effect has the same edit rights as an admin.

Here you have to consider how many people are going to leave the admin menus the way they are and use exising DNN 4 modules / skin objects vs those who do change the admin pages.

IMO that will be at least around 25:1

I respectfully disagree with you Timo ... in DNN 5 it is EXPLICITLY possible to give non admin users access to part of the admin menu. Any module checking for "IsAdmin" would hide that page, regardless of actual permissions, which in turn will cause the user to NOT be able to navigate to that page. The issue with the IsAdmin flag is that it doesnt do any permission checking, it only checks based on a location in the menu. This was good when we could safely assume that the only role accessing that page in that menu was the admin role. Since we cannot and should not assume that anymore, the IsAdmin flag should always return False (and let permissions do their work).

Quite frankly, i think this whole discussion is academic. Can someone please give an actual example where a module or skin object behaves differently between dnn 4 and 5 and where this is a major issue.

DNN Blog | Twitter: @erikvb | LinkedIn: