Simple permissions: bulk editing pages' permissions?
Permalink
Hi,
I noticed that in 5.6.2.1 the bulk editing of pages' permissions (i.e. checking several pages in page search -> "with selected" to change permissions) is only possible when the advanced permissions model is activated - why? I can't see a reason it shouldn't be possible with the simple permissions, too. Unfortunately I realized this only now that I have a site where editors have been adding and editing dozens of pages with the "view as guest" -checkbox unchecked and now all of them should be made public. It'll be a lot of clicking and repeating...
Any ideas on this; is there a good reason for leaving this option out or could it be added?
Regards,
Patrik
I noticed that in 5.6.2.1 the bulk editing of pages' permissions (i.e. checking several pages in page search -> "with selected" to change permissions) is only possible when the advanced permissions model is activated - why? I can't see a reason it shouldn't be possible with the simple permissions, too. Unfortunately I realized this only now that I have a site where editors have been adding and editing dozens of pages with the "view as guest" -checkbox unchecked and now all of them should be made public. It'll be a lot of clicking and repeating...
Any ideas on this; is there a good reason for leaving this option out or could it be added?
Regards,
Patrik
Interesting. Are there no utility tools exist to bulk update page permissions? Might be helpful for this situation. I would imagine if you were comfortable with SQL you could go into the database and figure out how to update a batch by changing the permissions tables directly... a bit risky but could be a time-saver for the adventurous type.
That's the thing that I haven't found any easy way to do it, even though I can't figure out a reason to not have the option available.. SQL if of course one way to do it, but this kind of feature should be available also to those editors who aren't comfortable with (or haven't even allowed access to) the database. In my opinion, this would be a quite useful (a must) feature for a cms..
