Hello!

I think you will understand all when you will see my screenshots. I don't know how to explain this)

ps thank you very much for your great module!!!! =)

Comments

svendecabooter’s picture

Status: Active » Postponed (maintainer needs more info)

Hmm 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...

svendecabooter’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)
jm.federico’s picture

StatusFileSize
new26.89 KB

Hi

I'm having the same issue, attaching image.

I happens with the last module in the list.

Federico

jm.federico’s picture

Priority: Normal » Minor
Status: Closed (won't fix) » Needs review
jm.federico’s picture

StatusFileSize
new804 bytes

I 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

svendecabooter’s picture

Assigned: Unassigned » svendecabooter

Thanks. Looking into it ASAP.

svendecabooter’s picture

Assigned: svendecabooter » Unassigned
Status: Needs review » Fixed

Problem fixed!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.