Difference between revisions of "Geeklog Permissions"
m (=Interactions of Article and Topic Permissions=) |
|||
| Line 17: | Line 17: | ||
over riding reason to do so. | over riding reason to do so. | ||
| − | This is not a security hole because you need read/edit for | + | This is not a security hole because you need read/edit for ''both'' the |
article you want to edit and the topic that it is in. Again, it just | article you want to edit and the topic that it is in. Again, it just | ||
allows the Geeklog admin a much finer level of control. | allows the Geeklog admin a much finer level of control. | ||
Revision as of 01:56, 19 July 2004
The best way to learn about Geeklog permissions is to try things out and see what happens.
Interactions of Article and Topic Permissions
If you want a user to be able to edit an article that they are the owner of they need both READ and EDIT permissions for both the article and the topic to which that article belongs.
The thinking behind this is that you should not be able to edit an article (even if you originally wrote it and/or are the current owner) unless you have edit permissions for the topic as well. This allows a site Admin to restrict certain types of access to a given topic. Granted, this is not the simplest thing to understand and it perhaps should be rethought. However, since its been this way for several major releases now it is unlikely it will be changed unless there is an over riding reason to do so.
This is not a security hole because you need read/edit for both the article you want to edit and the topic that it is in. Again, it just allows the Geeklog admin a much finer level of control.
