Permissions reset on every node update
slb534 - May 8, 2008 - 22:56
| Project: | node privacy byrole |
| Version: | 5.x-1.1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | deekayen |
| Status: | closed |
Jump to:
Description
Hi,
This module is perfect for my uses except for 1 thing: Every time one of my users updates one of the Page modules on our website, we get "Access Denied". I have configured this module to grant "View" permissions across all pages on my website to the anonymous user. However, when one of these pages is updated, my authenticated users often forget to re-click the "View" permission for "anonymous". It would be nice if all of the previous permission settings were automatically clicked on by default so we don't have to remember to re-enable them every single time we need to update the page.
I hope this makes sense. Thanks very much for this great module!
#1
Oops, I meant to say "Every time one of my users updates one of the Page ***nodes***". Sorry!
#2
I'm working on it.
#3
good thinking!
Subscribing ... will keep an eye out for patches to be tested or anything necesssary to push this foward -=]
#4
I've kind of interpreted what might be the problem and put in a fix. There are various different descriptions in the queue of how it happens, but what I committed fixes the problem I found to this point. Please review it.
http://cvs.drupal.org/viewvc.py/drupal/contributions/modules/node_privac...
#5
assuming what I did fixed it
#6
Hi,
Sorry for my delay in getting back to you! I replaced my node_privacy_byrole module with the new code that you posted. It looks like it's fixed!!
First, I went into "Edit" on several of my pages, and noticed that the existing permissions were checked-on by default, instead of being all blank like they were before. This is great!! (This also helps me because I was forgetting how I had set some permissions in the past, and I had no way to look them up before short of doing an sql query...!)
Next, I went and updated the permissions on a few of the pages, and from what I have observed so far everything looks like it is working properly.
If I bump into any more problems with this in the future, I will come back to this thread. But in the meantime, it's looking like it's fixed!
Thank you SOOOOOO much!
#7
Automatically closed -- issue fixed for two weeks with no activity.