I use this module to seperate which members have access to "game books" for the various RPG's that are run on our site. Since upgrading, I have been receiving several complaints from member that they suddenly lose the edit tab from the book. I check their role and the role's permissions and they are still showing as a member of the group that is allowed access via the module.

To fix it, I have to remove the member from the role, re-assign them to the role, then rebuild permissions. Can anyone help figure out why they are losing their access rights when nothing else is changing?

Thanks

Comments

Mark Nielsen’s picture

Mark Nielsen commented

I can confirm this.

I have:

  1. Added a test user with no permissions for creating/editing any kind of node.
  2. Added permissions for the test user to view and edit pages in a book.
  3. Logged as the test user and found the book.
  4. As the test user I can edit and save each page in the book just once.
  5. When I go back a second time to edit that page, I'm no longer allowed to.

Rebuilding the permissions cache in "Administer » Content management » Post settings" resets things to how they were, and my test user can edit each book page just once again before being locked out.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Title: Members Losing Access Sporadically » Members losing access sporadically
avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented
Status: Active » Fixed

The code should have rebuilt the access table for a node being edited each time a node has been edited. That is the reason of the behavior described from Mark Gibbens, who had to manually force a rebuilt of the permission cache.

I have changed the code, and committed it. Thanks for your report.

Mark Nielsen’s picture

Mark Nielsen commented

Many thanks, kiamlaluno. Great news!

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

The code has been committed for the development snapshot; between 5 days another release candidate will be created.

Status: Fixed » Closed (fixed)

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