Great module Rob, but I have a question about it if you use it a lot.  When exporting a site using it as a template, is there a way to make the template "carry" the module settings for Buckley's module?  It seems to loose the settings in a template export.

Clay

I don't actually use his toolbar myself for reasons described below and also because of the risky long-term viability of control panel replacements, but it certainly sounds like it won't export settings.

The foggy line between Admin users and Content editors is an ongoing problem when one tries to set DNN up for a client. The Admin role is too powerful, yet is needed in order to carry out basic content editing tasks such as deleting a file.

I would really suggest you attempt to obtain your desired functionality without assigning admin rights to users. It's not always easy, but most things can be achieved using existing modules or addons.

I'm also in the process of setting up a large multi-portal system, but after much research I've decided it might be better for my users/portal owners to pre-build groups of portals using a combination of templates and manual settings and then simply assign them to people on request. This gets around the problem that so many modules are not very useful in their default configurations. I've decided that I don't need people to have instant access to their portals and they won't particularly need it either, seeing as they are in for the long term and will benefit more from good usability rather than instant access.

If you do require that users can change skins, I believe there's a skin-selector skin module or skinobject floating around somewhere.

Let us know what you end up doing.

Rob

Thanks for the input Rob.  The reason I started using Buckner's control panel replacement was because the only way I could find to allow a user to manage the "titles" in containers without giving that permission to everyone was to use it.

I tried changing the .ascx used to generate the container titles, but being that I am not a "real" coder, I had a problem in that when modified, the permission setting allows all users, even unauthenticated users to change those titles.  Obviously not good.

I have already set up templates that allow several different roles to edit different parts of the site, but this titles thing has been the main issue for me.

It would be nice if I could find a solution to allow content editors to change those container titles, and not give them access to the page settings to do it.  Alas, it takes a much better coder than I.

I do agree about the exposure in using control panel replacement.  I may default back to using containers that have no titles in them at all.   That is not an attractive solution, but hey.

Again, thank you for the input.

Clay