Moving node grants into a fieldset
| Project: | Nodeaccess |
| Version: | HEAD |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
I'm not very familiar yet with this module, however it seems to me that having the grants in a tab has a major drawback: We can't assign grants before first submitting the node.
For example, if anonymous users are granted view access to some node type by default, it means that the author of a private node has no choice but making the content publicly viewable first, then edit the node to remove the grant. It means that the content has to be publicly viewable for a while, but even a short while can be too long. Then, of course, we could change the default grant, but that defeats the benefit of having a configurable default... If the most frequent use case for a site is to have the content viewable by default, it is not so convenient to require authors to explicitly assign grants each time (and they will inevitably forget once in a while).
Wouldn't it make more sense to have the grants edited in a fieldset in the node form? It would be available both on node creation and editing. I also think it would be more intuitive, since people sometimes don't notice extra tabs.
#1
I personally prefer it to be it's own tab, just seems cleaner to me. But I'm not opposed to a fieldset either, if there were a lot of people who prefer it that way. For the time being I'm trying to get a stable release together so until that happens I won't be changing it.
#2
I'd just like to emphasize that my main point was not a matter of preference or taste, but the fact that using a separate page from the node submission form greatly lessens the module's usefulness. But I understand your priorities. Keep up the good work!
#3
I tend agree with David. I use this module on an Intranet where complicated control is needed for regulating access to policies and procedures for different departments. Having the content viewable before setting access isn't a big deal since we're only talking about a few seconds, and if it were crucial information I could choose not to publish the page until after setting access. However, it would help streamline the node creation process if it were in the node/add page.
I can't think of another alternative unless you could put a tab within the node/add screen, but I don't know if that's possible.
#4
+1 for David's idea. Maybe as an admin option in case people like the tab method?
#5
I think this is a duplicate of http://drupal.org/node/139080 where the defaults are not automatically applied when a new page is created.
#6
This is not a duplicate. The main request here is to be able to choose grants at node creation, regardless of the defaults.
#7
Would this be possible to have in 2.0? Or is this already planned? I would prefer to have it in a fieldset. Fewer tabs, clicks and seconds spent.
#8
I subscribe David's idea
You don't have to save twice when submiting and when you change grants...
#9
There are ways to grant node access via CCK; using User Reference for example. It allows the access settings to be on the edit page, and you can also output some data on the viewers/authors in the node if needed.