- This topic has 3 replies, 2 voices, and was last updated 3 years, 1 month ago by .
Viewing 4 posts - 1 through 4 (of 4 total)
Viewing 4 posts - 1 through 4 (of 4 total)
- You must be logged in to reply to this topic.
Just checking to make the sure logic behind our roles assignment doesn’t need to be re-assessed since the big update.
We have several roles where it seemed the secondary roles are overriding the primary roles. It’s a site for a school where Teachers and Parents have separate roles. Teachers have higher credential / clearance levels than parents. ie, all Teacher roles can access all Parent roles content but Parents cannot access Teacher content.
We had assigned secondary roles to the Teachers for several of the various Parent level roles. However, it was causing the their primary Teacher content page to throw a 404. when we removed the secondary roles, it no longer threw the 404. Is that to be expected now or should any role be able to have a secondary role that is below it and still work with it’s higher, primary role content?
Hi David,
Please update to version 3.2.0-RC1, then set the “Extended Permissions Precedence Type” to “Allow” in “Settings” page.
Thanks,
Syam
Thanks Syam – that seemed to do the trick.
I also noticed that several of my Roles permissions were wiped and i had to re-activate certain permissions for them.
Not sure if that was a new feature and it just required updating OR if the v3 update erased / removed existing capabilities. Either way, once I went through, everything seems to be working as expected.
thanks for all the work on this.
best,
-david
Hi David,
Glad to know that its working fine.
v3 doesn’t remove existing permissions. But it adds a few more permissions. There is logic to set these new permissions based on the existing permissions. But there were reports that these permissions are not calculating correctly. I have made a few changes in the latest version. Hopefully that will fix this issue.
Thanks,
Syam