Index: openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.html,v diff -u -r1.16.2.2 -r1.16.2.3 --- openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.html 21 Nov 2003 11:14:09 -0000 1.16.2.2 +++ openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.html 8 Dec 2003 15:41:18 -0000 1.16.2.3 @@ -1,15 +1,15 @@ -
+
by Vadim Nasardinov. Modified and converted to Docbook XML by Roberto Mello -
The code has been modified since this document was written so it is now obsolete. See this forum thread.
- The general permissions system has a relatively complex data model in OpenACS 4.x. +
The code has been modified since this document was written so it is now out of date. See this forum thread.
+ The general permissions system has a relatively complex data model in OpenACS. Developers who haven't had the time to learn the internals of the data model may end up writing seemingly correct code that crashes their system in weird ways. This writeup is the result of my running into such a piece of code and trying to understand exactly what went wrong. It is geared towards developers who understand the general permissions system to the extent that is described in the - - OpenACS 4.x Permissions documentation, + + OpenACS Permissions documentation, but who haven't had the opportunity to take a long, careful look at the system internals.
@@ -100,7 +100,7 @@
Suppose objects A, B, ..., and F form the following hierarchy. -
Table�8.1.�Context Hierarchy Example
A + Table�8.1.�Context Hierarchy Example
|