lack of documentation ...
| Project: | Simple Access |
| Version: | 6.x-2.0-rc1 |
| Component: | Documentation |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Hi,
I'm sorry, I don't understand clearly how the module works : I'm not completely fluent in english (nobody's perfect) ; in fact, I'm french. As you may know, english language is more concise than french ; sometimes it's hard to understand the developper's thinking.
1st q° : What do you call an "access profile" (the words are clear, of course, but the meaning in this context is not, to me) ?
2nd q° : the reason why I tried this module is that I want to set a family website. I want (well, would like) the children's nodes to be editable and/or deletable by their parents (but only THEIR parents) by default (the children would not have to grant access when creating the node). I didn't succeed to get it, so I wonder whether it's impossible with Simple Access or just wrong settings. Could you tell me whether I have to search another module or completely "sink" into yours ?
Any hint would be helpful.
Par avance, merci !
#1
Basically access profiles are a method of setting up a specific configuration of settings which a user can apply.
For example, if you want to have a members groups and a publishers group, where the members have full access to view the content, and publishers are able to view and edit, but not delete.
With groups you need to set up each node like this, which can be prone to error. Where as with a profile you can configure a single profile which specifies all this, and then is only 1 checkbox to set this configuration.
This also means that you can give access to setting profiles to lesser trained users as they will not be able to stuff up the access.
Also you can combine multiple profiles together and change the profile at the admin level and all these changes will flow though the system.
#2
#3
Automatically closed -- issue fixed for 2 weeks with no activity.