Blog Security (Role that can edit Content) Problem

This is the place to report bugs and get support. When posting in this forum, please always provide as much detail as possible.

Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum, do not report it as a bug.

This is the place to report bugs and get support

When posting in this forum, please try to provide as many relevant details as possible. Particularly the following:

  • What operating system were you running when the bug appeared?
  • What database platform is your site using?
  • What version of mojoPortal are you running?
  • What version of .NET do you use?
  • What steps are necessary to reproduce the issue? Compare expected results vs actual results.
Please do not report problems with a custom build or custom code in this forum. If you are producing your own build from the source code and have problems or questions, ask in the developer forum.
This thread is closed to new posts. You must sign in to post in the forums.
12/21/2011 11:16:27 AM
Gravatar
Total Posts 18439

Re: Blog Security (Role that can edit Content) Problem

But I wonder if that would still be just as confusing because if it says "Administrators Only" then people may think checking it trumps other checkboxes which it doesn't. It is only locked down to Administrators when that is the only role checked. I'm not sure of a good way to make it obvious, it is a special case locking down content to only Administrators.

12/21/2011 11:43:22 AM
Gravatar
Total Posts 1203
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: Blog Security (Role that can edit Content) Problem

Well, if you're open to a philosophical change, I think the other way it could be handled is to actually change it to work in an additive way, using visual cues. I'm thinking that in page and module settings, it could show the Administrators role as always checked and grayed out (indicating that admins always have access), and content administrators as always checked by default but not grayed out (so the user can just uncheck content administrators to prevent them having access at that level).

If it were implemented this way then gurus would need to unlearn the old way of doing it, but I think it would be a lot more obvious what was going on for less experienced admins, and the checkboxes would really work the same for all of the roles.

Jamie

12/21/2011 11:55:48 AM
Gravatar
Total Posts 18439

Re: Blog Security (Role that can edit Content) Problem

No, I'm not open to that. It is too big a change and too much chance to introduce new bugs. If the user is admin we don't have to check object level permissions and it should never be possible to lock out admins from anything greyed out or not.

What I could do is add a config setting that allows you to not even show the administrators checkbox so that if you are not using the feature to lock out content administrators anywhere you can avoid the confusion. But I would have to keep the default as showing it since people may already have it checked.

Best,

Joe

12/21/2011 12:23:02 PM
Gravatar
Total Posts 18439

Re: Blog Security (Role that can edit Content) Problem

I think what I will do is show explicit instructions that explain it clearly without having to click the help link.

Best,

Joe

12/21/2011 12:39:40 PM
Gravatar
Total Posts 1203
Proud member of the mojoPortal team

Help support mojoPortal!
Add-on modules

Re: Blog Security (Role that can edit Content) Problem

Thanks Joe, I thought it might have been a stretch to fundamentally change it like that. Your idea sounds like a good one.

Jamie

You must sign in to post in the forums. This thread is closed to new posts.