Index: openacs-4/packages/acs-core-docs/www/aolserver4.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/aolserver4.adp,v diff -u -N -r1.1.2.8 -r1.1.2.9 --- openacs-4/packages/acs-core-docs/www/aolserver4.adp 6 Jan 2017 09:18:41 -0000 1.1.2.8 +++ openacs-4/packages/acs-core-docs/www/aolserver4.adp 21 Apr 2017 15:07:52 -0000 1.1.2.9 @@ -94,7 +94,7 @@

Configure, compile and install AOLserver. Many people need to run more than -one version of AOLserver in parallel. This section accomodates +one version of AOLserver in parallel. This section accommodates future upgrades by installing AOLserver 4 in /usr/local/aolserver40r9.

 [root aolserver]# cd /usr/local/src/aolserver40r10/aolserver
 [root aolserver]# ./configure --prefix=/usr/local/aolserver40r10 --with-tcl=/usr/local/lib/
@@ -174,7 +174,7 @@
 look like this:

 ../configure --enable-threads --disable-tdomalloc
           --prefix=/usr/local/aolserver --with-tcl=/usr/local/lib
-

Note that the location of the Tcl library may vary on differnt +

Note that the location of the Tcl library may vary on different platforms (e.g. for Debian 3.0: --with-tcl=/usr/lib/tcl8.4)

Now you can compile and configure tDOM

 [root unix]# sh CONFIG
 [root unix]# make install
Index: openacs-4/packages/acs-core-docs/www/aolserver4.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/aolserver4.html,v
diff -u -N -r1.27.2.13 -r1.27.2.14
--- openacs-4/packages/acs-core-docs/www/aolserver4.html	6 Jan 2017 09:18:41 -0000	1.27.2.13
+++ openacs-4/packages/acs-core-docs/www/aolserver4.html	21 Apr 2017 15:07:52 -0000	1.27.2.14
@@ -60,7 +60,7 @@
 cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/aolserver co -r v2_7 nsoracle
 wget http://www.tdom.org/files/tDOM-0.8.0.tar.gz
 tar xvfz tDOM-0.8.0.tar.gz
-cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/tcllib co -r tcllib-1-8 tcllib
  • Configure, compile and install AOLserver. Many people need to run more than one version of AOLserver in parallel. This section accomodates future upgrades by installing AOLserver 4 in /usr/local/aolserver40r9.

    [root aolserver]# cd /usr/local/src/aolserver40r10/aolserver
    +cvs -z3 -d:pserver:anonymous@cvs.sourceforge.net:/cvsroot/tcllib co -r tcllib-1-8 tcllib
  • Configure, compile and install AOLserver. Many people need to run more than one version of AOLserver in parallel. This section accommodates future upgrades by installing AOLserver 4 in /usr/local/aolserver40r9.

    [root aolserver]# cd /usr/local/src/aolserver40r10/aolserver
     [root aolserver]# ./configure --prefix=/usr/local/aolserver40r10 --with-tcl=/usr/local/lib/
     [root aolserver]# make install
     cd /usr/local/src/aolserver40r10/aolserver
    @@ -82,7 +82,7 @@
                     ldd /usr/local/src/aolserver40r10/nspostgres/nspostgres.so
                   

    If you run into problems with libpq.a do the following (and repeat the step above)

    [root nspostgres]# ranlib /usr/local/pgsql/lib/libpq.a

    If you run into problems with the linker, edit the Makefile. Add -lnsdb to the MODLIBS var.

    MODLIBS = -L$(PGLIB) -lpq -lnsdb
  • Install nssha1

    [root nspostgres]# cd ../nssha1

    Now install nssha1:

    [root nssha1]# make install AOLSERVER=/usr/local/aolserver

    If the make fails you will have to edit nssha1.c. Comment out the following 2 lines (lines 139-140):

    // typedef unsigned int u_int32_t;
     // typedef unsigned char u_int8_t;
  • Install tDOM

    [root nssha1]# cd ../tDOM-0.8.0/unix

    Edit the CONFIG file. Uncomment the instructions meant for AOLserver 4, but edit it to look like this:

    ../configure --enable-threads --disable-tdomalloc
    -          --prefix=/usr/local/aolserver --with-tcl=/usr/local/lib

    Note that the location of the Tcl library may vary on differnt platforms (e.g. for Debian 3.0: --with-tcl=/usr/lib/tcl8.4)

    Now you can compile and configure tDOM

    [root unix]# sh CONFIG
    +          --prefix=/usr/local/aolserver --with-tcl=/usr/local/lib

    Note that the location of the Tcl library may vary on different platforms (e.g. for Debian 3.0: --with-tcl=/usr/lib/tcl8.4)

    Now you can compile and configure tDOM

    [root unix]# sh CONFIG
     [root unix]# make install
  • Install TCLLIB

    [root nssha1]# cd ../tcllib

    Configure and compile TCLLIB

    [root unix]# ./configure -prefix=/usr/local/aolserver40r10
     [root unix]# make install
  • Add a database-specific wrapper script. This script 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 -N -r1.1.2.16 -r1.1.2.17 --- openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp 6 Jan 2017 09:18:41 -0000 1.1.2.16 +++ openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp 21 Apr 2017 15:07:52 -0000 1.1.2.17 @@ -109,7 +109,7 @@

    Checkout .LRN

    .LRN consists of a given version openacs core, plus a set of packages. These are collectively packages together to form a -distrubution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0. +distribution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0. .LRN also uses an OpenACS install.xml file during installation; this file is distributed within the dotlrn package and must be moved. To get a development checkout of .LRN in the subdirectory 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 -N -r1.10.2.14 -r1.10.2.15 --- openacs-4/packages/acs-core-docs/www/cvs-guidelines.html 6 Jan 2017 09:18:41 -0000 1.10.2.14 +++ openacs-4/packages/acs-core-docs/www/cvs-guidelines.html 21 Apr 2017 15:07:52 -0000 1.10.2.15 @@ -77,7 +77,7 @@ -r tag.

    To check out HEAD for development, which requires an OpenACS developer account:

    cvs -d:ext:cvs.openacs.org:/cvsroot checkout acs-core

    To check out HEAD anonymously:

    cvs -d:pserver:anonymous@cvs.openacs.org:/cvsroot checkout acs-core

    Checkout .LRN

    .LRN consists of a given version openacs core, plus a set of packages. These are collectively packages together to form a - distrubution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0. + distribution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0. .LRN also uses an OpenACS install.xml file during installation; this file is distributed within the dotlrn package and must be moved. To get a development checkout of .LRN in the subdirectory Index: openacs-4/packages/acs-core-docs/www/db-api-detailed.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/db-api-detailed.adp,v diff -u -N -r1.1.2.9 -r1.1.2.10 --- openacs-4/packages/acs-core-docs/www/db-api-detailed.adp 6 Jan 2017 09:18:41 -0000 1.1.2.9 +++ openacs-4/packages/acs-core-docs/www/db-api-detailed.adp 21 Apr 2017 15:07:52 -0000 1.1.2.10 @@ -522,7 +522,7 @@ db_write_blobstatement-namesql [ -bind bind_set_id | -bind bind_value_list ] db_blob_get_filestatement-namesql [ -bind bind_set_id | -bind bind_value_list ] -

    Analagous to ns_ora +

    Analogous to ns_ora write_clob/write_blob/blob_get_file.

    db_release_unused_handles
    Index: openacs-4/packages/acs-core-docs/www/db-api-detailed.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/db-api-detailed.html,v diff -u -N -r1.48.2.15 -r1.48.2.16 --- openacs-4/packages/acs-core-docs/www/db-api-detailed.html 6 Jan 2017 09:18:41 -0000 1.48.2.15 +++ openacs-4/packages/acs-core-docs/www/db-api-detailed.html 21 Apr 2017 15:07:52 -0000 1.48.2.16 @@ -494,7 +494,7 @@ db_write_blob statement-name sql [ -bind bind_set_id | -bind bind_value_list ] db_blob_get_file statement-name sql [ -bind bind_set_id | -bind bind_value_list ] -

    Analagous to ns_ora write_clob/write_blob/blob_get_file. +

    Analogous to ns_ora write_clob/write_blob/blob_get_file.

    db_release_unused_handles
    Index: openacs-4/packages/acs-core-docs/www/db-api.adp
    ===================================================================
    RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/db-api.adp,v
    diff -u -N -r1.1.2.9 -r1.1.2.10
    --- openacs-4/packages/acs-core-docs/www/db-api.adp	6 Jan 2017 09:18:41 -0000	1.1.2.9
    +++ openacs-4/packages/acs-core-docs/www/db-api.adp	21 Apr 2017 15:07:52 -0000	1.1.2.10
    @@ -91,7 +91,7 @@
     

    What the DB API (in conjuntion with the database drivers implemented for aolserver) do is send the SQL statement to the server for parsing, then bind values to the variables and sends -those values along seperately as a second step. This seperate +those values along separately as a second step. This separate binding step is where the term bind variable comes from.

    This split has several advantages. First, type checking happens on the literal. If the column we are comparing against holds @@ -484,7 +484,7 @@ db_blob_get_file statement-namesql [ -bind bind_set_id | -bind bind_value_list ] -

    Analagous to ns_ora +

    Analogous to ns_ora write_clob/write_blob/blob_get_file.

    db_release_unused_handles
    Index: openacs-4/packages/acs-core-docs/www/db-api.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/db-api.html,v diff -u -N -r1.50.2.15 -r1.50.2.16 --- openacs-4/packages/acs-core-docs/www/db-api.html 6 Jan 2017 09:18:41 -0000 1.50.2.15 +++ openacs-4/packages/acs-core-docs/www/db-api.html 21 Apr 2017 15:07:52 -0000 1.50.2.16 @@ -103,8 +103,8 @@ What the DB API (in conjuntion with the database drivers implemented for aolserver) do is send the SQL statement to the server for parsing, then bind values to the - variables and sends those values along seperately as a second - step. This seperate binding step is where the term + variables and sends those values along separately as a second + step. This separate binding step is where the term bind variable comes from.

    This split has several advantages. First, type checking happens @@ -549,7 +549,7 @@ db_write_blob statement-name sql [ -bind bind_set_id | -bind bind_value_list ] db_blob_get_file statement-name sql [ -bind bind_set_id | -bind bind_value_list ] -

    Analagous to ns_ora write_clob/write_blob/blob_get_file. +

    Analogous to ns_ora write_clob/write_blob/blob_get_file.

    db_release_unused_handles
    Index: openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.adp
    ===================================================================
    RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.adp,v
    diff -u -N -r1.1.2.8 -r1.1.2.9
    --- openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.adp	6 Jan 2017 09:18:41 -0000	1.1.2.8
    +++ openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.adp	21 Apr 2017 15:07:52 -0000	1.1.2.9
    @@ -129,7 +129,7 @@
     

    Salient features of ad_page_contract:

    • A mandatory documentation string is the first argument. This has the standard form with javadoc-style \@author, \@cvs-id, etc, and -should contain a short description of the recieved variables and +should contain a short description of the received variables and any necessary explanations.

    • The second argument specifies the page inputs. The syntax for switches/flags (e.g. multiple-list, array, etc.) uses a colon (:) followed by any number of flags separated by commas (,), e.g. Index: openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html,v diff -u -N -r1.48.2.13 -r1.48.2.14 --- openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html 6 Jan 2017 09:18:41 -0000 1.48.2.13 +++ openacs-4/packages/acs-core-docs/www/eng-standards-filenaming.html 21 Apr 2017 15:07:52 -0000 1.48.2.14 @@ -121,7 +121,7 @@

      Salient features of ad_page_contract:

      • A mandatory documentation string is the first argument. This has -the standard form with javadoc-style @author, @cvs-id, etc, and should contain a short description of the recieved variables and any necessary explanations.

      • The second argument specifies the page +the standard form with javadoc-style @author, @cvs-id, etc, and should contain a short description of the received variables and any necessary explanations.

      • The second argument specifies the page inputs. The syntax for switches/flags (e.g. multiple-list, array, etc.) uses a colon (:) followed by any number of flags separated by commas (,), Index: openacs-4/packages/acs-core-docs/www/eng-standards-plsql.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-plsql.adp,v diff -u -N -r1.1.2.7 -r1.1.2.8 --- openacs-4/packages/acs-core-docs/www/eng-standards-plsql.adp 6 Jan 2017 09:18:41 -0000 1.1.2.7 +++ openacs-4/packages/acs-core-docs/www/eng-standards-plsql.adp 21 Apr 2017 15:07:52 -0000 1.1.2.8 @@ -83,7 +83,7 @@ acs_user.create(first_names_in => 'Jane', last_name_in => 'Doe', etc.) -

        To achieve this we must fully qualify arguements passed into +

        To achieve this we must fully qualify arguments passed into procedures or functions when using them inside a SQL statement. This will get rid of any ambiguities in your code, i.e. it will tell the parser when you want the value of the column and when you @@ -129,7 +129,7 @@ ) return acs_objects.object_id%TYPE;

        takes the optional argument object_id. Do this to allow people to use the same API call when they are doing double click protection, that -is, tehy have already gotten an object_id and now they want to create the +is, they have already gotten an object_id and now they want to create the object with that object_id.

      Index: openacs-4/packages/acs-core-docs/www/eng-standards-plsql.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/eng-standards-plsql.html,v diff -u -N -r1.49.2.13 -r1.49.2.14 --- openacs-4/packages/acs-core-docs/www/eng-standards-plsql.html 6 Jan 2017 09:18:41 -0000 1.49.2.13 +++ openacs-4/packages/acs-core-docs/www/eng-standards-plsql.html 21 Apr 2017 15:07:52 -0000 1.49.2.14 @@ -81,7 +81,7 @@

      - To achieve this we must fully qualify arguements passed into + To achieve this we must fully qualify arguments passed into procedures or functions when using them inside a SQL statement. This will get rid of any ambiguities in your code, i.e. it will tell the parser when you want the value of the column @@ -139,7 +139,7 @@

      takes the optional argument object_id. Do this to allow people to use the same API call when they are doing double - click protection, that is, tehy have already gotten an + click protection, that is, they have already gotten an object_id and now they want to create the object with that object_id.

    Style

    Index: openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp,v diff -u -N -r1.1.2.13 -r1.1.2.14 --- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp 6 Jan 2017 09:18:41 -0000 1.1.2.13 +++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp 21 Apr 2017 15:07:52 -0000 1.1.2.14 @@ -224,7 +224,7 @@ EXT-AUTH-08AAutomation of batch Synchronization -EXT-AUTH-15BOn-demand syncronization +EXT-AUTH-15BOn-demand synchronization

    Regardless of the login method, the user needs to have a row in @@ -374,7 +374,7 @@ site configured to expire people's login after e.g. 2, 4, or 8 hours.

    The other advantage is that we can still offer certain functionality to you, even when your login is not trusted. For -example, we could let you browse publically available forums, and +example, we could let you browse publicly available forums, and only when you want to post do you need to log in. This makes it even more feasible to have a more secure login expiration setting.

    By default, auth::require_login Index: openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html,v diff -u -N -r1.40.2.14 -r1.40.2.15 --- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html 6 Jan 2017 09:18:41 -0000 1.40.2.14 +++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html 21 Apr 2017 15:07:52 -0000 1.40.2.15 @@ -117,7 +117,7 @@ the "local" authority, meaning we'll authenticate as normal using the local users table. This will, just like any other authority, be implemetned using a service contract.

    Synchronizing -and Linking Users

    FeatureStatusDescription
    Synchronizing and linking users
    EXT-AUTH-28ACreate service contract for Batch Sync.
    EXT-AUTH-38ABatch User Synchronization API
    EXT-AUTH-38AIMS Synchronization driver
    EXT-AUTH-08AAutomation of batch Synchronization
    EXT-AUTH-15BOn-demand syncronization

    Regardless of the login method, the user needs to have a row +and Linking Users

    FeatureStatusDescription
    Synchronizing and linking users
    EXT-AUTH-28ACreate service contract for Batch Sync.
    EXT-AUTH-38ABatch User Synchronization API
    EXT-AUTH-38AIMS Synchronization driver
    EXT-AUTH-08AAutomation of batch Synchronization
    EXT-AUTH-15BOn-demand synchronization

    Regardless of the login method, the user needs to have a row in the OpenACS users table. This can happen through a batch job, in real-time, or both in combination. We use the IMS Enterprise 1.1 specification.

    Batch job means that we do a synchronization (import new users, modify changed, purge deleted) on a regular interval, e.g. @@ -221,7 +221,7 @@ site configured to expire people's login after e.g. 2, 4, or 8 hours.

    The other advantage is that we can still offer certain functionality to you, even when your login is not trusted. For -example, we could let you browse publically available forums, and +example, we could let you browse publicly available forums, and only when you want to post do you need to log in. This makes it even more feasible to have a more secure login expiration setting.

    By default, auth::require_login would Index: openacs-4/packages/acs-core-docs/www/how-do-I.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/how-do-I.adp,v diff -u -N -r1.1.2.13 -r1.1.2.14 --- openacs-4/packages/acs-core-docs/www/how-do-I.adp 6 Jan 2017 09:18:41 -0000 1.1.2.13 +++ openacs-4/packages/acs-core-docs/www/how-do-I.adp 21 Apr 2017 15:07:52 -0000 1.1.2.14 @@ -58,7 +58,7 @@ file is usually:

     <master>
     

    If it appears exactly like this, without any arguments, the -template processer uses default-master for that subsite. For pages +template processor uses default-master for that subsite. For pages in /var/lib/aolserver/$OPENACS_SERVICE_NAME/www, this is /var/lib/aolserver/$OPENACS_SERVICE_NAME/www/default-master.adp and the associated .tcl file.

    Index: openacs-4/packages/acs-core-docs/www/how-do-I.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/how-do-I.html,v diff -u -N -r1.27.2.13 -r1.27.2.14 --- openacs-4/packages/acs-core-docs/www/how-do-I.html 6 Jan 2017 09:18:41 -0000 1.27.2.13 +++ openacs-4/packages/acs-core-docs/www/how-do-I.html 21 Apr 2017 15:07:52 -0000 1.27.2.14 @@ -1,7 +1,7 @@ How Do I?

    How Do I?

    How do I edit the front page of a new site through a web interface?

    The easiest way is to install the Edit-This-Page package.

    1. Log in to the web site as an administrator.

    2. Click on Admin > Install Software > Install from OpenACS Repository / Install new application

    3. Choose Edit This Page and install

    4. Follow the instructions within Edit This Page (the link will only work after Edit This Page is installed).

    How do I let anybody who registers post to a weblog?

    Go to /admin/permissions and grant Create to Registered Users

    How do I replace the front page of a new site with the front page of an application on that site

    Suppose you install a new site and install Weblogger, and you want all visitors to see weblogger automatically.

    1. On the front page, click the Admin button.

    2. On the administration page, click Parameters link.

    3. Change the parameter IndexRedirectUrl to be the URI of the desired application. For a default weblogger installation, this would be weblogger/. Note the trailing slash.

    How do I put custom functionality on front page of a new site?

    Every page within an OpenACS site is part of a subsite More information). The home page of the entire site is the front page is a special, default instance of a subsite, served from /var/lib/aolserver/$OPENACS_SERVICE_NAME/www. If an index page is not found there, the default index page for all subsites is used. To customize the code on the front page, copy the default index page from the Subsite package to the Main site and edit it:

    1. cp /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-subsite/www/index* /var/lib/aolserver/$OPENACS_SERVICE_NAME/www
    2. Edit the new index.adp to change the text; you shouldn't need to edit index.tcl unless you are adding new functionality.

    How do I change the site-wide style?

    Almost all pages on an OpenACS site use ACS Templating, and so their appearance is driven by a layer of different files. Let's examine how this works:

    • A templated page uses an ADP/Tcl pair. The first line in the ADP file is usually: -

      <master>

      If it appears exactly like this, without any arguments, the template processer uses default-master for that subsite. For pages in /var/lib/aolserver/$OPENACS_SERVICE_NAME/www, this is /var/lib/aolserver/$OPENACS_SERVICE_NAME/www/default-master.adp and the associated .tcl file. +

      <master>

      If it appears exactly like this, without any arguments, the template processor uses default-master for that subsite. For pages in /var/lib/aolserver/$OPENACS_SERVICE_NAME/www, this is /var/lib/aolserver/$OPENACS_SERVICE_NAME/www/default-master.adp and the associated .tcl file.

    • The default-master is itself a normal ADP page. It draws the subsite navigation elements and invokes site-master (/var/lib/aolserver/$OPENACS_SERVICE_NAME/www/site-master.adp and .tcl)

    • The site-master draws site-wide navigation elements and invokes blank-master (/var/lib/aolserver/$OPENACS_SERVICE_NAME/www/blank-master.adp and .tcl).

    • Blank-master does HTML housekeeping and provides a framework for special sitewide navigation "meta" elements such as Translator widgets and Admin widgets.

    Figure 4.1. Site Templates

    Site Templates

    How do I diagnose a permissions problem?

    • Steps to Reproduce. The events package does not allow users to register for new events.

      1. Go to the http://yourserver.net/events as a visitor (ie, log out and, if necessary, clear cookies). This in on a 4.6.3 site with events version 0.1d3.

      2. Select an available event

      3. A link such as Registration: Deadline is 03/15/2004 10:00am. » Login or sign up to register for this event. is visible. Click on "Login or sign up"

      4. Complete a new registration. Afterwards, you should be redirected back to the same page.

      Actual Results: The page says "You do not have permission to register for this event."

      Expected results: A link or form to sign up for the event is shown.

    • Finding the problem. We start with the page that has the error. In the URL it's http://myserver.net/events/event-info.tcl, so open the file /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/events/www/event-info.tcl. It contains this line:

      set can_register_p [events::security::can_register_for_event_p -event_id $event_id]

      We need to know what that procedure does, so go to /api-doc, paste events::security::can_register_for_event_p into the ACS Tcl API Search box, and click Feeling Lucky. The next pages shows the proc, and we click "show source" to see more information. The body of the proc is simply

      return [permission::permission_p -party_id $user_id -object_id $event_id -privilege write]

      This means that a given user must have the write privilige on the event in order to register. Let's assume that the priviliges inherit, so that if a user has the write privilige on the whole package, they will have the write privilege on the event.

    • Setting Permissions. A permission has three parts: the privilige, the object of the privilige, and the subject being granted the privilige. In this case the privilige is "write," the object is the Events package, and the subject is all Registered Users.

      1. To grant permissions on a package, start at the site map. Find the event package and click "Set permissions".

      2. Click "Grant Permission"

      3. Grant the write permission to Registered Users.

        Figure 4.2. Granting Permissions

        Granting Permissions

      OpenACS 5.0 offers a prettier version at /admin/applications.

      Figure 4.3. Granting Permissions in 5.0

      Granting Permissions in 5.0

    Index: openacs-4/packages/acs-core-docs/www/i18n-introduction.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/i18n-introduction.adp,v diff -u -N -r1.1.2.8 -r1.1.2.9 --- openacs-4/packages/acs-core-docs/www/i18n-introduction.adp 19 Nov 2016 09:21:53 -0000 1.1.2.8 +++ openacs-4/packages/acs-core-docs/www/i18n-introduction.adp 21 Apr 2017 15:07:52 -0000 1.1.2.9 @@ -158,7 +158,7 @@ replace the procedure call with a variable lookup on the syntax %var_name%. Remember to initialize a tcl variable with the same name on some line above the text.

  • If the text is in a tcl file you must replace variable lookups -(occurences of $var_name or ${var_name}) with %var_name%

  • You are now ready to follow the normal procedure and mark up the +(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 replace tags with keys in the APM.

  • Index: openacs-4/packages/acs-core-docs/www/i18n-introduction.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/i18n-introduction.html,v diff -u -N -r1.18.2.8 -r1.18.2.9 --- openacs-4/packages/acs-core-docs/www/i18n-introduction.html 6 Jan 2017 09:18:41 -0000 1.18.2.8 +++ openacs-4/packages/acs-core-docs/www/i18n-introduction.html 21 Apr 2017 15:07:52 -0000 1.18.2.9 @@ -128,7 +128,7 @@ For each message call in the text, decide on a variable name and replace the procedure call with a variable lookup on the syntax %var_name%. Remember to initialize a tcl variable with the same name on some line above the text.

  • If the text is in a tcl file you must replace variable lookups - (occurences 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 + (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 replace tags with keys in the APM.

  • The variable values in the message are usually fetched with upvar, here is an example from dotlrn: Index: openacs-4/packages/acs-core-docs/www/i18n-requirements.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/i18n-requirements.adp,v diff -u -N -r1.1.2.4 -r1.1.2.5 --- openacs-4/packages/acs-core-docs/www/i18n-requirements.adp 19 Nov 2016 09:21:53 -0000 1.1.2.4 +++ openacs-4/packages/acs-core-docs/www/i18n-requirements.adp 21 Apr 2017 15:07:52 -0000 1.1.2.5 @@ -427,7 +427,7 @@ 100.10 Since UTF8 strings can use up to three (UCS2) or six (UCS4) bytes per character, make sure that column size declarations in the schema are large enough -to accomodate required data (such as email addresses in Japanese). +to accommodate required data (such as email addresses in Japanese). Since 5.0.0, this is covered in the database install instructions for both PostgreSQL and Oracle. Index: openacs-4/packages/acs-core-docs/www/i18n-requirements.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/i18n-requirements.html,v diff -u -N -r1.26.2.5 -r1.26.2.6 --- openacs-4/packages/acs-core-docs/www/i18n-requirements.html 6 Jan 2017 09:18:41 -0000 1.26.2.5 +++ openacs-4/packages/acs-core-docs/www/i18n-requirements.html 21 Apr 2017 15:07:52 -0000 1.26.2.6 @@ -261,7 +261,7 @@ universal time zone such as GMT.

    Database

    100.10 Since UTF8 strings can use up to three (UCS2) or six (UCS4) bytes per character, make sure that column size declarations in the schema are large enough to -accomodate required data (such as email addresses in +accommodate required data (such as email addresses in Japanese). Since 5.0.0, this is covered in the database install instructions for both PostgreSQL and Oracle.

    Email and Messaging

    When sending an email message, just as when delivering the content in web page over an HTTP connection, it is necessary to be Index: openacs-4/packages/acs-core-docs/www/i18n-translators.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/i18n-translators.adp,v diff -u -N -r1.1.2.4 -r1.1.2.5 --- openacs-4/packages/acs-core-docs/www/i18n-translators.adp 19 Nov 2016 09:21:53 -0000 1.1.2.4 +++ openacs-4/packages/acs-core-docs/www/i18n-translators.adp 21 Apr 2017 15:07:52 -0000 1.1.2.5 @@ -42,7 +42,7 @@ messages.

    When creating a new locale based on an existing one, such as -creating the Guatamalan version of Spanish, you can copy the +creating the Guatemalan version of Spanish, you can copy the existing locale's catalog files using the script /packages/acs-core-docs/www/files/create-new-catalog.sh.

    -Translator's Guide

    Translator's Guide

    Most translators use the OpenACS Public Translation Server, because the process of getting new message keys onto the server and getting new translations back into the distribution are handled by the maintainers of that machine. You can also do translation work on your own OpenACS site; this makes your own translations more readily available to you but also means that your work will not be shared with other users unless you take extra steps (contacting an OpenACS core developer or submitting a patch) to get your work back to the OpenACS core.

    The basic steps for translators:

    • Go to the Localization page and choose the locale that you are translating to. If the locale is not present you need to visit Administration of Localization and create the locale.

    • Translating with Translator Mode. To translate messages in the pages they appear, Toggle Translator Mode and then browse to the page you want to translate. Untranslated messages will have a yellow background and a red star that you click to translate the message. Translated messages have a green star next to them that is a hyperlink to editing your translation. There is a history mechanism that allows you to see previous translations in case you would want to revert a translation.

      While in Translator mode, a list of all message keys appears at the bottom of each page.

    • Batch translation. To translate many messages at once, go to Administration of Localization, click on the locale to translate, then click on a package, and then click Batch edit these messages.

    When creating a new locale based on an existing one, such as creating the Guatamalan version of Spanish, you can copy the existing locale's catalog files using the script /packages/acs-core-docs/www/files/create-new-catalog.sh.

    +Translator's Guide

    Translator's Guide

    Most translators use the OpenACS Public Translation Server, because the process of getting new message keys onto the server and getting new translations back into the distribution are handled by the maintainers of that machine. You can also do translation work on your own OpenACS site; this makes your own translations more readily available to you but also means that your work will not be shared with other users unless you take extra steps (contacting an OpenACS core developer or submitting a patch) to get your work back to the OpenACS core.

    The basic steps for translators:

    • Go to the Localization page and choose the locale that you are translating to. If the locale is not present you need to visit Administration of Localization and create the locale.

    • Translating with Translator Mode. To translate messages in the pages they appear, Toggle Translator Mode and then browse to the page you want to translate. Untranslated messages will have a yellow background and a red star that you click to translate the message. Translated messages have a green star next to them that is a hyperlink to editing your translation. There is a history mechanism that allows you to see previous translations in case you would want to revert a translation.

      While in Translator mode, a list of all message keys appears at the bottom of each page.

    • Batch translation. To translate many messages at once, go to Administration of Localization, click on the locale to translate, then click on a package, and then click Batch edit these messages.

    When creating a new locale based on an existing one, such as creating the Guatemalan version of Spanish, you can copy the existing locale's catalog files using the script /packages/acs-core-docs/www/files/create-new-catalog.sh.

    Index: openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.adp,v diff -u -N -r1.1.2.13 -r1.1.2.14 --- openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.adp 6 Jan 2017 09:18:42 -0000 1.1.2.13 +++ openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.adp 21 Apr 2017 15:07:52 -0000 1.1.2.14 @@ -31,7 +31,7 @@ installed tsearch2 from a package, you can use the http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/regprocedure_update.sql regprocedure script to update the database after tsearch2 is -installed into it. TODO link to section decribing how to fix an +installed into it. TODO link to section describing how to fix an existing tsearch2 database with this patch.

  • As of May 9, 2004 there is a source patch available for tsearch2. The patch provides changes to the pg_ts_ configuration Index: openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.html,v diff -u -N -r1.11.2.13 -r1.11.2.14 --- openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.html 6 Jan 2017 09:18:42 -0000 1.11.2.13 +++ openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.html 21 Apr 2017 15:07:52 -0000 1.11.2.14 @@ -18,7 +18,7 @@ tsearch2 from a package, you can use the http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/regprocedure_update.sql regprocedure script to update the database after tsearch2 is - installed into it. TODO link to section decribing how to fix + installed into it. TODO link to section describing how to fix an existing tsearch2 database with this patch.

  • As of May 9, 2004 there is a source patch available for tsearch2. The patch provides changes to the pg_ts_ Index: openacs-4/packages/acs-core-docs/www/install-nsopenssl.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-nsopenssl.adp,v diff -u -N -r1.1.2.3 -r1.1.2.4 --- openacs-4/packages/acs-core-docs/www/install-nsopenssl.adp 19 Nov 2016 09:21:53 -0000 1.1.2.3 +++ openacs-4/packages/acs-core-docs/www/install-nsopenssl.adp 21 Apr 2017 15:07:52 -0000 1.1.2.4 @@ -87,7 +87,7 @@ ln -s /usr/local/ssl/lib/libssl.so.0.9.7 libssl.so.0.9.7 ln -s /usr/local/ssl/lib/libcrypto.so.0.9.7 libcrypto.so.0.9.7 -

    SSL support must be enabled seperately in each OpenACS server +

    SSL support must be enabled separately in each OpenACS server (Generate ssl certificates.

    If your ports for SSL are privileged (below 1024), you will have to start AOLserver with prebinds for both your HTTP and your HTTPS Index: openacs-4/packages/acs-core-docs/www/install-nsopenssl.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-nsopenssl.html,v diff -u -N -r1.26.2.4 -r1.26.2.5 --- openacs-4/packages/acs-core-docs/www/install-nsopenssl.html 6 Jan 2017 09:18:42 -0000 1.26.2.4 +++ openacs-4/packages/acs-core-docs/www/install-nsopenssl.html 21 Apr 2017 15:07:52 -0000 1.26.2.5 @@ -61,7 +61,7 @@ ln -s /usr/local/ssl/lib/libcrypto.so.0.9.7 libcrypto.so.0.9.7

    -

    SSL support must be enabled seperately in each OpenACS +

    SSL support must be enabled separately in each OpenACS server (Generate ssl certificates.

    If your ports for SSL are privileged (below 1024), you will have to start AOLserver with prebinds for both your HTTP and your HTTPS port (usually by adding -b Index: openacs-4/packages/acs-core-docs/www/install-squirrelmail.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-squirrelmail.adp,v diff -u -N -r1.1.2.2 -r1.1.2.3 --- openacs-4/packages/acs-core-docs/www/install-squirrelmail.adp 19 Nov 2016 09:21:54 -0000 1.1.2.2 +++ openacs-4/packages/acs-core-docs/www/install-squirrelmail.adp 21 Apr 2017 15:07:52 -0000 1.1.2.3 @@ -19,7 +19,7 @@ OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

    This section is work in progress. It will detail how you can install Squirrelmail as a webmail frontend for OpenACS, thereby -neglecting the need to have a seperate webmail package within +neglecting the need to have a separate webmail package within OpenACS

     [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]# cd www
     [$OPENACS_SERVICE_NAME www]# wget http://cesnet.dl.sourceforge.net/sourceforge/squirrelmail/squirrelmail-1.4.4.tar.gz
    Index: openacs-4/packages/acs-core-docs/www/install-squirrelmail.html
    ===================================================================
    RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-squirrelmail.html,v
    diff -u -N -r1.16.2.2 -r1.16.2.3
    --- openacs-4/packages/acs-core-docs/www/install-squirrelmail.html	19 Nov 2016 09:21:54 -0000	1.16.2.2
    +++ openacs-4/packages/acs-core-docs/www/install-squirrelmail.html	21 Apr 2017 15:07:52 -0000	1.16.2.3
    @@ -2,7 +2,7 @@
     Install Squirrelmail for use as a webmail system for OpenACS

    Install Squirrelmail for use as a webmail system for OpenACS

    By Malte Sussdorff

    OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff. -

    This section is work in progress. It will detail how you can install Squirrelmail as a webmail frontend for OpenACS, thereby neglecting the need to have a seperate webmail package within OpenACS

    [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]# cd www
    +        

    This section is work in progress. It will detail how you can install Squirrelmail as a webmail frontend for OpenACS, thereby neglecting the need to have a separate webmail package within OpenACS

    [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]# cd www
     [$OPENACS_SERVICE_NAME www]# wget http://cesnet.dl.sourceforge.net/sourceforge/squirrelmail/squirrelmail-1.4.4.tar.gz
     [$OPENACS_SERVICE_NAME www]# tar xfz squirrelmail-1.4.4.tar.gz
     [$OPENACS_SERVICE_NAME www]# mv squirrelmail-1.4.4 mail
    Index: openacs-4/packages/acs-core-docs/www/oracle.adp
    ===================================================================
    RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/oracle.adp,v
    diff -u -N -r1.1.2.11 -r1.1.2.12
    --- openacs-4/packages/acs-core-docs/www/oracle.adp	6 Jan 2017 09:18:42 -0000	1.1.2.11
    +++ openacs-4/packages/acs-core-docs/www/oracle.adp	21 Apr 2017 15:07:52 -0000	1.1.2.12
    @@ -345,7 +345,7 @@
     

  • Run the script. Switch to the oracle user first to set the environment appropriately and then do su to get root privileges, while -keeping the oracle user's enviroment.

    +keeping the oracle user's environment.

     [joeuser ~]$ su - oracle
     Password: *********
     [oracle ~]$ su
    Index: openacs-4/packages/acs-core-docs/www/oracle.html
    ===================================================================
    RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/oracle.html,v
    diff -u -N -r1.49.2.14 -r1.49.2.15
    --- openacs-4/packages/acs-core-docs/www/oracle.html	6 Jan 2017 09:18:42 -0000	1.49.2.14
    +++ openacs-4/packages/acs-core-docs/www/oracle.html	21 Apr 2017 15:07:52 -0000	1.49.2.15
    @@ -532,7 +532,7 @@
                 Run the script. Switch to the oracle user first
                 to set the environment appropriately and then do
                 su to get root privileges, while keeping
    -            the oracle user's enviroment.
    +            the oracle user's environment.
                 

     [joeuser ~]$ su - oracle
     Password: *********
    Index: openacs-4/packages/acs-core-docs/www/packages.adp
    ===================================================================
    RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/packages.adp,v
    diff -u -N -r1.1.2.15 -r1.1.2.16
    --- openacs-4/packages/acs-core-docs/www/packages.adp	6 Jan 2017 09:18:42 -0000	1.1.2.15
    +++ openacs-4/packages/acs-core-docs/www/packages.adp	21 Apr 2017 15:07:52 -0000	1.1.2.16
    @@ -50,7 +50,7 @@
     

    What a Package Looks Like

    Each package encapsulates all of its data model, library code, -logic, adminstration pages and user pages in a single part of the +logic, administration pages and user pages in a single part of the file tree. This means developers can track down everything that is related to a particular package without hunting all over the file system. Encapsulating everything about a package in one place also makes it @@ -168,7 +168,7 @@ can be done by including \@\@ filename in the creation or drop scripts. See the Oracle FAQ for examples. In PostgreSQL the same -is acomplished by including \i +is accomplished by including \i filename.sql/<database>/*.sql Data Model Upgrade ScriptsContain changes to the data model between versions. The APM can Index: openacs-4/packages/acs-core-docs/www/packages.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/packages.html,v diff -u -N -r1.51.2.14 -r1.51.2.15 --- openacs-4/packages/acs-core-docs/www/packages.html 6 Jan 2017 09:18:42 -0000 1.51.2.14 +++ openacs-4/packages/acs-core-docs/www/packages.html 21 Apr 2017 15:07:52 -0000 1.51.2.15 @@ -33,7 +33,7 @@ www/ Pages not in packages (static content, customized pages)


    What a Package Looks Like

    Each package encapsulates all of its data model, library code, - logic, adminstration pages and user pages in a single part of + logic, administration pages and user pages in a single part of the file tree. This means developers can track down everything that is related to a particular package without hunting all over the file system. Encapsulating @@ -151,7 +151,7 @@ @@ filename in the creation or drop scripts. See the Oracle FAQ for examples. In - PostgreSQL the same is acomplished by including \i filename. + PostgreSQL the same is accomplished by including \i filename. sql/<database>/*.sql Data Model Upgrade Scripts 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 -N -r1.1.2.9 -r1.1.2.10 --- openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp 6 Jan 2017 09:18:42 -0000 1.1.2.9 +++ openacs-4/packages/acs-core-docs/www/releasing-openacs-core.adp 21 Apr 2017 15:07:52 -0000 1.1.2.10 @@ -105,7 +105,7 @@ for dir in *; do ( cd $dir && cvs tag -F openacs-5-0-compat ); done

    Note that for the compat tag we use the -F flag which will force the tag to the new version (just in case someone has created -the tag already on another version). Excercise care when doing this +the tag already on another version). Exercise care when doing this since you don't want to inadvertently move a prior release tag. Also if the tagging goes horribly wrong for some reason you can delete the tag via cvs tag -d 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 -N -r1.20.2.15 -r1.20.2.16 --- openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html 6 Jan 2017 09:18:42 -0000 1.20.2.15 +++ openacs-4/packages/acs-core-docs/www/releasing-openacs-core.html 21 Apr 2017 15:07:52 -0000 1.20.2.16 @@ -28,7 +28,7 @@ for dir in *; do ( cd $dir && cvs tag dotlrn-2-0-2-final ); done for dir in *; do ( cd $dir && cvs tag -F openacs-5-0-compat ); done

    Note that for the compat tag we use the -F flag which will force the tag to the new version (just in - case someone has created the tag already on another version). Excercise care when doing this since + case someone has created the tag already on another version). Exercise care when doing this since you don't want to inadvertently move a prior release tag. Also if the tagging goes horribly wrong for some reason you can delete the tag via cvs tag -d <symbolic_tag>.

  • Apply the final tag across the tree. First, check out the entire OpenACS tree, getting the most recent stable version of each package. This is most simply done on openacs.org:

    cd /var/tmp
     cvs -d /cvsroot checkout -r openacs-5-1-compat openacs-4
    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 -N -r1.1.2.8 -r1.1.2.9
    --- openacs-4/packages/acs-core-docs/www/request-processor.adp	6 Jan 2017 09:18:42 -0000	1.1.2.8
    +++ openacs-4/packages/acs-core-docs/www/request-processor.adp	21 Apr 2017 15:07:52 -0000	1.1.2.9
    @@ -46,7 +46,7 @@
     either extracts or sets up new session tokens for the user.

    Stage 3: Authorization

    Next, the Request Processor checks if the user has appropriate access privileges to the requested part of the site. In OpenACS 5.9.0, access control is dictated by the permissions system. In this case, -the RP checks if the user has "read" priviledges on the +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 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 -N -r1.49.2.14 -r1.49.2.15 --- openacs-4/packages/acs-core-docs/www/request-processor.html 6 Jan 2017 09:18:42 -0000 1.49.2.14 +++ openacs-4/packages/acs-core-docs/www/request-processor.html 21 Apr 2017 15:07:52 -0000 1.49.2.15 @@ -38,7 +38,7 @@ Next, the Request Processor checks if the user has appropriate access privileges to the requested part of the site. In OpenACS 5.9.0, access control is dictated by the permissions system. In -this case, the RP checks if the user has "read" priviledges on the +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 Index: openacs-4/packages/acs-core-docs/www/snapshot-backup.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/snapshot-backup.adp,v diff -u -N -r1.1.2.4 -r1.1.2.5 --- openacs-4/packages/acs-core-docs/www/snapshot-backup.adp 19 Nov 2016 09:21:55 -0000 1.1.2.4 +++ openacs-4/packages/acs-core-docs/www/snapshot-backup.adp 21 Apr 2017 15:07:52 -0000 1.1.2.5 @@ -109,7 +109,7 @@

    Back up the file system. Back up all of the files in the service, including the database backup file -but excluding the auto-generated supervise directory, which is unneccesary and has +but excluding the auto-generated supervise directory, which is unnecessary and has complicated permissions.

    In the tar command,

    • c create a new tar Index: openacs-4/packages/acs-core-docs/www/snapshot-backup.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/snapshot-backup.html,v diff -u -N -r1.13.2.5 -r1.13.2.6 --- openacs-4/packages/acs-core-docs/www/snapshot-backup.html 6 Jan 2017 09:18:42 -0000 1.13.2.5 +++ openacs-4/packages/acs-core-docs/www/snapshot-backup.html 21 Apr 2017 15:07:52 -0000 1.13.2.6 @@ -76,7 +76,7 @@ exit

  • Back up the file system. Back up all of the files in the service, including the database backup file but excluding the auto-generated supervise directory, which is - unneccesary and has complicated permissions.

    In the tar command,

    • c create a + unnecessary and has complicated permissions.

      In the tar command,

      • c create a new tar archive

      • p preserves permissions.

      • s preserves file sort order

      • z compresses the output with gzip.

      • The --exclude clauses skips some daemontools files that are owned by root and thus cannot be backed up by the service owner. These files are autogenerated and we don't Index: openacs-4/packages/acs-core-docs/www/tutorial-caching.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-caching.adp,v diff -u -N -r1.1.2.3 -r1.1.2.4 --- openacs-4/packages/acs-core-docs/www/tutorial-caching.adp 19 Nov 2016 09:21:55 -0000 1.1.2.3 +++ openacs-4/packages/acs-core-docs/www/tutorial-caching.adp 21 Apr 2017 15:07:52 -0000 1.1.2.4 @@ -28,9 +28,9 @@ return [util_memoize [list my_proc_not_cached -foo $foo]] } -

      • In your code, always call my_proc. There will be a seperate +

      • In your code, always call my_proc. There will be a separate cache item for each unique call to my_proc_not_cached so that calls -with different arguments are cached seperately. You can flush the +with different arguments are cached separately. You can flush the cache for each cache key by calling util_memoize_flush my_proc_not_cached args.

      • The cached material will of course become obsolete over time. Index: openacs-4/packages/acs-core-docs/www/tutorial-caching.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-caching.html,v diff -u -N -r1.11.2.4 -r1.11.2.5 --- openacs-4/packages/acs-core-docs/www/tutorial-caching.html 6 Jan 2017 09:18:42 -0000 1.11.2.4 +++ openacs-4/packages/acs-core-docs/www/tutorial-caching.html 21 Apr 2017 15:07:52 -0000 1.11.2.5 @@ -6,6 +6,6 @@ Get a cached version of my_proc. } { return [util_memoize [list my_proc_not_cached -foo $foo]] -}

      • In your code, always call my_proc. There will be a seperate cache item for each unique call to my_proc_not_cached so that calls with different arguments are cached seperately. You can flush the cache for each cache key by calling util_memoize_flush my_proc_not_cached args.

      • +}

      • In your code, always call my_proc. There will be a separate cache item for each unique call to my_proc_not_cached so that calls with different arguments are cached separately. You can flush the cache for each cache key by calling util_memoize_flush my_proc_not_cached args.

      • The cached material will of course become obsolete over time. There are two ways to handle this.

        • Timed Expiration: pass in max_age to util_memoize. If the content is older than max_age, it will be re-generated.

        • Direct Flushing. In any proc which invalidates the cached content, call util_memoize_flush my_proc_not_cached args.

      • If you are correctly flushing the cached value, then it will need to be reloaded. You may wish to pre-load it, so that the loading delay does not impact users. If you have a sequence of pages, you could call the cached proc in advance, to increase the chances that it's loaded and current when the user reaches it. Or, you can call (and discard) it immediately after flushing it.

    Index: openacs-4/packages/acs-core-docs/www/tutorial-database.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-database.adp,v diff -u -N -r1.1.2.15 -r1.1.2.16 --- openacs-4/packages/acs-core-docs/www/tutorial-database.adp 6 Jan 2017 09:18:42 -0000 1.1.2.15 +++ openacs-4/packages/acs-core-docs/www/tutorial-database.adp 21 Apr 2017 15:07:52 -0000 1.1.2.16 @@ -73,7 +73,7 @@ select content_folder__register_content_type(-100,'mfp_note','t');

    The creation script calls a function in PL/pgSQL (PL/pgSQL is a -procedural language extention to sql), content_type__create_type, which in turn +procedural language extension to sql), content_type__create_type, which in turn creates the necessary database changes to support our data object. Notice the use of "mfp." This is derived from "My First Package" and ensures that our object is unlikely to Index: openacs-4/packages/acs-core-docs/www/tutorial-database.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-database.html,v diff -u -N -r1.44.2.13 -r1.44.2.14 --- openacs-4/packages/acs-core-docs/www/tutorial-database.html 6 Jan 2017 09:18:42 -0000 1.44.2.13 +++ openacs-4/packages/acs-core-docs/www/tutorial-database.html 21 Apr 2017 15:07:52 -0000 1.44.2.14 @@ -56,7 +56,7 @@ -- necessary to work around limitation of content repository: select content_folder__register_content_type(-100,'mfp_note','t'); -

    The creation script calls a function in PL/pgSQL (PL/pgSQL is a procedural language extention to sql), +

    The creation script calls a function in PL/pgSQL (PL/pgSQL is a procedural language extension to sql), content_type__create_type, which in turn creates the necessary database changes to support our data object. Notice the use of "mfp." This is derived from "My Index: openacs-4/packages/acs-core-docs/www/tutorial-hierarchical.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-hierarchical.adp,v diff -u -N -r1.1.2.3 -r1.1.2.4 --- openacs-4/packages/acs-core-docs/www/tutorial-hierarchical.adp 19 Nov 2016 09:21:55 -0000 1.1.2.3 +++ openacs-4/packages/acs-core-docs/www/tutorial-hierarchical.adp 21 Apr 2017 15:07:52 -0000 1.1.2.4 @@ -54,7 +54,7 @@ and parent.tree_sortkey <> children.tree_sortkey and parent.key = :the_parent_key; -

    The reason we substract the parent's tree_level from the +

    The reason we subtract the parent's tree_level from the child's tree_level is that the tree_levels are global, so if you want the parent's tree_level to start with 0, you'll want the subtraction in there. This is a reason you'll commonly Index: openacs-4/packages/acs-core-docs/www/tutorial-hierarchical.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-hierarchical.html,v diff -u -N -r1.11.2.4 -r1.11.2.5 --- openacs-4/packages/acs-core-docs/www/tutorial-hierarchical.html 6 Jan 2017 09:18:42 -0000 1.11.2.4 +++ openacs-4/packages/acs-core-docs/www/tutorial-hierarchical.html 21 Apr 2017 15:07:52 -0000 1.11.2.5 @@ -43,7 +43,7 @@ children.tree_sortkey between parent.tree_sortkey and tree_right(parent.tree_sortkey) and parent.tree_sortkey <> children.tree_sortkey and parent.key = :the_parent_key; -

    The reason we substract the parent's tree_level from the +

    The reason we subtract the parent's tree_level from the child's tree_level is that the tree_levels are global, so if you want the parent's tree_level to start with 0, you'll want the subtraction in there. This is a reason you'll commonly see magic Index: openacs-4/packages/acs-core-docs/www/tutorial-notifications.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-notifications.adp,v diff -u -N -r1.1.2.3 -r1.1.2.4 --- openacs-4/packages/acs-core-docs/www/tutorial-notifications.adp 19 Nov 2016 09:21:55 -0000 1.1.2.3 +++ openacs-4/packages/acs-core-docs/www/tutorial-notifications.adp 21 Apr 2017 15:07:52 -0000 1.1.2.4 @@ -16,7 +16,7 @@ OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

    The notifications package allows you to send notifications through any defined communications medium (e.g. email, sms) upon -some event occuring within the system.

    This tutorial steps through the process of integrating the +some event occurring within the system.

    This tutorial steps through the process of integrating the notifications package with your package.

    First step is to create the notification types. To do this a script similar to the one below needs to be loaded into Postgresql. I create this script in a Index: openacs-4/packages/acs-core-docs/www/tutorial-notifications.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-notifications.html,v diff -u -N -r1.17.2.4 -r1.17.2.5 --- openacs-4/packages/acs-core-docs/www/tutorial-notifications.html 6 Jan 2017 09:18:42 -0000 1.17.2.4 +++ openacs-4/packages/acs-core-docs/www/tutorial-notifications.html 21 Apr 2017 15:07:52 -0000 1.17.2.5 @@ -3,7 +3,7 @@ OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

    The notifications package allows you to send notifications through any - defined communications medium (e.g. email, sms) upon some event occuring within + defined communications medium (e.g. email, sms) upon some event occurring within the system.

    This tutorial steps through the process of integrating the notifications package with your package.

    First step is to create the notification types. To do this a script similar to the one below needs to be loaded into Postgresql. I create this script in a Index: openacs-4/packages/acs-core-docs/www/tutorial-pages.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-pages.adp,v diff -u -N -r1.1.2.16 -r1.1.2.17 --- openacs-4/packages/acs-core-docs/www/tutorial-pages.adp 6 Jan 2017 09:18:42 -0000 1.1.2.16 +++ openacs-4/packages/acs-core-docs/www/tutorial-pages.adp 21 Apr 2017 15:07:52 -0000 1.1.2.17 @@ -24,7 +24,7 @@ of all objects; the second shows a single object in view or edit mode, and can also be used to add an object. The index page will display the list, but since we might reuse the list later, -we'll put it in a seperate file and include it on the index +we'll put it in a separate file and include it on the index page.

    Figure 9.5. Page Map

    Page Map
    Index: openacs-4/packages/acs-core-docs/www/tutorial-pages.html =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-pages.html,v diff -u -N -r1.44.2.13 -r1.44.2.14 --- openacs-4/packages/acs-core-docs/www/tutorial-pages.html 6 Jan 2017 09:18:42 -0000 1.44.2.13 +++ openacs-4/packages/acs-core-docs/www/tutorial-pages.html 21 Apr 2017 15:07:52 -0000 1.44.2.14 @@ -3,7 +3,7 @@ OpenACS docs are written by the named authors, and may be edited by OpenACS documentation staff.

    Install some API

    As a workaround for missing content-repository functionality, copy a provided file into the directory for tcl files:

    -    cp /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/files/tutorial/note-procs.tcl /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/tcl/

    To make this file take effect, go to the APM and choose "Reload changed" for "MyFirstPackage".

    Page Map

    Our package will have two visible pages. The first shows a list of all objects; the second shows a single object in view or edit mode, and can also be used to add an object. The index page will display the list, but since we might reuse the list later, we'll put it in a seperate file and include it on the index page.

    Figure 9.5. Page Map

    Page Map

    Build the "Index" page

    Each user-visible page in your package has, typically, + cp /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/acs-core-docs/www/files/tutorial/note-procs.tcl /var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/tcl/

    To make this file take effect, go to the APM and choose "Reload changed" for "MyFirstPackage".

    Page Map

    Our package will have two visible pages. The first shows a list of all objects; the second shows a single object in view or edit mode, and can also be used to add an object. The index page will display the list, but since we might reuse the list later, we'll put it in a separate file and include it on the index page.

    Figure 9.5. Page Map

    Page Map

    Build the "Index" page

    Each user-visible page in your package has, typically, three parts. The tcl file holds the procedural logic for the page, including Tcl and database-independent SQL code, and does things like Index: openacs-4/packages/acs-core-docs/www/tutorial-second-database.adp =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-second-database.adp,v diff -u -N -r1.1.2.3 -r1.1.2.4 --- openacs-4/packages/acs-core-docs/www/tutorial-second-database.adp 19 Nov 2016 09:21:55 -0000 1.1.2.3 +++ openacs-4/packages/acs-core-docs/www/tutorial-second-database.adp 21 Apr 2017 15:07:52 -0000 1.1.2.4 @@ -13,7 +13,7 @@ databases. In this example, the OpenACS site uses a PostGre database, and accesses another PostGre database called legacy.

    1. -

      Modify config.tcl to accomodate the legacy database, and to +

      Modify config.tcl to accommodate the legacy database, and to ensure that the legacy database is not used for standard OpenACS queries:

       ns_section ns/db/pools
      Index: openacs-4/packages/acs-core-docs/www/tutorial-second-database.html
      ===================================================================
      RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-second-database.html,v
      diff -u -N -r1.10.2.2 -r1.10.2.3
      --- openacs-4/packages/acs-core-docs/www/tutorial-second-database.html	19 Nov 2016 09:21:55 -0000	1.10.2.2
      +++ openacs-4/packages/acs-core-docs/www/tutorial-second-database.html	21 Apr 2017 15:07:52 -0000	1.10.2.3
      @@ -2,7 +2,7 @@
       Connect to a second database

      Connect to a second database

      It is possible to use the OpenACS Tcl database API with other databases. In this example, the OpenACS site uses a PostGre database, and accesses another PostGre database called - legacy.

      1. Modify config.tcl to accomodate the legacy database, and to + legacy.

        1. Modify config.tcl to accommodate the legacy database, and to ensure that the legacy database is not used for standard OpenACS queries:

          ns_section ns/db/pools
           ns_param   pool1              "Pool 1"
          Index: openacs-4/packages/acs-core-docs/www/files/package-documentation.xml
          ===================================================================
          RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/files/package-documentation.xml,v
          diff -u -N -r1.2.24.1 -r1.2.24.2
          --- openacs-4/packages/acs-core-docs/www/files/package-documentation.xml	23 Jun 2016 08:32:46 -0000	1.2.24.1
          +++ openacs-4/packages/acs-core-docs/www/files/package-documentation.xml	21 Apr 2017 15:07:52 -0000	1.2.24.2
          @@ -304,7 +304,7 @@
                     
                       Use the template system to generate a form for
                       editing/creating a note.  If an existing note id was
          -            passed in, populate the form fields wih that note's
          +            passed in, populate the form fields with that note's
                       values.
           
                     
          Index: openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml
          ===================================================================
          RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml,v
          diff -u -N -r1.22.2.3 -r1.22.2.4
          --- openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml	3 Oct 2016 09:17:51 -0000	1.22.2.3
          +++ openacs-4/packages/acs-core-docs/www/xml/releasing-openacs.xml	21 Apr 2017 15:07:52 -0000	1.22.2.4
          @@ -107,7 +107,7 @@
           for dir in *; do ( cd $dir && cvs tag -F openacs-5-0-compat ); done
           
                   Note that for the compat tag we use the -F flag which will force the tag to the new version (just in 
          -          case someone has created the tag already on another version).  Excercise care when doing this since 
          +          case someone has created the tag already on another version).  Exercise care when doing this since 
                     you don't want to inadvertently move a prior release tag.  Also if the tagging goes horribly wrong 
                     for some reason you can delete the tag via cvs tag -d <symbolic_tag>.
                 
          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 -N -r1.13.8.3 -r1.13.8.4
          --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml	3 Oct 2016 09:17:51 -0000	1.13.8.3
          +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml	21 Apr 2017 15:07:52 -0000	1.13.8.4
          @@ -171,8 +171,8 @@
                 What the DB API (in conjuntion with the database drivers
                 implemented for aolserver) do is send the SQL statement to the
                 server for parsing, then bind values to the
          -      variables and sends those values along seperately as a second
          -      step. This seperate binding step is where the term
          +      variables and sends those values along separately as a second
          +      step. This separate binding step is where the term
                 bind variable comes from.
               
           
          @@ -886,7 +886,7 @@
           db_blob_get_file statement-name sql [ -bind bind_set_id | -bind bind_value_list ]
           	  
           
          -	  Analagous to ns_ora write_clob/write_blob/blob_get_file. 
          +	  Analogous to ns_ora write_clob/write_blob/blob_get_file. 
           
           
           	  
          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 -N -r1.27.2.5 -r1.27.2.6
          --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml	3 Oct 2016 09:17:51 -0000	1.27.2.5
          +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/i18n.xml	21 Apr 2017 15:07:52 -0000	1.27.2.6
          @@ -282,7 +282,7 @@
                       the procedure call with a variable lookup on the syntax %var_name%. Remember
                       to initialize a tcl variable with the same name on some line above the text.
                   If the text is in a tcl file you must replace variable lookups 
          -            (occurences of $var_name or ${var_name}) with %var_name%
          +            (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 
                       replace tags with keys in the APM.
          @@ -960,6 +960,6 @@
           
                 
               
          -    When creating a new locale based on an existing one, such as creating the Guatamalan version of Spanish, you can copy the existing locale's catalog files using the script /packages/acs-core-docs/www/files/create-new-catalog.sh.
          +    When creating a new locale based on an existing one, such as creating the Guatemalan version of Spanish, you can copy the existing locale's catalog files using the script /packages/acs-core-docs/www/files/create-new-catalog.sh.
             
           
          Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml
          ===================================================================
          RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml,v
          diff -u -N -r1.9.14.2 -r1.9.14.3
          --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml	3 Oct 2016 09:17:51 -0000	1.9.14.2
          +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml	21 Apr 2017 15:07:52 -0000	1.9.14.3
          @@ -62,7 +62,7 @@
           
               
                 Each package encapsulates all of its data model, library code,
          -      logic, adminstration pages and user pages in a single part of
          +      logic, administration pages and user pages in a single part of
                 the file tree.  This means developers can track down
                 everything that is related to a particular
                 package without hunting all over the file system.  Encapsulating
          @@ -223,7 +223,7 @@
                     scripts. See the 
                   Oracle FAQ for examples. In
          -          PostgreSQL the same is acomplished by including \i filename.
          +          PostgreSQL the same is accomplished by including \i filename.
                   
                   
                     sql/<database>/*.sql
          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 -N -r1.12.6.2 -r1.12.6.3
          --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml	3 Oct 2016 09:17:51 -0000	1.12.6.2
          +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/rp.xml	21 Apr 2017 15:07:52 -0000	1.12.6.3
          @@ -78,7 +78,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
          -this case, the RP checks if the user has "read" priviledges on the
          +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
          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 -N -r1.52.2.4 -r1.52.2.5
          --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml	4 Feb 2017 14:04:24 -0000	1.52.2.4
          +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml	21 Apr 2017 15:07:52 -0000	1.52.2.5
          @@ -870,7 +870,7 @@
               
           
               The notifications package allows you to send notifications through any 
          -    defined communications medium (e.g. email, sms) upon some event occuring within 
          +    defined communications medium (e.g. email, sms) upon some event occurring within 
               the system.
               This tutorial steps through the process of integrating the notifications 
               package with your package.
          @@ -1155,7 +1155,7 @@
                 and parent.key = :the_parent_key;
                 
           
          -    The reason we substract the parent's tree_level from the
          +    The reason we subtract the parent's tree_level from the
               child's tree_level is that the tree_levels are global, so if you
               want the parent's tree_level to start with 0, you'll want the
               subtraction in there. This is a reason you'll commonly see magic
          @@ -1367,7 +1367,7 @@
           }
                 
                 
          -        In your code, always call my_proc.  There will be a seperate cache item for each unique call to my_proc_not_cached so that calls with different arguments are cached seperately. You can flush the cache for each cache key by calling util_memoize_flush my_proc_not_cached args.
          +        In your code, always call my_proc.  There will be a separate cache item for each unique call to my_proc_not_cached so that calls with different arguments are cached separately. You can flush the cache for each cache key by calling util_memoize_flush my_proc_not_cached args.
                 
                 
                   
          @@ -1596,7 +1596,7 @@
               legacy.
               
                 
          -        Modify config.tcl to accomodate the legacy database, and to
          +        Modify config.tcl to accommodate the legacy database, and to
                   ensure that the legacy database is not used for standard
                   OpenACS queries:
                   ns_section ns/db/pools
          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 -N -r1.18.6.1 -r1.18.6.2
          --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-db.xml	23 Jun 2016 08:32:46 -0000	1.18.6.1
          +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-db.xml	21 Apr 2017 15:07:52 -0000	1.18.6.2
          @@ -65,7 +65,7 @@
                   The Database Creation Script
               example missing
                 
          -    The creation script calls a function in PL/pgSQL (PL/pgSQL is a procedural language extention to sql),
          +    The creation script calls a function in PL/pgSQL (PL/pgSQL is a procedural language extension to sql),
               content_type__create_type, which
               in turn creates the necessary database changes to support our data
               object.  Notice the use of "mfp."  This is derived from "My
          Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-pages.xml
          ===================================================================
          RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-pages.xml,v
          diff -u -N -r1.20.2.2 -r1.20.2.3
          --- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-pages.xml	6 Jan 2017 09:18:43 -0000	1.20.2.2
          +++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-pages.xml	21 Apr 2017 15:07:52 -0000	1.20.2.3
          @@ -20,7 +20,7 @@
             
             
               Page Map
          -    Our package will have two visible pages.  The first shows a list of all objects; the second shows a single object in view or edit mode, and can also be used to add an object.  The index page will display the list, but since we might reuse the list later, we'll put it in a seperate file and include it on the index page.
          +    Our package will have two visible pages.  The first shows a list of all objects; the second shows a single object in view or edit mode, and can also be used to add an object.  The index page will display the list, but since we might reuse the list later, we'll put it in a separate file and include it on the index page.
                 
          Page Map Index: openacs-4/packages/acs-core-docs/www/xml/engineering-standards/cvs.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/engineering-standards/cvs.xml,v diff -u -N -r1.6.14.2 -r1.6.14.3 --- openacs-4/packages/acs-core-docs/www/xml/engineering-standards/cvs.xml 5 Aug 2016 14:27:22 -0000 1.6.14.2 +++ openacs-4/packages/acs-core-docs/www/xml/engineering-standards/cvs.xml 21 Apr 2017 15:07:52 -0000 1.6.14.3 @@ -152,7 +152,7 @@ .LRN consists of a given version openacs core, plus a set of packages. These are collectively packages together to form a - distrubution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0. + distribution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0. .LRN also uses an OpenACS install.xml file during installation; this file is distributed within the dotlrn package and must be moved. To get a development checkout of .LRN in the subdirectory Index: openacs-4/packages/acs-core-docs/www/xml/engineering-standards/filenaming.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/engineering-standards/filenaming.xml,v diff -u -N -r1.7.2.2 -r1.7.2.3 --- openacs-4/packages/acs-core-docs/www/xml/engineering-standards/filenaming.xml 11 Nov 2016 08:53:59 -0000 1.7.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/engineering-standards/filenaming.xml 21 Apr 2017 15:07:52 -0000 1.7.2.3 @@ -286,7 +286,7 @@ A mandatory documentation string is the first argument. This has -the standard form with javadoc-style @author, @cvs-id, etc, and should contain a short description of the recieved variables and any necessary explanations. +the standard form with javadoc-style @author, @cvs-id, etc, and should contain a short description of the received variables and any necessary explanations. The second argument specifies the page inputs. The syntax for switches/flags (e.g. multiple-list, array, Index: openacs-4/packages/acs-core-docs/www/xml/engineering-standards/plsql.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/engineering-standards/plsql.xml,v diff -u -N -r1.6.14.1 -r1.6.14.2 --- openacs-4/packages/acs-core-docs/www/xml/engineering-standards/plsql.xml 23 Jun 2016 08:32:46 -0000 1.6.14.1 +++ openacs-4/packages/acs-core-docs/www/xml/engineering-standards/plsql.xml 21 Apr 2017 15:07:52 -0000 1.6.14.2 @@ -126,7 +126,7 @@ - To achieve this we must fully qualify arguements passed into + To achieve this we must fully qualify arguments passed into procedures or functions when using them inside a SQL statement. This will get rid of any ambiguities in your code, i.e. it will tell the parser when you want the value of the column @@ -202,7 +202,7 @@ takes the optional argument object_id. Do this to allow people to use the same API call when they are doing double - click protection, that is, tehy have already gotten an + click protection, that is, they have already gotten an object_id and now they want to create the object with that object_id. Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/aolserver4.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/aolserver4.xml,v diff -u -N -r1.31.2.1 -r1.31.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/aolserver4.xml 23 Jun 2016 08:32:46 -0000 1.31.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/aolserver4.xml 21 Apr 2017 15:07:52 -0000 1.31.2.2 @@ -100,7 +100,7 @@ Configure, compile and install AOLserver - Many people need to run more than one version of AOLserver in parallel. This section accomodates future upgrades by installing AOLserver 4 in /usr/local/aolserver40r9. + Many people need to run more than one version of AOLserver in parallel. This section accommodates future upgrades by installing AOLserver 4 in /usr/local/aolserver40r9. [root aolserver]# cd /usr/local/src/aolserver40r10/aolserver [root aolserver]# ./configure --prefix=/usr/local/aolserver40r10 --with-tcl=/usr/local/lib/ @@ -170,7 +170,7 @@ Edit the CONFIG file. Uncomment the instructions meant for AOLserver 4, but edit it to look like this: ../configure --enable-threads --disable-tdomalloc --prefix=/usr/local/aolserver --with-tcl=/usr/local/lib - Note that the location of the Tcl library may vary on differnt platforms (e.g. for Debian 3.0: --with-tcl=/usr/lib/tcl8.4) + Note that the location of the Tcl library may vary on different platforms (e.g. for Debian 3.0: --with-tcl=/usr/lib/tcl8.4) Now you can compile and configure tDOM [root unix]# sh CONFIG [root unix]# make install Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml,v diff -u -N -r1.13.2.1 -r1.13.2.2 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml 23 Jun 2016 08:32:46 -0000 1.13.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/configuring.xml 21 Apr 2017 15:07:52 -0000 1.13.2.2 @@ -209,7 +209,7 @@ A templated page uses an ADP/Tcl pair. The first line in the ADP file is usually: <master> - If it appears exactly like this, without any arguments, the template processer uses default-master for that subsite. For pages in /var/lib/aolserver/$OPENACS_SERVICE_NAME/www, this is /var/lib/aolserver/$OPENACS_SERVICE_NAME/www/default-master.adp and the associated .tcl file. + If it appears exactly like this, without any arguments, the template processor uses default-master for that subsite. For pages in /var/lib/aolserver/$OPENACS_SERVICE_NAME/www, this is /var/lib/aolserver/$OPENACS_SERVICE_NAME/www/default-master.adp and the associated .tcl file. Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml,v diff -u -N -r1.21.14.2 -r1.21.14.3 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml 4 Dec 2016 11:24:07 -0000 1.21.14.2 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/oracle.xml 21 Apr 2017 15:07:53 -0000 1.21.14.3 @@ -920,7 +920,7 @@ Run the script. Switch to the oracle user first to set the environment appropriately and then do su to get root privileges, while keeping - the oracle user's enviroment. + the oracle user's environment. 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 -N -r1.29.14.2 -r1.29.14.3 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml 3 Oct 2016 09:17:51 -0000 1.29.14.2 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml 21 Apr 2017 15:07:53 -0000 1.29.14.3 @@ -511,7 +511,7 @@ tsearch2 from a package, you can use the http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/regprocedure_update.sql regprocedure script to update the database after tsearch2 is - installed into it. TODO link to section decribing how to fix + installed into it. TODO link to section describing how to fix an existing tsearch2 database with this patch. @@ -1088,7 +1088,7 @@ - SSL support must be enabled seperately in each OpenACS + SSL support must be enabled separately in each OpenACS server (. If your ports for SSL are privileged (below 1024), you @@ -1145,7 +1145,7 @@ By Malte Sussdorff - This section is work in progress. It will detail how you can install Squirrelmail as a webmail frontend for OpenACS, thereby neglecting the need to have a seperate webmail package within OpenACS + This section is work in progress. It will detail how you can install Squirrelmail as a webmail frontend for OpenACS, thereby neglecting the need to have a separate webmail package within OpenACS [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]# cd www [$OPENACS_SERVICE_NAME www]# wget http://cesnet.dl.sourceforge.net/sourceforge/squirrelmail/squirrelmail-1.4.4.tar.gz [$OPENACS_SERVICE_NAME www]# tar xfz squirrelmail-1.4.4.tar.gz Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml,v diff -u -N -r1.17.6.2 -r1.17.6.3 --- openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml 3 Oct 2016 09:17:51 -0000 1.17.6.2 +++ openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml 21 Apr 2017 15:07:53 -0000 1.17.6.3 @@ -214,7 +214,7 @@ Back up all of the files in the service, including the database backup file but excluding the auto-generated supervise directory, which is - unneccesary and has complicated permissions. + unnecessary and has complicated permissions. In the tar command, 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 -N -r1.11.2.2 -r1.11.2.3 --- openacs-4/packages/acs-core-docs/www/xml/kernel/db-api.xml 23 Jun 2016 08:32:47 -0000 1.11.2.2 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/db-api.xml 21 Apr 2017 15:07:53 -0000 1.11.2.3 @@ -870,7 +870,7 @@ db_blob_get_file statement-name sql [ -bind bind_set_id | -bind bind_value_list ] -Analagous to ns_ora write_clob/write_blob/blob_get_file. +Analogous to ns_ora write_clob/write_blob/blob_get_file. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth.xml,v diff -u -N -r1.4.6.3 -r1.4.6.4 --- openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth.xml 3 Oct 2016 09:17:51 -0000 1.4.6.3 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/ext-auth.xml 21 Apr 2017 15:07:53 -0000 1.4.6.4 @@ -330,7 +330,7 @@ EXT-AUTH-15 B - On-demand syncronization + On-demand synchronization @@ -539,7 +539,7 @@ hours. The other advantage is that we can still offer certain functionality to you, even when your login is not trusted. For -example, we could let you browse publically available forums, and +example, we could let you browse publicly available forums, and only when you want to post do you need to log in. This makes it even more feasible to have a more secure login expiration setting. Index: openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml,v diff -u -N -r1.7.2.1 -r1.7.2.2 --- openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml 23 Jun 2016 08:32:47 -0000 1.7.2.1 +++ openacs-4/packages/acs-core-docs/www/xml/kernel/i18n-requirements.xml 21 Apr 2017 15:07:53 -0000 1.7.2.2 @@ -681,7 +681,7 @@ 100.10 Since UTF8 strings can use up to three (UCS2) or six (UCS4) bytes per character, make sure that column size declarations in the schema are large enough to -accomodate required data (such as email addresses in +accommodate required data (such as email addresses in Japanese). Since 5.0.0, this is covered in the database install instructions for both PostgreSQL and Oracle. Index: openacs-4/packages/xowf/tcl/test-item-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xowf/tcl/test-item-procs.tcl,v diff -u -N -r1.2.2.5 -r1.2.2.6 --- openacs-4/packages/xowf/tcl/test-item-procs.tcl 27 Mar 2017 10:37:42 -0000 1.2.2.5 +++ openacs-4/packages/xowf/tcl/test-item-procs.tcl 21 Apr 2017 15:11:28 -0000 1.2.2.6 @@ -387,7 +387,7 @@ # Build a complex form composed of the specified form pages names # contained in the value of this field. The form-fields have to # be renamed. This affects the input field names in the form and - # the form constaints. We use the item-id contained pages as a the + # the form constraints. We use the item-id contained pages as a the # prefix for the form-fields. This method must be most likely # extended for other question types. # Index: openacs-4/packages/xowf/tcl/xowf-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xowf/tcl/xowf-procs.tcl,v diff -u -N -r1.3.2.13 -r1.3.2.14 --- openacs-4/packages/xowf/tcl/xowf-procs.tcl 27 Mar 2017 10:37:42 -0000 1.3.2.13 +++ openacs-4/packages/xowf/tcl/xowf-procs.tcl 21 Apr 2017 15:11:28 -0000 1.3.2.14 @@ -820,7 +820,7 @@ } WorkflowPage ad_instproc is_wf_instance {} { - Check, if the current page is a workflow instance (page, refering to a workflow) + Check, if the current page is a workflow instance (page, referring to a workflow) } { # we cannot call get_template_object here, because this will lead # to a recursive loop. Index: openacs-4/packages/acs-admin/catalog/acs-admin.it_IT.ISO-8859-1.xml =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-admin/catalog/acs-admin.it_IT.ISO-8859-1.xml,v diff -u -N -r1.1.2.1 -r1.1.2.2 --- openacs-4/packages/acs-admin/catalog/acs-admin.it_IT.ISO-8859-1.xml 14 Feb 2017 18:29:50 -0000 1.1.2.1 +++ openacs-4/packages/acs-admin/catalog/acs-admin.it_IT.ISO-8859-1.xml 21 Apr 2017 15:17:23 -0000 1.1.2.2 @@ -11,23 +11,23 @@ Sei sicuro/a di voler eliminare l'authority %authorities.pretty_name%? Autenticazione Nome authority - Questo viene usato quando ci si riferisce all'authorithy nei parametri ecc. Anche se dovessi cambiare il nome visualizzato sopra, questo dovrebbe rimanere immutato. + Questo viene usato quando ci si riferisce all'authority nei parametri ecc. Anche se dovessi cambiare il nome visualizzato sopra, questo dovrebbe rimanere immutato. Sincronizzazione batch abilitata Sincronizzazione batch URL di modifica password Al posto di un driver per la gestione delle password, puoi fornire un URL verso il quale gli utenti saranno reindirizzati quando volessero cambiare la loro password. Qualsiasi username in questo URL deve essere nella forma foo={username} and {username} sar� sostituito con il vero username. Utente creazione Elimina Callback di eliminazione - Disabilita questa authorithy + Disabilita questa authority Documento Ora fine documento Messaggio documento Ora inizio documento Status documento scarica Callback di modifica - Abilita questa authorithy + Abilita questa authority Abilitato/a Ora fine Generale Index: openacs-4/packages/acs-admin/www/auth/authority-delete.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-admin/www/auth/authority-delete.tcl,v diff -u -N -r1.4.2.1 -r1.4.2.2 --- openacs-4/packages/acs-admin/www/auth/authority-delete.tcl 10 Sep 2015 08:21:06 -0000 1.4.2.1 +++ openacs-4/packages/acs-admin/www/auth/authority-delete.tcl 21 Apr 2017 15:17:23 -0000 1.4.2.2 @@ -18,7 +18,7 @@ ad_returnredirect "." } else { - ad_return_error "Cannot delete authority" "Deleting this authority would mean that all site-wide administrator users are shut out from the system, meaning the system could no longer be adminstered." + ad_return_error "Cannot delete authority" "Deleting this authority would mean that all site-wide administrator users are shut out from the system, meaning the system could no longer be administered." } # Local variables: Index: openacs-4/packages/acs-admin/www/auth/authority-set-enabled-p.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-admin/www/auth/authority-set-enabled-p.tcl,v diff -u -N -r1.4.2.1 -r1.4.2.2 --- openacs-4/packages/acs-admin/www/auth/authority-set-enabled-p.tcl 10 Sep 2015 08:21:06 -0000 1.4.2.1 +++ openacs-4/packages/acs-admin/www/auth/authority-set-enabled-p.tcl 21 Apr 2017 15:17:23 -0000 1.4.2.2 @@ -22,7 +22,7 @@ ad_returnredirect . ad_script_abort } else { - ad_return_error "Cannot disable authority" "Disabling this authority would mean that all site-wide administrator users are shut out from the system, meaning the system could no longer be adminstered." + ad_return_error "Cannot disable authority" "Disabling this authority would mean that all site-wide administrator users are shut out from the system, meaning the system could no longer be administered." } # Local variables: Index: openacs-4/packages/acs-admin/www/users/one.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-admin/www/users/one.tcl,v diff -u -N -r1.17.2.5 -r1.17.2.6 --- openacs-4/packages/acs-admin/www/users/one.tcl 22 Feb 2017 12:02:27 -0000 1.17.2.5 +++ openacs-4/packages/acs-admin/www/users/one.tcl 21 Apr 2017 15:17:23 -0000 1.17.2.6 @@ -35,7 +35,7 @@ set ad_conn_user_id [ad_conn user_id] # -# Define the url for switching side-wide admin priviledges with a timeout of 60 seconds +# Define the url for switching side-wide admin privileges with a timeout of 60 seconds # if { $site_wide_admin_p } { set modify_admin_url [export_vars -base modify-admin-privileges {user_id:sign(max_age=60) {action:sign revoke}}]