Hi Diego,

Is the user in both roles?

I would look in the settings for the blogs under the security tab and make sure it doesn't have "Administrators" as the only role checked for edit permissions. If it is checked I would uncheck it and save since admins don't need permission. The purpose of listing Administrators there is only for the case where one wants to limit editing to only Administrators. ie normally Content Administrators can edit anything and don't need permission, but it is possible to make content only editable by administrators if you set Administrators as the only edit role on the page and on the feature settings. However it is possible that older content may have been flagged with administrators role in the instance settings by default and that could cause the problem. So unchecking Administrators in the blog settings security tab should solve it if it is checked.

Hope that helps and sorry for the delayed response, it really just occurred to me what might cause this.

Best,

Joe

Hi Diego,

That does explain it. By design if Administrators role is checked and no other roles then only Administrators can edit the page, not even Content Administrators can edit the page in that case, so that is working as intended. If no roles are checked then by default Administrators and Content Administrators can still  edit. So this is a feature that enables you to lock out Content Administrators from editing a page. However to really protect it the feature instances should also be marked as Administrators only, otherwise Content Administrators can still get to the content from Content Manager where there is no page context to enforce page roles.

We fixed a few bugs related to enforcing this Administrators only configfuration in the 2.3.7.5 release so that is why it changed from before, we were not enforcing it correctly before.

Best,

Joe

Hi Joe,

Are you sure you don't have Administrators role checked in page edit settings or in module edit settings? If so uncheck them.

Best,

Joe

Hey guys, I have to agree that although this "subtractive" use of the Administrators role is a well established part of mojoPortal security, it is pretty confusing since it works very differently than any other role. If possible, my suggestion would be to make the Administrators role appear as something like "Administrators Only" for these situations, so it's obvious that selecting that role will have some significant side effects.

Jamie

Actually it is only 2 places, Page Settings and Module Settings so maybe coding in replacement text from a resource file there would be the best solution. Renaming the display name would make it weird when you wanted to add a user to the "Administrators Only" role.

Best,

Joe

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

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

Best,

Joe