Mar 19 2011

A note on DotNetNuke Pro Permissions and Work Flow

For the past two or three months, I have had the distinct privilege of working in depth with the DotNetNuke Professional edition. Most notably with the extended permissions and advanced work flow options. The combination of these two very powerful pieces of functionality gives the end user almost limitless options in how he or she wishes to configure his or her website.

The site that I have been working on for the past few months is utilizing DotNetNuke to its full capacity. The complex and intricate permission grid and work flow system they have in place is amazing, but there have certainly been a few bumps and surprises getting it all in set up.

Most notably, we have created for ourselves an issue in regards to the ability to edit of module titles. The particular needs of this client dictate that “website editors” have access to update module content and module titles, but only through a specific work flow. Obviously, we did not want to give these users the ability to manage module settings as that would allow them to change/bypass the work flow in place. We quickly discovered that when we revoked rights to module settings that we also revoked the ability to change the modules title. We thought that enabling the inline editors available in (Admin > Site Settings | Advanced Settings | Usability Settings | ) would allow for module title updates, but it would appear that even the inline editors are bound by the module settings permissions. The inline editors for content work as expected, but module titles are not editable. Thus we now have a scenario where our website editors can add modules, delete modules, and edit the content of said modules, but not edit the modules title.

I'm not sure if this is by design or just an issue that found its way into the permissions/work flow schema unintentionally, but it seems to be an issue.

If anyone else has experienced this type of issue or knows something I'm missing, I would really like to hear from you.

Who is this?

ArchiveS ArchiveS