Hi Timo,

Thanks for the suggestions. A separate skin for admin pages is a solution, but AFAIK would involve manually configuring all admin pages to use it. I'd like to avoid that if at all possible as there are quite a few of them and I have development, staging and production sites to consider.

Your skin object is useful (I've often had to add bits of code to the skins to attach classes based on page name, user roles etc), but I don't think it is able to dynamically add a class depending on whether a module is for content or administration ... or have I missed something?

Cheers,

---

Paul Taylor

DotNetNuke, ASP.NET and SQL Server Development

The new flexibility of DNN 5 makes it kind of impossible to "know" what's an admin skin and what's not.
Even admin modules don't really exist anymore as with the right settings anyone could use them.
So I'm guessing this will not be re-added to DNN (although that's not my call at all).

I do see now that an admin page could be defined as a page where only admins have edit and view rights.
I'll consider adding support for filtering on Edit roles too, which might be a valid addition for some.

---