Hi,

I installed this module and used "Role based access control settings" for a content type. There I grant access to two custom roles "admins2" and "admins3". They have the permission "View any buchung content" (no other role has this exept administrator). "admins2" has also the permissons "Edit any buchung content" and "Delete any buchung content". "Per content node access control settings" are not enabled. The content type is created by role "customer" (it is a booking content type)

Now the following appears: when a user creates a booking the roles "admins2" and "admins3" do not get access to those newly created nodes. Just when I rebuild permissions they see these new bookings. Just the administrator gets access to those new nodes.

I remember that I had similar problems with other access modules like "View Unpublished"... does anyone have an idea what can cause this?

Best,
Tobias

Comments

vegantriathlete’s picture

vegantriathlete
he/him/his
Primary language English
Location Lakewood, CO
commented
Status: Active » Postponed

I was not able to reproduce this.

Here are the steps I took:

Install the module.
Rebuild permissions.
Edit a content type's access control (admin/structure/types/manage//access)
Assign "View any content" to some roles.
Create a new piece of content.
Verify that one of the roles (that did not create the piece of content) is able to see the piece of content.

When you installed the module did you take the link to rebuild permissions?

Please see if things now work as expected (since it appears you did rebuild permissions at some point) and then close out the issue. I did not want to immediately set it to closed (cannot reproduce) on my own.

Wouter Van den Bosch’s picture

Wouter Van den Bosch commented
Status: Postponed » Active

Would like to state that I'm having the same issue

Drupal v7.2 (Time for an update, I know), content access v 7.x-1.2-beta1.

  • Installed content access module without error
  • Notification of unsuccessful node permission rebuild after install
  • Subsequent rebuild successful
  • Now, new content is automatically inaccessible, unless I do a rebuild
  • No errors in logs
  • Uninstalling for now

Let me know if you want me to do some more digging or provide you with more info, should you want to look into this. Happy to help.

/Setting to active again for now.

gisle’s picture

gisle
he/him
Primary language Norwegian Bokmål
Location Norway
commented
Version: 7.x-1.2-beta1 » 7.x-1.x-dev
Issue summary: View changes
Status: Active » Closed (outdated)

This issue has not received any updates in the previous 7 years. If you believe it to still be relevant, you are encouraged to reopen the issue and update it.

If you got an email about this Issue status update, it is because you at one time (possibly a very long time ago), subscribed to it. To learn how to unsubscribe yourself, please visit: https://www.drupal.org/project/webmasters/issues/3142987