Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml,v diff -u -r1.17.2.4 -r1.17.2.5 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml 10 Jul 2023 08:36:09 -0000 1.17.2.4 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml 5 Feb 2024 15:35:06 -0000 1.17.2.5 @@ -155,7 +155,7 @@ Another very important reason for using bind variables is performance. Oracle can cache previously parsed queries. If there are values in the where clause, that is how the query - is cached. It also performs bind variable susbstitution + is cached. It also performs bind variable substitution after parsing the SQL statement. This means that SQL statements that use bind variables will always match (assuming all else is the same) while SQL statements that do @@ -521,8 +521,7 @@ Notice the nonstandard numbering (everything - else in Tcl starts at 0); the reason is that the graphics designer, a non - programmer, may wish to work with row numbers. + else in Tcl starts at 0); the reason is that the graphics designer, a non-programmer, may wish to work with row numbers. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml,v diff -u -r1.28.2.3 -r1.28.2.4 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml 10 Jul 2023 08:38:37 -0000 1.28.2.3 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml 5 Feb 2024 15:35:06 -0000 1.28.2.4 @@ -129,7 +129,7 @@ Separate Templates for each Locale - If the request processor finds a filenamed filename.locale.adp, where locale matches the user's locale, it will process that file instead of filename.adp. For example, for a user with locale tl_PH, the file index.tl_PH.adp, if found, will be used instead of index.adp. The locale-specific file should thus contain text in the language appropriate for that locale. The code in the page, however, should still be in English. Message keys are processed normally. + If the request processor finds a file named filename.locale.adp, where locale matches the user's locale, it will process that file instead of filename.adp. For example, for a user with locale tl_PH, the file index.tl_PH.adp, if found, will be used instead of index.adp. The locale-specific file should thus contain text in the language appropriate for that locale. The code in the page, however, should still be in English. Message keys are processed normally. Message Catalogs @@ -284,7 +284,7 @@ If the text is in a Tcl file you must replace variable lookups (occurrences of $var_name or ${var_name}) with %var_name% You are now ready to follow the normal procedure and mark up the text using a - tempoarary message tag (<#_ text_with_percentage_vars#>) and run the action + temporary message tag (<#_ text_with_percentage_vars#>) and run the action replace tags with keys in the APM. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/objects.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/objects.xml,v diff -u -r1.10 -r1.10.2.1 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/objects.xml 7 Aug 2017 23:47:54 -0000 1.10 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/objects.xml 5 Feb 2024 15:35:06 -0000 1.10.2.1 @@ -469,7 +469,7 @@ In particular, never assign any application specific semantics to the context_id attribute of an object. This field is used for -a very specific purpose by the permissions system, and using this +a very specific purpose by the permission system, and using this field in any other way whatsoever is guaranteed to make your application act strangely. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/parties.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/parties.xml,v diff -u -r1.10.2.2 -r1.10.2.3 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/parties.xml 28 Mar 2023 11:20:36 -0000 1.10.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/parties.xml 5 Feb 2024 15:35:07 -0000 1.10.2.3 @@ -197,7 +197,7 @@ Two types of group relations are represented in the data model: membership relations and composite relations. The full range of sophisticated group structures that exist in the real -world can be modelled in OpenACS by these two relationship types. +world can be modeled in OpenACS by these two relationship types. Membership relations represent direct membership relation between parties and groups. A party may be a "member" of a group. Direct membership relations are common in administrative practices, and do not follow basic set Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions-tediously-explained.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions-tediously-explained.xml,v diff -u -r1.10.2.1 -r1.10.2.2 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions-tediously-explained.xml 2 Jul 2020 08:39:25 -0000 1.10.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions-tediously-explained.xml 5 Feb 2024 15:35:07 -0000 1.10.2.2 @@ -21,13 +21,12 @@ (object_id). - The general permissions system has a flexible (and relatively complex) data model in OpenACS. + The general permission system has a flexible (and relatively complex) data model in OpenACS. Developers who have not 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 + It is geared towards developers who understand the general permission system to the extent that is described in the Groups, Context, Permissions documentation, but who have not had the opportunity to take a long, careful look at the @@ -72,7 +71,7 @@ allows developers to define relationships between any two entities A and B by defining a relationship between their corresponding entries in the acs_objects table. One of the applications of this - powerful capability is the general permissions system. + powerful capability is the general permission system. @@ -205,7 +204,7 @@ Although quite feasible, this approach fails to take advantage of the fact - that objects in the system are commonly organized hierarchally, + that objects in the system are commonly organized hierarchically, and permissions usually follow the hierarchical structure, so that if user X has the read privilege on object A, she typically also has the read privilege on all objects attached under A. @@ -706,7 +705,7 @@ Party Hierarchy - Now for the third hierarchy playing a promiment role in the permission system. The party + Now for the third hierarchy playing a prominent role in the permission system. The party data model is set up as follows. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml,v diff -u -r1.18.2.3 -r1.18.2.4 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml 5 Jan 2021 17:33:40 -0000 1.18.2.3 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/permissions.xml 5 Feb 2024 15:35:07 -0000 1.18.2.4 @@ -23,7 +23,7 @@ set access control policies at the object level, that is, any application or system object represented by a row in the acs_objects table can be access-controlled via a -PL/SQL or Tcl interface. The permissions system manages a data model +PL/SQL or Tcl interface. The permission system manages a data model that then allows scripts to check permissions using another API call. @@ -42,7 +42,7 @@ The rest of this document discusses each of these parts, and how they fit together with the -permissions system. +permission system. @@ -136,7 +136,7 @@ Permissions - NOTE: Much more detailed information about the permissions system + NOTE: Much more detailed information about the permission system and how to use it is available in the document. Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml,v diff -u -r1.13.2.2 -r1.13.2.3 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml 9 Aug 2019 20:04:23 -0000 1.13.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml 5 Feb 2024 15:35:07 -0000 1.13.2.3 @@ -77,7 +77,7 @@ Next, the Request Processor checks if the user has appropriate access privileges to the requested part of the site. In OpenACS &version;, access control -is dictated by the permissions system. In +is dictated by the permission system. In this case, the RP checks if the user has "read" privileges on the object in the site map specified by the URL. This object is typically a package instance, but it could easily be something more granular, Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml,v diff -u -r1.60.2.11 -r1.60.2.12 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml 27 Apr 2022 12:22:29 -0000 1.60.2.11 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml 5 Feb 2024 15:35:07 -0000 1.60.2.12 @@ -178,7 +178,7 @@ The OpenACS templating system allows you to give your site a consistent look and feel. It also promotes code maintainability in the presentation layer, by allowing presentation components to be reused across multiple pages. If you need to change the layout for some reason, then you only need to make that change in one location, instead of across many files. - In this problem set you will familiarise yourself with the templating system in openacs. This will be achieved through customising an existing edit-this-page application template. + In this problem set you will familiarize yourself with the templating system in OpenACS. This will be achieved through customizing an existing edit-this-page application template. Before proceeding, it is strongly advised to read the templating documentation on your OpenACS installation (http://localhost:8000/doc/acs-templating). The documentation lists the special tags available for ADP files. @@ -571,7 +571,7 @@ note-edit.tcl requires a note_id to determine which record should be deleted. It also looks for a confirmation variable, which -should initially be absert. If it is absent, we create a form to +should initially be absent. If it is absent, we create a form to allow the user to confirm the deletion. Note that in entry-edit.tcl we used ad_form to access the Form Template commands; here, we call them directly because we don't need the extra Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-db.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-db.xml,v diff -u -r1.19.2.1 -r1.19.2.2 --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-db.xml 22 Nov 2019 16:30:46 -0000 1.19.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-db.xml 5 Feb 2024 15:35:07 -0000 1.19.2.2 @@ -26,7 +26,7 @@ TABLE command, however, because we want to integrate our table with the OpenACS system. By making each record in our table an OpenACS object, we gain access to the - permissions system and to services that integrate with OpenACS + permission system and to services that integrate with OpenACS objects, such as general-comments and notification. The cost is that our table creation code must include several functions, Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml,v diff -u -r1.37.2.4 -r1.37.2.5 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml 10 Jul 2023 08:38:37 -0000 1.37.2.4 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml 5 Feb 2024 15:35:07 -0000 1.37.2.5 @@ -234,7 +234,7 @@ [root qmail-1.03]# rm -f /usr/bin/sendmail /usr/sbin/sendmail ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail - Configure qmail - specifically, run the config script to set up files in /var/qmail/control specifying the computer's identity and which addresses it should accept mail for. This command will automatically set up qmail correctly if you have correctly set a valid host name. If not, you'll want to read /var/qmail/doc/INSTALL.ctl to find out how to configure qmail. + Configure qmail - specifically, run the config script to set up files in /var/qmail/control specifying the computer's identity and which addresses it should accept mail for. This command will automatically set up qmail correctly if you have correctly set a valid hostname. If not, you'll want to read /var/qmail/doc/INSTALL.ctl to find out how to configure qmail. [root qmail-1.03]# ./config-fast yourserver.test Your fully qualified hostname is yourserver.test. Putting yourserver.test into control/me... Index: openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml,v diff -u -r1.11.2.2 -r1.11.2.3 --- openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml 2 Sep 2021 16:56:02 -0000 1.11.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml 5 Feb 2024 15:35:07 -0000 1.11.2.3 @@ -51,8 +51,7 @@ A typical website will tend to offer its users a number of web-based services or applications, e.g. a bulletin board, calendaring, classified ads, -etc. A website may also have underlying subsystems, such as a permissions -system, content management system, etc. For such applications and subsystem +etc. A website may also have underlying subsystems, such as a permission system, content management system, etc. For such applications and subsystem components, modularity - or the degree to which a component can be encapsulated and decoupled from the rest of the system - is of great value. Thus the OpenACS Package Manager (APM) was created to allow website components, Index: openacs-4/packages/acs-core-docs/www/xml/kernel/db-api.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/db-api.xml,v diff -u -r1.12.2.4 -r1.12.2.5 --- openacs-4/packages/acs-core-docs/www/xml/kernel/db-api.xml 2 May 2021 20:18:15 -0000 1.12.2.4 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/db-api.xml 5 Feb 2024 15:35:07 -0000 1.12.2.5 @@ -1006,8 +1006,7 @@ Notice the nonstandard numbering (everything - else in Tcl starts at 0); the reason is that the graphics designer, a non - programmer, may wish to work with row numbers. + else in Tcl starts at 0); the reason is that the graphics designer, a non-programmer, may wish to work with row numbers. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml,v diff -u -r1.11.2.3 -r1.11.2.4 --- openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml 2 Sep 2021 16:56:02 -0000 1.11.2.3 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml 5 Feb 2024 15:35:07 -0000 1.11.2.4 @@ -128,7 +128,7 @@ Related Links -This design document should be read along with the design documents for the new groups system, subsites and the permissions system +This design document should be read along with the design documents for the new groups system, subsites and the permission system @@ -205,7 +205,7 @@ Object Context and Access Control -Until the implementation of the general permissions system, every OpenACS +Until the implementation of the general permission system, every OpenACS application had to manage access control to its data separately. Later on, a notion of "scoping" was introduced into the core data model. @@ -278,7 +278,7 @@ The context system forms the basis for the rest of the OpenACS access control system, which is described in two separate documents: one for the -permissions system and another for the +permission system and another for the party groups system. The context system is also used to implement subsites. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-req.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-req.xml,v diff -u -r1.8.2.1 -r1.8.2.2 --- openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-req.xml 2 Jul 2020 08:39:25 -0000 1.8.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-req.xml 5 Feb 2024 15:35:07 -0000 1.8.2.2 @@ -111,7 +111,7 @@ Support for Unified Access Control Access control should be as transparent as possible to the application -developer. Until the implementation of the general permissions system, every +developer. Until the implementation of the general permission system, every OpenACS application had to manage access control to its data separately. Later on, a notion of "scoping" was introduced into the core data model. @@ -528,12 +528,12 @@ The OpenACS 4 Object Model provides a generalized notion of scope that allows developers to represent a hierarchy of object contexts. These -contexts are used as the basis for the permissions system. In general, if an +contexts are used as the basis for the permission system. In general, if an object has no explicit permissions attached to it, then it inherits permissions from its context. The context data model also forms the basis of the subsites system, and is -a basic part of the permissions system, +a basic part of the permission system, described in separate documents. The context data model should provide the following facilities: Index: openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-design.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-design.xml,v diff -u -r1.8.2.1 -r1.8.2.2 --- openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-design.xml 5 Oct 2019 13:43:47 -0000 1.8.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-design.xml 5 Feb 2024 15:35:07 -0000 1.8.2.2 @@ -75,7 +75,7 @@ Problems resulting from this piecemeal approach to permissions and access control were many, the two major ones being inconsistency, and repeated/redundant code. Thus the drive in OpenACS 4 to provide a unified, -consistent permissions system that both programmers and administrators can +consistent permission system that both programmers and administrators can readily use. @@ -247,7 +247,7 @@ There are three essential areas in which all transactions in the -permissions system fall: +permission system fall: Modification of methods and privileges @@ -308,7 +308,7 @@ API -The API to the permissions system consists of a few well-known tables, +The API to the permission system consists of a few well-known tables, plus a pair of PL/SQL procedures and a pair of Tcl functions. Tables @@ -384,7 +384,7 @@ User Interface -All users of the permissions system are the same at the user-interface +All users of the permission system are the same at the user-interface level. If you have the administer_privileges method permission on an object, then you may edit privileges for that object with the UI. @@ -412,7 +412,7 @@ Configuration/Parameters -There are no configuration options for the permissions system. +There are no configuration options for the permission system. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-requirements.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-requirements.xml,v diff -u -r1.6 -r1.6.16.1 --- openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-requirements.xml 17 Jul 2006 05:38:38 -0000 1.6 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-requirements.xml 5 Feb 2024 15:35:07 -0000 1.6.16.1 @@ -51,7 +51,7 @@ Problems resulting from this piecemeal approach to permissions and access control were many, the two major ones being inconsistency, and repeated/redundant code. Thus the drive in OpenACS 4 to provide a unified, -consistent permissions system that both programmers and administrators can +consistent permission system that both programmers and administrators can readily use.