Closed (fixed)
Project:
User protect
Version:
7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
20 Jan 2012 at 17:34 UTC
Updated:
2 Jun 2014 at 18:20 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
jnettikSo I was able to figure this out, I had to uninstall and re-install the module. The roles that were throwing the errors were created after this module was installed. I'm guessing the those roles weren't added to the $role_protections variable when they were created.
Not sure if this is still a bug or not, probably could have just went back and resaved the protections by role page.
Comment #2
jimboh commentedI can confirm this bug and that the work-around of going to the protected roles admin page and re-saving does clear the errors.
I am very grateful to the maintainer for this module but respectfully suggest that if the module throws up errors after a new role is added that this is really a bug and that the module should perhaps hook into new role addition and update its own variables (if this is indeed the problem).
Comment #3
h3rj4n commentedA small and dirty fix for this issue. Solved it in my case.
It changes the following:
into
Comment #4
h3rj4n commentedForgot to set it to 'needs review'.
Comment #6
megachrizNot a dirty fix at all. Thanks, committed.