Closed (fixed)
Project:
Permissions Lock
Version:
6.x-1.1
Component:
User interface
Priority:
Minor
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
1 Feb 2010 at 18:25 UTC
Updated:
22 Jul 2010 at 11:10 UTC
Jump to comment: Most recent file
Comments
Comment #1
svendecabooterHmm very strange. There is a function in the module that was created to avoid this situation (_permissions_lock_cleanup_orphan_headers).
I have tested this with probably the same workflow as you did (lock the views & views_export permissions), and when I check the permissions table with a locked down user account, the table header is gone.
I'd like to see if anyone else is able to reproduce this, as I can't seem to do so...
Comment #2
svendecabooterComment #3
jm.federico commentedHi
I'm having the same issue, attaching image.
I happens with the last module in the list.
Federico
Comment #4
jm.federico commentedComment #5
jm.federico commentedI know why it is happening, we are lacking one iteration in _permissions_lock_cleanup_orphan_headers()
The foreach unsets the number that was run in the previoius iteration, like this
Lets say we have 10 rows
when iteration 0 unset nothing
when iteration 1 unset 0
when iteration 2 unset 1
...
when iteration 8 unset 7
when iteration 9 unset 8
when iteration 10 unset 9
And there it ends, we never get iteration 11 to unset 10
I'm attaching patch
Cheers
Comment #6
svendecabooterThanks. Looking into it ASAP.
Comment #7
svendecabooterProblem fixed!