Index: openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp,v diff -u -r1.5.2.3 -r1.5.2.4 --- openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp 27 Jun 2019 18:22:21 -0000 1.5.2.3 +++ openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp 10 Aug 2019 18:05:33 -0000 1.5.2.4 @@ -307,7 +307,7 @@ HEAD, not to release branches.

  • For core packages, bug fixes should be committed on the current release branch whenever applicable.

  • For non-core packages, developers should work on a checkout of -the release branch of the lastest release. For example, if OpenACS +the release branch of the latest release. For example, if OpenACS 5.1.0 is released, developers should work on the oacs-5-1 branch. When oacs-5-2 is branched, developers should continue working on oacs-5-1 until OpenACS 5.2.0 is actually released.

    Reason: First, this ensures that @@ -351,7 +351,7 @@

  • When to TIP

    1. -

      A TIP is a Techical Improvement Proposal ( more information ). A proposed change must be +

      A TIP is a Technical Improvement Proposal ( more information ). A proposed change must be approved by TIP if:

      1. It changes the core data model, or

      2. It will change the behavior of any core package in a way that affects existing code (typically, by changing public API), or

      3. It is a non-backwards-compatible change to any core or standard Index: openacs-4/packages/acs-core-docs/www/cvs-guidelines.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/cvs-guidelines.html,v diff -u -r1.14.2.3 -r1.14.2.4 --- openacs-4/packages/acs-core-docs/www/cvs-guidelines.html 27 Jun 2019 18:22:21 -0000 1.14.2.3 +++ openacs-4/packages/acs-core-docs/www/cvs-guidelines.html 10 Aug 2019 18:05:33 -0000 1.14.2.4 @@ -194,7 +194,7 @@ current release branch whenever applicable.

      4. For non-core packages, developers should work on a - checkout of the release branch of the lastest release. For example, + checkout of the release branch of the latest release. For example, if OpenACS 5.1.0 is released, developers should work on the oacs-5-1 branch. When oacs-5-2 is branched, developers should continue working on oacs-5-1 until OpenACS 5.2.0 is actually @@ -252,7 +252,7 @@

    2. When to TIP

      1. - A TIP is a Techical Improvement Proposal ( + A TIP is a Technical Improvement Proposal ( more information Index: openacs-4/packages/acs-core-docs/www/docbook-primer.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/docbook-primer.adp,v diff -u -r1.6.2.4 -r1.6.2.5 --- openacs-4/packages/acs-core-docs/www/docbook-primer.adp 27 Jun 2019 18:22:21 -0000 1.6.2.4 +++ openacs-4/packages/acs-core-docs/www/docbook-primer.adp 10 Aug 2019 18:05:33 -0000 1.6.2.5 @@ -280,7 +280,7 @@ active processes.

      2. Create a list of administrative tools that are useful to administrating OpenACS, including developer support, schema-browser and API browser. Link to AOLserver's config file -documentation.

      3. Resources on high level subjects such as web services, security +documentation.

      4. Resources on high-level subjects such as web services, security guidelines

      5. Describe typical skill sets (and perhaps mapped to standardized job titles) for administrating an OpenACS system (human-resources style). For a subsite admin/moderator attributes might include Index: openacs-4/packages/acs-core-docs/www/docbook-primer.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/docbook-primer.html,v diff -u -r1.56.2.3 -r1.56.2.4 --- openacs-4/packages/acs-core-docs/www/docbook-primer.html 27 Jun 2019 18:22:21 -0000 1.56.2.3 +++ openacs-4/packages/acs-core-docs/www/docbook-primer.html 10 Aug 2019 18:05:33 -0000 1.56.2.4 @@ -366,7 +366,7 @@ schema-browser and API browser. Link to AOLserver's config file documentation.

      6. - Resources on high level subjects such as web services, + Resources on high-level subjects such as web services, security guidelines

      7. Describe typical skill sets (and perhaps mapped to Index: openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp,v diff -u -r1.6.2.1 -r1.6.2.2 --- openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp 2 Mar 2019 19:30:04 -0000 1.6.2.1 +++ openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.adp 10 Aug 2019 18:05:33 -0000 1.6.2.2 @@ -123,7 +123,7 @@ constraints. So, if you want to name them, please do so and follow the above naming standard. But, naming not null constraints is not a requirement.

        About Naming the not null constraints

        Though naming "not null" constraints doesn't help -immeditately in error debugging (e.g. the error will say something +immediately in error debugging (e.g. the error will say something like "Cannot insert null value into column"), we recommend naming not null constraints to be consistent in our naming of all constraints.

        ($‌Id: constraint-naming.xml,v 1.10 2018/03/24 Index: openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html,v diff -u -r1.53.2.3 -r1.53.2.4 --- openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html 27 Jun 2019 18:22:21 -0000 1.53.2.3 +++ openacs-4/packages/acs-core-docs/www/eng-standards-constraint-naming.html 10 Aug 2019 18:05:33 -0000 1.53.2.4 @@ -79,7 +79,7 @@

        About Naming the not null constraints

        -Though naming "not null" constraints doesn't help immeditately in error +Though naming "not null" constraints doesn't help immediately in error debugging (e.g. the error will say something like "Cannot insert null value into column"), we recommend naming not null constraints to be consistent in our naming of all constraints. Index: openacs-4/packages/acs-core-docs/www/install-redhat.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-redhat.adp,v diff -u -r1.5.2.3 -r1.5.2.4 --- openacs-4/packages/acs-core-docs/www/install-redhat.adp 27 Jun 2019 18:22:22 -0000 1.5.2.3 +++ openacs-4/packages/acs-core-docs/www/install-redhat.adp 10 Aug 2019 18:05:33 -0000 1.5.2.4 @@ -232,7 +232,7 @@ level indicating which services should be up and down at any given service level. We'll use this system for PostgreSQL, but we'll use daemontools to perform a similar function for -AOLserver. (The reason for these discrepencies is that, while +AOLserver. (The reason for these discrepancies is that, while daemontools is better, it's a pain in the ass to deal with and nobody's had any trouble leaving PostgreSQL the way it is.)

        [root root]# service pcmcia stop
 [root root]# service netfs stop
Index: openacs-4/packages/acs-core-docs/www/install-redhat.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-redhat.html,v
diff -u -r1.44.2.3 -r1.44.2.4
--- openacs-4/packages/acs-core-docs/www/install-redhat.html	27 Jun 2019 18:22:22 -0000	1.44.2.3
+++ openacs-4/packages/acs-core-docs/www/install-redhat.html	10 Aug 2019 18:05:33 -0000	1.44.2.4
@@ -146,7 +146,7 @@
          which services should be up and down at any given service
          level.  We'll use this system for PostgreSQL, but we'll use
          daemontools to perform a similar function for AOLserver.
-         (The reason for these discrepencies is that, while daemontools
+         (The reason for these discrepancies is that, while daemontools
          is better, it's a pain in the ass to deal with and nobody's
          had any trouble leaving PostgreSQL the way it is.)
        
        [root root]# service pcmcia stop
Index: openacs-4/packages/acs-core-docs/www/kernel-overview.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/kernel-overview.adp,v
diff -u -r1.3.2.1 -r1.3.2.2
--- openacs-4/packages/acs-core-docs/www/kernel-overview.adp	2 Mar 2019 19:30:05 -0000	1.3.2.1
+++ openacs-4/packages/acs-core-docs/www/kernel-overview.adp	10 Aug 2019 18:05:33 -0000	1.3.2.2
@@ -22,7 +22,7 @@
 services built on top of the Kernel and Core. Application packages
 are developed separately from the Kernel, and are typically
 released independently of it.
        8. -

      This document provides a high level overview of the kernel +

    This document provides a high-level overview of the kernel package. Documentation for other packages on this server

    Index: openacs-4/packages/acs-core-docs/www/kernel-overview.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/kernel-overview.html,v diff -u -r1.33.2.1 -r1.33.2.2 --- openacs-4/packages/acs-core-docs/www/kernel-overview.html 2 Mar 2019 19:30:05 -0000 1.33.2.1 +++ openacs-4/packages/acs-core-docs/www/kernel-overview.html 10 Aug 2019 18:05:33 -0000 1.33.2.2 @@ -21,6 +21,6 @@ released independently of it.

    • - This document provides a high level overview of the kernel + This document provides a high-level overview of the kernel package. Documentation for other packages on this server

    Prev Home Next
    Chapter 15. Kernel Documentation Up Object Model Requirements
    docs@openacs.org
    Index: openacs-4/packages/acs-core-docs/www/programming-with-aolserver.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/programming-with-aolserver.adp,v diff -u -r1.5.2.1 -r1.5.2.2 --- openacs-4/packages/acs-core-docs/www/programming-with-aolserver.adp 2 Mar 2019 19:30:05 -0000 1.5.2.1 +++ openacs-4/packages/acs-core-docs/www/programming-with-aolserver.adp 10 Aug 2019 18:05:33 -0000 1.5.2.2 @@ -51,7 +51,7 @@ ns_schedule_proc and ad_schedule_proc each take a -thread flag to cause a -scheduled procedure to run asychronously, in its own thread. It +scheduled procedure to run asynchronously, in its own thread. It almost always seems like a good idea to specify this switch, but there's a problem.

    It turns out that whenever a task scheduled with ns_schedule_proc -thread or ad_schedule_proc -thread t is run, AOLserver creates a brand new thread and a brand new interpreter, Index: openacs-4/packages/acs-core-docs/www/programming-with-aolserver.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/programming-with-aolserver.html,v diff -u -r1.53.2.3 -r1.53.2.4 --- openacs-4/packages/acs-core-docs/www/programming-with-aolserver.html 27 Jun 2019 18:22:22 -0000 1.53.2.3 +++ openacs-4/packages/acs-core-docs/www/programming-with-aolserver.html 10 Aug 2019 18:05:33 -0000 1.53.2.4 @@ -28,7 +28,7 @@ appropriate term.

    Threads and Scheduled Procedures

    ns_schedule_proc and ad_schedule_proc each take a -thread flag to cause a scheduled procedure to run -asychronously, in its own thread. It almost always seems like a good idea to +asynchronously, in its own thread. It almost always seems like a good idea to specify this switch, but there's a problem.

    It turns out that whenever a task scheduled with ns_schedule_proc -thread or ad_schedule_proc -thread t is run, AOLserver Index: openacs-4/packages/acs-core-docs/www/release-notes.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/release-notes.adp,v diff -u -r1.8.2.4 -r1.8.2.5 --- openacs-4/packages/acs-core-docs/www/release-notes.adp 27 Jun 2019 18:22:22 -0000 1.8.2.4 +++ openacs-4/packages/acs-core-docs/www/release-notes.adp 10 Aug 2019 18:05:33 -0000 1.8.2.5 @@ -556,7 +556,7 @@ "outdated" package in the 5.9 or 6.0 release)

  • General overhaul of package management

  • Install-from-local and install-from-repository can be used to install the provided packages based on a acs-core installation. This means that also DotLRN can be installed from repository or -from local into an existing OpenACS instance.

  • Install-from-repository offers filtering functions, allows to +from local into an existing OpenACS instance.

  • Install-from-repository offers filtering functions, allows one to install optionally from head-channel (for packages not in the base channel of the installed instance). Install-from-repository works more like an app-store, showing as well vendor information

  • Packages can be equipped with xml-based configuration files Index: openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp,v diff -u -r1.6.2.3 -r1.6.2.4 --- openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp 27 Jun 2019 18:22:22 -0000 1.6.2.3 +++ openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp 10 Aug 2019 18:05:33 -0000 1.6.2.4 @@ -184,7 +184,7 @@ TAG=1 # What release version are we building; version format should be -# dashes rather than dots eg. OACS_VERSION=5-0-0b4 +# dashes rather than dots e.g. OACS_VERSION=5-0-0b4 OACS_VERSION=5-0-0b4 DOTLRN_VERSION=2-0-0b4 @@ -239,7 +239,7 @@ mkdir tarball cd tarball cvs -d $OACS_CVSROOT export -r openacs-$OACS_VERSION acs-core -mv opeancs-4 openacs-${OACS_VERSION//-/.} +mv openacs-4 openacs-${OACS_VERSION//-/.} tar -czf ../openacs-${OACS_VERSION//-/.}.tar.gz openacs-${OACS_VERSION//-/.} cd .. Index: openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html,v diff -u -r1.25.2.3 -r1.25.2.4 --- openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html 27 Jun 2019 18:22:22 -0000 1.25.2.3 +++ openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html 10 Aug 2019 18:05:33 -0000 1.25.2.4 @@ -64,7 +64,7 @@ TAG=1 # What release version are we building; version format should be -# dashes rather than dots eg. OACS_VERSION=5-0-0b4 +# dashes rather than dots e.g. OACS_VERSION=5-0-0b4 OACS_VERSION=5-0-0b4 DOTLRN_VERSION=2-0-0b4 @@ -119,7 +119,7 @@ mkdir tarball cd tarball cvs -d $OACS_CVSROOT export -r openacs-$OACS_VERSION acs-core -mv opeancs-4 openacs-${OACS_VERSION//-/.} +mv openacs-4 openacs-${OACS_VERSION//-/.} tar -czf ../openacs-${OACS_VERSION//-/.}.tar.gz openacs-${OACS_VERSION//-/.} cd .. Index: openacs-4/packages/acs-core-docs/www/request-processor.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/request-processor.adp,v diff -u -r1.4.2.1 -r1.4.2.2 --- openacs-4/packages/acs-core-docs/www/request-processor.adp 2 Mar 2019 19:30:05 -0000 1.4.2.1 +++ openacs-4/packages/acs-core-docs/www/request-processor.adp 10 Aug 2019 18:05:33 -0000 1.4.2.2 @@ -16,7 +16,7 @@

    Overview

    This document is a brief introduction to the OpenACS 5.9.0 Request Processor; more details can be found in the OpenACS 4 -Request Processor Design. Here we cover the high level concepts +Request Processor Design. Here we cover the high-level concepts behind the system, and implications and usage for the application developer.

    • @@ -49,7 +49,7 @@ 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, such as whehter the user can view a particular piece of +granular, such as whether the user can view a particular piece of content within a package instance. This automatic check makes it easy to set up sites with areas that are only accessible to specific groups of users.

    Stage 4: URL Processing, File Index: openacs-4/packages/acs-core-docs/www/request-processor.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/request-processor.html,v diff -u -r1.52.2.3 -r1.52.2.4 --- openacs-4/packages/acs-core-docs/www/request-processor.html 27 Jun 2019 18:22:22 -0000 1.52.2.3 +++ openacs-4/packages/acs-core-docs/www/request-processor.html 10 Aug 2019 18:05:33 -0000 1.52.2.4 @@ -4,7 +4,7 @@ by OpenACS documentation staff.

    Overview

    This document is a brief introduction to the OpenACS 5.9.0 Request Processor; -more details can be found in the OpenACS 4 Request Processor Design. Here we cover the high level concepts behind the +more details can be found in the OpenACS 4 Request Processor Design. Here we cover the high-level concepts behind the system, and implications and usage for the application developer.

    Request Processor

    The 5.9.0 Request Processor is a global filter and set of Tcl procs that @@ -41,7 +41,7 @@ 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, -such as whehter the user can view a particular piece of content within +such as whether the user can view a particular piece of content within a package instance. This automatic check makes it easy to set up sites with areas that are only accessible to specific groups of users.

    Stage 4: URL Processing, File Search

    Index: openacs-4/packages/acs-core-docs/www/requirements-template.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/requirements-template.adp,v diff -u -r1.4.2.1 -r1.4.2.2 --- openacs-4/packages/acs-core-docs/www/requirements-template.adp 2 Mar 2019 19:30:06 -0000 1.4.2.1 +++ openacs-4/packages/acs-core-docs/www/requirements-template.adp 10 Aug 2019 18:05:33 -0000 1.4.2.2 @@ -107,7 +107,7 @@ Implementation Notes

    Although in theory coding comes after design, which comes after requirements, we do not, and perhaps should not, always follow such a rigid process (a.k.a. the -waterfall lifecyle). Often, there is a pre-existing system or +waterfall lifecycle). Often, there is a pre-existing system or prototype first, and thus you may want to write some thoughts on implementation, for aiding and guiding yourself or other programmers.

    Index: openacs-4/packages/acs-core-docs/www/requirements-template.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/requirements-template.html,v diff -u -r1.52.2.3 -r1.52.2.4 --- openacs-4/packages/acs-core-docs/www/requirements-template.html 27 Jun 2019 18:22:22 -0000 1.52.2.3 +++ openacs-4/packages/acs-core-docs/www/requirements-template.html 10 Aug 2019 18:05:33 -0000 1.52.2.4 @@ -77,7 +77,7 @@ requirements as well.

    Optional: Implementation Notes

    Although in theory coding comes after design, which comes after requirements, we do not, and perhaps should not, always follow such a - rigid process (a.k.a. the waterfall lifecyle). Often, there is a + rigid process (a.k.a. the waterfall lifecycle). Often, there is a pre-existing system or prototype first, and thus you may want to write some thoughts on implementation, for aiding and guiding yourself or other programmers. Index: openacs-4/packages/acs-core-docs/www/subsites-design.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/subsites-design.adp,v diff -u -r1.5.2.1 -r1.5.2.2 --- openacs-4/packages/acs-core-docs/www/subsites-design.adp 2 Mar 2019 19:30:06 -0000 1.5.2.1 +++ openacs-4/packages/acs-core-docs/www/subsites-design.adp 10 Aug 2019 18:05:33 -0000 1.5.2.2 @@ -28,7 +28,7 @@ a highly structured project subsite with multiple interdependent applications. Thus, flexibility in application deployment is the overarching philosophy of subsites.

    Meeting such broad requirements of flexibility demands -architecture-level support, i.e. very low level support from the +architecture-level support, i.e. very low-level support from the core OpenACS 4 data model. For example, the subsites concept demands that any package can have multiple instances installed at different URLs - entailing support from the APM and the Request Index: openacs-4/packages/acs-core-docs/www/subsites-design.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/subsites-design.html,v diff -u -r1.39.2.1 -r1.39.2.2 --- openacs-4/packages/acs-core-docs/www/subsites-design.html 2 Mar 2019 19:30:06 -0000 1.39.2.1 +++ openacs-4/packages/acs-core-docs/www/subsites-design.html 10 Aug 2019 18:05:33 -0000 1.39.2.2 @@ -11,7 +11,7 @@ own news and forums), to a highly structured project subsite with multiple interdependent applications. Thus, flexibility in application deployment is the overarching philosophy of subsites.

    Meeting such broad requirements of flexibility demands architecture-level -support, i.e. very low level support from the core OpenACS 4 data model. For +support, i.e. very low-level support from the core OpenACS 4 data model. For example, the subsites concept demands that any package can have multiple instances installed at different URLs - entailing support from the APM and the Request Processor. Since the design and implementation directly Index: openacs-4/packages/acs-core-docs/www/xml/non-xml/release-notes-4-6-3.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/non-xml/release-notes-4-6-3.html,v diff -u -r1.2 -r1.2.2.1 --- openacs-4/packages/acs-core-docs/www/xml/non-xml/release-notes-4-6-3.html 7 Aug 2017 23:47:55 -0000 1.2 +++ openacs-4/packages/acs-core-docs/www/xml/non-xml/release-notes-4-6-3.html 10 Aug 2019 18:05:33 -0000 1.2.2.1 @@ -88,7 +88,7 @@

    You may want to begin by reading our installation documentation for -Unix, Windows, and Mac OS X. +Unix, Windows, and macOS.

    Index: openacs-4/packages/acs-content-repository/sql/oracle/packages-create.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/oracle/packages-create.sql,v diff -u -r1.32 -r1.32.2.1 --- openacs-4/packages/acs-content-repository/sql/oracle/packages-create.sql 11 Apr 2018 21:35:06 -0000 1.32 +++ openacs-4/packages/acs-content-repository/sql/oracle/packages-create.sql 10 Aug 2019 18:09:52 -0000 1.32.2.1 @@ -340,7 +340,7 @@ -- @param description A short description for the item (4000 characters maximum) -- @param mime_type The file type of the item, defaults to 'text/plain' -- @param nls_language The language for the item, used for Intermedia search - -- @param text The text content of the new revision, 4000 charcters maximum. + -- @param text The text content of the new revision, 4000 characters maximum. -- Cannot be specified simultaneously with the data -- parameter -- @param data The blob content of the new revision. Cannot be specified Index: openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-4.7d6-5.0d1.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-4.7d6-5.0d1.sql,v diff -u -r1.5 -r1.5.2.1 --- openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-4.7d6-5.0d1.sql 11 Apr 2018 21:35:06 -0000 1.5 +++ openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-4.7d6-5.0d1.sql 10 Aug 2019 18:09:52 -0000 1.5.2.1 @@ -4319,7 +4319,7 @@ -- @param description A short description for the item (4000 characters maximum) -- @param mime_type The file type of the item, defaults to 'text/plain' -- @param nls_language The language for the item, used for Intermedia search - -- @param text The text content of the new revision, 4000 charcters maximum. + -- @param text The text content of the new revision, 4000 characters maximum. -- Cannot be specified simultaneously with the data -- parameter -- @param data The blob content of the new revision. Cannot be specified Index: openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.1.1d2-5.1.1d3.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.1.1d2-5.1.1d3.sql,v diff -u -r1.5 -r1.5.2.1 --- openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.1.1d2-5.1.1d3.sql 11 Apr 2018 21:35:06 -0000 1.5 +++ openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.1.1d2-5.1.1d3.sql 10 Aug 2019 18:09:52 -0000 1.5.2.1 @@ -43,7 +43,7 @@ -- @param description A short description for the item (4000 characters maximum) -- @param mime_type The file type of the item, defaults to 'text/plain' -- @param nls_language The language for the item, used for Intermedia search - -- @param text The text content of the new revision, 4000 charcters maximum. + -- @param text The text content of the new revision, 4000 characters maximum. -- Cannot be specified simultaneously with the data -- parameter -- @param data The blob content of the new revision. Cannot be specified Index: openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.1.5d2-5.1.5d3.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.1.5d2-5.1.5d3.sql,v diff -u -r1.6 -r1.6.2.1 --- openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.1.5d2-5.1.5d3.sql 11 Apr 2018 21:35:06 -0000 1.6 +++ openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.1.5d2-5.1.5d3.sql 10 Aug 2019 18:09:52 -0000 1.6.2.1 @@ -42,7 +42,7 @@ -- @param description A short description for the item (4000 characters maximum) -- @param mime_type The file type of the item, defaults to 'text/plain' -- @param nls_language The language for the item, used for Intermedia search - -- @param text The text content of the new revision, 4000 charcters maximum. + -- @param text The text content of the new revision, 4000 characters maximum. -- Cannot be specified simultaneously with the data -- parameter -- @param data The blob content of the new revision. Cannot be specified Index: openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.2.0b5-5.2.0b6.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.2.0b5-5.2.0b6.sql,v diff -u -r1.6 -r1.6.2.1 --- openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.2.0b5-5.2.0b6.sql 15 Aug 2018 16:48:01 -0000 1.6 +++ openacs-4/packages/acs-content-repository/sql/oracle/upgrade/upgrade-5.2.0b5-5.2.0b6.sql 10 Aug 2019 18:09:52 -0000 1.6.2.1 @@ -50,7 +50,7 @@ -- @param description A short description for the item (4000 characters maximum) -- @param mime_type The file type of the item, defaults to 'text/plain' -- @param nls_language The language for the item, used for Intermedia search - -- @param text The text content of the new revision, 4000 charcters maximum. + -- @param text The text content of the new revision, 4000 characters maximum. -- Cannot be specified simultaneously with the data -- parameter -- @param data The blob content of the new revision. Cannot be specified Index: openacs-4/packages/acs-content-repository/sql/postgresql/content-folder.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/postgresql/content-folder.sql,v diff -u -r1.53 -r1.53.2.1 --- openacs-4/packages/acs-content-repository/sql/postgresql/content-folder.sql 25 Mar 2018 20:56:30 -0000 1.53 +++ openacs-4/packages/acs-content-repository/sql/postgresql/content-folder.sql 10 Aug 2019 18:09:52 -0000 1.53.2.1 @@ -693,10 +693,10 @@ and f.folder_id = copy__folder_id; - -- would be better to check if the copy__name alredy exists in the destination folder. + -- would be better to check if the copy__name already exists in the destination folder. if v_current_folder_id = copy__target_folder_id and (v_name = copy__name or copy__name is null) then - raise EXCEPTION '-20000: content_folder.copy - Destination folder is parent folder and folder alredy exists'; + raise EXCEPTION '-20000: content_folder.copy - Destination folder is parent folder and folder already exists'; end if; -- create the new folder Index: openacs-4/packages/acs-content-repository/sql/postgresql/content-type.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/postgresql/content-type.sql,v diff -u -r1.62 -r1.62.2.1 --- openacs-4/packages/acs-content-repository/sql/postgresql/content-type.sql 16 Jan 2019 09:47:33 -0000 1.62 +++ openacs-4/packages/acs-content-repository/sql/postgresql/content-type.sql 10 Aug 2019 18:09:52 -0000 1.62.2.1 @@ -697,7 +697,7 @@ -- to work reliably in PostgreSQL. Currently we are using a rule to insert -- into the input view when a new content revision is added. Pg locks the -- underlying table when the rule is dropped, so the dropping and recreating --- of the new content revisons seems like it would be reliable, but the +-- of the new content revisions seems like it would be reliable, but the -- possibility of a race condition exists for either the initial creation -- of dropping of a type. I'm not sure if the possibility of a race condition -- actually exists in practice. The thing to do here might be to just create Index: openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.4.0d8-5.4.0d9.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.4.0d8-5.4.0d9.sql,v diff -u -r1.2 -r1.2.2.1 --- openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.4.0d8-5.4.0d9.sql 25 Mar 2018 20:56:30 -0000 1.2 +++ openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.4.0d8-5.4.0d9.sql 10 Aug 2019 18:09:52 -0000 1.2.2.1 @@ -150,7 +150,7 @@ -- new changes: documenting defaults for the arguments -- --- note, that i changed the default value in function_args from "lob" to null, +-- note that i changed the default value in function_args from "lob" to null, -- since apprarently the default in cr_items is "text" (therefore, "lob" was incorrect). -- However, the default in Oracle is "lob", i changed this here to "null" Index: openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.5.0d2-5.5.0d3.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.5.0d2-5.5.0d3.sql,v diff -u -r1.2 -r1.2.12.1 --- openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.5.0d2-5.5.0d3.sql 24 Oct 2008 13:50:14 -0000 1.2 +++ openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.5.0d2-5.5.0d3.sql 10 Aug 2019 18:09:52 -0000 1.2.12.1 @@ -67,10 +67,10 @@ and f.folder_id = copy__folder_id; - -- would be better to check if the copy__name alredy exists in the destination folder. + -- would be better to check if the copy__name already exists in the destination folder. if v_current_folder_id = copy__target_folder_id and (v_name = copy__name or copy__name is null) then - raise EXCEPTION ''-20000: content_folder.copy - Destination folder is parent folder and folder alredy exists''; + raise EXCEPTION ''-20000: content_folder.copy - Destination folder is parent folder and folder already exists''; end if; -- create the new folder Index: openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.9.1b4-5.9.1b5.sql =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.9.1b4-5.9.1b5.sql,v diff -u -r1.2 -r1.2.2.1 --- openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.9.1b4-5.9.1b5.sql 7 Aug 2017 23:47:47 -0000 1.2 +++ openacs-4/packages/acs-content-repository/sql/postgresql/upgrade/upgrade-5.9.1b4-5.9.1b5.sql 10 Aug 2019 18:09:52 -0000 1.2.2.1 @@ -85,10 +85,10 @@ and f.folder_id = copy__folder_id; - -- would be better to check if the copy__name alredy exists in the destination folder. + -- would be better to check if the copy__name already exists in the destination folder. if v_current_folder_id = copy__target_folder_id and (v_name = copy__name or copy__name is null) then - raise EXCEPTION '-20000: content_folder.copy - Destination folder is parent folder and folder alredy exists'; + raise EXCEPTION '-20000: content_folder.copy - Destination folder is parent folder and folder already exists'; end if; -- create the new folder Index: openacs-4/packages/acs-content-repository/www/doc/api/item.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/api/item.adp,v diff -u -r1.6 -r1.6.2.1 --- openacs-4/packages/acs-content-repository/www/doc/api/item.adp 30 Apr 2018 08:15:07 -0000 1.6 +++ openacs-4/packages/acs-content-repository/www/doc/api/item.adp 10 Aug 2019 18:09:52 -0000 1.6.2.1 @@ -447,11 +447,11 @@ nls_language:  The language for the item, used for Intermedia search -text:  The text content of the new revision, 4000 charcters maximum. +text:  The text content of the new revision, 4000 characters maximum. Cannot be specified simultaneously with the data parameter -data:  The blob content of the new revison. Cannot be specified +data:  The blob content of the new revision. Cannot be specified simultaneously with the text parameter relation_tag:  If a parent-child relationship is registered for these content Index: openacs-4/packages/acs-content-repository/www/doc/api/item.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/api/item.html,v diff -u -r1.6 -r1.6.2.1 --- openacs-4/packages/acs-content-repository/www/doc/api/item.html 11 Apr 2018 21:35:06 -0000 1.6 +++ openacs-4/packages/acs-content-repository/www/doc/api/item.html 10 Aug 2019 18:09:52 -0000 1.6.2.1 @@ -843,13 +843,13 @@ text: -   The text content of the new revision, 4000 charcters maximum. +   The text content of the new revision, 4000 characters maximum. Cannot be specified simultaneously with the data parameter data: -   The blob content of the new revison. Cannot be specified +   The blob content of the new revision. Cannot be specified simultaneously with the text parameter Index: openacs-4/packages/acs-content-repository/www/doc/guide/types.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/guide/types.adp,v diff -u -r1.4 -r1.4.2.1 --- openacs-4/packages/acs-content-repository/www/doc/guide/types.adp 30 Apr 2018 08:15:07 -0000 1.4 +++ openacs-4/packages/acs-content-repository/www/doc/guide/types.adp 10 Aug 2019 18:09:52 -0000 1.4.2.1 @@ -103,7 +103,7 @@ attribute tables in the class hierarchy of a particular content type. This view may be used to query attributes when serving content.

    -

    Creating compund items

    +

    Creating compound items

    In many cases your content items will serve as containers for other items. You can include the set of allowable components as part of a content type definition. See Object Relationships for Index: openacs-4/packages/acs-content-repository/www/doc/guide/types.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-content-repository/www/doc/guide/types.html,v diff -u -r1.2 -r1.2.2.1 --- openacs-4/packages/acs-content-repository/www/doc/guide/types.html 7 Aug 2017 23:47:47 -0000 1.2 +++ openacs-4/packages/acs-content-repository/www/doc/guide/types.html 10 Aug 2019 18:09:52 -0000 1.2.2.1 @@ -114,7 +114,7 @@ attribute tables in the class hierarchy of a particular content type. This view may be used to query attributes when serving content.

    -

    Creating compund items

    +

    Creating compound items

    In many cases your content items will serve as containers for other items. You can include the set of allowable components as part of a