Index: openacs-4/packages/acs-core-docs/www/backup-recovery.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/backup-recovery.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/backup-recovery.adp	3 Sep 2021 09:14:49 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/backup-recovery.adp	7 Sep 2021 09:39:19 -0000	1.4.2.6
@@ -27,7 +27,7 @@
 to set up, are far from the best solution).</p><p>There are three basic things which need to be backed up, the
 database data, the server source tree, and the
 acs-content-repository (which is in the server source tree).</p><div class="figure">
-<a name="idp140665974112560" id="idp140665974112560"></a><p class="title"><strong>Figure 8.1. Backup and Recovery
+<a name="idp140697730262912" id="idp140697730262912"></a><p class="title"><strong>Figure 8.1. Backup and Recovery
 Strategy</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/backup.png" align="middle" alt="Backup and Recovery Strategy"></div></div>
 </div><p><br class="figure-break"></p>
 OpenACS docs are written by the named authors, and may be edited by
Index: openacs-4/packages/acs-core-docs/www/backup-recovery.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/backup-recovery.html,v
diff -u -r1.46.2.4 -r1.46.2.5
--- openacs-4/packages/acs-core-docs/www/backup-recovery.html	3 Sep 2021 09:14:50 -0000	1.46.2.4
+++ openacs-4/packages/acs-core-docs/www/backup-recovery.html	7 Sep 2021 09:39:19 -0000	1.46.2.5
@@ -6,7 +6,7 @@
     oracle, while easy to set up, are far from the best solution).
     </p><p>There are three basic things which need to be backed up, the database data, the server 
     source tree, and the acs-content-repository (which is in the server source tree).</p><p>
-    </p><div class="figure"><a name="idp140665974112560"></a><p class="title"><b>Figure 8.1. Backup and Recovery Strategy</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/backup.png" align="middle" alt="Backup and Recovery Strategy"></div></div></div><p><br class="figure-break">
+    </p><div class="figure"><a name="idp140697730262912"></a><p class="title"><b>Figure 8.1. Backup and Recovery Strategy</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/backup.png" align="middle" alt="Backup and Recovery Strategy"></div></div></div><p><br class="figure-break">
   </p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
Index: openacs-4/packages/acs-core-docs/www/configuring-configuring-packages.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-configuring-packages.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/configuring-configuring-packages.adp	3 Sep 2021 09:14:51 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/configuring-configuring-packages.adp	7 Sep 2021 09:39:20 -0000	1.4.2.6
@@ -16,7 +16,7 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823498496" id="idp140665823498496"></a>Configuring an OpenACS package</h3></div></div></div><p>After you&#39;ve installed and mounted your package, you can
+<a name="idp140698011136128" id="idp140698011136128"></a>Configuring an OpenACS package</h3></div></div></div><p>After you&#39;ve installed and mounted your package, you can
 configure each instance to act as you would like.</p><p>This is done from the Applications page. Log in, go to the Admin
 or Control Panel, click on the subsite the application is in, and
 click on Applications. If you click on the 'Parameters'
Index: openacs-4/packages/acs-core-docs/www/configuring-configuring-packages.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-configuring-packages.html,v
diff -u -r1.13.2.4 -r1.13.2.5
--- openacs-4/packages/acs-core-docs/www/configuring-configuring-packages.html	3 Sep 2021 09:14:51 -0000	1.13.2.4
+++ openacs-4/packages/acs-core-docs/www/configuring-configuring-packages.html	7 Sep 2021 09:39:20 -0000	1.13.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Configuring an OpenACS package</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="configuring-new-site.html" title="Chapter 4. Configuring a new OpenACS Site"><link rel="previous" href="configuring-mounting-packages.html" title="Mounting OpenACS packages"><link rel="next" href="configuring-configuring-permissions.html" title="Setting Permissions on an OpenACS package"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="configuring-mounting-packages.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Configuring a new OpenACS Site</th><td width="20%" align="right"> <a accesskey="n" href="configuring-configuring-permissions.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuring-configuring-packages"></a>Configuring an OpenACS package</h2></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:jade@rubick.com" target="_top">Jade Rubick</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823498496"></a>Configuring an OpenACS package</h3></div></div></div><p>After you've installed and mounted your package, you can
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011136128"></a>Configuring an OpenACS package</h3></div></div></div><p>After you've installed and mounted your package, you can
       configure each instance to act as you would like. </p><p>This is done from the Applications page. Log in, go to the
       Admin or Control Panel, click on the subsite the application is
       in, and click on Applications. If you click on the 'Parameters'
Index: openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.adp	3 Sep 2021 09:14:51 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.adp	7 Sep 2021 09:39:20 -0000	1.4.2.6
@@ -16,7 +16,7 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823748848" id="idp140665823748848"></a>Setting Permission on an OpenACS
+<a name="idp140698011124144" id="idp140698011124144"></a>Setting Permission on an OpenACS
 package</h3></div></div></div><p>After you&#39;ve installed and mounted your package, you can
 configure each instance to act as you would like.</p><p>This is done from the Applications page. Log in, go to the Admin
 or Control Panel, click on the subsite the application is in, and
Index: openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.html,v
diff -u -r1.13.2.4 -r1.13.2.5
--- openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.html	3 Sep 2021 09:14:51 -0000	1.13.2.4
+++ openacs-4/packages/acs-core-docs/www/configuring-configuring-permissions.html	7 Sep 2021 09:39:20 -0000	1.13.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Setting Permissions on an OpenACS package</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="configuring-new-site.html" title="Chapter 4. Configuring a new OpenACS Site"><link rel="previous" href="configuring-configuring-packages.html" title="Configuring an OpenACS package"><link rel="next" href="how-do-I.html" title="How Do I?"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="configuring-configuring-packages.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Configuring a new OpenACS Site</th><td width="20%" align="right"> <a accesskey="n" href="how-do-I.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuring-configuring-permissions"></a>Setting Permissions on an OpenACS package</h2></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:jade@rubick.com" target="_top">Jade Rubick</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823748848"></a>Setting Permission on an OpenACS package</h3></div></div></div><p>After you've installed and mounted your package, you can
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011124144"></a>Setting Permission on an OpenACS package</h3></div></div></div><p>After you've installed and mounted your package, you can
       configure each instance to act as you would like. </p><p>This is done from the Applications page. Log in, go to the
       Admin or Control Panel, click on the subsite the application is
       in, and click on Applications. If you click on the 'Permissions'
Index: openacs-4/packages/acs-core-docs/www/configuring-install-packages.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-install-packages.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/configuring-install-packages.adp	3 Sep 2021 09:14:51 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/configuring-install-packages.adp	7 Sep 2021 09:39:20 -0000	1.4.2.6
@@ -15,7 +15,7 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665974379472" id="idp140665974379472"></a>Installing OpenACS packages</h3></div></div></div><p>An OpenACS package extends your website and lets it do things it
+<a name="idp140698455376816" id="idp140698455376816"></a>Installing OpenACS packages</h3></div></div></div><p>An OpenACS package extends your website and lets it do things it
 was not able to do before. You can have a weblog, a forums, a
 calendar, or even do sophisticated project-management via your
 website.</p><p>After you&#39;ve installed OpenACS, you can congratulate
Index: openacs-4/packages/acs-core-docs/www/configuring-install-packages.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-install-packages.html,v
diff -u -r1.13.2.4 -r1.13.2.5
--- openacs-4/packages/acs-core-docs/www/configuring-install-packages.html	3 Sep 2021 09:14:52 -0000	1.13.2.4
+++ openacs-4/packages/acs-core-docs/www/configuring-install-packages.html	7 Sep 2021 09:39:20 -0000	1.13.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Installing OpenACS packages</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="configuring-new-site.html" title="Chapter 4. Configuring a new OpenACS Site"><link rel="previous" href="configuring-new-site.html" title="Chapter 4. Configuring a new OpenACS Site"><link rel="next" href="configuring-mounting-packages.html" title="Mounting OpenACS packages"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="configuring-new-site.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Configuring a new OpenACS Site</th><td width="20%" align="right"> <a accesskey="n" href="configuring-mounting-packages.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuring-install-packages"></a>Installing OpenACS packages</h2></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:jade@rubick.com" target="_top">Jade Rubick</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665974379472"></a>Installing OpenACS packages</h3></div></div></div><p>An OpenACS package extends your website and lets it do
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698455376816"></a>Installing OpenACS packages</h3></div></div></div><p>An OpenACS package extends your website and lets it do
       things it was not able to do before. You can have a weblog, a
       forums, a calendar, or even do sophisticated project-management
       via your website.</p><p>After you've installed OpenACS, you can congratulate
Index: openacs-4/packages/acs-core-docs/www/configuring-mounting-packages.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-mounting-packages.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/configuring-mounting-packages.adp	3 Sep 2021 09:14:52 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/configuring-mounting-packages.adp	7 Sep 2021 09:39:21 -0000	1.4.2.6
@@ -15,7 +15,7 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823687376" id="idp140665823687376"></a>Mounting OpenACS packages</h3></div></div></div><p>After you&#39;ve installed your packages, you have to
+<a name="idp140698011165616" id="idp140698011165616"></a>Mounting OpenACS packages</h3></div></div></div><p>After you&#39;ve installed your packages, you have to
 'mount' them in order to make them appear on your
 website.</p><p>Make sure you are logged in, and then click on the
 'Admin' or 'Control Panel' link to get to the
Index: openacs-4/packages/acs-core-docs/www/configuring-mounting-packages.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/configuring-mounting-packages.html,v
diff -u -r1.13.2.4 -r1.13.2.5
--- openacs-4/packages/acs-core-docs/www/configuring-mounting-packages.html	3 Sep 2021 09:14:52 -0000	1.13.2.4
+++ openacs-4/packages/acs-core-docs/www/configuring-mounting-packages.html	7 Sep 2021 09:39:21 -0000	1.13.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Mounting OpenACS packages</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="configuring-new-site.html" title="Chapter 4. Configuring a new OpenACS Site"><link rel="previous" href="configuring-install-packages.html" title="Installing OpenACS packages"><link rel="next" href="configuring-configuring-packages.html" title="Configuring an OpenACS package"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="configuring-install-packages.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Configuring a new OpenACS Site</th><td width="20%" align="right"> <a accesskey="n" href="configuring-configuring-packages.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="configuring-mounting-packages"></a>Mounting OpenACS packages</h2></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:jade@rubick.com" target="_top">Jade Rubick</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823687376"></a>Mounting OpenACS packages</h3></div></div></div><p>After you've installed your packages, you have to 'mount'
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011165616"></a>Mounting OpenACS packages</h3></div></div></div><p>After you've installed your packages, you have to 'mount'
       them in order to make them appear on your website.</p><p>Make sure you are logged in, and then click on the
       'Admin' or 'Control Panel' link to get to the Site-Wide
       Administration page (at /acs-admin). Click on the subsite you'd
Index: openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp,v
diff -u -r1.5.2.6 -r1.5.2.7
--- openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp	3 Sep 2021 09:14:53 -0000	1.5.2.6
+++ openacs-4/packages/acs-core-docs/www/cvs-guidelines.adp	7 Sep 2021 09:39:21 -0000	1.5.2.7
@@ -18,7 +18,7 @@
 <div class="titlepage"><div><div><h3 class="title">
 <a name="using-cvs-with-openacs" id="using-cvs-with-openacs"></a>Using CVS with OpenACS</h3></div></div></div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665975061728" id="idp140665975061728"></a>Getting Started</h4></div></div></div><p>All OpenACS code is available anonymously. To get code
+<a name="idp140698005779616" id="idp140698005779616"></a>Getting Started</h4></div></div></div><p>All OpenACS code is available anonymously. To get code
 anonymously, use the parameter <code class="computeroutput">-d:pserver:anonymous\@cvs.openacs.org:/cvsroot</code>
 immediately after <code class="computeroutput">cvs</code> in a cvs
 command to check out or export code.</p><p>If you are an OpenACS developer, you should check out code so
@@ -77,7 +77,7 @@
 </div>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665013540656" id="idp140665013540656"></a>Checkout for Package Development</h4></div></div></div><p>If you are actively developing a non-core package, you should
+<a name="idp140698006039264" id="idp140698006039264"></a>Checkout for Package Development</h4></div></div></div><p>If you are actively developing a non-core package, you should
 work from the latest core release branch. Currently this is
 oacs-5-9. This ensures that you are working on top of a stable
 OpenACS core, but still allows you to commit feature changes to
@@ -94,7 +94,7 @@
 packages and their current state.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665013165472" id="idp140665013165472"></a>Checkout for Core Development</h4></div></div></div><p>If you are actively developing packages in the OpenACS Core,
+<a name="idp140698006854768" id="idp140698006854768"></a>Checkout for Core Development</h4></div></div></div><p>If you are actively developing packages in the OpenACS Core,
 work from the HEAD branch. HEAD is used for active development of
 the next version of core OpenACS. It may be very buggy; it may not
 even install correctly. Do not use this branch for development of
@@ -103,7 +103,7 @@
 developer account:</p><pre class="screen"><span class="action"><span class="action">cvs -d:ext:cvs.openacs.org:/cvsroot checkout acs-core</span></span></pre><p>To check out HEAD anonymously:</p><pre class="screen"><span class="action"><span class="action">cvs -d:pserver:anonymous\@cvs.openacs.org:/cvsroot checkout acs-core</span></span></pre>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665013170144" id="idp140665013170144"></a>Checkout .LRN</h4></div></div></div><p>.LRN consists of a given version OpenACS core, plus a set of
+<a name="idp140698006498096" id="idp140698006498096"></a>Checkout .LRN</h4></div></div></div><p>.LRN consists of a given version OpenACS core, plus a set of
 packages. These are collectively packages together to form a
 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;
@@ -128,7 +128,7 @@
 <div class="titlepage"><div><div><h3 class="title">
 <a name="openacs-cvs-concepts" id="openacs-cvs-concepts"></a>OpenACS CVS Concepts</h3></div></div></div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665013424560" id="idp140665013424560"></a>Modules</h4></div></div></div><p>All OpenACS code resides within a single CVS module,
+<a name="idp140698006505856" id="idp140698006505856"></a>Modules</h4></div></div></div><p>All OpenACS code resides within a single CVS module,
 <code class="computeroutput">openacs-4</code>. (The openacs-4
 directory contains code for all versions of OpenACS 4 and later,
 and .LRN 1 and later.) Checking out this module retrieves all
@@ -163,7 +163,7 @@
 module of the same name.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665012962640" id="idp140665012962640"></a> Tags and Branches</h4></div></div></div><p>Tags and Branches look similar in commands, but behave
+<a name="idp140698006249792" id="idp140698006249792"></a> Tags and Branches</h4></div></div></div><p>Tags and Branches look similar in commands, but behave
 differently. A tag is a fixed point on a branch. Check out a tag to
 get a specific version of OpenACS. Check out a branch to get the
 most current code for that major-minor version (e.g., 5.0.x or
@@ -403,7 +403,7 @@
 </ol></div>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665013117168" id="idp140665013117168"></a> Informal Guidelines</h4></div></div></div><p>Informal guidelines which may be obsolete in places and should
+<a name="idp140698006696832" id="idp140698006696832"></a> Informal Guidelines</h4></div></div></div><p>Informal guidelines which may be obsolete in places and should
 be reviewed:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem"><p>Before committing to cvs you must submit a bug report and patch
 to the <a class="ulink" href="http://openacs.org/bugtracker/openacs" target="_top">OpenACS bug
Index: openacs-4/packages/acs-core-docs/www/cvs-guidelines.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/cvs-guidelines.html,v
diff -u -r1.14.2.5 -r1.14.2.6
--- openacs-4/packages/acs-core-docs/www/cvs-guidelines.html	3 Sep 2021 09:14:53 -0000	1.14.2.5
+++ openacs-4/packages/acs-core-docs/www/cvs-guidelines.html	7 Sep 2021 09:39:21 -0000	1.14.2.6
@@ -6,7 +6,7 @@
     </p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="using-cvs-with-openacs"></a>Using CVS with OpenACS</h3></div></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665975061728"></a>Getting Started</h4></div></div></div><p>
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="using-cvs-with-openacs"></a>Using CVS with OpenACS</h3></div></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698005779616"></a>Getting Started</h4></div></div></div><p>
         All OpenACS code is available anonymously.  To get code
       anonymously, use the parameter
       <code class="computeroutput">-d:pserver:anonymous@cvs.openacs.org:/cvsroot</code> immediately after <code class="computeroutput">cvs</code> in a cvs command to check out or export code.
@@ -53,7 +53,7 @@
 cd CVSROOT
 emacs avail</span></span></pre><p>Add an avail line of the form:</p><pre class="programlisting">avail|<span class="replaceable"><span class="replaceable">username</span></span>|openacs-4</pre><pre class="screen"><span class="action"><span class="action">cvs commit -m "added commit on X for username" avail</span></span></pre></li></ol></div></div><div class="sidebar"><div class="titlepage"><div><div><p class="title"><b></b></p></div></div></div><p>Branimir suggests an additional level of abstraction.  If you put</p><pre class="programlisting">Host cvs-server
       HostName cvs.openacs.org
-      User <span class="replaceable"><span class="replaceable">yournamehere</span></span></pre><p>into your <code class="computeroutput">~/.ssh/config</code> file, then you can use <code class="computeroutput">-d :ext:cvs-server:/cvsroot</code> instead of <code class="computeroutput">-d :ext:cvs.openacs.org:/cvsroot</code>.  You can then change the definition of <code class="computeroutput">cvs-server</code> by changing one file instead of editing hundreds of <code class="computeroutput">CVSROOT/Repository</code> files.</p></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665013540656"></a>Checkout for Package Development</h4></div></div></div><p>If you are actively developing a non-core package, you
+      User <span class="replaceable"><span class="replaceable">yournamehere</span></span></pre><p>into your <code class="computeroutput">~/.ssh/config</code> file, then you can use <code class="computeroutput">-d :ext:cvs-server:/cvsroot</code> instead of <code class="computeroutput">-d :ext:cvs.openacs.org:/cvsroot</code>.  You can then change the definition of <code class="computeroutput">cvs-server</code> by changing one file instead of editing hundreds of <code class="computeroutput">CVSROOT/Repository</code> files.</p></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698006039264"></a>Checkout for Package Development</h4></div></div></div><p>If you are actively developing a non-core package, you
       should work from the latest core release branch.  Currently this
       is oacs-5-9.  This ensures that you are working on top
       of a stable OpenACS core, but still allows you to commit feature
@@ -68,13 +68,13 @@
             Inventory</a> and <a class="ulink" href="http://openacs.org/projects/openacs/packages/" target="_top">Package
             maintainers and status</a> for a list of available
             packages and their current state.
-      </p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665013165472"></a>Checkout for Core Development</h4></div></div></div><p>If you are actively developing packages in the OpenACS
+      </p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698006854768"></a>Checkout for Core Development</h4></div></div></div><p>If you are actively developing packages in the OpenACS
       Core, work from the HEAD branch.  HEAD is used for active
               development of the next version of core OpenACS. It may be very
               buggy; it may not even install correctly. Do not use this branch for
               development of non-core features unless your work depends on some
               of the HEAD core work. To check out HEAD, omit the
-              <code class="computeroutput">-r</code> tag.</p><p></p><p>To check out HEAD for development, which requires an OpenACS developer account:</p><pre class="screen"><span class="action"><span class="action">cvs -d:ext:cvs.openacs.org:/cvsroot checkout acs-core</span></span></pre><p>To check out HEAD anonymously:</p><pre class="screen"><span class="action"><span class="action">cvs -d:pserver:anonymous@cvs.openacs.org:/cvsroot checkout acs-core</span></span></pre></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665013170144"></a>Checkout .LRN</h4></div></div></div><p>
+              <code class="computeroutput">-r</code> tag.</p><p></p><p>To check out HEAD for development, which requires an OpenACS developer account:</p><pre class="screen"><span class="action"><span class="action">cvs -d:ext:cvs.openacs.org:/cvsroot checkout acs-core</span></span></pre><p>To check out HEAD anonymously:</p><pre class="screen"><span class="action"><span class="action">cvs -d:pserver:anonymous@cvs.openacs.org:/cvsroot checkout acs-core</span></span></pre></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698006498096"></a>Checkout .LRN</h4></div></div></div><p>
         .LRN consists of a given version OpenACS core, plus a set of
         packages. These are collectively packages together to form a
         distribution of .LRN. F .LRN 2.0.0 sits on top of OpenACS 5.0.0.
@@ -89,7 +89,7 @@
 mv dotlrn/install.xml ..</span></span></pre></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="working-with-cvs"></a>Working with CVS</h4></div></div></div><p>
       Once you have a checkout you can use some commands to track
       what has changed since you checked out your copy.  <code class="computeroutput">cvs -n update</code> does not change any files, but reports which changes have been updated or locally modified, or are not present in CVS.
-    </p><p>To update your files, use <code class="computeroutput">cvs update</code>.  This will merge changes from the repository with your local files.  It has no effect on the cvs.openacs.org repository.</p></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="openacs-cvs-concepts"></a>OpenACS CVS Concepts</h3></div></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665013424560"></a>Modules</h4></div></div></div><p>
+    </p><p>To update your files, use <code class="computeroutput">cvs update</code>.  This will merge changes from the repository with your local files.  It has no effect on the cvs.openacs.org repository.</p></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="openacs-cvs-concepts"></a>OpenACS CVS Concepts</h3></div></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698006505856"></a>Modules</h4></div></div></div><p>
         All OpenACS code resides within a single CVS module, <code class="computeroutput">openacs-4</code>.  (The openacs-4 directory contains code for all versions of OpenACS 4 and later, and .LRN 1 and later.)   Checking out this module retrieves all OpenACS code of any type.  For convenience, subsets of <code class="computeroutput">openacs-4</code> are repackaged as smaller modules.</p><p>
           <code class="computeroutput">acs-core</code> contains only critical common
           packages. It does not have any user applications, such as forums,
@@ -117,7 +117,7 @@
           <code class="computeroutput">project-manager-all</code> contains the packages required, in combination with acs-core, to run the project-manager package.
         </p><p>
           Each OpenACS package (i.e., directory in <code class="computeroutput">openacs-4/packages/</code>) is also aliased as a module of the same name.
-        </p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665012962640"></a>
+        </p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698006249792"></a>
         Tags and Branches
       </h4></div></div></div><p>
         Tags and Branches look similar in commands, but behave differently. A tag is a fixed point on a branch.  Check out
@@ -317,7 +317,7 @@
           flag which defaults to no-effect wouldn't require a TIP. Added a
           new mandatory flag to an existing function would require a
           TIP.
-        </p></li></ol></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665013117168"></a>
+        </p></li></ol></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698006696832"></a>
       Informal Guidelines
     </h4></div></div></div><p>
       Informal guidelines which may be obsolete in places and should be reviewed:
Index: openacs-4/packages/acs-core-docs/www/cvs-tips.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/cvs-tips.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/cvs-tips.adp	3 Sep 2021 09:14:54 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/cvs-tips.adp	7 Sep 2021 09:39:21 -0000	1.4.2.6
@@ -16,7 +16,7 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><p>
 <a name="cvs-service-import" id="cvs-service-import"></a><strong>Add the Service to CVS -
-OPTIONAL. </strong><a class="indexterm" name="idp140665822462816" id="idp140665822462816"></a>These steps take
+OPTIONAL. </strong><a class="indexterm" name="idp140698286296560" id="idp140698286296560"></a>These steps take
 an existing OpenACS directory and add it to a <a class="link" href="install-cvs" title="Initialize CVS (OPTIONAL)">CVS
 repository</a>.</p><div class="orderedlist"><ol class="orderedlist" type="1">
 <li class="listitem">
Index: openacs-4/packages/acs-core-docs/www/cvs-tips.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/cvs-tips.html,v
diff -u -r1.37.2.4 -r1.37.2.5
--- openacs-4/packages/acs-core-docs/www/cvs-tips.html	3 Sep 2021 09:14:54 -0000	1.37.2.4
+++ openacs-4/packages/acs-core-docs/www/cvs-tips.html	7 Sep 2021 09:39:22 -0000	1.37.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Appendix D. Using CVS with an OpenACS Site</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="acs-package-dev.html" title="Part III. For OpenACS Package Developers"><link rel="previous" href="i18n-translators.html" title="Translator's Guide"><link rel="next" href="acs-plat-dev.html" title="Part IV. For OpenACS Platform Developers"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="i18n-translators.html">Prev</a> </td><th width="60%" align="center">Part III. For OpenACS Package Developers</th><td width="20%" align="right"> <a accesskey="n" href="acs-plat-dev.html">Next</a></td></tr></table><hr></div><div class="appendix"><div class="titlepage"><div><div><h2 class="title"><a name="cvs-tips"></a>Appendix D. Using CVS with an OpenACS Site</h2></div></div></div><div class="authorblurb"><p>      By <a class="ulink" href="mailto:joel@aufrecht.org" target="_top">Joel Aufrecht</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><p><a name="cvs-service-import"></a><b>Add the Service to CVS - OPTIONAL. </b><a class="indexterm" name="idp140665822462816"></a>These steps take an existing OpenACS directory and add
+        </div><p><a name="cvs-service-import"></a><b>Add the Service to CVS - OPTIONAL. </b><a class="indexterm" name="idp140698286296560"></a>These steps take an existing OpenACS directory and add
           it to a <a class="link" href="install-cvs.html" title="Initialize CVS (OPTIONAL)">CVS
           repository</a>.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Create and set permissions on a subdirectory in the local cvs repository.</p><pre class="screen">[root root]# <strong class="userinput"><code>mkdir /cvsroot/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></code></strong>
 [root root]#<strong class="userinput"><code> chown <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME.$OPENACS_SERVICE_NAME</span></span> /cvsroot/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></code></strong>
Index: openacs-4/packages/acs-core-docs/www/docbook-primer.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/docbook-primer.adp,v
diff -u -r1.6.2.7 -r1.6.2.8
--- openacs-4/packages/acs-core-docs/www/docbook-primer.adp	3 Sep 2021 09:14:55 -0000	1.6.2.7
+++ openacs-4/packages/acs-core-docs/www/docbook-primer.adp	7 Sep 2021 09:39:23 -0000	1.6.2.8
@@ -409,7 +409,7 @@
 tools will be marked up to conform to the <a class="ulink" href="http://docbook.org/xml/index.html" target="_top">DocBook XML
 DTD</a>. The remaining discussion is about publishing using
 Docbook.</p><p>
-<a class="indexterm" name="idp140665822014416" id="idp140665822014416"></a> is a publishing standard based on XML
+<a class="indexterm" name="idp140697733797888" id="idp140697733797888"></a> is a publishing standard based on XML
 with similar goals to the OpenACS Documentation project. Some
 specific reasons why we are using DocBook:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem"><p>It is open-source.</p></li><li class="listitem"><p>The DocBook community <a class="ulink" href="http://docbook.org/help" target="_top">mailing lists</a>
@@ -449,7 +449,7 @@
 of elements</a> and use more exotic features in your documents. The
 list is made up of SGML-elements but basically the same elements
 are valid in the XML DTD <span class="strong"><strong>as long as
-you remember to</strong></span>: <a class="indexterm" name="idp140665975637728" id="idp140665975637728"></a>
+you remember to</strong></span>: <a class="indexterm" name="idp140697734146944" id="idp140697734146944"></a>
 </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem"><p>Always close your tags with corresponding end-tags and to
 <span class="strong"><strong>not use other tag
@@ -490,7 +490,7 @@
 <div class="titlepage"><div><div><h3 class="title">
 <a name="dbprimer-structure" id="dbprimer-structure"></a>Document Structure</h3></div></div></div><p>The documentation for each package will make up a little
 "book" that is structured like this - examples are
-<span class="emphasis"><em>emphasized</em></span>: <a class="indexterm" name="idp140665974966240" id="idp140665974966240"></a>
+<span class="emphasis"><em>emphasized</em></span>: <a class="indexterm" name="idp140697733808672" id="idp140697733808672"></a>
 </p><pre class="programlisting">
     book                        : <span class="strong"><strong>Docs for one package</strong></span> - <span class="emphasis"><em>templating</em></span>
      |
@@ -515,19 +515,19 @@
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="dbprimer-sections" id="dbprimer-sections"></a>Headlines, Sections</h3></div></div></div><p>
-<a class="indexterm" name="idp140665823877280" id="idp140665823877280"></a> Given that your job starts at the
+<a class="indexterm" name="idp140697734129104" id="idp140697734129104"></a> Given that your job starts at the
 <code class="computeroutput">sect1</code>-level, all your documents
 should open with a <a class="ulink" href="http://docbook.org/tdg/en/html/sect1.html" target="_top"><code class="computeroutput">&lt;sect1&gt;</code></a>-tag
 and end with the corresponding <code class="computeroutput">&lt;/sect1&gt;</code>.</p><p>
-<a class="indexterm" name="idp140665823075360" id="idp140665823075360"></a> You need to feed every <code class="computeroutput">&lt;sect1&gt;</code> two attributes. The first
+<a class="indexterm" name="idp140697733816128" id="idp140697733816128"></a> You need to feed every <code class="computeroutput">&lt;sect1&gt;</code> two attributes. The first
 attribute, <code class="computeroutput">id</code>, is standard and
 can be used with all elements. It comes in very handy when
 interlinking between documents (more about this when talking about
 links in <a class="xref" href="docbook-primer" title="Links">the section called “Links”</a>). The value of
 <code class="computeroutput">id</code> has to be unique throughout
 the book you&#39;re making since the <code class="computeroutput">id</code>'s in your <code class="computeroutput">sect1</code>'s will turn into filenames when
 the book is parsed into HTML.</p><p>
-<a class="indexterm" name="idp140665822752272" id="idp140665822752272"></a> The other attribute is <code class="computeroutput">xreflabel</code>. The value of this is the text
+<a class="indexterm" name="idp140697733366080" id="idp140697733366080"></a> The other attribute is <code class="computeroutput">xreflabel</code>. The value of this is the text
 that will appear as the link when referring to this <code class="computeroutput">sect1</code>.</p><p>Right after the opening tag you put the title of the document -
 this is usually the same as <code class="computeroutput">xreflabel</code>-attribute. E.g. the top level of
 the document you&#39;re reading right now looks like this:</p><pre class="programlisting">
@@ -538,7 +538,7 @@
 
 &lt;/sect1&gt;
 </pre><p>
-<a class="indexterm" name="idp140665974349840" id="idp140665974349840"></a> Inside this container your document will
+<a class="indexterm" name="idp140697733370448" id="idp140697733370448"></a> Inside this container your document will
 be split up into <a class="ulink" href="http://docbook.org/tdg/en/html/sect2.html" target="_top"><code class="computeroutput">&lt;sect2&gt;</code></a>'s,
 each with the same requirements - <code class="computeroutput">id</code> and <code class="computeroutput">xreflabel</code> attributes, and a <code class="computeroutput">&lt;title&gt;</code>-tag inside. Actually, the
 <code class="computeroutput">xreflabel</code> is never required in
@@ -548,7 +548,7 @@
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="dbprimer-code" id="dbprimer-code"></a>Code</h3></div></div></div><p>
-<a class="indexterm" name="idp140665973829792" id="idp140665973829792"></a> For displaying a snippet of code, a
+<a class="indexterm" name="idp140697733314448" id="idp140697733314448"></a> For displaying a snippet of code, a
 filename or anything else you just want to appear as a part of a
 sentence, we use <a class="ulink" href="http://docbook.org/tdg/en/html/computeroutput.html" target="_top"><code class="computeroutput">&lt;computeroutput&gt;</code></a> and <a class="ulink" href="http://docbook.org/tdg/en/html/code.html" target="_top"><code class="code">&lt;code&gt;</code></a> tags. These
 replace the HTML-tag <code class="code">&lt;code&gt;</code> tag,
@@ -562,15 +562,15 @@
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="dbprimer-links" id="dbprimer-links"></a>Links</h3></div></div></div><p>
-<a class="indexterm" name="idp140665013477248" id="idp140665013477248"></a> Linking falls into two different
+<a class="indexterm" name="idp140697733358768" id="idp140697733358768"></a> Linking falls into two different
 categories: inside the book you&#39;re making and outside:</p><div class="variablelist"><dl class="variablelist">
 <dt><span class="term"><span class="strong"><strong>1. Inside
 linking, cross-referencing other parts of your
 book</strong></span></span></dt><dd>
 <p>By having unique <code class="computeroutput">id</code>'s
 you can cross-reference any part of your book with a simple tag,
 regardless of where that part is.</p><p>
-<a class="indexterm" name="idp140665824170144" id="idp140665824170144"></a>Check out how I link to a subsection of
+<a class="indexterm" name="idp140697733362368" id="idp140697733362368"></a>Check out how I link to a subsection of
 the Developer&#39;s Guide:</p><p>Put this in your XML:</p><pre class="programlisting">
 - Find information about creating a package in
 &lt;xref linkend="packages-making-a-package"&gt;&lt;/xref&gt;.
@@ -594,7 +594,7 @@
 </dd><dt><span class="term"><span class="strong"><strong>2. Linking
 outside the documentation</strong></span></span></dt><dd>
 <p>
-<a class="indexterm" name="idp140665822702832" id="idp140665822702832"></a> If you&#39;re hyper-linking out of the
+<a class="indexterm" name="idp140697733436384" id="idp140697733436384"></a> If you&#39;re hyper-linking out of the
 documentation, it works almost the same way as HTML - the tag is
 just a little different (<a class="ulink" href="http://docbook.org/tdg/en/html/ulink.html" target="_top"><code class="computeroutput">&lt;ulink&gt;</code></a>):</p><pre class="programlisting">&lt;ulink url="http://www.oracle.com/"&gt;Oracle Corporation&lt;/ulink&gt;</pre><p>....will create a hyper-link to Oracle in the HTML-version of
 the documentation.</p><p>
@@ -611,7 +611,7 @@
 <span class="strong"><strong>Note:</strong></span> The graphics guidelines are
 not written in stone. Use another valid approach if it works better
 for you.</em></span></p><p>
-<a class="indexterm" name="idp140665013210416" id="idp140665013210416"></a> To insert a graphic we use the elements
+<a class="indexterm" name="idp140697734233808" id="idp140697734233808"></a> To insert a graphic we use the elements
 <a class="ulink" href="http://docbook.org/tdg/en/html/mediaobject.html" target="_top"><code class="computeroutput">&lt;mediaobject&gt;</code></a>,
 <a class="ulink" href="http://docbook.org/tdg/en/html/imageobject.html" target="_top"><code class="computeroutput">&lt;imageobject&gt;</code></a>,
 <a class="ulink" href="http://docbook.org/tdg/en/html/imagedata.html" target="_top"><code class="computeroutput">&lt;imagedata&gt;</code></a>,
@@ -636,7 +636,7 @@
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="dbprimer-lists" id="dbprimer-lists"></a>Lists</h3></div></div></div><p>
-<a class="indexterm" name="idp140665822475824" id="idp140665822475824"></a> Here&#39;s how you make the DocBook
+<a class="indexterm" name="idp140697733926048" id="idp140697733926048"></a> Here&#39;s how you make the DocBook
 equivalent of the three usual HTML-lists:</p><div class="variablelist"><dl class="variablelist">
 <dt><span class="term"><span class="strong"><strong>1. How to make
 an &lt;ul&gt;</strong></span></span></dt><dd>
@@ -689,7 +689,7 @@
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="dbprimer-tables" id="dbprimer-tables"></a>Tables</h3></div></div></div><p>
-<a class="indexterm" name="idp140665822018848" id="idp140665822018848"></a> DocBook supports several types of tables,
+<a class="indexterm" name="idp140697734146544" id="idp140697734146544"></a> DocBook supports several types of tables,
 but in most cases, the <a class="ulink" href="http://docbook.org/tdg/en/html/informaltable.html" target="_top"><code class="computeroutput">&lt;informaltable&gt;</code></a> is enough:</p><pre class="programlisting">
 &lt;informaltable frame="all"&gt;
   &lt;tgroup cols="3"&gt;
@@ -735,7 +735,7 @@
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="dbprimer-emphasis" id="dbprimer-emphasis"></a>Emphasis</h3></div></div></div><p>
-<a class="indexterm" name="idp140665975427056" id="idp140665975427056"></a> Our documentation uses two flavors of
+<a class="indexterm" name="idp140697733277648" id="idp140697733277648"></a> Our documentation uses two flavors of
 emphasis - italics and bold type. DocBook uses one - <a class="ulink" href="http://docbook.org/tdg/en/html/emphasis.html" target="_top"><code class="computeroutput">&lt;emphasis&gt;</code></a>.</p><p>The <code class="computeroutput">&lt;emphasis&gt;</code> tag
 defaults to italics when parsed. If you&#39;re looking for
 emphasizing with bold type, use <code class="computeroutput">&lt;emphasis
Index: openacs-4/packages/acs-core-docs/www/docbook-primer.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/docbook-primer.html,v
diff -u -r1.56.2.5 -r1.56.2.6
--- openacs-4/packages/acs-core-docs/www/docbook-primer.html	3 Sep 2021 09:14:55 -0000	1.56.2.5
+++ openacs-4/packages/acs-core-docs/www/docbook-primer.html	7 Sep 2021 09:39:23 -0000	1.56.2.6
@@ -578,7 +578,7 @@
       DTD</a>. The remaining discussion is about publishing using
     Docbook.
 </p><p>
-<a class="indexterm" name="idp140665822014416"></a> 
+<a class="indexterm" name="idp140697733797888"></a> 
       is a publishing standard based on XML with
       similar goals to the OpenACS Documentation project.  Some specific reasons why we are using DocBook:
     </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>      
@@ -640,7 +640,7 @@
     list of elements</a> and use more exotic features in your
       documents. The list is made up of SGML-elements but basically
       the same elements are valid in the XML DTD <span class="strong"><strong>as long as you remember to</strong></span>:
-      <a class="indexterm" name="idp140665975637728"></a>
+      <a class="indexterm" name="idp140697734146944"></a>
     </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
       Always close your tags with corresponding end-tags and to
       <span class="strong"><strong>not use other tag minimization</strong></span>
@@ -689,7 +689,7 @@
       The documentation for each package will make up a little "book" that is structured like this 
       - examples are <span class="emphasis"><em>emphasized</em></span>:
 
-      <a class="indexterm" name="idp140665974966240"></a>
+      <a class="indexterm" name="idp140697733808672"></a>
 
     </p><pre class="programlisting">
     book                        : <span class="strong"><strong>Docs for one package</strong></span> - <span class="emphasis"><em>templating</em></span>
@@ -713,20 +713,20 @@
       <a class="ulink" href="https://github.com/openacs/openacs-core/tree/oacs-5-9/packages/acs-core-docs/www/xml/engineering-standards" target="_top">sources of these DocBook documents</a>
       to get an idea of how they are tied together.
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="dbprimer-sections"></a>Headlines, Sections</h3></div></div></div><p>
-      <a class="indexterm" name="idp140665823877280"></a>
+      <a class="indexterm" name="idp140697734129104"></a>
       Given that your job starts at the <code class="computeroutput">sect1</code>-level, all your documents should open with a
       <a class="ulink" href="http://docbook.org/tdg/en/html/sect1.html" target="_top"><code class="computeroutput">&lt;sect1&gt;</code></a>-tag and end 
       with the corresponding <code class="computeroutput">&lt;/sect1&gt;</code>.
     </p><p>
-      <a class="indexterm" name="idp140665823075360"></a>
+      <a class="indexterm" name="idp140697733816128"></a>
       You need to feed every <code class="computeroutput">&lt;sect1&gt;</code> two attributes. The first attribute,
       <code class="computeroutput">id</code>, is standard and can be used with all elements. It comes in  very 
       handy when interlinking between documents (more about this when talking about links in <a class="xref" href="docbook-primer.html#dbprimer-links" title="Links">the section called “Links”</a>). 
       The value of <code class="computeroutput">id</code> has to be unique 
       throughout the book you're making since the <code class="computeroutput">id</code>'s in your 
       <code class="computeroutput">sect1</code>'s will turn into filenames when the book is parsed into HTML.
     </p><p>
-      <a class="indexterm" name="idp140665822752272"></a>
+      <a class="indexterm" name="idp140697733366080"></a>
       The other attribute is <code class="computeroutput">xreflabel</code>. The value of this is the text that will appear
       as the link when referring to this <code class="computeroutput">sect1</code>.
     </p><p>
@@ -741,7 +741,7 @@
 
 &lt;/sect1&gt;
 </pre><p>
-      <a class="indexterm" name="idp140665974349840"></a>
+      <a class="indexterm" name="idp140697733370448"></a>
       Inside this container your document will be split up into 
       <a class="ulink" href="http://docbook.org/tdg/en/html/sect2.html" target="_top"><code class="computeroutput">&lt;sect2&gt;</code></a>'s,
       each with the same requirements - <code class="computeroutput">id</code> and <code class="computeroutput">xreflabel</code>
@@ -750,7 +750,7 @@
       When it comes to naming your
       <code class="computeroutput">sect2</code>'s and below, prefix them with some abbreviation of the <code class="computeroutput">id</code> in the <code class="computeroutput">sect1</code> such as <code class="computeroutput">requirements-overview</code>.
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="dbprimer-code"></a>Code</h3></div></div></div><p>
-      <a class="indexterm" name="idp140665973829792"></a>
+      <a class="indexterm" name="idp140697733314448"></a>
       For displaying a snippet of code, a filename or anything else you just want to appear as a part of
       a sentence, we use  
       <a class="ulink" href="http://docbook.org/tdg/en/html/computeroutput.html" target="_top"><code class="computeroutput">&lt;computeroutput&gt;</code></a>
@@ -768,12 +768,12 @@
       tag around text that has been wrapped by combinations of <a class="ulink" href="http://docbook.org/tdg/en/html/computeroutput.html" target="_top"><code class="computeroutput">&lt;computeroutput&gt;</code></a>
       and <a class="ulink" href="http://docbook.org/tdg/en/html/userinput.html" target="_top"><strong class="userinput"><code>&lt;userinput&gt;</code></strong></a>
 </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="dbprimer-links"></a>Links</h3></div></div></div><p>
-      <a class="indexterm" name="idp140665013477248"></a>
+      <a class="indexterm" name="idp140697733358768"></a>
       Linking falls into two different categories: inside the book you're making and outside:
     </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="strong"><strong>1. Inside linking, cross-referencing other parts of your book</strong></span></span></dt><dd><p>
         By having unique <code class="computeroutput">id</code>'s you can cross-reference any part of your book
         with a simple tag, regardless of where that part is.
-      </p><p><a class="indexterm" name="idp140665824170144"></a>Check out how I link to a subsection of the Developer's Guide:</p><p>Put this in your XML:</p><pre class="programlisting">
+      </p><p><a class="indexterm" name="idp140697733362368"></a>Check out how I link to a subsection of the Developer's Guide:</p><p>Put this in your XML:</p><pre class="programlisting">
 - Find information about creating a package in
 &lt;xref linkend="packages-making-a-package"&gt;&lt;/xref&gt;.
 </pre><p>And the output is:</p><pre class="programlisting">
@@ -797,7 +797,7 @@
         <code class="computeroutput">packages-looks</code>, the
         parser will try its best to explain where the link takes you.
       </p></dd><dt><span class="term"><span class="strong"><strong>2. Linking outside the documentation</strong></span></span></dt><dd><p>
-        <a class="indexterm" name="idp140665822702832"></a>
+        <a class="indexterm" name="idp140697733436384"></a>
         If you're hyper-linking out of the documentation, it works almost the same way as HTML - the tag is just
         a little different
 
@@ -818,7 +818,7 @@
     for you.
       </em></span>
     </p><p>
-      <a class="indexterm" name="idp140665013210416"></a>
+      <a class="indexterm" name="idp140697734233808"></a>
       To insert a graphic we use the elements 
       <a class="ulink" href="http://docbook.org/tdg/en/html/mediaobject.html" target="_top"><code class="computeroutput">&lt;mediaobject&gt;</code></a>,
       <a class="ulink" href="http://docbook.org/tdg/en/html/imageobject.html" target="_top"><code class="computeroutput">&lt;imageobject&gt;</code></a>,
@@ -844,7 +844,7 @@
       Put your graphics in a separate directory ("images") and link to them 
       only with relative paths.
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="dbprimer-lists"></a>Lists</h3></div></div></div><p>
-      <a class="indexterm" name="idp140665822475824"></a>
+      <a class="indexterm" name="idp140697733926048"></a>
       Here's how you make the DocBook equivalent of the three usual HTML-lists:
     </p><div class="variablelist"><dl class="variablelist"><dt><span class="term"><span class="strong"><strong>1. How to make an &lt;ul&gt;</strong></span></span></dt><dd><p>
         Making an unordered list is pretty much like doing the same thing in HTML - if you close your <code class="computeroutput">&lt;li&gt;</code>, that is. The only differences are that each list item has to be wrapped in something more, such as
@@ -889,7 +889,7 @@
 
 &lt;/variablelist&gt;
 </pre></dd></dl></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="dbprimer-tables"></a>Tables</h3></div></div></div><p>
-      <a class="indexterm" name="idp140665822018848"></a>
+      <a class="indexterm" name="idp140697734146544"></a>
       DocBook supports several types of tables, but in most cases, the
       <a class="ulink" href="http://docbook.org/tdg/en/html/informaltable.html" target="_top"><code class="computeroutput">&lt;informaltable&gt;</code></a>
       is enough:
@@ -926,7 +926,7 @@
       <a class="ulink" href="http://docbook.org/tdg/en/html/table.html" target="_top"><code class="computeroutput">&lt;table&gt;</code></a>
       for an example.
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="dbprimer-emphasis"></a>Emphasis</h3></div></div></div><p>
-      <a class="indexterm" name="idp140665975427056"></a>
+      <a class="indexterm" name="idp140697733277648"></a>
       Our documentation uses two flavors of emphasis - italics and bold type. DocBook uses one - 
       <a class="ulink" href="http://docbook.org/tdg/en/html/emphasis.html" target="_top"><code class="computeroutput">&lt;emphasis&gt;</code></a>.
     </p><p>
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 -r1.6.2.6 -r1.6.2.7
--- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp	3 Sep 2021 09:14:59 -0000	1.6.2.6
+++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.adp	7 Sep 2021 09:39:24 -0000	1.6.2.7
@@ -12,7 +12,7 @@
 <a name="ext-auth-requirements" id="ext-auth-requirements"></a>External
 Authentication Requirements</h2></div></div></div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665976249600" id="idp140665976249600"></a>Vision</h3></div></div></div><p>People have plenty of usernames and passwords already, we
+<a name="idp140696662465536" id="idp140696662465536"></a>Vision</h3></div></div></div><p>People have plenty of usernames and passwords already, we
 don&#39;t want them to have yet another. We want people to be able
 to log in to OpenACS with the same password they use to log in to
 any other system.</p><p>Besides, administrators have better things to do than create
@@ -74,7 +74,7 @@
 <div class="titlepage"><div><div><h3 class="title">
 <a name="Requirements" id="Requirements"></a>Requirements</h3></div></div></div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665823563712" id="idp140665823563712"></a>New API</h4></div></div></div><div class="segmentedlist"><table border="1" cellpadding="3" cellspacing="0" width="90%">
+<a name="idp140696662482880" id="idp140696662482880"></a>New API</h4></div></div></div><div class="segmentedlist"><table border="1" cellpadding="3" cellspacing="0" width="90%">
 <tr>
 <th width="15%">Feature</th><th width="8%">Status</th><th width="77%">Description</th>
 </tr><thead><tr><th>New API</th></tr></thead><tbody>
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 -r1.45.2.4 -r1.45.2.5
--- openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html	3 Sep 2021 09:14:59 -0000	1.45.2.4
+++ openacs-4/packages/acs-core-docs/www/ext-auth-requirements.html	7 Sep 2021 09:39:24 -0000	1.45.2.5
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>External Authentication Requirements</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="kernel-doc.html" title="Chapter 15. Kernel Documentation"><link rel="previous" href="bootstrap-acs.html" title="Bootstrapping OpenACS"><link rel="next" href="releasing-openacs.html" title="Chapter 16. Releasing OpenACS"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="bootstrap-acs.html">Prev</a> </td><th width="60%" align="center">Chapter 15. Kernel Documentation</th><td width="20%" align="right"> <a accesskey="n" href="releasing-openacs.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ext-auth-requirements"></a>External Authentication Requirements</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665976249600"></a>Vision</h3></div></div></div><p>People have plenty of usernames and passwords already, we
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>External Authentication Requirements</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="kernel-doc.html" title="Chapter 15. Kernel Documentation"><link rel="previous" href="bootstrap-acs.html" title="Bootstrapping OpenACS"><link rel="next" href="releasing-openacs.html" title="Chapter 16. Releasing OpenACS"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="bootstrap-acs.html">Prev</a> </td><th width="60%" align="center">Chapter 15. Kernel Documentation</th><td width="20%" align="right"> <a accesskey="n" href="releasing-openacs.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="ext-auth-requirements"></a>External Authentication Requirements</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140696662465536"></a>Vision</h3></div></div></div><p>People have plenty of usernames and passwords already, we
 don't want them to have yet another. We want people to be able to
 log in to OpenACS with the same password they use to log in to any
 other system.</p><p>Besides, administrators have better things to do than create
@@ -45,7 +45,7 @@
         only one implementation of the authentication API, namly the one
         included in OpenACS Core.</p></li><li class="listitem"><p>Authentication Driver API: The service contract which
         authentication drivers implement.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="Diagram"></a>Conceptual Pictures</h3></div></div></div><p>Authentication:</p><p><span class="inlinemediaobject"><img src="images/ext-auth.png"></span>
-</p><p>Account Management (NO PICTURE YET)</p><p>Batch Synchronization (NO PICTURE YET)</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="Requirements"></a>Requirements</h3></div></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665823563712"></a>New API</h4></div></div></div><div class="segmentedlist"><table border="1" cellpadding="3" cellspacing="0" width="90%"><tr><th width="15%">Feature</th><th width="8%">Status</th><th width="77%">Description</th></tr><thead><tr><th>New API</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">EXT-AUTH-01</td><td class="seg">A</td><td class="seg">Extend Authentication/Acct Status API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-03</td><td class="seg">A</td><td class="seg">Account Creation API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-05</td><td class="seg">A</td><td class="seg">Password Management API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-30</td><td class="seg">A</td><td class="seg">Authority Management API</td></tr></tbody></table></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="Login"></a>Login</h4></div></div></div><div class="segmentedlist"><table border="1" cellpadding="3" cellspacing="0" width="90%"><tr><th width="15%">Feature</th><th width="8%">Status</th><th width="77%">Description</th></tr><thead><tr><th>Login</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">EXT-AUTH-04</td><td class="seg">A</td><td class="seg">Rewrite login, register, and admin pages to use APIs</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-38</td><td class="seg">A</td><td class="seg">ad_form complain feature</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-19</td><td class="seg">A</td><td class="seg">Rewrite password recovery to use API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-21</td><td class="seg">A</td><td class="seg">Rewrite email verification with API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-28</td><td class="seg">A</td><td class="seg">Username is email switch</td></tr></tbody></table></div><p>Users will log in using a username, an authority, and a
+</p><p>Account Management (NO PICTURE YET)</p><p>Batch Synchronization (NO PICTURE YET)</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="Requirements"></a>Requirements</h3></div></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140696662482880"></a>New API</h4></div></div></div><div class="segmentedlist"><table border="1" cellpadding="3" cellspacing="0" width="90%"><tr><th width="15%">Feature</th><th width="8%">Status</th><th width="77%">Description</th></tr><thead><tr><th>New API</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">EXT-AUTH-01</td><td class="seg">A</td><td class="seg">Extend Authentication/Acct Status API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-03</td><td class="seg">A</td><td class="seg">Account Creation API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-05</td><td class="seg">A</td><td class="seg">Password Management API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-30</td><td class="seg">A</td><td class="seg">Authority Management API</td></tr></tbody></table></div></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="Login"></a>Login</h4></div></div></div><div class="segmentedlist"><table border="1" cellpadding="3" cellspacing="0" width="90%"><tr><th width="15%">Feature</th><th width="8%">Status</th><th width="77%">Description</th></tr><thead><tr><th>Login</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">EXT-AUTH-04</td><td class="seg">A</td><td class="seg">Rewrite login, register, and admin pages to use APIs</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-38</td><td class="seg">A</td><td class="seg">ad_form complain feature</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-19</td><td class="seg">A</td><td class="seg">Rewrite password recovery to use API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-21</td><td class="seg">A</td><td class="seg">Rewrite email verification with API</td></tr><tr class="seglistitem"><td class="seg">EXT-AUTH-28</td><td class="seg">A</td><td class="seg">Username is email switch</td></tr></tbody></table></div><p>Users will log in using a username, an authority, and a
       password.  The authority is the source for user/password
       verification.  OpenACS can be an authority itself. </p><p>Each user in OpenACS will belong to exactly one authority, which
 can either be the "local" OpenACS users table, in which case the
Index: openacs-4/packages/acs-core-docs/www/form-builder.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/form-builder.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/form-builder.adp	3 Sep 2021 09:15:00 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/form-builder.adp	7 Sep 2021 09:39:24 -0000	1.4.2.6
@@ -25,7 +25,7 @@
 <a name="multi-part-elements" id="multi-part-elements"></a>Multi-part Elements</h3></div></div></div><p>Some elements have more than one choice, or can submit more than
 one value.</p><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665975380304" id="idp140665975380304"></a>SELECT elements</h4></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
+<a name="idp140698005637072" id="idp140698005637072"></a>SELECT elements</h4></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem">
 <p>
 <strong>Creating the form element. </strong>Populate a list
 of lists with values for the option list.</p><pre class="programlisting">set foo_options [db_list_of_lists foo_option_list "
@@ -96,7 +96,7 @@
 Errors</h3></div></div></div><p>Here are some common errors and what to do when you encounter
 them:</p><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665025508960" id="idp140665025508960"></a>Error when selecting values</h4></div></div></div><p>This generally happens when there is an error in your query.</p>
+<a name="idp140698008600576" id="idp140698008600576"></a>Error when selecting values</h4></div></div></div><p>This generally happens when there is an error in your query.</p>
 </div>
 </div>
 </div>
Index: openacs-4/packages/acs-core-docs/www/form-builder.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/form-builder.html,v
diff -u -r1.33.2.4 -r1.33.2.5
--- openacs-4/packages/acs-core-docs/www/form-builder.html	3 Sep 2021 09:15:00 -0000	1.33.2.4
+++ openacs-4/packages/acs-core-docs/www/form-builder.html	7 Sep 2021 09:39:24 -0000	1.33.2.5
@@ -6,7 +6,7 @@
 adaptable UI. Error handling includes inline error reporting, and is customizable.
  However, ad_form can be tricky to use. In addition to this document,
  the ad_form <a class="ulink" href="http://openacs.org/api-doc/proc-view?proc=ad_form" target="_top">api
- documentation</a> is helpful.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="multi-part-elements"></a>Multi-part Elements</h3></div></div></div><p>Some elements have more than one choice, or can submit more than one value.</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665975380304"></a>SELECT elements</h4></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><b>Creating the form element. </b>Populate a list of lists with values for the option list.</p><pre class="programlisting">set foo_options [db_list_of_lists foo_option_list "
+ documentation</a> is helpful.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="multi-part-elements"></a>Multi-part Elements</h3></div></div></div><p>Some elements have more than one choice, or can submit more than one value.</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698005637072"></a>SELECT elements</h4></div></div></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><b>Creating the form element. </b>Populate a list of lists with values for the option list.</p><pre class="programlisting">set foo_options [db_list_of_lists foo_option_list "
     select foo,
            foo_id
       from foos
@@ -51,5 +51,5 @@
     ns_set print $mypage
 }
     </pre></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="form-widgets"></a>Tips for form widgets</h3></div></div></div><p>Here are some tips for dealing with some of the form widgets:</p><p><a class="ulink" href="http://openacs.org/forums/message-view?message_id=106331" target="_top">Current widget</a></p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="errors"></a>Common Errors</h3></div></div></div><p>Here are some common errors and what to do when you
-    encounter them:</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665025508960"></a>Error when selecting values</h4></div></div></div><p>This generally happens when there is an error in your
+    encounter them:</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698008600576"></a>Error when selecting values</h4></div></div></div><p>This generally happens when there is an error in your
           query.</p></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="programming-with-aolserver.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="eng-standards.html">Next</a></td></tr><tr><td width="40%" align="left">Programming with AOLserver </td><td width="20%" align="center"><a accesskey="u" href="dev-guide.html">Up</a></td><td width="40%" align="right"> Chapter 12. Engineering Standards</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/high-avail.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/high-avail.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/high-avail.adp	3 Sep 2021 09:15:01 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/high-avail.adp	7 Sep 2021 09:39:25 -0000	1.4.2.6
@@ -12,7 +12,7 @@
 <a name="high-avail" id="high-avail"></a>High Availability/High Performance
 Configurations</h2></div></div></div><p>See also <a class="xref" href="remote-postgres" title="Running a PostgreSQL database on another server">the section
 called “Running a PostgreSQL database on another server”</a>.</p><div class="figure">
-<a name="idp140665012739840" id="idp140665012739840"></a><p class="title"><strong>Figure 6.1. Multiple-server
+<a name="idp140698011712560" id="idp140698011712560"></a><p class="title"><strong>Figure 6.1. Multiple-server
 configuration</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/hpha.png" align="middle" alt="Multiple-server configuration"></div></div>
 </div><br class="figure-break">
 </div>
Index: openacs-4/packages/acs-core-docs/www/high-avail.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/high-avail.html,v
diff -u -r1.27.2.4 -r1.27.2.5
--- openacs-4/packages/acs-core-docs/www/high-avail.html	3 Sep 2021 09:15:01 -0000	1.27.2.4
+++ openacs-4/packages/acs-core-docs/www/high-avail.html	7 Sep 2021 09:39:25 -0000	1.27.2.5
@@ -1,2 +1,2 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>High Availability/High Performance Configurations</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="maintenance-web.html" title="Chapter 6. Production Environments"><link rel="previous" href="install-next-add-server.html" title="Running multiple services on one machine"><link rel="next" href="maintenance-deploy.html" title="Staged Deployment for Production Networks"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="install-next-add-server.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Production Environments</th><td width="20%" align="right"> <a accesskey="n" href="maintenance-deploy.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="high-avail"></a>High Availability/High Performance Configurations</h2></div></div></div><p>See also <a class="xref" href="remote-postgres.html" title="Running a PostgreSQL database on another server">the section called “Running a PostgreSQL database on another server”</a>.</p><div class="figure"><a name="idp140665012739840"></a><p class="title"><b>Figure 6.1. Multiple-server configuration</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/hpha.png" align="middle" alt="Multiple-server configuration"></div></div></div><br class="figure-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install-next-add-server.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="maintenance-deploy.html">Next</a></td></tr><tr><td width="40%" align="left">Running multiple services on one machine </td><td width="20%" align="center"><a accesskey="u" href="maintenance-web.html">Up</a></td><td width="40%" align="right"> Staged Deployment for Production Networks</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>High Availability/High Performance Configurations</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="maintenance-web.html" title="Chapter 6. Production Environments"><link rel="previous" href="install-next-add-server.html" title="Running multiple services on one machine"><link rel="next" href="maintenance-deploy.html" title="Staged Deployment for Production Networks"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="install-next-add-server.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Production Environments</th><td width="20%" align="right"> <a accesskey="n" href="maintenance-deploy.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="high-avail"></a>High Availability/High Performance Configurations</h2></div></div></div><p>See also <a class="xref" href="remote-postgres.html" title="Running a PostgreSQL database on another server">the section called “Running a PostgreSQL database on another server”</a>.</p><div class="figure"><a name="idp140698011712560"></a><p class="title"><b>Figure 6.1. Multiple-server configuration</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/hpha.png" align="middle" alt="Multiple-server configuration"></div></div></div><br class="figure-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="install-next-add-server.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="maintenance-deploy.html">Next</a></td></tr><tr><td width="40%" align="left">Running multiple services on one machine </td><td width="20%" align="center"><a accesskey="u" href="maintenance-web.html">Up</a></td><td width="40%" align="right"> Staged Deployment for Production Networks</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
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 -r1.5.2.5 -r1.5.2.6
--- openacs-4/packages/acs-core-docs/www/how-do-I.adp	3 Sep 2021 09:15:01 -0000	1.5.2.5
+++ openacs-4/packages/acs-core-docs/www/how-do-I.adp	7 Sep 2021 09:39:25 -0000	1.5.2.6
@@ -11,20 +11,20 @@
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="how-do-I" id="how-do-I"></a>How Do I?</h2></div></div></div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823454368" id="idp140665823454368"></a>How do I edit the front page of a new site
+<a name="idp140697734042272" id="idp140697734042272"></a>How do I edit the front page of a new site
 through a web interface?</h3></div></div></div><p>The easiest way is to install the Edit-This-Page package.</p><div class="orderedlist"><ol class="orderedlist" type="1">
 <li class="listitem"><p>Log in to the web site as an administrator.</p></li><li class="listitem"><p>Click on Admin &gt; Install Software &gt; Install from OpenACS
 Repository / Install new application</p></li><li class="listitem"><p>Choose Edit This Page and install</p></li><li class="listitem"><p>Follow the instructions within <a class="ulink" href="/doc/edit-this-page/install" target="_top">Edit This Page</a> (the
 link will only work after Edit This Page is installed).</p></li>
 </ol></div>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823305728" id="idp140665823305728"></a>How do I let anybody who registers post to
+<a name="idp140697734047648" id="idp140697734047648"></a>How do I let anybody who registers post to
 a weblog?</h3></div></div></div><p>Go to <code class="computeroutput"><a class="ulink" href="/admin/permissions" target="_top">/admin/permissions</a></code>
 and grant Create to Registered Users</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665822197072" id="idp140665822197072"></a>How do I replace the front page of a new
+<a name="idp140697734049568" id="idp140697734049568"></a>How do I replace the front page of a new
 site with the front page of an application on that site</h3></div></div></div><p>Suppose you install a new site and install Weblogger, and you
 want all visitors to see weblogger automatically.</p><div class="orderedlist"><ol class="orderedlist" type="1">
 <li class="listitem"><p>On the front page, click the <code class="computeroutput"><a class="ulink" href="/admin" target="_top">Admin</a></code> button.</p></li><li class="listitem"><p>On the administration page, click <code class="computeroutput">Parameters</code> link.</p></li><li class="listitem"><p>Change the parameter <code class="computeroutput">IndexRedirectUrl</code> to be the URI of the
@@ -34,7 +34,7 @@
 </ol></div>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823327088" id="idp140665823327088"></a>How do I put custom functionality on front
+<a name="idp140697734056224" id="idp140697734056224"></a>How do I put custom functionality on front
 page of a new site?</h3></div></div></div><p>Every page within an OpenACS site is part of a <span class="strong"><strong>subsite</strong></span><a class="ulink" href="/doc/acs-subsite" target="_top">More information)</a>. The home
 page of the entire site is the front page is a special, default
 instance of a subsite, served from <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www</code>. If an
@@ -49,7 +49,7 @@
 </ol></div>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823428608" id="idp140665823428608"></a>How do I change the site-wide style?</h3></div></div></div><p>Almost all pages on an OpenACS site use <a class="ulink" href="/doc/acs-templating" target="_top">ACS Templating</a>, and so
+<a name="idp140697734064768" id="idp140697734064768"></a>How do I change the site-wide style?</h3></div></div></div><p>Almost all pages on an OpenACS site use <a class="ulink" href="/doc/acs-templating" target="_top">ACS Templating</a>, and so
 their appearance is driven by a layer of different files. Let&#39;s
 examine how this works:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem">
@@ -71,12 +71,12 @@
 navigation "meta" elements such as Translator widgets and
 Admin widgets.</p></li>
 </ul></div><div class="figure">
-<a name="idp140665823450560" id="idp140665823450560"></a><p class="title"><strong>Figure 4.1. Site
+<a name="idp140697734077328" id="idp140697734077328"></a><p class="title"><strong>Figure 4.1. Site
 Templates</strong></p><div class="figure-contents"><div class="mediaobject"><img src="images/site-templates.png" alt="Site Templates"></div></div>
 </div><br class="figure-break">
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823460464" id="idp140665823460464"></a>How do I diagnose a permissions
+<a name="idp140697734079632" id="idp140697734079632"></a>How do I diagnose a permissions
 problem?</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem">
 <p>
@@ -117,12 +117,12 @@
 <li class="listitem"><p>To grant permissions on a package, start at the <a class="ulink" href="/admin/site-map" target="_top">site map</a>. Find the event
 package and click "Set permissions".</p></li><li class="listitem"><p>Click "Grant Permission"</p></li><li class="listitem">
 <p>Grant the write permission to Registered Users.</p><div class="figure">
-<a name="idp140665823430176" id="idp140665823430176"></a><p class="title"><strong>Figure 4.2. Granting
+<a name="idp140697734097808" id="idp140697734097808"></a><p class="title"><strong>Figure 4.2. Granting
 Permissions</strong></p><div class="figure-contents"><div class="mediaobject"><img src="images/grant-perm-463.png" alt="Granting Permissions"></div></div>
 </div><br class="figure-break">
 </li>
 </ol></div><p>OpenACS 5.0 offers a prettier version at <a class="ulink" href="/admin/applications" target="_top">/admin/applications</a>.</p><div class="figure">
-<a name="idp140665823011856" id="idp140665823011856"></a><p class="title"><strong>Figure 4.3. Granting Permissions
+<a name="idp140697734101136" id="idp140697734101136"></a><p class="title"><strong>Figure 4.3. Granting Permissions
 in 5.0</strong></p><div class="figure-contents"><div class="mediaobject"><img src="images/grant-perm-50.png" alt="Granting Permissions in 5.0"></div></div>
 </div><br class="figure-break">
 </li>
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 -r1.31.2.4 -r1.31.2.5
--- openacs-4/packages/acs-core-docs/www/how-do-I.html	3 Sep 2021 09:15:01 -0000	1.31.2.4
+++ openacs-4/packages/acs-core-docs/www/how-do-I.html	7 Sep 2021 09:39:25 -0000	1.31.2.5
@@ -1,7 +1,7 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>How Do I?</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="configuring-new-site.html" title="Chapter 4. Configuring a new OpenACS Site"><link rel="previous" href="configuring-configuring-permissions.html" title="Setting Permissions on an OpenACS package"><link rel="next" href="upgrade.html" title="Chapter 5. Upgrading"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="configuring-configuring-permissions.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Configuring a new OpenACS Site</th><td width="20%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="how-do-I"></a>How Do I?</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823454368"></a>How do I edit the front page of a new site through a web interface?</h3></div></div></div><p>The easiest way is to install the Edit-This-Page package.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Log in to the web site as an administrator.</p></li><li class="listitem"><p>Click on Admin &gt; Install Software &gt; Install from OpenACS Repository / Install new application</p></li><li class="listitem"><p>Choose Edit This Page and install</p></li><li class="listitem"><p>Follow the instructions within <a class="ulink" href="/doc/edit-this-page/install" target="_top">Edit This Page</a> (the link will only work after Edit This Page is installed).</p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823305728"></a>How do I let anybody who registers post to a weblog?</h3></div></div></div><p>Go to <code class="computeroutput"><a class="ulink" href="/admin/permissions" target="_top">/admin/permissions</a></code> and grant Create to Registered Users</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665822197072"></a>How do I replace the front page of a new site with the front page of an application on that site</h3></div></div></div><p>Suppose you install a new site and install Weblogger, and you want all visitors to see weblogger automatically.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>On the front page, click the <code class="computeroutput"><a class="ulink" href="/admin" target="_top">Admin</a></code> button.</p></li><li class="listitem"><p>On the administration page, click <code class="computeroutput">Parameters</code> link.</p></li><li class="listitem"><p>Change the parameter <code class="computeroutput">IndexRedirectUrl</code> to be the URI of the desired application.  For a default weblogger installation, this would be <code class="computeroutput"><strong class="userinput"><code>weblogger/</code></strong></code>.  Note the trailing slash.</p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823327088"></a>How do I put custom functionality on front page of a new site?</h3></div></div></div><p>Every page within an OpenACS site is part of a <span class="strong"><strong>subsite</strong></span> <a class="ulink" href="/doc/acs-subsite" target="_top">More information)</a>.  The home page of the entire site is the front page is a special, default instance of a subsite, served from <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www</code>.  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:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><pre class="screen"><strong class="userinput"><code>cp <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/acs-subsite/www/index*</code> <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www</code></code></strong></pre></li><li class="listitem"><p>Edit the new <code class="computeroutput">index.adp</code> to change the text; you shouldn't need to edit <code class="computeroutput">index.tcl</code> unless you are adding new functionality.</p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823428608"></a>How do I change the site-wide style?</h3></div></div></div><p>Almost all pages on an OpenACS site use <a class="ulink" href="/doc/acs-templating" target="_top">ACS Templating</a>, and so their appearance is driven by a layer of different files.  Let's examine how this works:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>How Do I?</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="configuring-new-site.html" title="Chapter 4. Configuring a new OpenACS Site"><link rel="previous" href="configuring-configuring-permissions.html" title="Setting Permissions on an OpenACS package"><link rel="next" href="upgrade.html" title="Chapter 5. Upgrading"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="configuring-configuring-permissions.html">Prev</a> </td><th width="60%" align="center">Chapter 4. Configuring a new OpenACS Site</th><td width="20%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="how-do-I"></a>How Do I?</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697734042272"></a>How do I edit the front page of a new site through a web interface?</h3></div></div></div><p>The easiest way is to install the Edit-This-Page package.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Log in to the web site as an administrator.</p></li><li class="listitem"><p>Click on Admin &gt; Install Software &gt; Install from OpenACS Repository / Install new application</p></li><li class="listitem"><p>Choose Edit This Page and install</p></li><li class="listitem"><p>Follow the instructions within <a class="ulink" href="/doc/edit-this-page/install" target="_top">Edit This Page</a> (the link will only work after Edit This Page is installed).</p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697734047648"></a>How do I let anybody who registers post to a weblog?</h3></div></div></div><p>Go to <code class="computeroutput"><a class="ulink" href="/admin/permissions" target="_top">/admin/permissions</a></code> and grant Create to Registered Users</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697734049568"></a>How do I replace the front page of a new site with the front page of an application on that site</h3></div></div></div><p>Suppose you install a new site and install Weblogger, and you want all visitors to see weblogger automatically.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>On the front page, click the <code class="computeroutput"><a class="ulink" href="/admin" target="_top">Admin</a></code> button.</p></li><li class="listitem"><p>On the administration page, click <code class="computeroutput">Parameters</code> link.</p></li><li class="listitem"><p>Change the parameter <code class="computeroutput">IndexRedirectUrl</code> to be the URI of the desired application.  For a default weblogger installation, this would be <code class="computeroutput"><strong class="userinput"><code>weblogger/</code></strong></code>.  Note the trailing slash.</p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697734056224"></a>How do I put custom functionality on front page of a new site?</h3></div></div></div><p>Every page within an OpenACS site is part of a <span class="strong"><strong>subsite</strong></span> <a class="ulink" href="/doc/acs-subsite" target="_top">More information)</a>.  The home page of the entire site is the front page is a special, default instance of a subsite, served from <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www</code>.  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:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><pre class="screen"><strong class="userinput"><code>cp <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/acs-subsite/www/index*</code> <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www</code></code></strong></pre></li><li class="listitem"><p>Edit the new <code class="computeroutput">index.adp</code> to change the text; you shouldn't need to edit <code class="computeroutput">index.tcl</code> unless you are adding new functionality.</p></li></ol></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697734064768"></a>How do I change the site-wide style?</h3></div></div></div><p>Almost all pages on an OpenACS site use <a class="ulink" href="/doc/acs-templating" target="_top">ACS Templating</a>, and so their appearance is driven by a layer of different files.  Let's examine how this works:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
           A templated page uses an ADP/Tcl pair.  The first line in the ADP file is usually:
           </p><pre class="programlisting">&lt;master&gt;</pre><p>If it appears exactly like this, without any arguments, the template processor uses <code class="computeroutput">default-master</code> for that subsite.  For pages in <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www</code>, this is <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www/default-master.adp</code> and the associated .tcl file.
-          </p></li><li class="listitem"><p>The <code class="computeroutput">default-master</code> is itself a normal ADP page.  It draws the subsite navigation elements and invokes <code class="computeroutput">site-master</code> (<code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www/site-master.adp</code> and .tcl)</p></li><li class="listitem"><p>The <code class="computeroutput">site-master</code> draws site-wide navigation elements and invokes <code class="computeroutput">blank-master</code> (<code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www/blank-master.adp</code> and .tcl).  </p></li><li class="listitem"><p><code class="computeroutput">Blank-master</code> does HTML housekeeping and provides a framework for special sitewide navigation "meta" elements such as Translator widgets and Admin widgets.</p></li></ul></div><div class="figure"><a name="idp140665823450560"></a><p class="title"><b>Figure 4.1. Site Templates</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/site-templates.png" alt="Site Templates"></div></div></div><br class="figure-break"></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823460464"></a>How do I diagnose a permissions problem?</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><b>Steps to Reproduce. </b>The events package does not allow users to register for new events.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>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.</p></li><li class="listitem"><p>Select an available event</p></li><li class="listitem"><p>A link such as <code class="computeroutput">Registration: Deadline is 03/15/2004 10:00am. 
+          </p></li><li class="listitem"><p>The <code class="computeroutput">default-master</code> is itself a normal ADP page.  It draws the subsite navigation elements and invokes <code class="computeroutput">site-master</code> (<code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www/site-master.adp</code> and .tcl)</p></li><li class="listitem"><p>The <code class="computeroutput">site-master</code> draws site-wide navigation elements and invokes <code class="computeroutput">blank-master</code> (<code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/www/blank-master.adp</code> and .tcl).  </p></li><li class="listitem"><p><code class="computeroutput">Blank-master</code> does HTML housekeeping and provides a framework for special sitewide navigation "meta" elements such as Translator widgets and Admin widgets.</p></li></ul></div><div class="figure"><a name="idp140697734077328"></a><p class="title"><b>Figure 4.1. Site Templates</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/site-templates.png" alt="Site Templates"></div></div></div><br class="figure-break"></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697734079632"></a>How do I diagnose a permissions problem?</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><b>Steps to Reproduce. </b>The events package does not allow users to register for new events.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>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.</p></li><li class="listitem"><p>Select an available event</p></li><li class="listitem"><p>A link such as <code class="computeroutput">Registration: Deadline is 03/15/2004 10:00am. 
 » Login or sign up to register for this event.</code> is visible.  Click on "Login or sign up"
-          </p></li><li class="listitem"><p>Complete a new registration.  Afterwards, you should be redirected back to the same page.</p></li></ol></div><p>Actual Results: The page says <code class="computeroutput">"You do not have permission to register for this event."</code></p><p>Expected results: A link or form to sign up for the event is shown.</p></li><li class="listitem"><p><b>Finding the problem. </b>We start with the page that has the error.  In the URL it's <code class="computeroutput">http://myserver.net/events/event-info.tcl</code>, so open the file <code class="computeroutput">/var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/events/www/event-info.tcl</code>.  It contains this line:</p><pre class="programlisting">set can_register_p [events::security::can_register_for_event_p -event_id $event_id]</pre><p>We need to know what that procedure does, so go to <a class="ulink" href="/api-doc" target="_top">/api-doc</a>, 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</p><pre class="programlisting">return [permission::permission_p -party_id $user_id -object_id $event_id -privilege write]</pre><p>This means that a given user must have the write privilege on the event in order to register.  Let's assume that the privileges inherit, so that if a user has the write privilege on the whole package, they will have the write privilege on the event.</p></li><li class="listitem"><p><b>Setting Permissions. </b>A permission has three parts: the privilege, the object of the privilege, and the subject being granted the privilege.  In this case the privilege is "write," the object is the Events package, and the subject is all Registered Users.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>To grant permissions on a package, start at the <a class="ulink" href="/admin/site-map" target="_top">site map</a>.  Find the event package and click "Set permissions".  </p></li><li class="listitem"><p>Click "Grant Permission"</p></li><li class="listitem"><p>Grant the write permission to Registered Users.</p><div class="figure"><a name="idp140665823430176"></a><p class="title"><b>Figure 4.2. Granting Permissions</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/grant-perm-463.png" alt="Granting Permissions"></div></div></div><br class="figure-break"></li></ol></div><p>OpenACS 5.0 offers a prettier version at <a class="ulink" href="/admin/applications" target="_top">/admin/applications</a>.</p><div class="figure"><a name="idp140665823011856"></a><p class="title"><b>Figure 4.3. Granting Permissions in 5.0</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/grant-perm-50.png" alt="Granting Permissions in 5.0"></div></div></div><br class="figure-break"></li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="configuring-configuring-permissions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr><tr><td width="40%" align="left">Setting Permissions on an OpenACS package </td><td width="20%" align="center"><a accesskey="u" href="configuring-new-site.html">Up</a></td><td width="40%" align="right"> Chapter 5. Upgrading</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
+          </p></li><li class="listitem"><p>Complete a new registration.  Afterwards, you should be redirected back to the same page.</p></li></ol></div><p>Actual Results: The page says <code class="computeroutput">"You do not have permission to register for this event."</code></p><p>Expected results: A link or form to sign up for the event is shown.</p></li><li class="listitem"><p><b>Finding the problem. </b>We start with the page that has the error.  In the URL it's <code class="computeroutput">http://myserver.net/events/event-info.tcl</code>, so open the file <code class="computeroutput">/var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/events/www/event-info.tcl</code>.  It contains this line:</p><pre class="programlisting">set can_register_p [events::security::can_register_for_event_p -event_id $event_id]</pre><p>We need to know what that procedure does, so go to <a class="ulink" href="/api-doc" target="_top">/api-doc</a>, 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</p><pre class="programlisting">return [permission::permission_p -party_id $user_id -object_id $event_id -privilege write]</pre><p>This means that a given user must have the write privilege on the event in order to register.  Let's assume that the privileges inherit, so that if a user has the write privilege on the whole package, they will have the write privilege on the event.</p></li><li class="listitem"><p><b>Setting Permissions. </b>A permission has three parts: the privilege, the object of the privilege, and the subject being granted the privilege.  In this case the privilege is "write," the object is the Events package, and the subject is all Registered Users.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>To grant permissions on a package, start at the <a class="ulink" href="/admin/site-map" target="_top">site map</a>.  Find the event package and click "Set permissions".  </p></li><li class="listitem"><p>Click "Grant Permission"</p></li><li class="listitem"><p>Grant the write permission to Registered Users.</p><div class="figure"><a name="idp140697734097808"></a><p class="title"><b>Figure 4.2. Granting Permissions</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/grant-perm-463.png" alt="Granting Permissions"></div></div></div><br class="figure-break"></li></ol></div><p>OpenACS 5.0 offers a prettier version at <a class="ulink" href="/admin/applications" target="_top">/admin/applications</a>.</p><div class="figure"><a name="idp140697734101136"></a><p class="title"><b>Figure 4.3. Granting Permissions in 5.0</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/grant-perm-50.png" alt="Granting Permissions in 5.0"></div></div></div><br class="figure-break"></li></ul></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="configuring-configuring-permissions.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrade.html">Next</a></td></tr><tr><td width="40%" align="left">Setting Permissions on an OpenACS package </td><td width="20%" align="center"><a accesskey="u" href="configuring-new-site.html">Up</a></td><td width="40%" align="right"> Chapter 5. Upgrading</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/i18n-convert.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/i18n-convert.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/i18n-convert.adp	3 Sep 2021 09:15:02 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/i18n-convert.adp	7 Sep 2021 09:39:25 -0000	1.4.2.6
@@ -144,7 +144,7 @@
 </li>
 </ol></div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140664745045712" id="idp140664745045712"></a>Avoiding common i18n mistakes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<a name="idp140696925923856" id="idp140696925923856"></a>Avoiding common i18n mistakes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem">
 <p>
 <strong>Replace complicated keys with longer, simpler
Index: openacs-4/packages/acs-core-docs/www/i18n-convert.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/i18n-convert.html,v
diff -u -r1.29.2.4 -r1.29.2.5
--- openacs-4/packages/acs-core-docs/www/i18n-convert.html	3 Sep 2021 09:15:02 -0000	1.29.2.4
+++ openacs-4/packages/acs-core-docs/www/i18n-convert.html	7 Sep 2021 09:39:25 -0000	1.29.2.5
@@ -72,7 +72,7 @@
         test. If you don't provide the package_key argument then all
         packages with catalog files will be checked. 
         The script will run its checks primarily on en_US XML catalog files.
-      </p></li></ol></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140664745045712"></a>Avoiding common i18n mistakes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><b>Replace complicated keys with longer, simpler keys. </b>When writing in one language, it is possible to create clever code to make correct text.  In English, for example, you can put an <code class="computeroutput">if</code> command at the end of a word which adds "s" if a count is anything but 1.  This pluralizes nouns correctly based on the data.  However, it is confusing to read and, when internationalized, may result in message keys that are both confusing and impossible to set correctly in some languages.  While internationalizing, watch out that the automate converter does not create such keys.  Also, refactor compound text as you encounter it.</p><p>The automated system can easily get confused by tags within message texts, so that it tries to create two or three message keys for one long string with a tag in the middle.  In these cases, uncheck those keys during the conversion and then edit the files directly.  For example, this code:</p><pre class="programlisting">  &lt;p class="form-help-text"&gt;&lt;b&gt;Invitations&lt;/b&gt; are sent,
+      </p></li></ol></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140696925923856"></a>Avoiding common i18n mistakes</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><b>Replace complicated keys with longer, simpler keys. </b>When writing in one language, it is possible to create clever code to make correct text.  In English, for example, you can put an <code class="computeroutput">if</code> command at the end of a word which adds "s" if a count is anything but 1.  This pluralizes nouns correctly based on the data.  However, it is confusing to read and, when internationalized, may result in message keys that are both confusing and impossible to set correctly in some languages.  While internationalizing, watch out that the automate converter does not create such keys.  Also, refactor compound text as you encounter it.</p><p>The automated system can easily get confused by tags within message texts, so that it tries to create two or three message keys for one long string with a tag in the middle.  In these cases, uncheck those keys during the conversion and then edit the files directly.  For example, this code:</p><pre class="programlisting">  &lt;p class="form-help-text"&gt;&lt;b&gt;Invitations&lt;/b&gt; are sent,
           when this wizard is completed and casting begins.&lt;/p&gt;</pre><p>has a bold tag which confuses the converter into thinking there are two message keys for the text beginning "Invitations ..." where there should be one:</p><div class="mediaobject" align="center"><img src="images/i18n-3.png" align="middle"></div><p>Instead, we cancel those keys, edit the file manually, and put in a single temporary message tag:</p><pre class="programlisting">  &lt;p class="form-help-text"&gt; &lt;#Invitations_are_sent &lt;b&gt;Invitations&lt;/b&gt; are sent, 
 when this wizard is completed and casting begins.#&gt;
   &lt;/p&gt;</pre><p>Complex if statements may produce convoluted message keys that are very hard to localize.  Rewrite these if statements.  For example:</p><pre class="programlisting">Select which case &lt;if @simulation.casting_type@ eq "open"&gt;and
Index: openacs-4/packages/acs-core-docs/www/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/index.adp,v
diff -u -r1.29.2.5 -r1.29.2.6
--- openacs-4/packages/acs-core-docs/www/index.adp	3 Sep 2021 09:15:03 -0000	1.29.2.5
+++ openacs-4/packages/acs-core-docs/www/index.adp	7 Sep 2021 09:39:25 -0000	1.29.2.6
@@ -9,7 +9,7 @@
 		    <div class="book">
 <div class="titlepage">
 <div><div><h1 class="title">
-<a name="idp140665820845792" id="idp140665820845792"></a>OpenACS Core Documentation</h1></div></div><hr>
+<a name="idp140698004070832" id="idp140698004070832"></a>OpenACS Core Documentation</h1></div></div><hr>
 </div><div class="toc">
 <p><strong>Table of Contents</strong></p><dl class="toc">
 <dt><span class="part"><a href="for-everyone">I. OpenACS For
Index: openacs-4/packages/acs-core-docs/www/index.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/index.html,v
diff -u -r1.56.2.4 -r1.56.2.5
--- openacs-4/packages/acs-core-docs/www/index.html	3 Sep 2021 09:15:03 -0000	1.56.2.4
+++ openacs-4/packages/acs-core-docs/www/index.html	7 Sep 2021 09:39:26 -0000	1.56.2.5
@@ -1,4 +1,4 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>OpenACS Core Documentation</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="next" href="for-everyone.html" title="Part I. OpenACS For Everyone"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"> </td><th width="60%" align="center"></th><td width="20%" align="right"> <a accesskey="n" href="for-everyone.html">Next</a></td></tr></table><hr></div><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idp140665820845792"></a>OpenACS Core Documentation</h1></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="part"><a href="for-everyone.html">I. OpenACS For Everyone</a></span></dt><dd><dl><dt><span class="chapter"><a href="general-documents.html">1. High level information: What is OpenACS?</a></span></dt><dd><dl><dt><span class="sect1"><a href="openacs-overview.html">Overview</a></span></dt><dt><span class="sect1"><a href="release-notes.html">OpenACS Release Notes</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="acs-admin.html">II. Administrator's Guide</a></span></dt><dd><dl><dt><span class="chapter"><a href="install-overview.html">2. Installation Overview</a></span></dt><dd><dl><dt><span class="sect1"><a href="install-steps.html">Basic Steps</a></span></dt><dt><span class="sect1"><a href="individual-programs.html">Prerequisite Software</a></span></dt></dl></dd><dt><span class="chapter"><a href="complete-install.html">3. Complete Installation</a></span></dt><dd><dl><dt><span class="sect1"><a href="unix-installation.html">Install a Unix-like system and supporting software</a></span></dt><dt><span class="sect1"><a href="oracle.html">Install Oracle 8.1.7</a></span></dt><dt><span class="sect1"><a href="postgres.html">Install PostgreSQL</a></span></dt><dt><span class="sect1"><a href="aolserver4.html">Install AOLserver 4</a></span></dt><dt><span class="sect1"><a href="openacs.html">Install OpenACS 5.9.0</a></span></dt><dt><span class="sect1"><a href="win2k-installation.html">OpenACS Installation Guide for Windows</a></span></dt><dt><span class="sect1"><a href="mac-installation.html">OpenACS Installation Guide for macOS</a></span></dt></dl></dd><dt><span class="chapter"><a href="configuring-new-site.html">4. Configuring a new OpenACS Site</a></span></dt><dd><dl><dt><span class="sect1"><a href="configuring-install-packages.html">Installing OpenACS packages</a></span></dt><dt><span class="sect1"><a href="configuring-mounting-packages.html">Mounting OpenACS packages</a></span></dt><dt><span class="sect1"><a href="configuring-configuring-packages.html">Configuring an OpenACS package</a></span></dt><dt><span class="sect1"><a href="configuring-configuring-permissions.html">Setting Permissions on an OpenACS package</a></span></dt><dt><span class="sect1"><a href="how-do-I.html">How Do I?</a></span></dt></dl></dd><dt><span class="chapter"><a href="upgrade.html">5. Upgrading</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrade-overview.html">Overview</a></span></dt><dt><span class="sect1"><a href="upgrade-4.5-to-4.6.html">Upgrading 4.5 or higher to 4.6.3</a></span></dt><dt><span class="sect1"><a href="upgrade-4.6.3-to-5.html">Upgrading OpenACS 4.6.3 to 5.0</a></span></dt><dt><span class="sect1"><a href="upgrade-5-0-dot.html">Upgrading an OpenACS 5.0.0 or greater installation</a></span></dt><dt><span class="sect1"><a href="upgrade-openacs-files.html">Upgrading the OpenACS files</a></span></dt><dt><span class="sect1"><a href="upgrade-supporting.html">Upgrading Platform components</a></span></dt></dl></dd><dt><span class="chapter"><a href="maintenance-web.html">6. Production Environments</a></span></dt><dd><dl><dt><span class="sect1"><a href="install-openacs-keepalive.html">Starting and Stopping an OpenACS instance.</a></span></dt><dt><span class="sect1"><a href="install-openacs-inittab.html">AOLserver keepalive with inittab</a></span></dt><dt><span class="sect1"><a href="install-next-add-server.html">Running multiple services on one machine</a></span></dt><dt><span class="sect1"><a href="high-avail.html">High Availability/High Performance Configurations</a></span></dt><dt><span class="sect1"><a href="maintenance-deploy.html">Staged Deployment for Production Networks</a></span></dt><dt><span class="sect1"><a href="install-ssl.html">Installing SSL Support for an OpenACS service</a></span></dt><dt><span class="sect1"><a href="analog-setup.html">Set up Log Analysis Reports</a></span></dt><dt><span class="sect1"><a href="uptime.html">External uptime validation</a></span></dt><dt><span class="sect1"><a href="maint-performance.html">Diagnosing Performance Problems</a></span></dt></dl></dd><dt><span class="chapter"><a href="database-management.html">7. Database Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="remote-postgres.html">Running a PostgreSQL database on another server</a></span></dt><dt><span class="sect1"><a href="install-openacs-delete-tablespace.html">Deleting a tablespace</a></span></dt><dt><span class="sect1"><a href="install-next-nightly-vacuum.html">Vacuum Postgres nightly</a></span></dt></dl></dd><dt><span class="chapter"><a href="backup-recovery.html">8. Backup and Recovery</a></span></dt><dd><dl><dt><span class="sect1"><a href="install-next-backups.html">Backup Strategy</a></span></dt><dt><span class="sect1"><a href="snapshot-backup.html">Manual backup and recovery</a></span></dt><dt><span class="sect1"><a href="automated-backup.html">Automated Backup</a></span></dt><dt><span class="sect1"><a href="backups-with-cvs.html">Using CVS for backup-recovery</a></span></dt></dl></dd><dt><span class="appendix"><a href="install-redhat.html">A. Install Red Hat 8/9</a></span></dt><dt><span class="appendix"><a href="install-more-software.html">B. Install additional supporting software</a></span></dt><dd><dl><dt><span class="sect1"><a href="openacs-unpack.html">Unpack the OpenACS tarball</a></span></dt><dt><span class="sect1"><a href="install-cvs.html">Initialize CVS (OPTIONAL)</a></span></dt><dt><span class="sect1"><a href="psgml-for-emacs.html">Add PSGML commands to emacs init file (OPTIONAL)</a></span></dt><dt><span class="sect1"><a href="install-daemontools.html">Install Daemontools (OPTIONAL)</a></span></dt><dt><span class="sect1"><a href="install-qmail.html">Install qmail (OPTIONAL)</a></span></dt><dt><span class="sect1"><a href="analog-install.html">Install Analog web file analyzer</a></span></dt><dt><span class="sect1"><a href="install-nspam.html">Install nspam</a></span></dt><dt><span class="sect1"><a href="install-full-text-search-tsearch2.html">Install Full Text Search using Tsearch2</a></span></dt><dt><span class="sect1"><a href="install-nsopenssl.html">Install nsopenssl</a></span></dt><dt><span class="sect1"><a href="install-tclwebtest.html">Install tclwebtest.</a></span></dt><dt><span class="sect1"><a href="install-php.html">Install PHP for use in AOLserver</a></span></dt><dt><span class="sect1"><a href="install-squirrelmail.html">Install Squirrelmail for use as a webmail system for OpenACS</a></span></dt><dt><span class="sect1"><a href="install-pam-radius.html">Install PAM Radius for use as external authentication</a></span></dt><dt><span class="sect1"><a href="install-ldap-radius.html">Install LDAP for use as external authentication</a></span></dt><dt><span class="sect1"><a href="aolserver.html">Install AOLserver 3.3oacs1</a></span></dt></dl></dd><dt><span class="appendix"><a href="credits.html">C. Credits</a></span></dt><dd><dl><dt><span class="section"><a href="install-origins.html">Where did this document come from?</a></span></dt><dt><span class="section"><a href="os-install.html">Linux Install Guides</a></span></dt><dt><span class="section"><a href="os-security.html">Security Information</a></span></dt><dt><span class="section"><a href="install-resources.html">Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="acs-package-dev.html">III. For OpenACS Package Developers</a></span></dt><dd><dl><dt><span class="chapter"><a href="tutorial.html">9. Development Tutorial</a></span></dt><dd><dl><dt><span class="sect1"><a href="tutorial-newpackage.html">Creating an Application Package</a></span></dt><dt><span class="sect1"><a href="tutorial-database.html">Setting Up Database Objects</a></span></dt><dt><span class="sect1"><a href="tutorial-pages.html">Creating Web Pages</a></span></dt><dt><span class="sect1"><a href="tutorial-debug.html">Debugging and Automated Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="tutorial-advanced.html">10. Advanced Topics</a></span></dt><dd><dl><dt><span class="sect1"><a href="tutorial-specs.html">Write the Requirements and Design Specs</a></span></dt><dt><span class="sect1"><a href="tutorial-cvs.html">Add the new package to CVS</a></span></dt><dt><span class="sect1"><a href="tutorial-etp-templates.html">OpenACS Edit This Page Templates</a></span></dt><dt><span class="sect1"><a href="tutorial-comments.html">Adding Comments</a></span></dt><dt><span class="sect1"><a href="tutorial-admin-pages.html">Admin Pages</a></span></dt><dt><span class="sect1"><a href="tutorial-categories.html">Categories</a></span></dt><dt><span class="sect1"><a href="profile-code.html">Profile your code</a></span></dt><dt><span class="sect1"><a href="tutorial-distribute.html">Prepare the package for distribution.</a></span></dt><dt><span class="sect1"><a href="tutorial-upgrades.html">Distributing upgrades of your package</a></span></dt><dt><span class="sect1"><a href="tutorial-notifications.html">Notifications</a></span></dt><dt><span class="sect1"><a href="tutorial-hierarchical.html">Hierarchical data</a></span></dt><dt><span class="sect1"><a href="tutorial-vuh.html">Using .vuh files for pretty URLs</a></span></dt><dt><span class="sect1"><a href="tutorial-css-layout.html">Laying out a page with CSS instead of tables</a></span></dt><dt><span class="sect1"><a href="tutorial-html-email.html">Sending HTML email from your application</a></span></dt><dt><span class="sect1"><a href="tutorial-caching.html">Basic Caching</a></span></dt><dt><span class="sect1"><a href="tutorial-schedule-procs.html">Scheduled Procedures</a></span></dt><dt><span class="sect1"><a href="tutorial-wysiwyg-editor.html">Enabling WYSIWYG</a></span></dt><dt><span class="sect1"><a href="tutorial-parameters.html">Adding in parameters for your package</a></span></dt><dt><span class="sect1"><a href="tutorial-upgrade-scripts.html">Writing upgrade scripts</a></span></dt><dt><span class="sect1"><a href="tutorial-second-database.html">Connect to a second database</a></span></dt><dt><span class="sect1"><a href="tutorial-future-topics.html">Future Topics</a></span></dt></dl></dd><dt><span class="chapter"><a href="dev-guide.html">11. Development Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="packages.html">OpenACS Packages</a></span></dt><dt><span class="sect1"><a href="objects.html">OpenACS Data Models and the Object System</a></span></dt><dt><span class="sect1"><a href="request-processor.html">The Request Processor</a></span></dt><dt><span class="sect1"><a href="db-api.html">The OpenACS Database Access API</a></span></dt><dt><span class="sect1"><a href="templates.html">Using Templates in OpenACS</a></span></dt><dt><span class="sect1"><a href="permissions.html">Groups, Context, Permissions</a></span></dt><dt><span class="sect1"><a href="subsites.html">Writing OpenACS Application Pages</a></span></dt><dt><span class="sect1"><a href="parties.html">Parties in OpenACS</a></span></dt><dt><span class="sect1"><a href="permissions-tediously-explained.html">OpenACS Permissions Tediously Explained</a></span></dt><dt><span class="sect1"><a href="object-identity.html">Object Identity</a></span></dt><dt><span class="sect1"><a href="programming-with-aolserver.html">Programming with AOLserver</a></span></dt><dt><span class="sect1"><a href="form-builder.html">Using Form Builder: building html forms dynamically</a></span></dt></dl></dd><dt><span class="chapter"><a href="eng-standards.html">12. Engineering Standards</a></span></dt><dd><dl><dt><span class="sect1"><a href="style-guide.html">OpenACS Style Guide</a></span></dt><dt><span class="sect1"><a href="cvs-guidelines.html">
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>OpenACS Core Documentation</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="next" href="for-everyone.html" title="Part I. OpenACS For Everyone"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"> </td><th width="60%" align="center"></th><td width="20%" align="right"> <a accesskey="n" href="for-everyone.html">Next</a></td></tr></table><hr></div><div class="book"><div class="titlepage"><div><div><h1 class="title"><a name="idp140698004070832"></a>OpenACS Core Documentation</h1></div></div><hr></div><div class="toc"><p><b>Table of Contents</b></p><dl class="toc"><dt><span class="part"><a href="for-everyone.html">I. OpenACS For Everyone</a></span></dt><dd><dl><dt><span class="chapter"><a href="general-documents.html">1. High level information: What is OpenACS?</a></span></dt><dd><dl><dt><span class="sect1"><a href="openacs-overview.html">Overview</a></span></dt><dt><span class="sect1"><a href="release-notes.html">OpenACS Release Notes</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="acs-admin.html">II. Administrator's Guide</a></span></dt><dd><dl><dt><span class="chapter"><a href="install-overview.html">2. Installation Overview</a></span></dt><dd><dl><dt><span class="sect1"><a href="install-steps.html">Basic Steps</a></span></dt><dt><span class="sect1"><a href="individual-programs.html">Prerequisite Software</a></span></dt></dl></dd><dt><span class="chapter"><a href="complete-install.html">3. Complete Installation</a></span></dt><dd><dl><dt><span class="sect1"><a href="unix-installation.html">Install a Unix-like system and supporting software</a></span></dt><dt><span class="sect1"><a href="oracle.html">Install Oracle 8.1.7</a></span></dt><dt><span class="sect1"><a href="postgres.html">Install PostgreSQL</a></span></dt><dt><span class="sect1"><a href="aolserver4.html">Install AOLserver 4</a></span></dt><dt><span class="sect1"><a href="openacs.html">Install OpenACS 5.9.0</a></span></dt><dt><span class="sect1"><a href="win2k-installation.html">OpenACS Installation Guide for Windows</a></span></dt><dt><span class="sect1"><a href="mac-installation.html">OpenACS Installation Guide for macOS</a></span></dt></dl></dd><dt><span class="chapter"><a href="configuring-new-site.html">4. Configuring a new OpenACS Site</a></span></dt><dd><dl><dt><span class="sect1"><a href="configuring-install-packages.html">Installing OpenACS packages</a></span></dt><dt><span class="sect1"><a href="configuring-mounting-packages.html">Mounting OpenACS packages</a></span></dt><dt><span class="sect1"><a href="configuring-configuring-packages.html">Configuring an OpenACS package</a></span></dt><dt><span class="sect1"><a href="configuring-configuring-permissions.html">Setting Permissions on an OpenACS package</a></span></dt><dt><span class="sect1"><a href="how-do-I.html">How Do I?</a></span></dt></dl></dd><dt><span class="chapter"><a href="upgrade.html">5. Upgrading</a></span></dt><dd><dl><dt><span class="sect1"><a href="upgrade-overview.html">Overview</a></span></dt><dt><span class="sect1"><a href="upgrade-4.5-to-4.6.html">Upgrading 4.5 or higher to 4.6.3</a></span></dt><dt><span class="sect1"><a href="upgrade-4.6.3-to-5.html">Upgrading OpenACS 4.6.3 to 5.0</a></span></dt><dt><span class="sect1"><a href="upgrade-5-0-dot.html">Upgrading an OpenACS 5.0.0 or greater installation</a></span></dt><dt><span class="sect1"><a href="upgrade-openacs-files.html">Upgrading the OpenACS files</a></span></dt><dt><span class="sect1"><a href="upgrade-supporting.html">Upgrading Platform components</a></span></dt></dl></dd><dt><span class="chapter"><a href="maintenance-web.html">6. Production Environments</a></span></dt><dd><dl><dt><span class="sect1"><a href="install-openacs-keepalive.html">Starting and Stopping an OpenACS instance.</a></span></dt><dt><span class="sect1"><a href="install-openacs-inittab.html">AOLserver keepalive with inittab</a></span></dt><dt><span class="sect1"><a href="install-next-add-server.html">Running multiple services on one machine</a></span></dt><dt><span class="sect1"><a href="high-avail.html">High Availability/High Performance Configurations</a></span></dt><dt><span class="sect1"><a href="maintenance-deploy.html">Staged Deployment for Production Networks</a></span></dt><dt><span class="sect1"><a href="install-ssl.html">Installing SSL Support for an OpenACS service</a></span></dt><dt><span class="sect1"><a href="analog-setup.html">Set up Log Analysis Reports</a></span></dt><dt><span class="sect1"><a href="uptime.html">External uptime validation</a></span></dt><dt><span class="sect1"><a href="maint-performance.html">Diagnosing Performance Problems</a></span></dt></dl></dd><dt><span class="chapter"><a href="database-management.html">7. Database Management</a></span></dt><dd><dl><dt><span class="sect1"><a href="remote-postgres.html">Running a PostgreSQL database on another server</a></span></dt><dt><span class="sect1"><a href="install-openacs-delete-tablespace.html">Deleting a tablespace</a></span></dt><dt><span class="sect1"><a href="install-next-nightly-vacuum.html">Vacuum Postgres nightly</a></span></dt></dl></dd><dt><span class="chapter"><a href="backup-recovery.html">8. Backup and Recovery</a></span></dt><dd><dl><dt><span class="sect1"><a href="install-next-backups.html">Backup Strategy</a></span></dt><dt><span class="sect1"><a href="snapshot-backup.html">Manual backup and recovery</a></span></dt><dt><span class="sect1"><a href="automated-backup.html">Automated Backup</a></span></dt><dt><span class="sect1"><a href="backups-with-cvs.html">Using CVS for backup-recovery</a></span></dt></dl></dd><dt><span class="appendix"><a href="install-redhat.html">A. Install Red Hat 8/9</a></span></dt><dt><span class="appendix"><a href="install-more-software.html">B. Install additional supporting software</a></span></dt><dd><dl><dt><span class="sect1"><a href="openacs-unpack.html">Unpack the OpenACS tarball</a></span></dt><dt><span class="sect1"><a href="install-cvs.html">Initialize CVS (OPTIONAL)</a></span></dt><dt><span class="sect1"><a href="psgml-for-emacs.html">Add PSGML commands to emacs init file (OPTIONAL)</a></span></dt><dt><span class="sect1"><a href="install-daemontools.html">Install Daemontools (OPTIONAL)</a></span></dt><dt><span class="sect1"><a href="install-qmail.html">Install qmail (OPTIONAL)</a></span></dt><dt><span class="sect1"><a href="analog-install.html">Install Analog web file analyzer</a></span></dt><dt><span class="sect1"><a href="install-nspam.html">Install nspam</a></span></dt><dt><span class="sect1"><a href="install-full-text-search-tsearch2.html">Install Full Text Search using Tsearch2</a></span></dt><dt><span class="sect1"><a href="install-nsopenssl.html">Install nsopenssl</a></span></dt><dt><span class="sect1"><a href="install-tclwebtest.html">Install tclwebtest.</a></span></dt><dt><span class="sect1"><a href="install-php.html">Install PHP for use in AOLserver</a></span></dt><dt><span class="sect1"><a href="install-squirrelmail.html">Install Squirrelmail for use as a webmail system for OpenACS</a></span></dt><dt><span class="sect1"><a href="install-pam-radius.html">Install PAM Radius for use as external authentication</a></span></dt><dt><span class="sect1"><a href="install-ldap-radius.html">Install LDAP for use as external authentication</a></span></dt><dt><span class="sect1"><a href="aolserver.html">Install AOLserver 3.3oacs1</a></span></dt></dl></dd><dt><span class="appendix"><a href="credits.html">C. Credits</a></span></dt><dd><dl><dt><span class="section"><a href="install-origins.html">Where did this document come from?</a></span></dt><dt><span class="section"><a href="os-install.html">Linux Install Guides</a></span></dt><dt><span class="section"><a href="os-security.html">Security Information</a></span></dt><dt><span class="section"><a href="install-resources.html">Resources</a></span></dt></dl></dd></dl></dd><dt><span class="part"><a href="acs-package-dev.html">III. For OpenACS Package Developers</a></span></dt><dd><dl><dt><span class="chapter"><a href="tutorial.html">9. Development Tutorial</a></span></dt><dd><dl><dt><span class="sect1"><a href="tutorial-newpackage.html">Creating an Application Package</a></span></dt><dt><span class="sect1"><a href="tutorial-database.html">Setting Up Database Objects</a></span></dt><dt><span class="sect1"><a href="tutorial-pages.html">Creating Web Pages</a></span></dt><dt><span class="sect1"><a href="tutorial-debug.html">Debugging and Automated Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="tutorial-advanced.html">10. Advanced Topics</a></span></dt><dd><dl><dt><span class="sect1"><a href="tutorial-specs.html">Write the Requirements and Design Specs</a></span></dt><dt><span class="sect1"><a href="tutorial-cvs.html">Add the new package to CVS</a></span></dt><dt><span class="sect1"><a href="tutorial-etp-templates.html">OpenACS Edit This Page Templates</a></span></dt><dt><span class="sect1"><a href="tutorial-comments.html">Adding Comments</a></span></dt><dt><span class="sect1"><a href="tutorial-admin-pages.html">Admin Pages</a></span></dt><dt><span class="sect1"><a href="tutorial-categories.html">Categories</a></span></dt><dt><span class="sect1"><a href="profile-code.html">Profile your code</a></span></dt><dt><span class="sect1"><a href="tutorial-distribute.html">Prepare the package for distribution.</a></span></dt><dt><span class="sect1"><a href="tutorial-upgrades.html">Distributing upgrades of your package</a></span></dt><dt><span class="sect1"><a href="tutorial-notifications.html">Notifications</a></span></dt><dt><span class="sect1"><a href="tutorial-hierarchical.html">Hierarchical data</a></span></dt><dt><span class="sect1"><a href="tutorial-vuh.html">Using .vuh files for pretty URLs</a></span></dt><dt><span class="sect1"><a href="tutorial-css-layout.html">Laying out a page with CSS instead of tables</a></span></dt><dt><span class="sect1"><a href="tutorial-html-email.html">Sending HTML email from your application</a></span></dt><dt><span class="sect1"><a href="tutorial-caching.html">Basic Caching</a></span></dt><dt><span class="sect1"><a href="tutorial-schedule-procs.html">Scheduled Procedures</a></span></dt><dt><span class="sect1"><a href="tutorial-wysiwyg-editor.html">Enabling WYSIWYG</a></span></dt><dt><span class="sect1"><a href="tutorial-parameters.html">Adding in parameters for your package</a></span></dt><dt><span class="sect1"><a href="tutorial-upgrade-scripts.html">Writing upgrade scripts</a></span></dt><dt><span class="sect1"><a href="tutorial-second-database.html">Connect to a second database</a></span></dt><dt><span class="sect1"><a href="tutorial-future-topics.html">Future Topics</a></span></dt></dl></dd><dt><span class="chapter"><a href="dev-guide.html">11. Development Reference</a></span></dt><dd><dl><dt><span class="sect1"><a href="packages.html">OpenACS Packages</a></span></dt><dt><span class="sect1"><a href="objects.html">OpenACS Data Models and the Object System</a></span></dt><dt><span class="sect1"><a href="request-processor.html">The Request Processor</a></span></dt><dt><span class="sect1"><a href="db-api.html">The OpenACS Database Access API</a></span></dt><dt><span class="sect1"><a href="templates.html">Using Templates in OpenACS</a></span></dt><dt><span class="sect1"><a href="permissions.html">Groups, Context, Permissions</a></span></dt><dt><span class="sect1"><a href="subsites.html">Writing OpenACS Application Pages</a></span></dt><dt><span class="sect1"><a href="parties.html">Parties in OpenACS</a></span></dt><dt><span class="sect1"><a href="permissions-tediously-explained.html">OpenACS Permissions Tediously Explained</a></span></dt><dt><span class="sect1"><a href="object-identity.html">Object Identity</a></span></dt><dt><span class="sect1"><a href="programming-with-aolserver.html">Programming with AOLserver</a></span></dt><dt><span class="sect1"><a href="form-builder.html">Using Form Builder: building html forms dynamically</a></span></dt></dl></dd><dt><span class="chapter"><a href="eng-standards.html">12. Engineering Standards</a></span></dt><dd><dl><dt><span class="sect1"><a href="style-guide.html">OpenACS Style Guide</a></span></dt><dt><span class="sect1"><a href="cvs-guidelines.html">
     CVS Guidelines
-  </a></span></dt><dt><span class="sect1"><a href="eng-standards-versioning.html">Release Version Numbering</a></span></dt><dt><span class="sect1"><a href="eng-standards-constraint-naming.html">Constraint naming standard</a></span></dt><dt><span class="sect1"><a href="eng-standards-filenaming.html">ACS File Naming and Formatting Standards</a></span></dt><dt><span class="sect1"><a href="eng-standards-plsql.html">PL/SQL Standards</a></span></dt><dt><span class="sect1"><a href="variables.html">Variables</a></span></dt><dt><span class="sect1"><a href="automated-testing-best-practices.html">Automated Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="doc-standards.html">13. Documentation Standards</a></span></dt><dd><dl><dt><span class="sect1"><a href="docbook-primer.html">OpenACS Documentation Guide</a></span></dt><dt><span class="sect1"><a href="psgml-mode.html">Using PSGML mode in Emacs</a></span></dt><dt><span class="sect1"><a href="nxml-mode.html">Using nXML mode in Emacs</a></span></dt><dt><span class="sect1"><a href="filename.html">Detailed Design Documentation Template</a></span></dt><dt><span class="sect1"><a href="requirements-template.html">System/Application Requirements Template</a></span></dt></dl></dd><dt><span class="chapter"><a href="i18n.html">14. Internationalization</a></span></dt><dd><dl><dt><span class="sect1"><a href="i18n-overview.html">Internationalization and Localization Overview</a></span></dt><dt><span class="sect1"><a href="i18n-introduction.html">How Internationalization/Localization works in OpenACS</a></span></dt><dt><span class="sect1"><a href="i18n-convert.html">How to Internationalize a Package</a></span></dt><dt><span class="sect1"><a href="i18n-design.html">Design Notes</a></span></dt><dt><span class="sect1"><a href="i18n-translators.html">Translator's Guide</a></span></dt></dl></dd><dt><span class="appendix"><a href="cvs-tips.html">D. Using CVS with an OpenACS Site</a></span></dt></dl></dd><dt><span class="part"><a href="acs-plat-dev.html">IV. For OpenACS Platform Developers</a></span></dt><dd><dl><dt><span class="chapter"><a href="kernel-doc.html">15. Kernel Documentation</a></span></dt><dd><dl><dt><span class="sect1"><a href="kernel-overview.html">Overview</a></span></dt><dt><span class="sect1"><a href="object-system-requirements.html">Object Model Requirements</a></span></dt><dt><span class="sect1"><a href="object-system-design.html">Object Model Design</a></span></dt><dt><span class="sect1"><a href="permissions-requirements.html">Permissions Requirements</a></span></dt><dt><span class="sect1"><a href="permissions-design.html">Permissions Design</a></span></dt><dt><span class="sect1"><a href="groups-requirements.html">Groups Requirements</a></span></dt><dt><span class="sect1"><a href="groups-design.html">Groups Design</a></span></dt><dt><span class="sect1"><a href="subsites-requirements.html">Subsites Requirements</a></span></dt><dt><span class="sect1"><a href="subsites-design.html">Subsites Design Document</a></span></dt><dt><span class="sect1"><a href="apm-requirements.html">Package Manager Requirements</a></span></dt><dt><span class="sect1"><a href="apm-design.html">Package Manager Design</a></span></dt><dt><span class="sect1"><a href="db-api-detailed.html">Database Access API</a></span></dt><dt><span class="sect1"><a href="i18n-requirements.html">OpenACS Internationalization Requirements</a></span></dt><dt><span class="sect1"><a href="security-requirements.html">Security Requirements</a></span></dt><dt><span class="sect1"><a href="security-design.html">Security Design</a></span></dt><dt><span class="sect1"><a href="security-notes.html">Security Notes</a></span></dt><dt><span class="sect1"><a href="rp-requirements.html">Request Processor Requirements</a></span></dt><dt><span class="sect1"><a href="rp-design.html">Request Processor Design</a></span></dt><dt><span class="sect1"><a href="tcl-doc.html">Documenting Tcl Files: Page Contracts and Libraries</a></span></dt><dt><span class="sect1"><a href="bootstrap-acs.html">Bootstrapping OpenACS</a></span></dt><dt><span class="sect1"><a href="ext-auth-requirements.html">External Authentication Requirements</a></span></dt></dl></dd><dt><span class="chapter"><a href="releasing-openacs.html">16. Releasing OpenACS</a></span></dt><dd><dl><dt><span class="section"><a href="releasing-openacs-core.html">OpenACS Core and .LRN</a></span></dt><dt><span class="section"><a href="update-repository.html">How to Update the OpenACS.org repository</a></span></dt><dt><span class="section"><a href="releasing-package.html">How to package and release an OpenACS Package</a></span></dt><dt><span class="section"><a href="update-translations.html">How to Update the translations</a></span></dt></dl></dd></dl></dd><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>4.1. <a href="how-do-I.html#idp140665823450560">Site Templates</a></dt><dt>4.2. <a href="how-do-I.html#idp140665823430176">Granting Permissions</a></dt><dt>4.3. <a href="how-do-I.html#idp140665823011856">Granting Permissions in 5.0</a></dt><dt>5.1. <a href="upgrade-overview.html#idp140666101883488">Upgrading with the APM</a></dt><dt>5.2. <a href="upgrade-openacs-files.html#idp140666102001360">Upgrading a local CVS repository</a></dt><dt>6.1. <a href="high-avail.html#idp140665012739840">Multiple-server configuration</a></dt><dt>6.2. <a href="maintenance-deploy.html#idp140665012763456">Simple A/B Deployment - Step 1</a></dt><dt>6.3. <a href="maintenance-deploy.html#idp140665012766144">Simple A/B Deployment - Step 2</a></dt><dt>6.4. <a href="maintenance-deploy.html#idp140665012768832">Simple A/B Deployment - Step 3</a></dt><dt>6.5. <a href="maintenance-deploy.html#idp140665012772288">Complex A/B Deployment - Step 1</a></dt><dt>6.6. <a href="maintenance-deploy.html#idp140665012774976">Complex A/B Deployment - Step 2</a></dt><dt>6.7. <a href="maintenance-deploy.html#idp140665012777664">Complex A/B Deployment - Step 3</a></dt><dt>6.8. <a href="maint-performance.html#idp140665012847216">Query Analysis example</a></dt><dt>8.1. <a href="backup-recovery.html#idp140665974112560">Backup and Recovery Strategy</a></dt><dt>9.1. <a href="tutorial-newpackage.html#idp140665823728864">Assumptions in this section</a></dt><dt>9.2. <a href="tutorial-database.html#idp140665823975504">Tutorial Data Model</a></dt><dt>9.3. <a href="tutorial-database.html#idp140665822795008">The Database Creation Script</a></dt><dt>9.4. <a href="tutorial-database.html#idp140665823594672">Database Deletion Script</a></dt><dt>9.5. <a href="tutorial-pages.html#idp140666274144384">Page Map</a></dt><dt>10.1. <a href="tutorial-cvs.html#idp140665976169280">Upgrading a local CVS repository</a></dt><dt>11.1. <a href="packages.html#idp140665974209600">Server file layout diagram</a></dt><dt>11.2. <a href="packages.html#idp140665974168656">Package file layout diagram</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a href="install-steps.html#idp140665975271664">Default directories for a standard install</a></dt><dt>2.2. <a href="individual-programs.html#compatibility-matrix">Version Compatibility Matrix</a></dt><dt>5.1. <a href="upgrade-overview.html#idp140666101887168">Assumptions in this section</a></dt><dt>6.1. <a href="install-openacs-keepalive.html#idp140665976307824">How it Works</a></dt><dt>10.1. <a href="tutorial-etp-templates.html#idp140665975851424">table showing ETP layout</a></dt><dt>11.1. <a href="packages.html#idp140665973629920">Package files</a></dt><dt>11.2. <a href="permissions-tediously-explained.html#idp140665015347792">Context Hierarchy Example</a></dt><dt>11.3. <a href="permissions-tediously-explained.html#idp140665015364304">acs_objects example data</a></dt><dt>14.1. <a href="i18n-overview.html#i18n-l10n-process">Internationalization and Localization Overview</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>12.1. <a href="variables.html#idp140665014998576">Getting datetime from the database ANSI-style</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"></td><td width="40%" align="right"> <a accesskey="n" href="for-everyone.html">Next</a></td></tr><tr><td width="40%" align="left"> </td><td width="20%" align="center"></td><td width="40%" align="right"> Part I. OpenACS For Everyone</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
+  </a></span></dt><dt><span class="sect1"><a href="eng-standards-versioning.html">Release Version Numbering</a></span></dt><dt><span class="sect1"><a href="eng-standards-constraint-naming.html">Constraint naming standard</a></span></dt><dt><span class="sect1"><a href="eng-standards-filenaming.html">ACS File Naming and Formatting Standards</a></span></dt><dt><span class="sect1"><a href="eng-standards-plsql.html">PL/SQL Standards</a></span></dt><dt><span class="sect1"><a href="variables.html">Variables</a></span></dt><dt><span class="sect1"><a href="automated-testing-best-practices.html">Automated Testing</a></span></dt></dl></dd><dt><span class="chapter"><a href="doc-standards.html">13. Documentation Standards</a></span></dt><dd><dl><dt><span class="sect1"><a href="docbook-primer.html">OpenACS Documentation Guide</a></span></dt><dt><span class="sect1"><a href="psgml-mode.html">Using PSGML mode in Emacs</a></span></dt><dt><span class="sect1"><a href="nxml-mode.html">Using nXML mode in Emacs</a></span></dt><dt><span class="sect1"><a href="filename.html">Detailed Design Documentation Template</a></span></dt><dt><span class="sect1"><a href="requirements-template.html">System/Application Requirements Template</a></span></dt></dl></dd><dt><span class="chapter"><a href="i18n.html">14. Internationalization</a></span></dt><dd><dl><dt><span class="sect1"><a href="i18n-overview.html">Internationalization and Localization Overview</a></span></dt><dt><span class="sect1"><a href="i18n-introduction.html">How Internationalization/Localization works in OpenACS</a></span></dt><dt><span class="sect1"><a href="i18n-convert.html">How to Internationalize a Package</a></span></dt><dt><span class="sect1"><a href="i18n-design.html">Design Notes</a></span></dt><dt><span class="sect1"><a href="i18n-translators.html">Translator's Guide</a></span></dt></dl></dd><dt><span class="appendix"><a href="cvs-tips.html">D. Using CVS with an OpenACS Site</a></span></dt></dl></dd><dt><span class="part"><a href="acs-plat-dev.html">IV. For OpenACS Platform Developers</a></span></dt><dd><dl><dt><span class="chapter"><a href="kernel-doc.html">15. Kernel Documentation</a></span></dt><dd><dl><dt><span class="sect1"><a href="kernel-overview.html">Overview</a></span></dt><dt><span class="sect1"><a href="object-system-requirements.html">Object Model Requirements</a></span></dt><dt><span class="sect1"><a href="object-system-design.html">Object Model Design</a></span></dt><dt><span class="sect1"><a href="permissions-requirements.html">Permissions Requirements</a></span></dt><dt><span class="sect1"><a href="permissions-design.html">Permissions Design</a></span></dt><dt><span class="sect1"><a href="groups-requirements.html">Groups Requirements</a></span></dt><dt><span class="sect1"><a href="groups-design.html">Groups Design</a></span></dt><dt><span class="sect1"><a href="subsites-requirements.html">Subsites Requirements</a></span></dt><dt><span class="sect1"><a href="subsites-design.html">Subsites Design Document</a></span></dt><dt><span class="sect1"><a href="apm-requirements.html">Package Manager Requirements</a></span></dt><dt><span class="sect1"><a href="apm-design.html">Package Manager Design</a></span></dt><dt><span class="sect1"><a href="db-api-detailed.html">Database Access API</a></span></dt><dt><span class="sect1"><a href="i18n-requirements.html">OpenACS Internationalization Requirements</a></span></dt><dt><span class="sect1"><a href="security-requirements.html">Security Requirements</a></span></dt><dt><span class="sect1"><a href="security-design.html">Security Design</a></span></dt><dt><span class="sect1"><a href="security-notes.html">Security Notes</a></span></dt><dt><span class="sect1"><a href="rp-requirements.html">Request Processor Requirements</a></span></dt><dt><span class="sect1"><a href="rp-design.html">Request Processor Design</a></span></dt><dt><span class="sect1"><a href="tcl-doc.html">Documenting Tcl Files: Page Contracts and Libraries</a></span></dt><dt><span class="sect1"><a href="bootstrap-acs.html">Bootstrapping OpenACS</a></span></dt><dt><span class="sect1"><a href="ext-auth-requirements.html">External Authentication Requirements</a></span></dt></dl></dd><dt><span class="chapter"><a href="releasing-openacs.html">16. Releasing OpenACS</a></span></dt><dd><dl><dt><span class="section"><a href="releasing-openacs-core.html">OpenACS Core and .LRN</a></span></dt><dt><span class="section"><a href="update-repository.html">How to Update the OpenACS.org repository</a></span></dt><dt><span class="section"><a href="releasing-package.html">How to package and release an OpenACS Package</a></span></dt><dt><span class="section"><a href="update-translations.html">How to Update the translations</a></span></dt></dl></dd></dl></dd><dt><span class="index"><a href="ix01.html">Index</a></span></dt></dl></div><div class="list-of-figures"><p><b>List of Figures</b></p><dl><dt>4.1. <a href="how-do-I.html#idp140697734077328">Site Templates</a></dt><dt>4.2. <a href="how-do-I.html#idp140697734097808">Granting Permissions</a></dt><dt>4.3. <a href="how-do-I.html#idp140697734101136">Granting Permissions in 5.0</a></dt><dt>5.1. <a href="upgrade-overview.html#idp140698011417872">Upgrading with the APM</a></dt><dt>5.2. <a href="upgrade-openacs-files.html#idp140698011926320">Upgrading a local CVS repository</a></dt><dt>6.1. <a href="high-avail.html#idp140698011712560">Multiple-server configuration</a></dt><dt>6.2. <a href="maintenance-deploy.html#idp140698011372192">Simple A/B Deployment - Step 1</a></dt><dt>6.3. <a href="maintenance-deploy.html#idp140698012110512">Simple A/B Deployment - Step 2</a></dt><dt>6.4. <a href="maintenance-deploy.html#idp140698011944736">Simple A/B Deployment - Step 3</a></dt><dt>6.5. <a href="maintenance-deploy.html#idp140698011292048">Complex A/B Deployment - Step 1</a></dt><dt>6.6. <a href="maintenance-deploy.html#idp140698011388480">Complex A/B Deployment - Step 2</a></dt><dt>6.7. <a href="maintenance-deploy.html#idp140698011335488">Complex A/B Deployment - Step 3</a></dt><dt>6.8. <a href="maint-performance.html#idp140698012091248">Query Analysis example</a></dt><dt>8.1. <a href="backup-recovery.html#idp140697730262912">Backup and Recovery Strategy</a></dt><dt>9.1. <a href="tutorial-newpackage.html#idp140697463252912">Assumptions in this section</a></dt><dt>9.2. <a href="tutorial-database.html#idp140698002449680">Tutorial Data Model</a></dt><dt>9.3. <a href="tutorial-database.html#idp140698006946784">The Database Creation Script</a></dt><dt>9.4. <a href="tutorial-database.html#idp140698007213488">Database Deletion Script</a></dt><dt>9.5. <a href="tutorial-pages.html#idp140697731362544">Page Map</a></dt><dt>10.1. <a href="tutorial-cvs.html#idp140697193935072">Upgrading a local CVS repository</a></dt><dt>11.1. <a href="packages.html#idp140697732723312">Server file layout diagram</a></dt><dt>11.2. <a href="packages.html#idp140697732391776">Package file layout diagram</a></dt></dl></div><div class="list-of-tables"><p><b>List of Tables</b></p><dl><dt>2.1. <a href="install-steps.html#idp140698011826928">Default directories for a standard install</a></dt><dt>2.2. <a href="individual-programs.html#compatibility-matrix">Version Compatibility Matrix</a></dt><dt>5.1. <a href="upgrade-overview.html#idp140698012084400">Assumptions in this section</a></dt><dt>6.1. <a href="install-openacs-keepalive.html#idp140698012103328">How it Works</a></dt><dt>10.1. <a href="tutorial-etp-templates.html#idp140697193965744">table showing ETP layout</a></dt><dt>11.1. <a href="packages.html#idp140697732397568">Package files</a></dt><dt>11.2. <a href="permissions-tediously-explained.html#idp140698455516464">Context Hierarchy Example</a></dt><dt>11.3. <a href="permissions-tediously-explained.html#idp140698455103008">acs_objects example data</a></dt><dt>14.1. <a href="i18n-overview.html#i18n-l10n-process">Internationalization and Localization Overview</a></dt></dl></div><div class="list-of-examples"><p><b>List of Examples</b></p><dl><dt>12.1. <a href="variables.html#idp140696927585168">Getting datetime from the database ANSI-style</a></dt></dl></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"> </td><td width="20%" align="center"></td><td width="40%" align="right"> <a accesskey="n" href="for-everyone.html">Next</a></td></tr><tr><td width="40%" align="left"> </td><td width="20%" align="center"></td><td width="40%" align="right"> Part I. OpenACS For Everyone</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/install-cvs.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-cvs.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/install-cvs.adp	3 Sep 2021 09:15:04 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/install-cvs.adp	7 Sep 2021 09:39:26 -0000	1.4.2.6
@@ -9,7 +9,7 @@
 			rightLink="psgml-for-emacs" rightLabel="Next">
 		    <div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="install-cvs" id="install-cvs"></a>Initialize CVS (OPTIONAL)</h2></div></div></div><a class="indexterm" name="idp140665012998304" id="idp140665012998304"></a><p>CVS is a source control system. Create and initialize a
+<a name="install-cvs" id="install-cvs"></a>Initialize CVS (OPTIONAL)</h2></div></div></div><a class="indexterm" name="idp140698013677840" id="idp140698013677840"></a><p>CVS is a source control system. Create and initialize a
 directory for a local cvs repository.</p><pre class="screen">[root tmp]# <strong class="userinput"><code>mkdir /cvsroot</code></strong>
 [root tmp]#<strong class="userinput"><code> cvs -d /cvsroot init</code></strong>
 [root tmp]#
Index: openacs-4/packages/acs-core-docs/www/install-cvs.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-cvs.html,v
diff -u -r1.43.2.4 -r1.43.2.5
--- openacs-4/packages/acs-core-docs/www/install-cvs.html	3 Sep 2021 09:15:04 -0000	1.43.2.4
+++ openacs-4/packages/acs-core-docs/www/install-cvs.html	7 Sep 2021 09:39:26 -0000	1.43.2.5
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Initialize CVS (OPTIONAL)</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="install-more-software.html" title="Appendix B. Install additional supporting software"><link rel="previous" href="openacs-unpack.html" title="Unpack the OpenACS tarball"><link rel="next" href="psgml-for-emacs.html" title="Add PSGML commands to emacs init file (OPTIONAL)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="openacs-unpack.html">Prev</a> </td><th width="60%" align="center">Appendix B. Install additional supporting software</th><td width="20%" align="right"> <a accesskey="n" href="psgml-for-emacs.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="install-cvs"></a>Initialize CVS (OPTIONAL)</h2></div></div></div><a class="indexterm" name="idp140665012998304"></a><p>CVS is a source control system.  Create and initialize a
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Initialize CVS (OPTIONAL)</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="install-more-software.html" title="Appendix B. Install additional supporting software"><link rel="previous" href="openacs-unpack.html" title="Unpack the OpenACS tarball"><link rel="next" href="psgml-for-emacs.html" title="Add PSGML commands to emacs init file (OPTIONAL)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="openacs-unpack.html">Prev</a> </td><th width="60%" align="center">Appendix B. Install additional supporting software</th><td width="20%" align="right"> <a accesskey="n" href="psgml-for-emacs.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="install-cvs"></a>Initialize CVS (OPTIONAL)</h2></div></div></div><a class="indexterm" name="idp140698013677840"></a><p>CVS is a source control system.  Create and initialize a
       directory for a local cvs repository.</p><pre class="screen">[root tmp]# <strong class="userinput"><code>mkdir /cvsroot</code></strong>
 [root tmp]#<strong class="userinput"><code> cvs -d /cvsroot init</code></strong>
 [root tmp]#
Index: openacs-4/packages/acs-core-docs/www/install-daemontools.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-daemontools.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/install-daemontools.adp	3 Sep 2021 09:15:04 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/install-daemontools.adp	7 Sep 2021 09:39:26 -0000	1.4.2.6
@@ -15,7 +15,7 @@
 svgroup. svgroup is a script for granting permissions, to allow
 users other than root to use daemontools for specific services.</p><div class="orderedlist"><ol class="orderedlist" type="1">
 <li class="listitem">
-<p>Install Daemontools</p><a class="indexterm" name="idp140665014872560" id="idp140665014872560"></a><p>
+<p>Install Daemontools</p><a class="indexterm" name="idp140698013694016" id="idp140698013694016"></a><p>
 <a class="link" href="individual-programs">download
 daemontools</a> and install it.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem">
Index: openacs-4/packages/acs-core-docs/www/install-daemontools.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-daemontools.html,v
diff -u -r1.44.2.4 -r1.44.2.5
--- openacs-4/packages/acs-core-docs/www/install-daemontools.html	3 Sep 2021 09:15:05 -0000	1.44.2.4
+++ openacs-4/packages/acs-core-docs/www/install-daemontools.html	7 Sep 2021 09:39:27 -0000	1.44.2.5
@@ -4,7 +4,7 @@
       installed in /package.  These commands install daemontools and
       svgroup.  svgroup is a script for granting permissions, to allow
       users other than root to use daemontools for specific
-      services.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Install Daemontools</p><a class="indexterm" name="idp140665014872560"></a><p><a class="link" href="individual-programs.html#daemontools-download">download daemontools</a> and install it.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Red Hat 8</p><pre class="screen">[root root]# <strong class="userinput"><code>mkdir -p /package</code></strong>
+      services.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Install Daemontools</p><a class="indexterm" name="idp140698013694016"></a><p><a class="link" href="individual-programs.html#daemontools-download">download daemontools</a> and install it.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Red Hat 8</p><pre class="screen">[root root]# <strong class="userinput"><code>mkdir -p /package</code></strong>
 [root root]# <strong class="userinput"><code>chmod 1755 /package/</code></strong>
 [root root]# <strong class="userinput"><code>cd /package/</code></strong>
 [root package]# <strong class="userinput"><code>tar xzf /tmp/daemontools-0.76.tar.gz</code></strong>
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 -r1.5.2.5 -r1.5.2.6
--- openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.adp	3 Sep 2021 09:15:05 -0000	1.5.2.5
+++ openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.adp	7 Sep 2021 09:39:27 -0000	1.5.2.6
@@ -17,7 +17,7 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="install-tsearch2" id="install-tsearch2"></a>Install Tsearch2 module</h3></div></div></div><a class="indexterm" name="idp140665014818544" id="idp140665014818544"></a><p>In earlier versions of PostgreSQL (7.4), tsearch2 was a contrib
+<a name="install-tsearch2" id="install-tsearch2"></a>Install Tsearch2 module</h3></div></div></div><a class="indexterm" name="idp140698013419600" id="idp140698013419600"></a><p>In earlier versions of PostgreSQL (7.4), tsearch2 was a contrib
 module. With PostgreSQL 9.*, it was included in the standard
 PostgreSQL package with minor naming changes (e.g. the function
 "rank" became "ts_rank"). PostgreSQL 9 included
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 -r1.15.2.4 -r1.15.2.5
--- openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.html	3 Sep 2021 09:15:05 -0000	1.15.2.4
+++ openacs-4/packages/acs-core-docs/www/install-full-text-search-tsearch2.html	7 Sep 2021 09:39:27 -0000	1.15.2.5
@@ -6,7 +6,7 @@
       V2 Introduction by Andrew J. Kopciuch</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="install-tsearch2"></a>Install Tsearch2 module</h3></div></div></div><a class="indexterm" name="idp140665014818544"></a><p>In earlier versions of PostgreSQL (7.4), tsearch2 was a contrib
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="install-tsearch2"></a>Install Tsearch2 module</h3></div></div></div><a class="indexterm" name="idp140698013419600"></a><p>In earlier versions of PostgreSQL (7.4), tsearch2 was a contrib
       module. With PostgreSQL 9.*, it was included in the standard
       PostgreSQL package with minor naming changes (e.g. the function
       "rank" became "ts_rank"). PostgreSQL 9 included a backward
Index: openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.adp	3 Sep 2021 09:15:07 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.adp	7 Sep 2021 09:39:27 -0000	1.4.2.6
@@ -105,7 +105,7 @@
 commands.</p><p>More information can be found on the <a class="ulink" href="http://panoptic.com/wiki/aolserver/How_to_start_stop_AOLserver_using_Daemontools" target="_top">AOLserver Daemontools</a> page.</p>
 </li>
 </ol></div><div class="table">
-<a name="idp140665976307824" id="idp140665976307824"></a><p class="title"><strong>Table 6.1. How it
+<a name="idp140698012103328" id="idp140698012103328"></a><p class="title"><strong>Table 6.1. How it
 Works</strong></p><div class="table-contents"><table class="table" summary="How it Works" cellspacing="0" border="1">
 <colgroup>
 <col><col><col><col><col><col>
Index: openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.html,v
diff -u -r1.27.2.4 -r1.27.2.5
--- openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.html	3 Sep 2021 09:15:07 -0000	1.27.2.4
+++ openacs-4/packages/acs-core-docs/www/install-openacs-keepalive.html	7 Sep 2021 09:39:27 -0000	1.27.2.5
@@ -64,6 +64,6 @@
 
         More information can be found on the <a class="ulink" href="http://panoptic.com/wiki/aolserver/How_to_start_stop_AOLserver_using_Daemontools" target="_top">AOLserver
 	Daemontools</a> page.
-</p></li></ol></div><div class="table"><a name="idp140665976307824"></a><p class="title"><b>Table 6.1. How it Works</b></p><div class="table-contents"><table class="table" summary="How it Works" cellspacing="0" border="1"><colgroup><col><col><col><col><col><col></colgroup><thead><tr><th align="center">Program</th><th align="center">Invoked by this program ...</th><th align="center">... using this file</th><th align="center">Where to find errors</th><th align="center">Log goes to</th><th align="center">Use these commands to control it</th></tr></thead><tbody><tr><td align="center">svscanboot
+</p></li></ol></div><div class="table"><a name="idp140698012103328"></a><p class="title"><b>Table 6.1. How it Works</b></p><div class="table-contents"><table class="table" summary="How it Works" cellspacing="0" border="1"><colgroup><col><col><col><col><col><col></colgroup><thead><tr><th align="center">Program</th><th align="center">Invoked by this program ...</th><th align="center">... using this file</th><th align="center">Where to find errors</th><th align="center">Log goes to</th><th align="center">Use these commands to control it</th></tr></thead><tbody><tr><td align="center">svscanboot
       </td><td align="center">init</td><td align="center">/etc/inittab</td><td align="center">ps -auxw | grep readproctitle</td><td align="center">n/a</td><td align="center"> </td></tr><tr><td align="center">aolserver</td><td align="center"><code class="computeroutput"></code>supervise
 (a child of svscanboot)</td><td align="center">/service/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/run</td><td align="center">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/log/error.log</td><td align="center">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/log/$OPENACS_SERVICE_NAME.log</td><td align="center">svc -k /service/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td align="center">postgresql</td><td align="center">Redhat init scripts during boot</td><td align="center">/etc/init.d/postgresql</td><td align="center">/usr/local/pgsql/data/server.log</td><td align="center"> </td><td align="center">service postgresql start (Red Hat), /etc/init.d/postgresql start (Debian)</td></tr></tbody></table></div></div><br class="table-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="maintenance-web.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="install-openacs-inittab.html">Next</a></td></tr><tr><td width="40%" align="left">Chapter 6. Production Environments </td><td width="20%" align="center"><a accesskey="u" href="maintenance-web.html">Up</a></td><td width="40%" align="right"> AOLserver keepalive with inittab</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/install-qmail.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-qmail.adp,v
diff -u -r1.5.2.6 -r1.5.2.7
--- openacs-4/packages/acs-core-docs/www/install-qmail.adp	3 Sep 2021 09:15:09 -0000	1.5.2.6
+++ openacs-4/packages/acs-core-docs/www/install-qmail.adp	7 Sep 2021 09:39:27 -0000	1.5.2.7
@@ -19,7 +19,7 @@
 available from <a class="ulink" href="https://en.wikipedia.org/wiki/Qmail" target="_top">QMail wiki
 page</a>
 </p></li><li class="listitem">
-<p>Replace sendmail with qmail&#39;s wrapper.</p><a class="indexterm" name="idp140665014912016" id="idp140665014912016"></a><pre class="screen">[root qmail-1.03]# <strong class="userinput"><code>rm -f /usr/bin/sendmail /usr/sbin/sendmail</code></strong>
+<p>Replace sendmail with qmail&#39;s wrapper.</p><a class="indexterm" name="idp140698013738144" id="idp140698013738144"></a><pre class="screen">[root qmail-1.03]# <strong class="userinput"><code>rm -f /usr/bin/sendmail /usr/sbin/sendmail</code></strong>
 [root qmail-1.03]# <strong class="userinput"><code>ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail</code></strong>
 [root qmail-1.03]#
 <span class="action"><span class="action">rm -f /usr/bin/sendmail /usr/sbin/sendmail
@@ -55,7 +55,7 @@
 chmod 644 ~alias/.qmail* 
 /var/qmail/bin/maildirmake ~alias/Maildir/ 
 chown -R alias.nofiles /var/qmail/alias/Maildir</span></span>
-</pre><a class="indexterm" name="idp140665014925104" id="idp140665014925104"></a><p>Configure qmail to use the Maildir delivery format (instead of
+</pre><a class="indexterm" name="idp140698013752576" id="idp140698013752576"></a><p>Configure qmail to use the Maildir delivery format (instead of
 mbox), and install a version of the qmail startup script modified
 to use Maildir.</p><pre class="screen">[root alias]# <strong class="userinput"><code>echo "./Maildir" &gt; /var/qmail/bin/.qmail</code></strong>
 [root alias]# <strong class="userinput"><code>cp /tmp/openacs-5.9.0/packages/acs-core-docs/www/files/qmail.rc.txt /var/qmail/rc</code></strong>
Index: openacs-4/packages/acs-core-docs/www/install-qmail.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-qmail.html,v
diff -u -r1.45.2.4 -r1.45.2.5
--- openacs-4/packages/acs-core-docs/www/install-qmail.html	3 Sep 2021 09:15:10 -0000	1.45.2.4
+++ openacs-4/packages/acs-core-docs/www/install-qmail.html	7 Sep 2021 09:39:28 -0000	1.45.2.5
@@ -4,7 +4,7 @@
       send and receive mail, and you don't want to use an alternate
       MTA.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><b>Install qmail. </b>QMail is available as standard Debian/Ubuntu package,
       rpms for Fedora/Redhat/CenTOS are available from <a class="ulink" href="https://en.wikipedia.org/wiki/Qmail" target="_top">QMail wiki
-	     page</a></p></li><li class="listitem"><p>Replace sendmail with qmail's wrapper.</p><a class="indexterm" name="idp140665014912016"></a><pre class="screen">[root qmail-1.03]# <strong class="userinput"><code>rm -f /usr/bin/sendmail /usr/sbin/sendmail</code></strong>
+	     page</a></p></li><li class="listitem"><p>Replace sendmail with qmail's wrapper.</p><a class="indexterm" name="idp140698013738144"></a><pre class="screen">[root qmail-1.03]# <strong class="userinput"><code>rm -f /usr/bin/sendmail /usr/sbin/sendmail</code></strong>
 [root qmail-1.03]# <strong class="userinput"><code>ln -s /var/qmail/bin/sendmail /usr/sbin/sendmail</code></strong>
 [root qmail-1.03]#
 <span class="action"><span class="action">rm -f /usr/bin/sendmail /usr/sbin/sendmail
@@ -26,7 +26,7 @@
 <span class="action"><span class="action">cd ~alias; touch .qmail-postmaster .qmail-mailer-daemon .qmail-root 
 chmod 644 ~alias/.qmail* 
 /var/qmail/bin/maildirmake ~alias/Maildir/ 
-chown -R alias.nofiles /var/qmail/alias/Maildir</span></span></pre><a class="indexterm" name="idp140665014925104"></a><p>Configure qmail to use the Maildir delivery format
+chown -R alias.nofiles /var/qmail/alias/Maildir</span></span></pre><a class="indexterm" name="idp140698013752576"></a><p>Configure qmail to use the Maildir delivery format
           (instead of mbox), and install a version of the qmail startup script modified to use Maildir.</p><pre class="screen">[root alias]# <strong class="userinput"><code>echo "./Maildir" &gt; /var/qmail/bin/.qmail</code></strong>
 [root alias]# <strong class="userinput"><code>cp /tmp/openacs-5.9.0/packages/acs-core-docs/www/files/qmail.rc.txt /var/qmail/rc</code></strong>
 [root alias]# <strong class="userinput"><code>chmod 755 /var/qmail/rc</code></strong>
Index: openacs-4/packages/acs-core-docs/www/install-redhat.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-redhat.adp,v
diff -u -r1.5.2.7 -r1.5.2.8
--- openacs-4/packages/acs-core-docs/www/install-redhat.adp	3 Sep 2021 09:15:10 -0000	1.5.2.7
+++ openacs-4/packages/acs-core-docs/www/install-redhat.adp	7 Sep 2021 09:39:28 -0000	1.5.2.8
@@ -35,7 +35,7 @@
 <a name="install-first-step" id="install-first-step"></a>Unplug
 the network cable from your computer. We don&#39;t want to connect
 to the network until we&#39;re sure the computer is secure.
-<a class="indexterm" name="idp140665824084384" id="idp140665824084384"></a> (Wherever you see the word secure, you
+<a class="indexterm" name="idp140697732456080" id="idp140697732456080"></a> (Wherever you see the word secure, you
 should always read it as, "secure enough for our purposes,
 given the amount of work we&#39;re willing to exert and the
 estimated risk and consequences.")</p></li><li class="listitem"><p>Insert Red Hat 8.0 or 9.0 Disk 1 into the CD-ROM and reboot the
@@ -73,7 +73,7 @@
 screen</p></li>
 </ol></div>
 </li><li class="listitem">
-<p>Configure Networking. <a class="indexterm" name="idp140665823776944" id="idp140665823776944"></a> Again, if you
+<p>Configure Networking. <a class="indexterm" name="idp140697732480192" id="idp140697732480192"></a> Again, if you
 know what you&#39;re doing, do this step yourself, being sure to
 note the firewall holes. Otherwise, follow the instructions in this
 step to set up a computer directly connected to the internet with a
@@ -102,7 +102,7 @@
 development server we&#39;ll be setting up.</p></li>
 </ol></div>
 </li><li class="listitem"><p>
-<a class="indexterm" name="idp140665823447264" id="idp140665823447264"></a>Select any additional languages you want
+<a class="indexterm" name="idp140697732497952" id="idp140697732497952"></a>Select any additional languages you want
 the computer to support and then click <code class="computeroutput"><span class="guibutton"><span class="guibutton">
 <u><span class="accel">N</span></u>ext</span></span></code>
 </p></li><li class="listitem"><p>Choose your timezone and click <code class="computeroutput"><span class="guibutton"><span class="guibutton">
@@ -118,11 +118,11 @@
 web server, because that would conflict with the database and web
 server we&#39;ll install later.</p><table border="0" summary="Simple list" class="simplelist">
 <tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">Editors</span></span></code>
-(this installs emacs<a class="indexterm" name="idp140665823470304" id="idp140665823470304"></a>),</td></tr><tr><td>click <code class="computeroutput"><span class="guilabel"><span class="guilabel">Details</span></span></code> next
+(this installs emacs<a class="indexterm" name="idp140697732505680" id="idp140697732505680"></a>),</td></tr><tr><td>click <code class="computeroutput"><span class="guilabel"><span class="guilabel">Details</span></span></code> next
 to <code class="computeroutput"><span class="guilabel"><span class="guilabel">Text-based Internet</span></span></code>, check
 <code class="computeroutput"><span class="guilabel"><span class="guilabel">lynx</span></span></code>, and click <code class="computeroutput"><span class="guibutton"><span class="guibutton">
 <u><span class="accel">O</span></u>K</span></span></code>;</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">Authoring and
-Publishing</span></span></code> (<a class="indexterm" name="idp140665823618224" id="idp140665823618224"></a>this installs
+Publishing</span></span></code> (<a class="indexterm" name="idp140697732512496" id="idp140697732512496"></a>this installs
 docbook),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Server Configuration
 Tools</span></span></code>,</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Web
 Server</span></span></code>,</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Windows File
@@ -147,7 +147,7 @@
 will appear.</p><table border="0" summary="Simple list" class="simplelist">
 <tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">apmd</span></span></code>
 (monitors power, not very useful for servers),</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">ImageMagick</span></span></code>
-(required for the <a class="indexterm" name="idp140665823311984" id="idp140665823311984"></a>photo-album packages,</td></tr><tr><td>uncheck<code class="computeroutput"><span class="guilabel"><span class="guilabel">isdn4k-utils</span></span></code>
+(required for the <a class="indexterm" name="idp140697732531104" id="idp140697732531104"></a>photo-album packages,</td></tr><tr><td>uncheck<code class="computeroutput"><span class="guilabel"><span class="guilabel">isdn4k-utils</span></span></code>
 (unless you are using isdn, this installs a useless daemon),</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">mutt</span></span></code> (a mail
 program that reads Maildir),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">nfs-utils</span></span></code>
 (nfs is a major security risk),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">pam-devel</span></span></code> (I
@@ -192,7 +192,7 @@
 <p>Lock down SSH</p><div class="orderedlist"><ol class="orderedlist" type="a">
 <li class="listitem">
 <p>
-<a class="indexterm" name="idp140665824155088" id="idp140665824155088"></a> SSH is the protocol we use to connect
+<a class="indexterm" name="idp140697732248528" id="idp140697732248528"></a> SSH is the protocol we use to connect
 securely to the computer (replacing telnet, which is insecure).
 sshd is the daemon that listens for incoming ssh connections. As a
 security precaution, we are now going to tell ssh not to allow
Index: openacs-4/packages/acs-core-docs/www/install-redhat.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-redhat.html,v
diff -u -r1.44.2.5 -r1.44.2.6
--- openacs-4/packages/acs-core-docs/www/install-redhat.html	3 Sep 2021 09:15:11 -0000	1.44.2.5
+++ openacs-4/packages/acs-core-docs/www/install-redhat.html	7 Sep 2021 09:39:28 -0000	1.44.2.6
@@ -27,7 +27,7 @@
 	</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><a name="install-first-step"></a>Unplug the network cable from your
           computer.  We don't want to connect to the network
           until we're sure the computer is secure.  
-           <a class="indexterm" name="idp140665824084384"></a>
+           <a class="indexterm" name="idp140697732456080"></a>
   (Wherever you see
           the word secure, you should always read it as, "secure
           enough for our purposes, given the amount of work we're
@@ -55,7 +55,7 @@
 <code class="computeroutput"><span class="guilabel"><span class="guilabel">Re<u><span class="accel">v</span></u>iew (and modify if needed) the partitions created</span></span></code> and click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code></p></li><li class="listitem"><p>On the pop-up window asking "Are you sure
 	  you want to do this?" click
 	  <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">Y</span></u>es</span></span></code>
-	  IF YOU ARE WIPING YOUR HARD DRIVE.</p></li><li class="listitem"><p>Click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code> on the boot loader screen</p></li></ol></div></li><li class="listitem"><p>Configure Networking.  <a class="indexterm" name="idp140665823776944"></a>
+	  IF YOU ARE WIPING YOUR HARD DRIVE.</p></li><li class="listitem"><p>Click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code> on the boot loader screen</p></li></ol></div></li><li class="listitem"><p>Configure Networking.  <a class="indexterm" name="idp140697732480192"></a>
 Again, if you know what you're doing, do this step
           yourself, being sure to note the firewall holes. Otherwise,
           follow the instructions in this step to set up a computer directly connected to the internet with a dedicated IP address.</p><div class="orderedlist"><ol class="orderedlist" type="a"><li class="listitem"><p>DHCP is a system by which a computer that
@@ -75,7 +75,7 @@
 <code class="computeroutput"><span class="guilabel"><span class="guilabel">Mail (SMTP)</span></span></code>.  In the <code class="computeroutput"><span class="guilabel"><span class="guilabel">Other <u><span class="accel">p</span></u>orts</span></span></code>
 box, enter <strong class="userinput"><code>443, 8000, 8443</code></strong>.  Click
 <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code>.
-Port 443 is for https (http over ssl), and 8000 and 8443 are http and https access to the development server we'll be setting up.</p></li></ol></div></li><li class="listitem"><p><a class="indexterm" name="idp140665823447264"></a>Select any additional languages you want the
+Port 443 is for https (http over ssl), and 8000 and 8443 are http and https access to the development server we'll be setting up.</p></li></ol></div></li><li class="listitem"><p><a class="indexterm" name="idp140697732497952"></a>Select any additional languages you want the
 	  computer to support and then click
 	  <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code></p></li><li class="listitem"><p>Choose your timezone and click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code>.</p></li><li class="listitem"><p>Type in a root
 password, twice.</p></li><li class="listitem"><p>On the Package selection page, we're going to
@@ -87,13 +87,13 @@
 risk that's still screened by the firewall, or a resource hog.  Just
 don't install a database or web server, because that would conflict
 with the database and web server we'll install later.
-</p><table border="0" summary="Simple list" class="simplelist"><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">Editors</span></span></code> (this installs emacs<a class="indexterm" name="idp140665823470304"></a>),</td></tr><tr><td>click <code class="computeroutput"><span class="guilabel"><span class="guilabel">Details</span></span></code> next to <code class="computeroutput"><span class="guilabel"><span class="guilabel">Text-based Internet</span></span></code>, check <code class="computeroutput"><span class="guilabel"><span class="guilabel">lynx</span></span></code>, and click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">O</span></u>K</span></span></code>;</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">Authoring and Publishing</span></span></code> (<a class="indexterm" name="idp140665823618224"></a>this installs docbook),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Server Configuration Tools</span></span></code>,</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Web Server</span></span></code>,</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Windows File Server</span></span></code>,</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">SQL Database Server</span></span></code> (this installs PostgreSQL),</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">Development Tools</span></span></code> (this installs gmake and other build tools),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Administration Tools</span></span></code>, and</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Printing Support</span></span></code>.</td></tr></table><p>At the bottom, check <code class="computeroutput"><span class="guilabel"><span class="guilabel"><u><span class="accel">S</span></u>elect Individual Packages</span></span></code> and click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code></p></li><li class="listitem"><p>We need to fine-tune the exact list of packages.
+</p><table border="0" summary="Simple list" class="simplelist"><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">Editors</span></span></code> (this installs emacs<a class="indexterm" name="idp140697732505680"></a>),</td></tr><tr><td>click <code class="computeroutput"><span class="guilabel"><span class="guilabel">Details</span></span></code> next to <code class="computeroutput"><span class="guilabel"><span class="guilabel">Text-based Internet</span></span></code>, check <code class="computeroutput"><span class="guilabel"><span class="guilabel">lynx</span></span></code>, and click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">O</span></u>K</span></span></code>;</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">Authoring and Publishing</span></span></code> (<a class="indexterm" name="idp140697732512496"></a>this installs docbook),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Server Configuration Tools</span></span></code>,</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Web Server</span></span></code>,</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Windows File Server</span></span></code>,</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">SQL Database Server</span></span></code> (this installs PostgreSQL),</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">Development Tools</span></span></code> (this installs gmake and other build tools),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Administration Tools</span></span></code>, and</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">Printing Support</span></span></code>.</td></tr></table><p>At the bottom, check <code class="computeroutput"><span class="guilabel"><span class="guilabel"><u><span class="accel">S</span></u>elect Individual Packages</span></span></code> and click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code></p></li><li class="listitem"><p>We need to fine-tune the exact list of packages.
 The same rules apply as in the last step - you can add more stuff, but
 you shouldn't remove anything the guide adds.  We're going to go
 through all the packages in one big list, so select
 <code class="computeroutput"><span class="guilabel"><span class="guilabel"><u><span class="accel">F</span></u>lat
 View</span></span></code> and wait. In a minute, a
-list of packages will appear.</p><table border="0" summary="Simple list" class="simplelist"><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">apmd</span></span></code> (monitors power, not very useful for servers), </td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">ImageMagick</span></span></code> (required for the <a class="indexterm" name="idp140665823311984"></a>photo-album packages, </td></tr><tr><td>uncheck<code class="computeroutput"><span class="guilabel"><span class="guilabel">isdn4k-utils</span></span></code> (unless you are using isdn, this installs a useless daemon), </td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">mutt</span></span></code> (a mail program that reads Maildir),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">nfs-utils</span></span></code> (nfs is a major security risk), </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">pam-devel</span></span></code> (I don't remember why, but we don't want this), </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">portmap</span></span></code>, </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">postfix</span></span></code> (this is an MTA, but we're going to install qmail later), </td></tr><tr><td>check  <code class="computeroutput"><span class="guilabel"><span class="guilabel">postgresql-devel</span></span></code>,</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">rsh</span></span></code> (rsh is a security hole), </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">sendmail</span></span></code> (sendmail is an insecure MTA; we're going to install qmail instead later),</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">tcl</span></span></code> (we need tcl), and </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">xinetd</span></span></code> (xinetd handles incoming tcp connections.  We'll install a different, more secure program, ucspi-tcp).</td></tr><tr><td>Click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code></td></tr></table></li><li class="listitem"><p>Red Hat isn't completely happy with the combination
+list of packages will appear.</p><table border="0" summary="Simple list" class="simplelist"><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">apmd</span></span></code> (monitors power, not very useful for servers), </td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">ImageMagick</span></span></code> (required for the <a class="indexterm" name="idp140697732531104"></a>photo-album packages, </td></tr><tr><td>uncheck<code class="computeroutput"><span class="guilabel"><span class="guilabel">isdn4k-utils</span></span></code> (unless you are using isdn, this installs a useless daemon), </td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">mutt</span></span></code> (a mail program that reads Maildir),</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">nfs-utils</span></span></code> (nfs is a major security risk), </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">pam-devel</span></span></code> (I don't remember why, but we don't want this), </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">portmap</span></span></code>, </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">postfix</span></span></code> (this is an MTA, but we're going to install qmail later), </td></tr><tr><td>check  <code class="computeroutput"><span class="guilabel"><span class="guilabel">postgresql-devel</span></span></code>,</td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">rsh</span></span></code> (rsh is a security hole), </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">sendmail</span></span></code> (sendmail is an insecure MTA; we're going to install qmail instead later),</td></tr><tr><td>check <code class="computeroutput"><span class="guilabel"><span class="guilabel">tcl</span></span></code> (we need tcl), and </td></tr><tr><td>uncheck <code class="computeroutput"><span class="guilabel"><span class="guilabel">xinetd</span></span></code> (xinetd handles incoming tcp connections.  We'll install a different, more secure program, ucspi-tcp).</td></tr><tr><td>Click <code class="computeroutput"><span class="guibutton"><span class="guibutton"><u><span class="accel">N</span></u>ext</span></span></code></td></tr></table></li><li class="listitem"><p>Red Hat isn't completely happy with the combination
 of packages we've selected, and wants to satisfy some dependencies.
 Don't let it.  On the next screen, choose
 <code class="computeroutput"><span class="guilabel"><span class="guilabel">I<u><span class="accel">g</span></u>nore Package
@@ -119,7 +119,7 @@
         upgrading all of that.  Since you are upgrading the kernel,
         reboot after this step.
 </p></li><li class="listitem"><p>Lock down SSH</p><div class="orderedlist"><ol class="orderedlist" type="a"><li class="listitem"><p>
-              <a class="indexterm" name="idp140665824155088"></a>
+              <a class="indexterm" name="idp140697732248528"></a>
               SSH is the protocol we use to connect
               securely to the computer (replacing telnet, which is
               insecure).  sshd is the daemon that listens for incoming
Index: openacs-4/packages/acs-core-docs/www/install-steps.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-steps.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/install-steps.adp	3 Sep 2021 09:15:12 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/install-steps.adp	7 Sep 2021 09:39:28 -0000	1.4.2.6
@@ -99,8 +99,8 @@
 </ul></div>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665975271024" id="idp140665975271024"></a>Paths and Users</h3></div></div></div><div class="table">
-<a name="idp140665975271664" id="idp140665975271664"></a><p class="title"><strong>Table 2.1. Default directories
+<a name="idp140698011826288" id="idp140698011826288"></a>Paths and Users</h3></div></div></div><div class="table">
+<a name="idp140698011826928" id="idp140698011826928"></a><p class="title"><strong>Table 2.1. Default directories
 for a standard install</strong></p><div class="table-contents"><table class="table" summary="Default directories for a standard install" cellspacing="0" width="100%" border="1">
 <colgroup>
 <col><col>
@@ -111,7 +111,7 @@
 <td>name of administrative access account</td><td>remadmin</td>
 </tr><tr>
 <td>OpenACS service</td><td>
-<a class="indexterm" name="idp140665975292880" id="idp140665975292880"></a><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span> (set to service0
+<a class="indexterm" name="idp140698011831536" id="idp140698011831536"></a><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span> (set to service0
 in default install)</td>
 </tr><tr>
 <td>OpenACS service account</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td>
Index: openacs-4/packages/acs-core-docs/www/install-steps.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/install-steps.html,v
diff -u -r1.38.2.4 -r1.38.2.5
--- openacs-4/packages/acs-core-docs/www/install-steps.html	3 Sep 2021 09:15:12 -0000	1.38.2.4
+++ openacs-4/packages/acs-core-docs/www/install-steps.html	7 Sep 2021 09:39:29 -0000	1.38.2.5
@@ -44,7 +44,7 @@
 <span class="action"><span class="action">su - $OPENACS_SERVICE_NAME
 svc -d /service/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
 dropdb <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
-createdb <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></span></span></pre><p><a name="cut-and-paste-name-var"></a><b>Setting a global shell variable for cut and paste. </b>In order to cut and paste the instructions into your shell, you must set the environment variable $OPENACS_SERVICE_NAME.  In order to set it globally so that it works for any new users or special service users you may create, edit the file <code class="computeroutput">/etc/profile</code> ( <code class="computeroutput">/etc/share/skel/dot.profile</code> for FreeBSD) and add this line:</p><pre class="programlisting">export OPENACS_SERVICE_NAME=<span class="replaceable"><span class="replaceable">service0</span></span></pre></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665975271024"></a>Paths and Users</h3></div></div></div><div class="table"><a name="idp140665975271664"></a><p class="title"><b>Table 2.1. Default directories for a standard install</b></p><div class="table-contents"><table class="table" summary="Default directories for a standard install" cellspacing="0" width="100%" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Fully qualified domain name of your server</td><td><span class="replaceable"><span class="replaceable">yourserver.test</span></span></td></tr><tr><td>name of administrative access account</td><td>remadmin</td></tr><tr><td>OpenACS service</td><td><a class="indexterm" name="idp140665975292880"></a>
+createdb <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></span></span></pre><p><a name="cut-and-paste-name-var"></a><b>Setting a global shell variable for cut and paste. </b>In order to cut and paste the instructions into your shell, you must set the environment variable $OPENACS_SERVICE_NAME.  In order to set it globally so that it works for any new users or special service users you may create, edit the file <code class="computeroutput">/etc/profile</code> ( <code class="computeroutput">/etc/share/skel/dot.profile</code> for FreeBSD) and add this line:</p><pre class="programlisting">export OPENACS_SERVICE_NAME=<span class="replaceable"><span class="replaceable">service0</span></span></pre></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011826288"></a>Paths and Users</h3></div></div></div><div class="table"><a name="idp140698011826928"></a><p class="title"><b>Table 2.1. Default directories for a standard install</b></p><div class="table-contents"><table class="table" summary="Default directories for a standard install" cellspacing="0" width="100%" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Fully qualified domain name of your server</td><td><span class="replaceable"><span class="replaceable">yourserver.test</span></span></td></tr><tr><td>name of administrative access account</td><td>remadmin</td></tr><tr><td>OpenACS service</td><td><a class="indexterm" name="idp140698011831536"></a>
                 <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span> (set to service0 in default install)</td></tr><tr><td>OpenACS service account</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>OpenACS database name</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>Root of OpenACS service file tree (SERVERROOT)</td><td><span class="replaceable"><span class="replaceable">/var/lib/aolserver/$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>Location of source code tarballs for new software</td><td>/var/tmp</td></tr><tr><td>The OpenACS tarball contains some files which
                 are useful while setting up other software.  Those
                 files are located at:</td><td>/var/tmp/openacs-5.9.0/packages/acs-core-docs/www/files</td></tr><tr><td>Database backup directory</td><td><span class="replaceable"><span class="replaceable">/var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup</span></span></td></tr><tr><td>Service config files</td><td><span class="replaceable"><span class="replaceable">/var/lib/aolserver/$OPENACS_SERVICE_NAME/etc</span></span></td></tr><tr><td>Service log files</td><td><span class="replaceable"><span class="replaceable">/var/lib/aolserver/$OPENACS_SERVICE_NAME/log</span></span></td></tr><tr><td>Compile directory</td><td>/usr/local/src</td></tr><tr><td>PostgreSQL directory</td><td>/usr/local/pgsql</td></tr><tr><td>AOLserver directory</td><td>/usr/local/aolserver</td></tr></tbody></table></div></div><br class="table-break"><p>
Index: openacs-4/packages/acs-core-docs/www/ix01.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/ix01.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/ix01.adp	3 Sep 2021 09:15:12 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/ix01.adp	7 Sep 2021 09:39:29 -0000	1.4.2.6
@@ -8,23 +8,23 @@
 			rightLink="" rightLabel="">
 		    <div class="index">
 <div class="titlepage"><div><div><h1 class="title">
-<a name="idp140665821799696"></a>Index</h1></div></div></div><div xmlns:xlink="http://www.w3.org/1999/xlink" class="index">
+<a name="idp140698004166144"></a>Index</h1></div></div></div><div xmlns:xlink="http://www.w3.org/1999/xlink" class="index">
 <div class="indexdiv">
-<h3>Symbols</h3><dl><dt id="ientry-idp140665975292880">$OPENACS_SERVICE_NAME, <a class="indexterm" href="install-steps">Paths and
+<h3>Symbols</h3><dl><dt id="ientry-idp140698011831536">$OPENACS_SERVICE_NAME, <a class="indexterm" href="install-steps">Paths and
 Users</a>
 </dt></dl>
 </div><div class="indexdiv">
 <h3>A</h3><dl>
-<dt id="ientry-idp140666284873168">AOLserver</dt><dd><dl><dt>configuration, <a class="indexterm" href="openacs">Installation Option 2: Install
+<dt id="ientry-idp140697733683376">AOLserver</dt><dd><dl><dt>configuration, <a class="indexterm" href="openacs">Installation Option 2: Install
 from tarball</a>
-</dt></dl></dd><dt id="ientry-idp140665976138944">Automated tests, <a class="indexterm" href="tutorial-debug">Write
+</dt></dl></dd><dt id="ientry-idp140698012906160">Automated tests, <a class="indexterm" href="tutorial-debug">Write
 automated tests</a>
 </dt>
 </dl>
 </div><div class="indexdiv">
 <h3>C</h3><dl>
-<dt id="ientry-idp140665973829792">computeroutput</dt><dd><dl><dt>code, <a class="indexterm" href="docbook-primer">Code</a>
-</dt></dl></dd><dt id="ientry-idp140665012998304">cvs</dt><dd><dl>
+<dt id="ientry-idp140697733314448">computeroutput</dt><dd><dl><dt>code, <a class="indexterm" href="docbook-primer">Code</a>
+</dt></dl></dd><dt id="ientry-idp140698013677840">cvs</dt><dd><dl>
 <dt>initializing, <a class="indexterm" href="install-cvs">Initialize CVS (OPTIONAL)</a>
 </dt><dt>setup, <a class="indexterm" href="cvs-tips">Using CVS with
 an OpenACS Site</a>
@@ -33,98 +33,98 @@
 </dl>
 </div><div class="indexdiv">
 <h3>D</h3><dl>
-<dt id="ientry-idp140665014872560">daemontools</dt><dd><dl><dt>installation, <a class="indexterm" href="install-daemontools">Install Daemontools (OPTIONAL)</a>
-</dt></dl></dd><dt id="ientry-idp140665823618224">docbook</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
-</dt></dl></dd><dt id="ientry-idp140665014864128">DocBook</dt><dd><dl>
+<dt id="ientry-idp140698013694016">daemontools</dt><dd><dl><dt>installation, <a class="indexterm" href="install-daemontools">Install Daemontools (OPTIONAL)</a>
+</dt></dl></dd><dt id="ientry-idp140697732512496">docbook</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
+</dt></dl></dd><dt id="ientry-idp140698013683680">DocBook</dt><dd><dl>
 <dt>DTD, <a class="indexterm" href="docbook-primer">OpenACS Documentation Strategy:
 Why DocBook?</a>
 </dt><dt>emacs configuration for, <a class="indexterm" href="psgml-for-emacs">Add PSGML commands to emacs init file
 (OPTIONAL)</a>
 </dt>
-</dl></dd><dt id="ientry-idp140665974966240">Document structure, <a class="indexterm" href="docbook-primer">Document
+</dl></dd><dt id="ientry-idp140697733808672">Document structure, <a class="indexterm" href="docbook-primer">Document
 Structure</a>
 </dt>
 </dl>
 </div><div class="indexdiv">
 <h3>E</h3><dl>
-<dt id="ientry-idp140665823470304">emacs</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
-</dt></dl></dd><dt id="ientry-idp140665975427056">emphasis</dt><dd><dl><dt>bold, italics, <a class="indexterm" href="docbook-primer">Emphasis</a>
+<dt id="ientry-idp140697732505680">emacs</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
+</dt></dl></dd><dt id="ientry-idp140697733277648">emphasis</dt><dd><dl><dt>bold, italics, <a class="indexterm" href="docbook-primer">Emphasis</a>
 </dt></dl></dd>
 </dl>
 </div><div class="indexdiv">
 <h3>F</h3><dl>
-<dt id="ientry-idp140665014818544">full text search</dt><dd><dl><dt>installation, <a class="indexterm" href="install-full-text-search-tsearch2">Install
+<dt id="ientry-idp140698013419600">full text search</dt><dd><dl><dt>installation, <a class="indexterm" href="install-full-text-search-tsearch2">Install
 Tsearch2 module</a>
 </dt></dl></dd>
 </dl>
 </div><div class="indexdiv">
 <h3>G</h3><dl>
-<dt id="ientry-idp140665013210416">Graphics</dt><dd><dl><dt>Images, <a class="indexterm" href="docbook-primer">Graphics</a>
+<dt id="ientry-idp140697734233808">Graphics</dt><dd><dl><dt>Images, <a class="indexterm" href="docbook-primer">Graphics</a>
 </dt></dl></dd>
 </dl>
 </div><div class="indexdiv">
 <h3>I</h3><dl>
-<dt id="ientry-idp140665822018848">informaltable</dt><dd><dl><dt>table, <a class="indexterm" href="docbook-primer">Tables</a>
+<dt id="ientry-idp140697734146544">informaltable</dt><dd><dl><dt>table, <a class="indexterm" href="docbook-primer">Tables</a>
 </dt></dl></dd>
 </dl>
 </div><div class="indexdiv">
 <h3>L</h3><dl>
-<dt id="ientry-idp140665823447264">language</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
-</dt></dl></dd><dt id="ientry-idp140665013477248">Linking, <a class="indexterm" href="docbook-primer">Links</a>
-</dt><dt id="ientry-idp140665822475824">lists, <a class="indexterm" href="docbook-primer">Lists</a>
+<dt id="ientry-idp140697732497952">language</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
+</dt></dl></dd><dt id="ientry-idp140697733358768">Linking, <a class="indexterm" href="docbook-primer">Links</a>
+</dt><dt id="ientry-idp140697733926048">lists, <a class="indexterm" href="docbook-primer">Lists</a>
 </dt>
 </dl>
 </div><div class="indexdiv">
-<h3>O</h3><dl><dt id="ientry-idp140665974160992">OpenACS Package, <a class="indexterm" href="packages">What a Package
+<h3>O</h3><dl><dt id="ientry-idp140697732390544">OpenACS Package, <a class="indexterm" href="packages">What a Package
 Looks Like</a>
 </dt></dl>
 </div><div class="indexdiv">
 <h3>P</h3><dl>
-<dt id="ientry-idp140665823311984">photo-album</dt><dd><dl><dt>installation (see ImageMagick)</dt></dl></dd><dt id="ientry-idp140666284857616">Postgres</dt><dd><dl><dt>Vacuuming, <a class="indexterm" href="openacs">Installation Option 2: Install
+<dt id="ientry-idp140697732531104">photo-album</dt><dd><dl><dt>installation (see ImageMagick)</dt></dl></dd><dt id="ientry-idp140697733669392">Postgres</dt><dd><dl><dt>Vacuuming, <a class="indexterm" href="openacs">Installation Option 2: Install
 from tarball</a>
 </dt></dl></dd>
 </dl>
 </div><div class="indexdiv">
 <h3>Q</h3><dl>
-<dt id="ientry-idp140665014925104">qmail</dt><dd><dl><dt>Maildir, <a class="indexterm" href="install-qmail">Install
+<dt id="ientry-idp140698013752576">qmail</dt><dd><dl><dt>Maildir, <a class="indexterm" href="install-qmail">Install
 qmail (OPTIONAL)</a>
 </dt></dl></dd>
 </dl>
 </div><div class="indexdiv">
 <h3>S</h3><dl>
-<dt id="ientry-idp140665823075360">sect1, <a class="indexterm" href="docbook-primer">Headlines,
+<dt id="ientry-idp140697733816128">sect1, <a class="indexterm" href="docbook-primer">Headlines,
 Sections</a>
-</dt><dt id="ientry-idp140665974349840">sect2, <a class="indexterm" href="docbook-primer">Headlines,
+</dt><dt id="ientry-idp140697733370448">sect2, <a class="indexterm" href="docbook-primer">Headlines,
 Sections</a>
-</dt><dt id="ientry-idp140665823877280">Sections</dt><dd><dl><dt>Headlines, <a class="indexterm" href="docbook-primer">Headlines,
+</dt><dt id="ientry-idp140697734129104">Sections</dt><dd><dl><dt>Headlines, <a class="indexterm" href="docbook-primer">Headlines,
 Sections</a>
-</dt></dl></dd><dt id="ientry-idp140665824084384">security</dt><dd><dl>
+</dt></dl></dd><dt id="ientry-idp140697732456080">security</dt><dd><dl>
 <dt>definition, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
 </dt><dt>firewall, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
 </dt>
-</dl></dd><dt id="ientry-idp140665014912016">sendmail</dt><dd><dl><dt>removing, <a class="indexterm" href="install-qmail">Install qmail (OPTIONAL)</a>
-</dt></dl></dd><dt id="ientry-idp140665824155088">ssh, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
+</dl></dd><dt id="ientry-idp140698013738144">sendmail</dt><dd><dl><dt>removing, <a class="indexterm" href="install-qmail">Install qmail (OPTIONAL)</a>
+</dt></dl></dd><dt id="ientry-idp140697732248528">ssh, <a class="indexterm" href="install-redhat">Install Red Hat 8/9</a>
 </dt>
 </dl>
 </div><div class="indexdiv">
-<h3>T</h3><dl><dt id="ientry-idp140665976049392">The publish point for new
+<h3>T</h3><dl><dt id="ientry-idp140697194080608">The publish point for new
 packages should be fixed., <a class="indexterm" href="tutorial-distribute">Prepare the package for
 distribution.</a>
 </dt></dl>
 </div><div class="indexdiv">
 <h3>U</h3><dl>
-<dt id="ientry-idp140665822702832">ulink, <a class="indexterm" href="docbook-primer">Links</a>
-</dt><dt id="ientry-idp140666101895040">upgrade</dt><dd><dl>
+<dt id="ientry-idp140697733436384">ulink, <a class="indexterm" href="docbook-primer">Links</a>
+</dt><dt id="ientry-idp140698012076496">upgrade</dt><dd><dl>
 <dt>OpenACS 4.5 to 4.6.x</dt><dd><dl><dt>Linux/Unix, <a class="indexterm" href="upgrade-4.5-to-4.6">Upgrading 4.5 or higher to 4.6.3</a>
 </dt></dl></dd>
 </dl></dd>
 </dl>
 </div><div class="indexdiv">
 <h3>X</h3><dl>
-<dt id="ientry-idp140665975637728">XML guidelines, <a class="indexterm" href="docbook-primer">OpenACS
+<dt id="ientry-idp140697734146944">XML guidelines, <a class="indexterm" href="docbook-primer">OpenACS
 Documentation Strategy: Why DocBook?</a>
-</dt><dt id="ientry-idp140665824170144">xref</dt><dd><dl><dt>linkend, <a class="indexterm" href="docbook-primer">Links</a>
-</dt></dl></dd><dt id="ientry-idp140665822752272">xreflabel, <a class="indexterm" href="docbook-primer">Headlines,
+</dt><dt id="ientry-idp140697733362368">xref</dt><dd><dl><dt>linkend, <a class="indexterm" href="docbook-primer">Links</a>
+</dt></dl></dd><dt id="ientry-idp140697733366080">xreflabel, <a class="indexterm" href="docbook-primer">Headlines,
 Sections</a>
 </dt>
 </dl>
Index: openacs-4/packages/acs-core-docs/www/ix01.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/ix01.html,v
diff -u -r1.32.2.4 -r1.32.2.5
--- openacs-4/packages/acs-core-docs/www/ix01.html	3 Sep 2021 09:15:15 -0000	1.32.2.4
+++ openacs-4/packages/acs-core-docs/www/ix01.html	7 Sep 2021 09:39:29 -0000	1.32.2.5
@@ -1,3 +1,3 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Index</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="index.html" title="OpenACS Core Documentation"><link rel="previous" href="update-translations.html" title="How to Update the translations"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="update-translations.html">Prev</a> </td><th width="60%" align="center"></th><td width="20%" align="right"> </td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h1 class="title"><a name="idp140665821799696"></a>Index</h1></div></div></div><div xmlns:xlink="http://www.w3.org/1999/xlink" class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt id="ientry-idp140665975292880">$OPENACS_SERVICE_NAME, <a class="indexterm" href="install-steps.html#idp140665975271024">Paths and Users</a></dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt id="ientry-idp140666284873168">AOLserver</dt><dd><dl><dt>configuration, <a class="indexterm" href="openacs.html#install-from-tarball">Installation Option 2: Install from tarball</a></dt></dl></dd><dt id="ientry-idp140665976138944">Automated tests, <a class="indexterm" href="tutorial-debug.html#idp140665976136896">Write automated tests</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt id="ientry-idp140665973829792">computeroutput</dt><dd><dl><dt>code, <a class="indexterm" href="docbook-primer.html#dbprimer-code">Code</a></dt></dl></dd><dt id="ientry-idp140665012998304">cvs</dt><dd><dl><dt>initializing, <a class="indexterm" href="install-cvs.html">Initialize CVS (OPTIONAL)</a></dt><dt>setup, <a class="indexterm" href="cvs-tips.html">Using CVS with an OpenACS Site</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>D</h3><dl><dt id="ientry-idp140665014872560">daemontools</dt><dd><dl><dt>installation, <a class="indexterm" href="install-daemontools.html">Install Daemontools (OPTIONAL)</a></dt></dl></dd><dt id="ientry-idp140665823618224">docbook</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></dd><dt id="ientry-idp140665014864128">DocBook</dt><dd><dl><dt>DTD, <a class="indexterm" href="docbook-primer.html#dbprimer-why">OpenACS Documentation Strategy: Why DocBook?</a></dt><dt>emacs configuration for, <a class="indexterm" href="psgml-for-emacs.html">Add PSGML commands to emacs init file (OPTIONAL)</a></dt></dl></dd><dt id="ientry-idp140665974966240">Document structure, <a class="indexterm" href="docbook-primer.html#dbprimer-structure">Document Structure</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt id="ientry-idp140665823470304">emacs</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></dd><dt id="ientry-idp140665975427056">emphasis</dt><dd><dl><dt>bold, italics, <a class="indexterm" href="docbook-primer.html#dbprimer-emphasis">Emphasis</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>F</h3><dl><dt id="ientry-idp140665014818544">full text search</dt><dd><dl><dt>installation, <a class="indexterm" href="install-full-text-search-tsearch2.html#install-tsearch2">Install Tsearch2 module</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>G</h3><dl><dt id="ientry-idp140665013210416">Graphics</dt><dd><dl><dt>Images, <a class="indexterm" href="docbook-primer.html#dbprimer-graphics">Graphics</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>I</h3><dl><dt id="ientry-idp140665822018848">informaltable</dt><dd><dl><dt>table, <a class="indexterm" href="docbook-primer.html#dbprimer-tables">Tables</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt id="ientry-idp140665823447264">language</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></dd><dt id="ientry-idp140665013477248">Linking, <a class="indexterm" href="docbook-primer.html#dbprimer-links">Links</a></dt><dt id="ientry-idp140665822475824">lists, <a class="indexterm" href="docbook-primer.html#dbprimer-lists">Lists</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt id="ientry-idp140665974160992">OpenACS Package, <a class="indexterm" href="packages.html#packages-looks">What a Package Looks Like</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt id="ientry-idp140665823311984">photo-album</dt><dd><dl><dt>installation (see ImageMagick)</dt></dl></dd><dt id="ientry-idp140666284857616">Postgres</dt><dd><dl><dt>Vacuuming, <a class="indexterm" href="openacs.html#install-from-tarball">Installation Option 2: Install from tarball</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt id="ientry-idp140665014925104">qmail</dt><dd><dl><dt>Maildir, <a class="indexterm" href="install-qmail.html">Install qmail (OPTIONAL)</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>S</h3><dl><dt id="ientry-idp140665823075360">sect1, <a class="indexterm" href="docbook-primer.html#dbprimer-sections">Headlines, Sections</a></dt><dt id="ientry-idp140665974349840">sect2, <a class="indexterm" href="docbook-primer.html#dbprimer-sections">Headlines, Sections</a></dt><dt id="ientry-idp140665823877280">Sections</dt><dd><dl><dt>Headlines, <a class="indexterm" href="docbook-primer.html#dbprimer-sections">Headlines, Sections</a></dt></dl></dd><dt id="ientry-idp140665824084384">security</dt><dd><dl><dt>definition, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt><dt>firewall, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></dd><dt id="ientry-idp140665014912016">sendmail</dt><dd><dl><dt>removing, <a class="indexterm" href="install-qmail.html">Install qmail (OPTIONAL)</a></dt></dl></dd><dt id="ientry-idp140665824155088">ssh, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt id="ientry-idp140665976049392">The publish point for new packages should be
-        fixed., <a class="indexterm" href="tutorial-distribute.html">Prepare the package for distribution.</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt id="ientry-idp140665822702832">ulink, <a class="indexterm" href="docbook-primer.html#dbprimer-links">Links</a></dt><dt id="ientry-idp140666101895040">upgrade</dt><dd><dl><dt>OpenACS 4.5 to 4.6.x</dt><dd><dl><dt>Linux/Unix, <a class="indexterm" href="upgrade-4.5-to-4.6.html">Upgrading 4.5 or higher to 4.6.3</a></dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>X</h3><dl><dt id="ientry-idp140665975637728">XML guidelines, <a class="indexterm" href="docbook-primer.html#dbprimer-why">OpenACS Documentation Strategy: Why DocBook?</a></dt><dt id="ientry-idp140665824170144">xref</dt><dd><dl><dt>linkend, <a class="indexterm" href="docbook-primer.html#dbprimer-links">Links</a></dt></dl></dd><dt id="ientry-idp140665822752272">xreflabel, <a class="indexterm" href="docbook-primer.html#dbprimer-sections">Headlines, Sections</a></dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="update-translations.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left">How to Update the translations </td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"> </td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Index</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="index.html" title="OpenACS Core Documentation"><link rel="previous" href="update-translations.html" title="How to Update the translations"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="update-translations.html">Prev</a> </td><th width="60%" align="center"></th><td width="20%" align="right"> </td></tr></table><hr></div><div class="index"><div class="titlepage"><div><div><h1 class="title"><a name="idp140698004166144"></a>Index</h1></div></div></div><div xmlns:xlink="http://www.w3.org/1999/xlink" class="index"><div class="indexdiv"><h3>Symbols</h3><dl><dt id="ientry-idp140698011831536">$OPENACS_SERVICE_NAME, <a class="indexterm" href="install-steps.html#idp140698011826288">Paths and Users</a></dt></dl></div><div class="indexdiv"><h3>A</h3><dl><dt id="ientry-idp140697733683376">AOLserver</dt><dd><dl><dt>configuration, <a class="indexterm" href="openacs.html#install-from-tarball">Installation Option 2: Install from tarball</a></dt></dl></dd><dt id="ientry-idp140698012906160">Automated tests, <a class="indexterm" href="tutorial-debug.html#idp140698012904112">Write automated tests</a></dt></dl></div><div class="indexdiv"><h3>C</h3><dl><dt id="ientry-idp140697733314448">computeroutput</dt><dd><dl><dt>code, <a class="indexterm" href="docbook-primer.html#dbprimer-code">Code</a></dt></dl></dd><dt id="ientry-idp140698013677840">cvs</dt><dd><dl><dt>initializing, <a class="indexterm" href="install-cvs.html">Initialize CVS (OPTIONAL)</a></dt><dt>setup, <a class="indexterm" href="cvs-tips.html">Using CVS with an OpenACS Site</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>D</h3><dl><dt id="ientry-idp140698013694016">daemontools</dt><dd><dl><dt>installation, <a class="indexterm" href="install-daemontools.html">Install Daemontools (OPTIONAL)</a></dt></dl></dd><dt id="ientry-idp140697732512496">docbook</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></dd><dt id="ientry-idp140698013683680">DocBook</dt><dd><dl><dt>DTD, <a class="indexterm" href="docbook-primer.html#dbprimer-why">OpenACS Documentation Strategy: Why DocBook?</a></dt><dt>emacs configuration for, <a class="indexterm" href="psgml-for-emacs.html">Add PSGML commands to emacs init file (OPTIONAL)</a></dt></dl></dd><dt id="ientry-idp140697733808672">Document structure, <a class="indexterm" href="docbook-primer.html#dbprimer-structure">Document Structure</a></dt></dl></div><div class="indexdiv"><h3>E</h3><dl><dt id="ientry-idp140697732505680">emacs</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></dd><dt id="ientry-idp140697733277648">emphasis</dt><dd><dl><dt>bold, italics, <a class="indexterm" href="docbook-primer.html#dbprimer-emphasis">Emphasis</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>F</h3><dl><dt id="ientry-idp140698013419600">full text search</dt><dd><dl><dt>installation, <a class="indexterm" href="install-full-text-search-tsearch2.html#install-tsearch2">Install Tsearch2 module</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>G</h3><dl><dt id="ientry-idp140697734233808">Graphics</dt><dd><dl><dt>Images, <a class="indexterm" href="docbook-primer.html#dbprimer-graphics">Graphics</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>I</h3><dl><dt id="ientry-idp140697734146544">informaltable</dt><dd><dl><dt>table, <a class="indexterm" href="docbook-primer.html#dbprimer-tables">Tables</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>L</h3><dl><dt id="ientry-idp140697732497952">language</dt><dd><dl><dt>installation, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></dd><dt id="ientry-idp140697733358768">Linking, <a class="indexterm" href="docbook-primer.html#dbprimer-links">Links</a></dt><dt id="ientry-idp140697733926048">lists, <a class="indexterm" href="docbook-primer.html#dbprimer-lists">Lists</a></dt></dl></div><div class="indexdiv"><h3>O</h3><dl><dt id="ientry-idp140697732390544">OpenACS Package, <a class="indexterm" href="packages.html#packages-looks">What a Package Looks Like</a></dt></dl></div><div class="indexdiv"><h3>P</h3><dl><dt id="ientry-idp140697732531104">photo-album</dt><dd><dl><dt>installation (see ImageMagick)</dt></dl></dd><dt id="ientry-idp140697733669392">Postgres</dt><dd><dl><dt>Vacuuming, <a class="indexterm" href="openacs.html#install-from-tarball">Installation Option 2: Install from tarball</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>Q</h3><dl><dt id="ientry-idp140698013752576">qmail</dt><dd><dl><dt>Maildir, <a class="indexterm" href="install-qmail.html">Install qmail (OPTIONAL)</a></dt></dl></dd></dl></div><div class="indexdiv"><h3>S</h3><dl><dt id="ientry-idp140697733816128">sect1, <a class="indexterm" href="docbook-primer.html#dbprimer-sections">Headlines, Sections</a></dt><dt id="ientry-idp140697733370448">sect2, <a class="indexterm" href="docbook-primer.html#dbprimer-sections">Headlines, Sections</a></dt><dt id="ientry-idp140697734129104">Sections</dt><dd><dl><dt>Headlines, <a class="indexterm" href="docbook-primer.html#dbprimer-sections">Headlines, Sections</a></dt></dl></dd><dt id="ientry-idp140697732456080">security</dt><dd><dl><dt>definition, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt><dt>firewall, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></dd><dt id="ientry-idp140698013738144">sendmail</dt><dd><dl><dt>removing, <a class="indexterm" href="install-qmail.html">Install qmail (OPTIONAL)</a></dt></dl></dd><dt id="ientry-idp140697732248528">ssh, <a class="indexterm" href="install-redhat.html">Install Red Hat 8/9</a></dt></dl></div><div class="indexdiv"><h3>T</h3><dl><dt id="ientry-idp140697194080608">The publish point for new packages should be
+        fixed., <a class="indexterm" href="tutorial-distribute.html">Prepare the package for distribution.</a></dt></dl></div><div class="indexdiv"><h3>U</h3><dl><dt id="ientry-idp140697733436384">ulink, <a class="indexterm" href="docbook-primer.html#dbprimer-links">Links</a></dt><dt id="ientry-idp140698012076496">upgrade</dt><dd><dl><dt>OpenACS 4.5 to 4.6.x</dt><dd><dl><dt>Linux/Unix, <a class="indexterm" href="upgrade-4.5-to-4.6.html">Upgrading 4.5 or higher to 4.6.3</a></dt></dl></dd></dl></dd></dl></div><div class="indexdiv"><h3>X</h3><dl><dt id="ientry-idp140697734146944">XML guidelines, <a class="indexterm" href="docbook-primer.html#dbprimer-why">OpenACS Documentation Strategy: Why DocBook?</a></dt><dt id="ientry-idp140697733362368">xref</dt><dd><dl><dt>linkend, <a class="indexterm" href="docbook-primer.html#dbprimer-links">Links</a></dt></dl></dd><dt id="ientry-idp140697733366080">xreflabel, <a class="indexterm" href="docbook-primer.html#dbprimer-sections">Headlines, Sections</a></dt></dl></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="update-translations.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> </td></tr><tr><td width="40%" align="left">How to Update the translations </td><td width="20%" align="center"><a accesskey="u" href="index.html">Up</a></td><td width="40%" align="right"> </td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/maint-performance.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/maint-performance.adp,v
diff -u -r1.4.2.6 -r1.4.2.7
--- openacs-4/packages/acs-core-docs/www/maint-performance.adp	3 Sep 2021 09:15:16 -0000	1.4.2.6
+++ openacs-4/packages/acs-core-docs/www/maint-performance.adp	7 Sep 2021 09:39:30 -0000	1.4.2.7
@@ -31,7 +31,7 @@
 <p>This should return a list of database queries on the page,
 including the exact query (so it can be cut-paste into psql or
 oracle) and the time each query took.</p><div class="figure">
-<a name="idp140665012847216" id="idp140665012847216"></a><p class="title"><strong>Figure 6.8. Query Analysis
+<a name="idp140698012091248" id="idp140698012091248"></a><p class="title"><strong>Figure 6.8. Query Analysis
 example</strong></p><div class="figure-contents"><div class="mediaobject"><img src="images/query-duration.png" alt="Query Analysis example"></div></div>
 </div><br class="figure-break">
 </li>
@@ -109,7 +109,7 @@
 query, install "autotrace". I usually follow the
 instructions here <a class="ulink" href="http://asktom.oracle.com/~tkyte/article1/autotrace.html" target="_top">http://asktom.oracle.com/~tkyte/article1/autotrace.html</a>.</p><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665012870256" id="idp140665012870256"></a>Make sure that the Oracle CBO works with
+<a name="idp140698011620352" id="idp140698011620352"></a>Make sure that the Oracle CBO works with
 adequate statistics</h4></div></div></div><p>The Oracle Cost Based optimizer is a piece of software that
 tries to find the "optimal" execution plan for a given
 SQL statement. For that it estimates the costs of running a SQL
Index: openacs-4/packages/acs-core-docs/www/maint-performance.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/maint-performance.html,v
diff -u -r1.32.2.4 -r1.32.2.5
--- openacs-4/packages/acs-core-docs/www/maint-performance.html	3 Sep 2021 09:15:16 -0000	1.32.2.4
+++ openacs-4/packages/acs-core-docs/www/maint-performance.html	7 Sep 2021 09:39:30 -0000	1.32.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Diagnosing Performance Problems</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="maintenance-web.html" title="Chapter 6. Production Environments"><link rel="previous" href="uptime.html" title="External uptime validation"><link rel="next" href="database-management.html" title="Chapter 7. Database Management"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="uptime.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Production Environments</th><td width="20%" align="right"> <a accesskey="n" href="database-management.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="maint-performance"></a>Diagnosing Performance Problems</h2></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Did performance problems happen overnight, or did they sneak up on
     you? Any clue what caused the performance problems (e.g. loading 20K
     users into .LRN)</p></li><li class="listitem"><p>Is the filesystem out of space?  Is the machine swapping to disk constantly?</p></li><li class="listitem"><p>Isolating and solving database problems.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>Without daily internal maintenance, most databases slowly degrade in performance.  For PostGreSQL, see <a class="xref" href="install-next-nightly-vacuum.html" title="Vacuum Postgres nightly">the section called “Vacuum Postgres nightly”</a>.  For Oracle, use <code class="computeroutput">exec dbms_stats.gather_schema_stats('SCHEMA_NAME')</code> (<a class="ulink" href="http://www.piskorski.com/docs/oracle.html" target="_top">Andrew Piskorski's Oracle notes</a>).</p></li><li class="listitem"><p>You can track the exact amount of time each database query on a page takes:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Go to <a class="ulink" href="/acs-admin/install" target="_top">Main Site : Site-Wide Administration : Install Software</a></p></li><li class="listitem"><p>Click on "Install New Application" in "Install from OpenACS Repository"</p></li><li class="listitem"><p>Choose "ACS Developer Support"&gt;</p></li><li class="listitem"><p>After install is complete, restart the server.</p></li><li class="listitem"><p>Browse to Developer Support, which is automatically mounted at <code class="computeroutput"><a class="ulink" href="/ds" target="_top">/ds</a></code>.
-              </p></li><li class="listitem"><p>Turn on Database statistics</p></li><li class="listitem"><p>Browse directly to a slow page and click "Request Information" at the bottom of the page.</p></li><li class="listitem"><p>This should return a list of database queries on the page, including the exact query (so it can be cut-paste into psql or oracle) and the time each query took.</p><div class="figure"><a name="idp140665012847216"></a><p class="title"><b>Figure 6.8. Query Analysis example</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/query-duration.png" alt="Query Analysis example"></div></div></div><br class="figure-break"></li></ol></div></li><li class="listitem"><p>Identify a runaway Oracle query: first, use <strong class="userinput"><code>ps aux</code></strong> or <strong class="userinput"><code>top</code></strong> to get the UNIX process ID of a runaway Oracle process.</p><p>Log in to SQL*Plus as the admin:</p><pre class="screen">[<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span> ~]$ svrmgrl
+              </p></li><li class="listitem"><p>Turn on Database statistics</p></li><li class="listitem"><p>Browse directly to a slow page and click "Request Information" at the bottom of the page.</p></li><li class="listitem"><p>This should return a list of database queries on the page, including the exact query (so it can be cut-paste into psql or oracle) and the time each query took.</p><div class="figure"><a name="idp140698012091248"></a><p class="title"><b>Figure 6.8. Query Analysis example</b></p><div class="figure-contents"><div class="mediaobject"><img src="images/query-duration.png" alt="Query Analysis example"></div></div></div><br class="figure-break"></li></ol></div></li><li class="listitem"><p>Identify a runaway Oracle query: first, use <strong class="userinput"><code>ps aux</code></strong> or <strong class="userinput"><code>top</code></strong> to get the UNIX process ID of a runaway Oracle process.</p><p>Log in to SQL*Plus as the admin:</p><pre class="screen">[<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span> ~]$ svrmgrl
 
 Oracle Server Manager Release 3.1.7.0.0 - Production
 
@@ -59,7 +59,7 @@
     </p><p>
       To be able to get a overview of how Oracle executes a particular query,
       install "autotrace". I usually follow the instructions here <a class="ulink" href="http://asktom.oracle.com/~tkyte/article1/autotrace.html" target="_top">http://asktom.oracle.com/~tkyte/article1/autotrace.html</a>.
-    </p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665012870256"></a>Make sure that the Oracle CBO works with adequate statistics</h4></div></div></div><p>
+    </p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698011620352"></a>Make sure that the Oracle CBO works with adequate statistics</h4></div></div></div><p>
     The Oracle Cost Based optimizer is a piece of software that tries to find
     the "optimal" execution plan for a given SQL statement. For that it
     estimates the costs of running a SQL query in a particular way (by default
Index: openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp,v
diff -u -r1.5.2.6 -r1.5.2.7
--- openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp	3 Sep 2021 09:15:17 -0000	1.5.2.6
+++ openacs-4/packages/acs-core-docs/www/maintenance-deploy.adp	7 Sep 2021 09:39:30 -0000	1.5.2.7
@@ -24,7 +24,7 @@
 working configuration safely and quickly.</p></li>
 </ul></div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665012748352" id="idp140665012748352"></a>Method 1: Deployment with CVS</h3></div></div></div><p>With this method, we control the files on a site via CVS. This
+<a name="idp140698011212064" id="idp140698011212064"></a>Method 1: Deployment with CVS</h3></div></div></div><p>With this method, we control the files on a site via CVS. This
 example uses one developmental server (service0-dev) and one
 production server (service0). Depending on your needs, you can also
 have a staging server for extensive testing before you go live. The
@@ -102,7 +102,7 @@
 tags to follow ...</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665012760400" id="idp140665012760400"></a>Method 2: A/B Deployment</h3></div></div></div><p>The approach taken in this section is to always create a new
+<a name="idp140698011675136" id="idp140698011675136"></a>Method 2: A/B Deployment</h3></div></div></div><p>The approach taken in this section is to always create a new
 service with the desired changes, running in parallel with the
 existing site. This guarantees control, at least at the final step
 of the process: you know what changes you are about to make because
@@ -118,28 +118,28 @@
 risk losing data in the shuffle. It also requires extra steps if
 the database will be affected.</p><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665012762816" id="idp140665012762816"></a>Simple A/B Deployment: Database is not
+<a name="idp140698011402304" id="idp140698011402304"></a>Simple A/B Deployment: Database is not
 changed</h4></div></div></div><div class="figure">
-<a name="idp140665012763456" id="idp140665012763456"></a><p class="title"><strong>Figure 6.2. Simple A/B
+<a name="idp140698011372192" id="idp140698011372192"></a><p class="title"><strong>Figure 6.2. Simple A/B
 Deployment - Step 1</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-1.png" align="middle" alt="Simple A/B Deployment - Step 1"></div></div>
 </div><br class="figure-break"><div class="figure">
-<a name="idp140665012766144" id="idp140665012766144"></a><p class="title"><strong>Figure 6.3. Simple A/B
+<a name="idp140698012110512" id="idp140698012110512"></a><p class="title"><strong>Figure 6.3. Simple A/B
 Deployment - Step 2</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-2.png" align="middle" alt="Simple A/B Deployment - Step 2"></div></div>
 </div><br class="figure-break"><div class="figure">
-<a name="idp140665012768832" id="idp140665012768832"></a><p class="title"><strong>Figure 6.4. Simple A/B
+<a name="idp140698011944736" id="idp140698011944736"></a><p class="title"><strong>Figure 6.4. Simple A/B
 Deployment - Step 3</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-3.png" align="middle" alt="Simple A/B Deployment - Step 3"></div></div>
 </div><br class="figure-break">
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665012771648" id="idp140665012771648"></a>Complex A/B Deployment: Database is
+<a name="idp140698011361152" id="idp140698011361152"></a>Complex A/B Deployment: Database is
 changed</h4></div></div></div><div class="figure">
-<a name="idp140665012772288" id="idp140665012772288"></a><p class="title"><strong>Figure 6.5. Complex A/B
+<a name="idp140698011292048" id="idp140698011292048"></a><p class="title"><strong>Figure 6.5. Complex A/B
 Deployment - Step 1</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-1.png" align="middle" alt="Complex A/B Deployment - Step 1"></div></div>
 </div><br class="figure-break"><div class="figure">
-<a name="idp140665012774976" id="idp140665012774976"></a><p class="title"><strong>Figure 6.6. Complex A/B
+<a name="idp140698011388480" id="idp140698011388480"></a><p class="title"><strong>Figure 6.6. Complex A/B
 Deployment - Step 2</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-2.png" align="middle" alt="Complex A/B Deployment - Step 2"></div></div>
 </div><br class="figure-break"><div class="figure">
-<a name="idp140665012777664" id="idp140665012777664"></a><p class="title"><strong>Figure 6.7. Complex A/B
+<a name="idp140698011335488" id="idp140698011335488"></a><p class="title"><strong>Figure 6.7. Complex A/B
 Deployment - Step 3</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-3.png" align="middle" alt="Complex A/B Deployment - Step 3"></div></div>
 </div><br class="figure-break">
 </div>
Index: openacs-4/packages/acs-core-docs/www/maintenance-deploy.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/maintenance-deploy.html,v
diff -u -r1.28.2.4 -r1.28.2.5
--- openacs-4/packages/acs-core-docs/www/maintenance-deploy.html	3 Sep 2021 09:15:17 -0000	1.28.2.4
+++ openacs-4/packages/acs-core-docs/www/maintenance-deploy.html	7 Sep 2021 09:39:30 -0000	1.28.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Staged Deployment for Production Networks</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="maintenance-web.html" title="Chapter 6. Production Environments"><link rel="previous" href="high-avail.html" title="High Availability/High Performance Configurations"><link rel="next" href="install-ssl.html" title="Installing SSL Support for an OpenACS service"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="high-avail.html">Prev</a> </td><th width="60%" align="center">Chapter 6. Production Environments</th><td width="20%" align="right"> <a accesskey="n" href="install-ssl.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="maintenance-deploy"></a>Staged Deployment for Production Networks</h2></div></div></div><div class="authorblurb"><div class="cvstag">($Id$)</div><p>By <a class="ulink" href="mailto:joel@aufrecht.org" target="_top">Joel Aufrecht</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><p>This section describes two minimal-risk methods for deploying changes on a production network.  The important characteristics of a safe change deployment include:  (THIS SECTION IN DEVELOPMENT)</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Control: You know for sure that the change you are making is the change that you intend to make and is the change that you tested.</p></li><li class="listitem"><p>Rollback: If anything goes wrong, you can return to the previous working configuration safely and quickly.</p></li></ul></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665012748352"></a>Method 1: Deployment with CVS</h3></div></div></div><p>With this method, we control the files on a site via
+        </div><p>This section describes two minimal-risk methods for deploying changes on a production network.  The important characteristics of a safe change deployment include:  (THIS SECTION IN DEVELOPMENT)</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Control: You know for sure that the change you are making is the change that you intend to make and is the change that you tested.</p></li><li class="listitem"><p>Rollback: If anything goes wrong, you can return to the previous working configuration safely and quickly.</p></li></ul></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011212064"></a>Method 1: Deployment with CVS</h3></div></div></div><p>With this method, we control the files on a site via
       CVS. This example uses one developmental server (service0-dev) and one
       production server (service0). Depending on your needs, you can also
       have a staging server for extensive testing before you go
@@ -67,4 +67,4 @@
 cvs up -Pd index.adp</pre><p>If you make changes that require changes to the database,
       test them out first on service0-dev, using either -create.sql or
       upgrade scripts. Once you've tested them, you then update and
-      run the upgrade scripts from the package manager. </p><p>The production site can run "HEAD" from cvs.</p><p>The drawback to using HEAD as the live code is that you cannot commit new work on the development server without erasing the definition of 'working production code.'  So a better method is to use a tag.  This guarantees that, at any time in the future, you can retrieve exactly the same set of code.  This is useful for both of the characteristics of safe change deployment.  For control, you can use tags to define a body of code, test that code, and then know that what you are deploying is exactly that code.  For rollback, you can use return to the last working tag if the new tag (or new, untagged changes) cause problems.  .... example of using tags to follow ...</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665012760400"></a>Method 2: A/B Deployment</h3></div></div></div><p>The approach taken in this section is to always create a new service with the desired changes, running in parallel with the existing site.  This guarantees control, at least at the final step of the process: you know what changes you are about to make because you can see them directly.  It does not, by itself, guarantee the entire control chain.  You need additional measures to make sure that the change you are making is exactly and completely the change you intended to make and tested previously, and nothing more.  Those additional measures typically take the form of source control tags and system version numbers.  The parallel-server approach also guarantees rollback because the original working service is not touched; it is merely set aside.</p><p>This approach can has limitations.  If the database or filesystem regularly receiving new data, you must interrupt this function or risk losing data in the shuffle.  It also requires extra steps if the database will be affected.</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665012762816"></a>Simple A/B Deployment: Database is not changed</h4></div></div></div><div class="figure"><a name="idp140665012763456"></a><p class="title"><b>Figure 6.2. Simple A/B Deployment - Step 1</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-1.png" align="middle" alt="Simple A/B Deployment - Step 1"></div></div></div><br class="figure-break"><div class="figure"><a name="idp140665012766144"></a><p class="title"><b>Figure 6.3. Simple A/B Deployment - Step 2</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-2.png" align="middle" alt="Simple A/B Deployment - Step 2"></div></div></div><br class="figure-break"><div class="figure"><a name="idp140665012768832"></a><p class="title"><b>Figure 6.4. Simple A/B Deployment - Step 3</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-3.png" align="middle" alt="Simple A/B Deployment - Step 3"></div></div></div><br class="figure-break"></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665012771648"></a>Complex A/B Deployment: Database is changed</h4></div></div></div><div class="figure"><a name="idp140665012772288"></a><p class="title"><b>Figure 6.5. Complex A/B Deployment - Step 1</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-1.png" align="middle" alt="Complex A/B Deployment - Step 1"></div></div></div><br class="figure-break"><div class="figure"><a name="idp140665012774976"></a><p class="title"><b>Figure 6.6. Complex A/B Deployment - Step 2</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-2.png" align="middle" alt="Complex A/B Deployment - Step 2"></div></div></div><br class="figure-break"><div class="figure"><a name="idp140665012777664"></a><p class="title"><b>Figure 6.7. Complex A/B Deployment - Step 3</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-3.png" align="middle" alt="Complex A/B Deployment - Step 3"></div></div></div><br class="figure-break"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="high-avail.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="install-ssl.html">Next</a></td></tr><tr><td width="40%" align="left">High Availability/High Performance Configurations </td><td width="20%" align="center"><a accesskey="u" href="maintenance-web.html">Up</a></td><td width="40%" align="right"> Installing SSL Support for an OpenACS service</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
+      run the upgrade scripts from the package manager. </p><p>The production site can run "HEAD" from cvs.</p><p>The drawback to using HEAD as the live code is that you cannot commit new work on the development server without erasing the definition of 'working production code.'  So a better method is to use a tag.  This guarantees that, at any time in the future, you can retrieve exactly the same set of code.  This is useful for both of the characteristics of safe change deployment.  For control, you can use tags to define a body of code, test that code, and then know that what you are deploying is exactly that code.  For rollback, you can use return to the last working tag if the new tag (or new, untagged changes) cause problems.  .... example of using tags to follow ...</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011675136"></a>Method 2: A/B Deployment</h3></div></div></div><p>The approach taken in this section is to always create a new service with the desired changes, running in parallel with the existing site.  This guarantees control, at least at the final step of the process: you know what changes you are about to make because you can see them directly.  It does not, by itself, guarantee the entire control chain.  You need additional measures to make sure that the change you are making is exactly and completely the change you intended to make and tested previously, and nothing more.  Those additional measures typically take the form of source control tags and system version numbers.  The parallel-server approach also guarantees rollback because the original working service is not touched; it is merely set aside.</p><p>This approach can has limitations.  If the database or filesystem regularly receiving new data, you must interrupt this function or risk losing data in the shuffle.  It also requires extra steps if the database will be affected.</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698011402304"></a>Simple A/B Deployment: Database is not changed</h4></div></div></div><div class="figure"><a name="idp140698011372192"></a><p class="title"><b>Figure 6.2. Simple A/B Deployment - Step 1</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-1.png" align="middle" alt="Simple A/B Deployment - Step 1"></div></div></div><br class="figure-break"><div class="figure"><a name="idp140698012110512"></a><p class="title"><b>Figure 6.3. Simple A/B Deployment - Step 2</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-2.png" align="middle" alt="Simple A/B Deployment - Step 2"></div></div></div><br class="figure-break"><div class="figure"><a name="idp140698011944736"></a><p class="title"><b>Figure 6.4. Simple A/B Deployment - Step 3</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/simple-deploy-3.png" align="middle" alt="Simple A/B Deployment - Step 3"></div></div></div><br class="figure-break"></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698011361152"></a>Complex A/B Deployment: Database is changed</h4></div></div></div><div class="figure"><a name="idp140698011292048"></a><p class="title"><b>Figure 6.5. Complex A/B Deployment - Step 1</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-1.png" align="middle" alt="Complex A/B Deployment - Step 1"></div></div></div><br class="figure-break"><div class="figure"><a name="idp140698011388480"></a><p class="title"><b>Figure 6.6. Complex A/B Deployment - Step 2</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-2.png" align="middle" alt="Complex A/B Deployment - Step 2"></div></div></div><br class="figure-break"><div class="figure"><a name="idp140698011335488"></a><p class="title"><b>Figure 6.7. Complex A/B Deployment - Step 3</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/complex-deploy-3.png" align="middle" alt="Complex A/B Deployment - Step 3"></div></div></div><br class="figure-break"></div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="high-avail.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="install-ssl.html">Next</a></td></tr><tr><td width="40%" align="left">High Availability/High Performance Configurations </td><td width="20%" align="center"><a accesskey="u" href="maintenance-web.html">Up</a></td><td width="40%" align="right"> Installing SSL Support for an OpenACS service</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/objects.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/objects.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/objects.adp	3 Sep 2021 09:15:19 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/objects.adp	7 Sep 2021 09:39:30 -0000	1.4.2.6
@@ -86,7 +86,7 @@
 for the PG version) file created when we <a class="link" href="packages" title="OpenACS Packages">created the package</a>.
 Then, do the following:</p><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665012950704" id="idp140665012950704"></a>Describe the new type to the type
+<a name="idp140697463173936" id="idp140697463173936"></a>Describe the new type to the type
 system</h4></div></div></div><p>First, add an entry to the <code class="computeroutput">acs_object_types</code> table with the following
 PL/SQL call:</p><pre class="programlisting">
 begin  
@@ -142,7 +142,7 @@
 attributes, so there is no need for us to define them.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665012885408" id="idp140665012885408"></a>Define a table in which to store your
+<a name="idp140697463186624" id="idp140697463186624"></a>Define a table in which to store your
 objects</h4></div></div></div><p>The next thing we do is make a small modification to the data
 model to reflect the fact that each row in the <code class="computeroutput">notes</code> table represents something that is
 not only an object of type <code class="computeroutput">note</code>, but also an <code class="computeroutput">acs_object</code>. The new table definition looks
@@ -166,7 +166,7 @@
 <code class="computeroutput">acs_objects</code>.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665012933376" id="idp140665012933376"></a>Define a package for type specific
+<a name="idp140697463196912" id="idp140697463196912"></a>Define a package for type specific
 procedures</h4></div></div></div><p>The next step is to define a PL/SQL package for your new type,
 and write some basic procedures to create and delete objects. Here
 is a package definition for our new type:</p><pre class="programlisting">
@@ -213,7 +213,7 @@
 only" by default. We&#39;ll talk about this more later.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665012941088" id="idp140665012941088"></a>Define a package body for type specific
+<a name="idp140697194275104" id="idp140697194275104"></a>Define a package body for type specific
 procedures</h4></div></div></div><p>The PL/SQL package body contains the implementations of the
 procedures defined above. The only subtle thing going on here is
 that we must use <code class="computeroutput">acs_object.new</code>
Index: openacs-4/packages/acs-core-docs/www/objects.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/objects.html,v
diff -u -r1.55.2.4 -r1.55.2.5
--- openacs-4/packages/acs-core-docs/www/objects.html	3 Sep 2021 09:15:19 -0000	1.55.2.4
+++ openacs-4/packages/acs-core-docs/www/objects.html	7 Sep 2021 09:39:31 -0000	1.55.2.5
@@ -79,7 +79,7 @@
 Fire up your text editor and open the
 <code class="computeroutput">ROOT/packages/notes/sql/oracle/notes-create.sql</code> (<code class="computeroutput">ROOT/packages/notes/sql/postgresql/notes-create.sql</code> for the PG version) file created
 when we <a class="link" href="packages.html" title="OpenACS Packages">created the package</a>.  Then, do the following:
-</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665012950704"></a>Describe the new type to the type system</h4></div></div></div><p>
+</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140697463173936"></a>Describe the new type to the type system</h4></div></div></div><p>
 First, add an entry to the <code class="computeroutput">acs_object_types</code> table with the following PL/SQL call:
 </p><pre class="programlisting">
 begin  
@@ -139,7 +139,7 @@
 because the new type <code class="computeroutput">note</code> is a subtype of
 <code class="computeroutput">acs_object</code>, it will inherit these attributes, so there is
 no need for us to define them.
-</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665012885408"></a>Define a table in which to store your objects</h4></div></div></div><p>
+</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140697463186624"></a>Define a table in which to store your objects</h4></div></div></div><p>
 The next thing we do is make a small modification to the data model to
 reflect the fact that each row in the <code class="computeroutput">notes</code> table
 represents something that is not only an object of type
@@ -164,7 +164,7 @@
 use the <code class="computeroutput">acs_objects</code> table to find objects will
 transparently find any objects that are instances of any subtype of
 <code class="computeroutput">acs_objects</code>.
-</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665012933376"></a>Define a package for type specific procedures</h4></div></div></div><p>
+</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140697463196912"></a>Define a package for type specific procedures</h4></div></div></div><p>
 The next step is to define a PL/SQL package for your new type, and
 write some basic procedures to create and delete objects. Here is a
 package definition for our new type:
@@ -212,7 +212,7 @@
 object OBJ was "read only", then any other object that used OBJ as its
 context would also be "read only" by default. We'll talk about this more
 later.
-</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665012941088"></a>Define a package body for type specific procedures</h4></div></div></div><p>
+</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140697194275104"></a>Define a package body for type specific procedures</h4></div></div></div><p>
 The PL/SQL package body contains the implementations of the procedures
 defined above. The only subtle thing going on here is that we must use
 <code class="computeroutput">acs_object.new</code> to insert a row into
Index: openacs-4/packages/acs-core-docs/www/openacs.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/openacs.adp,v
diff -u -r1.4.2.6 -r1.4.2.7
--- openacs-4/packages/acs-core-docs/www/openacs.adp	3 Sep 2021 09:15:20 -0000	1.4.2.6
+++ openacs-4/packages/acs-core-docs/www/openacs.adp	7 Sep 2021 09:39:31 -0000	1.4.2.7
@@ -314,7 +314,7 @@
 automate vacuuming is to edit the cron file for the database user.
 Recommended: <code class="computeroutput">VACUUM ANALYZE</code>
 every hour and <code class="computeroutput">VACUUM FULL
-ANALYZE</code> every day.</p><a class="indexterm" name="idp140666284857616" id="idp140666284857616"></a><pre class="screen">[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>export EDITOR=emacs;crontab -e</code></strong>
+ANALYZE</code> every day.</p><a class="indexterm" name="idp140697733669392" id="idp140697733669392"></a><pre class="screen">[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>export EDITOR=emacs;crontab -e</code></strong>
 </pre><p>Add these lines to the file. The vacuum command cleans up
 temporary structures within a PostGreSQL database, and can improve
 performance. We vacuum gently every hour and completely every day.
@@ -346,7 +346,7 @@
 specific port, e.g. port 80. In order for OpenACS to work, you need
 to configure a virtual server. The Reference Platform uses a
 configuration file included in the OpenACS tarball, <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/etc/config.tcl</code>.
-Open it in an editor to adjust the parameters.</p><a class="indexterm" name="idp140666284873168" id="idp140666284873168"></a><pre class="screen">[root root]# <strong class="userinput"><code>su - <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
+Open it in an editor to adjust the parameters.</p><a class="indexterm" name="idp140697733683376" id="idp140697733683376"></a><pre class="screen">[root root]# <strong class="userinput"><code>su - <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
 </code></strong>
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/etc</code></strong>
 [$OPENACS_SERVICE_NAME etc]$ <strong class="userinput"><code>emacs config.tcl</code></strong>
Index: openacs-4/packages/acs-core-docs/www/openacs.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/openacs.html,v
diff -u -r1.54.2.4 -r1.54.2.5
--- openacs-4/packages/acs-core-docs/www/openacs.html	3 Sep 2021 09:15:20 -0000	1.54.2.4
+++ openacs-4/packages/acs-core-docs/www/openacs.html	7 Sep 2021 09:39:31 -0000	1.54.2.5
@@ -237,7 +237,7 @@
 CREATE DATABASE
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$
 <span class="action"><span class="action">su - <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
-/usr/local/pgsql/bin/createdb -E UNICODE <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></span></span></pre></li><li class="listitem"><p>Automate daily database Vacuuming.  This is a process which cleans out discarded data from the database.  A quick way to automate vacuuming is to edit the cron file for the database user.  Recommended: <code class="computeroutput">VACUUM ANALYZE</code> every hour and <code class="computeroutput">VACUUM FULL ANALYZE</code> every day.</p><a class="indexterm" name="idp140666284857616"></a><pre class="screen">[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>export EDITOR=emacs;crontab -e</code></strong></pre><p>Add these lines to the file.  The vacuum command cleans up temporary structures within a PostGreSQL database, and can improve performance.  We vacuum gently every hour and completely every day.  The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day, and every (*) day of month, month, and day of week.  Type <code class="computeroutput">man 5 crontab</code> for more information.</p><pre class="programlisting">0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --analyze <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
+/usr/local/pgsql/bin/createdb -E UNICODE <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></span></span></pre></li><li class="listitem"><p>Automate daily database Vacuuming.  This is a process which cleans out discarded data from the database.  A quick way to automate vacuuming is to edit the cron file for the database user.  Recommended: <code class="computeroutput">VACUUM ANALYZE</code> every hour and <code class="computeroutput">VACUUM FULL ANALYZE</code> every day.</p><a class="indexterm" name="idp140697733669392"></a><pre class="screen">[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>export EDITOR=emacs;crontab -e</code></strong></pre><p>Add these lines to the file.  The vacuum command cleans up temporary structures within a PostGreSQL database, and can improve performance.  We vacuum gently every hour and completely every day.  The numbers and stars at the beginning are cron columns that specify when the program should be run - in this case, whenever the minute is 0 and the hour is 1, i.e., 1:00 am every day, and every (*) day of month, month, and day of week.  Type <code class="computeroutput">man 5 crontab</code> for more information.</p><pre class="programlisting">0 1-23 * * * /usr/local/pgsql/bin/vacuumdb --analyze <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
 0 0 * * * /usr/local/pgsql/bin/vacuumdb --full --analyze <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></pre><p>Depending on your distribution, you may receive
                 email when the crontab items are executed. If you
                 don't want to receive email for those crontab items,
@@ -250,7 +250,7 @@
 	  need to configure a virtual server.  The Reference Platform
 	  uses a configuration file included in the OpenACS tarball,
 	  <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/etc/config.tcl</code>.
-	   Open it in an editor to adjust the parameters.</p><a class="indexterm" name="idp140666284873168"></a><pre class="screen">[root root]# <strong class="userinput"><code>su - <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></code></strong>
+	   Open it in an editor to adjust the parameters.</p><a class="indexterm" name="idp140697733683376"></a><pre class="screen">[root root]# <strong class="userinput"><code>su - <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></code></strong>
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/etc</code></strong>
 [$OPENACS_SERVICE_NAME etc]$ <strong class="userinput"><code>emacs config.tcl</code></strong>
 </pre><p>
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 -r1.7.2.6 -r1.7.2.7
--- openacs-4/packages/acs-core-docs/www/packages.adp	3 Sep 2021 09:15:21 -0000	1.7.2.6
+++ openacs-4/packages/acs-core-docs/www/packages.adp	7 Sep 2021 09:39:32 -0000	1.7.2.7
@@ -25,7 +25,7 @@
 <div class="titlepage"><div><div><h3 class="title">
 <a name="server-file-layout" id="server-file-layout"></a>Server file layout</h3></div></div></div><p>Here is how an OpenACS 5 server is laid out starting from the
 Server root (ROOT):</p><div class="figure">
-<a name="idp140665974209600" id="idp140665974209600"></a><p class="title"><strong>Figure 11.1. Server file layout
+<a name="idp140697732723312" id="idp140697732723312"></a><p class="title"><strong>Figure 11.1. Server file layout
 diagram</strong></p><div class="figure-contents"><pre class="programlisting">
 ROOT/
     bin/
@@ -64,7 +64,7 @@
 <a class="indexterm" name="baby" id="baby"></a> To illustrate
 the general structure of a package, let&#39;s see what the package
 for the "notes" application should look like.</p><div class="figure">
-<a name="idp140665974168656" id="idp140665974168656"></a><p class="title"><strong>Figure 11.2. Package file layout
+<a name="idp140697732391776" id="idp140697732391776"></a><p class="title"><strong>Figure 11.2. Package file layout
 diagram</strong></p><div class="figure-contents"><pre class="programlisting">
 ROOT/
   +-- packages/    APM Root
@@ -134,7 +134,7 @@
 files are not sourced in these directories. This makes it suitable
 for storing icons, css files, javascript, and other static content
 which can be treated this way.</p><div class="table">
-<a name="idp140665973629920" id="idp140665973629920"></a><p class="title"><strong>Table 11.1. Package
+<a name="idp140697732397568" id="idp140697732397568"></a><p class="title"><strong>Table 11.1. Package
 files</strong></p><div class="table-contents"><table class="table" summary="Package files" cellspacing="0" border="1">
 <colgroup>
 <col><col><col>
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 -r1.57.2.5 -r1.57.2.6
--- openacs-4/packages/acs-core-docs/www/packages.html	3 Sep 2021 09:15:21 -0000	1.57.2.5
+++ openacs-4/packages/acs-core-docs/www/packages.html	7 Sep 2021 09:39:32 -0000	1.57.2.6
@@ -13,7 +13,7 @@
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="server-file-layout"></a>Server file layout</h3></div></div></div><p>
       Here is how an OpenACS 5 server is laid out
       starting from the Server root (ROOT):
-    </p><div class="figure"><a name="idp140665974209600"></a><p class="title"><b>Figure 11.1. Server file layout diagram</b></p><div class="figure-contents"><pre class="programlisting">
+    </p><div class="figure"><a name="idp140697732723312"></a><p class="title"><b>Figure 11.1. Server file layout diagram</b></p><div class="figure-contents"><pre class="programlisting">
 ROOT/
     bin/
         Various executables and scripts for server maintenance.
@@ -51,7 +51,7 @@
       <a class="indexterm" name="baby"></a>
       To illustrate the general structure of a package, let's see what the
       package for the "notes" application should look like.
-    </p><div class="figure"><a name="idp140665974168656"></a><p class="title"><b>Figure 11.2. Package file layout diagram</b></p><div class="figure-contents"><pre class="programlisting">
+    </p><div class="figure"><a name="idp140697732391776"></a><p class="title"><b>Figure 11.2. Package file layout diagram</b></p><div class="figure-contents"><pre class="programlisting">
 ROOT/
   +-- packages/    APM Root
         |
@@ -124,7 +124,7 @@
       directories.  This makes it suitable for storing icons, css
       files, javascript, and other static content which can be treated
       this way.
-    </p><div class="table"><a name="idp140665973629920"></a><p class="title"><b>Table 11.1. Package files</b></p><div class="table-contents"><table class="table" summary="Package files" cellspacing="0" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>File Type</th><th>Its Use</th><th>Naming Convention</th></tr></thead><tbody><tr><td>Package Specification File</td><td>The package specification file is an XML file generated and
+    </p><div class="table"><a name="idp140697732397568"></a><p class="title"><b>Table 11.1. Package files</b></p><div class="table-contents"><table class="table" summary="Package files" cellspacing="0" border="1"><colgroup><col><col><col></colgroup><thead><tr><th>File Type</th><th>Its Use</th><th>Naming Convention</th></tr></thead><tbody><tr><td>Package Specification File</td><td>The package specification file is an XML file generated and
           maintained by the OpenACS Package Manager (APM).  It specifies
           information about the package including its parameters and its
           files.</td><td><code class="computeroutput">notes.info</code></td></tr><tr><td>Data Model Creation Script</td><td>
Index: openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.adp	3 Sep 2021 09:15:22 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.adp	7 Sep 2021 09:39:32 -0000	1.4.2.6
@@ -127,7 +127,7 @@
 <a name="permissions-tedious-context-hierarchy" id="permissions-tedious-context-hierarchy"></a>Context
 Hierarchy</h3></div></div></div><p>Suppose objects <span class="emphasis"><em>A</em></span>,
 <span class="emphasis"><em>B</em></span>, ..., and <span class="emphasis"><em>F</em></span> form the following hierarchy.</p><div class="table">
-<a name="idp140665015347792" id="idp140665015347792"></a><p class="title"><strong>Table 11.2. Context Hierarchy
+<a name="idp140698455516464" id="idp140698455516464"></a><p class="title"><strong>Table 11.2. Context Hierarchy
 Example</strong></p><div class="table-contents"><table class="table" summary="Context Hierarchy Example" cellspacing="0" border="1">
 <colgroup>
 <col align="center" class="c1"><col align="center" class="c2"><col align="center" class="c3">
@@ -153,7 +153,7 @@
 </table></div>
 </div><br class="table-break"><p>This can be represented in the <a class="xref" href="permissions-tediously-explained">acs_objects</a>
 table by the following entries:</p><div class="table">
-<a name="idp140665015364304" id="idp140665015364304"></a><p class="title"><strong>Table 11.3. acs_objects example
+<a name="idp140698455103008" id="idp140698455103008"></a><p class="title"><strong>Table 11.3. acs_objects example
 data</strong></p><div class="table-contents"><table class="table" summary="acs_objects example data" cellspacing="0" border="1">
 <colgroup>
 <col align="center" class="c1"><col align="center" class="c2">
Index: openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.html,v
diff -u -r1.49.2.4 -r1.49.2.5
--- openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.html	3 Sep 2021 09:15:22 -0000	1.49.2.4
+++ openacs-4/packages/acs-core-docs/www/permissions-tediously-explained.html	7 Sep 2021 09:39:33 -0000	1.49.2.5
@@ -105,7 +105,7 @@
     </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="permissions-tedious-context-hierarchy"></a>Context Hierarchy</h3></div></div></div><p>
       Suppose objects <span class="emphasis"><em>A</em></span>, <span class="emphasis"><em>B</em></span>, ..., 
       and <span class="emphasis"><em>F</em></span> form the following hierarchy. 
-    </p><div class="table"><a name="idp140665015347792"></a><p class="title"><b>Table 11.2. Context Hierarchy Example</b></p><div class="table-contents"><table class="table" summary="Context Hierarchy Example" cellspacing="0" border="1"><colgroup><col align="center" class="c1"><col align="center" class="c2"><col align="center" class="c3"></colgroup><tbody><tr><td colspan="3" align="center">
+    </p><div class="table"><a name="idp140698455516464"></a><p class="title"><b>Table 11.2. Context Hierarchy Example</b></p><div class="table-contents"><table class="table" summary="Context Hierarchy Example" cellspacing="0" border="1"><colgroup><col align="center" class="c1"><col align="center" class="c2"><col align="center" class="c3"></colgroup><tbody><tr><td colspan="3" align="center">
 	      <span class="bold"><strong>A</strong></span>
 	      <p>
   	        <code class="computeroutput">object_id=10</code>
@@ -139,7 +139,7 @@
       This can be represented in the 
       <a class="xref" href="permissions-tediously-explained.html#acs_objects">acs_objects</a> table
       by the following entries: 
-    </p><div class="table"><a name="idp140665015364304"></a><p class="title"><b>Table 11.3. acs_objects example data</b></p><div class="table-contents"><table class="table" summary="acs_objects example data" cellspacing="0" border="1"><colgroup><col align="center" class="c1"><col align="center" class="c2"></colgroup><thead><tr><th align="center">object_id</th><th align="center">context_id</th></tr></thead><tbody><tr><td align="center">20</td><td align="center">10</td></tr><tr><td align="center">30</td><td align="center">10</td></tr><tr><td align="center">40</td><td align="center">20</td></tr><tr><td align="center">50</td><td align="center">20</td></tr><tr><td align="center">60</td><td align="center">30</td></tr></tbody></table></div></div><br class="table-break"><p>
+    </p><div class="table"><a name="idp140698455103008"></a><p class="title"><b>Table 11.3. acs_objects example data</b></p><div class="table-contents"><table class="table" summary="acs_objects example data" cellspacing="0" border="1"><colgroup><col align="center" class="c1"><col align="center" class="c2"></colgroup><thead><tr><th align="center">object_id</th><th align="center">context_id</th></tr></thead><tbody><tr><td align="center">20</td><td align="center">10</td></tr><tr><td align="center">30</td><td align="center">10</td></tr><tr><td align="center">40</td><td align="center">20</td></tr><tr><td align="center">50</td><td align="center">20</td></tr><tr><td align="center">60</td><td align="center">30</td></tr></tbody></table></div></div><br class="table-break"><p>
       The first entry tells us that object 20 is the descendant of object 10, and
       the third entry shows that object 40 is the descendant of object 20. By
       running a <a class="ulink" href="http://www.oradoc.com/ora817/server.817/a85397/expressi.htm#1023748" target="_top">CONNECT BY</a> query,
Index: openacs-4/packages/acs-core-docs/www/psgml-for-emacs.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/psgml-for-emacs.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/psgml-for-emacs.adp	3 Sep 2021 09:15:24 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/psgml-for-emacs.adp	7 Sep 2021 09:39:33 -0000	1.4.2.6
@@ -11,7 +11,7 @@
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="psgml-for-emacs" id="psgml-for-emacs"></a>Add PSGML commands to emacs init file
 (OPTIONAL)</h2></div></div></div><p>
-<a class="indexterm" name="idp140665014864128" id="idp140665014864128"></a> If you plan to write or edit any
+<a class="indexterm" name="idp140698013683680" id="idp140698013683680"></a> If you plan to write or edit any
 documentation with emacs, install a customized emacs configuration
 file with DocBook commands in the skeleton directory, so it will be
 used for all new users. The file also fixes the backspace -&gt;
Index: openacs-4/packages/acs-core-docs/www/psgml-for-emacs.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/psgml-for-emacs.html,v
diff -u -r1.44.2.4 -r1.44.2.5
--- openacs-4/packages/acs-core-docs/www/psgml-for-emacs.html	3 Sep 2021 09:15:24 -0000	1.44.2.4
+++ openacs-4/packages/acs-core-docs/www/psgml-for-emacs.html	7 Sep 2021 09:39:33 -0000	1.44.2.5
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Add PSGML commands to emacs init file (OPTIONAL)</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="install-more-software.html" title="Appendix B. Install additional supporting software"><link rel="previous" href="install-cvs.html" title="Initialize CVS (OPTIONAL)"><link rel="next" href="install-daemontools.html" title="Install Daemontools (OPTIONAL)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="install-cvs.html">Prev</a> </td><th width="60%" align="center">Appendix B. Install additional supporting software</th><td width="20%" align="right"> <a accesskey="n" href="install-daemontools.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="psgml-for-emacs"></a>Add PSGML commands to emacs init file (OPTIONAL)</h2></div></div></div><p><a class="indexterm" name="idp140665014864128"></a>
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Add PSGML commands to emacs init file (OPTIONAL)</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="install-more-software.html" title="Appendix B. Install additional supporting software"><link rel="previous" href="install-cvs.html" title="Initialize CVS (OPTIONAL)"><link rel="next" href="install-daemontools.html" title="Install Daemontools (OPTIONAL)"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="install-cvs.html">Prev</a> </td><th width="60%" align="center">Appendix B. Install additional supporting software</th><td width="20%" align="right"> <a accesskey="n" href="install-daemontools.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="psgml-for-emacs"></a>Add PSGML commands to emacs init file (OPTIONAL)</h2></div></div></div><p><a class="indexterm" name="idp140698013683680"></a>
 If you plan to write or edit any documentation with emacs, install a
       customized emacs configuration file with DocBook commands in the skeleton
       directory, so it will be used for all new users.  The file also
Index: openacs-4/packages/acs-core-docs/www/release-notes.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/release-notes.adp,v
diff -u -r1.8.2.8 -r1.8.2.9
--- openacs-4/packages/acs-core-docs/www/release-notes.adp	3 Sep 2021 09:15:25 -0000	1.8.2.8
+++ openacs-4/packages/acs-core-docs/www/release-notes.adp	7 Sep 2021 09:39:34 -0000	1.8.2.9
@@ -11,12 +11,390 @@
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 <a name="release-notes" id="release-notes"></a>OpenACS Release Notes</h2></div></div></div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="release-notes-5-10-0" id="release-notes-5-10-0"></a>Release 5.10.0</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;"><li class="listitem"><p>... to be completed ....</p></li></ul></div><p>Altogether, OpenACS 5.10.0 differs from OpenACS 5.9.1 by the
+<a name="release-notes-5-10-0" id="release-notes-5-10-0"></a>Release 5.10.0</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>The release of OpenACS 5.10.0 contains the 93 packages of the
+oacs-5-10 branch. These packages include the OpenACS core packages,
+the major application packages (e.g. most the ones used on
+OpenACS.org), and DotLRN 2.10.0.</p></li><li class="listitem">
+<p>Functional improvements</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle;">
+<li class="listitem">
+<p>Features:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>Added additional page_contract filter: oneof(red|green|blue)</p></li><li class="listitem"><p>
+<code class="computeroutput">template::add_event_listener</code>
+and <code class="computeroutput">template::add_confirm_handler</code> now can
+target elements by CSS selector</p></li><li class="listitem"><p>Added text/markdown to the accepted text formats or rich-text
+widget</p></li><li class="listitem">
+<p>Support for range types in .xql files:</p><p>PostgreSQL supports range types since 9.5. When using range
+types, square braces have to be used in SQL statements. Since
+OpenACS uses always Tcl substitution in .xql files, and OpenACS
+does NOT allow backslash substitution in these files, square
+brackets could not be escaped and therefore not be used in .xql
+files so far. This change allows now a developer to deactivate the
+substitution by passing e.g. <code class="computeroutput">-subst
+none</code> to the db_* command using the .xql file. Valid values
+for <code class="computeroutput">-subst</code> are <code class="computeroutput">all</code>, <code class="computeroutput">none</code>, <code class="computeroutput">vars</code>, and <code class="computeroutput">commands</code>, default is <code class="computeroutput">all</code> which is exactly the behavior of
+previous releases. Therefore, this change is fully backward
+compatible.</p>
+</li><li class="listitem"><p>Improved API browser: Visualization for code dependencies (which
+procs calls what, from where is a proc being called) and
+test-coverage</p></li><li class="listitem"><p>Warn site administrators about expiring certificates</p></li><li class="listitem">
+<p>Additional input types (and widgets) for <code class="computeroutput">ad_form</code>:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>checkbox_text</p></li><li class="listitem"><p>color</p></li><li class="listitem"><p>email</p></li><li class="listitem"><p>tel</p></li><li class="listitem"><p>url</p></li><li class="listitem"><p>number</p></li><li class="listitem"><p>file (multiple)</p></li><li class="listitem"><p>h5date and h5time: date and time fields using native HTML5
+visualization and input normalization</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Registry for .js and .css libraries: allow besides classical
+URLs symbolic names for loading external resources (e.g. jquery),
+this makes it easier to upgrade libraries in multiple packages
+(without running into problems with duplicate versions) and
+supports switching between CDN and local pathsURN. The existing
+implementation is based on URNs and extends the existing
+template-head API to support registration for URNs. A URN provides
+an abstraction and a single place for e.g. updating references to
+external resources when switching between a CDN and a locally
+stored resource, or when a resource should be updated. Instead of
+adding e.g. a CDN URL via template::head::add_script, one can add
+an URN and control its content from a single place. Use common
+namespaces for OpenACS such as <code class="computeroutput">urn:ad:css:*</code> and <code class="computeroutput">urn:ad:js:*</code>.</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem">
+<p>Register URNs:</p><p>Example provider (e.g. in some theme):</p><pre class="programlisting">
+   template::register_urn \ 
+       -urn urn:ad:js:jquery \ 
+       -resource /resources/xowiki/jquery/jquery.min.js
+</pre>
+</li><li class="listitem">
+<p>The registered URN can be used like classical URL after
+registration.</p><p>Example consumer:</p><pre class="programlisting">
+   template::head::add_javascript -src urn:ad:js:jquery</pre>
+</li><li class="listitem">
+<p>Declare composite files: Provide an interface to define that a
+.js file or a .css file contains multiple other .js/.css files in
+order to reduce the number of requests.</p><pre class="programlisting">
+   template::head::includes -container urn:js::style.js -parts {urn:ad:js:jquery ...}</pre>
+</li>
+</ul></div>
+</li><li class="listitem"><p>Improved support for streaming HTML: The new API function
+<code class="computeroutput">template::collect_body_scripts</code>
+can be used to get the content of template::script or CSP calls
+(<code class="computeroutput">template::add_body_script</code>,
+<code class="computeroutput">template::add_event_listener</code>,
+<code class="computeroutput">template::add_body_handler</code>,
+<code class="computeroutput">template::add_script</code>) when
+streaming HTML (incremental HTML) is used. Before, these call could
+bot be used for streaming HTML.</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Reforms:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem">
+<p>Dynamic blueprint reloading:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>When reloading apm packages, watched files, etc. the NaviServer
+blueprint is now updated correctly. This solves the long-standing
+problem that changes for scheduled procedures required a restart of
+the server. Furthermore, the old-style reloading was based on a
+ever-growing list of reload operations each time a new reload was
+requested, causing slow-downs in long running server instances,
+especially, when new threads are started.</p></li><li class="listitem"><p>Now changes are applied to all NaviServer threads, including
+threads for schedules procedures, ns_jobs and the like. Note that
+the current job has to be finished before the changes can be
+applied.</p></li><li class="listitem"><p>For the transition, it is possible to switch between the
+classical reloading style and blueprint reloading by changing a
+variable in acs-tcl/tcl/apm-procs.tcl</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Login:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;"><li class="listitem"><p>Get rid of bugging "login page expired" messages. The
+17 years old construct was replaced by newer means to avoid caching
+of form values from the login form. Admins of existing sites should
+set the kernel parameter <code class="computeroutput">LoginPageExpirationTime</code> to 0</p></li></ul></div>
+</li><li class="listitem">
+<p>Forums:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>Removed hard-coded dependency with registered_users group when
+checking forum permissions</p></li><li class="listitem"><p>Don&#39;t rely so heavily on acs_permissions to model forum
+configuration, as this can have unexpected consequences in
+convoluted multi-group/multi-subsite scenarios. Prefer simpler
+table attributes instead</p></li><li class="listitem"><p>New style of attachments to the forums, allowing multiple
+attachments to a single message directly from the message post
+page, using the multiple file input widget. Retain compatibility
+with old style attachments, using the new 'AttachmentStyle'
+package instance parameter. Currently, this supports two values:
+'simple' (new behavior) and 'complex' previous
+behavior.</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Chat:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>Revamping of the GUI</p></li><li class="listitem"><p>Responsiveness</p></li><li class="listitem"><p>Full screen mode</p></li><li class="listitem"><p>Skins support (minimal, classic and bubbles, included): Skins
+are located in the new /packages/xowiki/www/resources/chat-skins/
+directory. New skins can be created by just adding the css and js
+files in the skins directory, and naming them accordingly
+(chat-$SKIN_NAME.{js|css}).</p></li><li class="listitem"><p>Avatars (can be enabled per room)</p></li><li class="listitem"><p>Number of active users in chat</p></li><li class="listitem"><p>Tab notifications of new messages</p></li><li class="listitem">
+<p>Web Notifications:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle;">
+<li class="listitem"><p>https://www.w3.org/TR/notifications/</p></li><li class="listitem"><p>
+https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API</p></li>
+</ul></div>
+</li>
+</ul></div>
+</li><li class="listitem">
+<p>acs-lang:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem">
+<p>admin pages:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle;">
+<li class="listitem"><p>Added the option to unregister (delete permanently the message
+key from all locales) a message key that has been already marked as
+deleted. Useful for cleaning up old message keys.</p></li><li class="listitem"><p>Added the option to undelete, using the new ::message::undelete
+proc.</p></li><li class="listitem"><p>Made number and category (untranslated/deleted/...) of messages
+coherent in all pages.</p></li><li class="listitem"><p>Added the columns 'total' and 'deleted' to the
+index page.</p></li>
+</ul></div>
+</li><li class="listitem"><p>object_id reference: it is now possible to associate a message
+key to an object_id in a way that e.g. when the object is deleted,
+so is the message key. This addresses cases such as the message
+keys generated by group creation or by the new XoWiki localized
+fields</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Notifications:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>Improved scalability for notifications: One of the most
+expensive operations in large site is the cleanup for
+notification_requests in situations, where the user has lost
+permissions on an object, on which the user wanted to receive
+notifications. This check was performed previously in <code class="computeroutput">notification::sweep::cleanup_notifications</code>
+via a permission check over all notification requests, which can be
+very costly on large sites. This change moves this cleanup into the
+actual notification sending, where the permissions have to be sent
+anyhow.</p></li><li class="listitem"><p>When sending a notification on behalf of a person, if the system
+is not configured to process replies to notification, do not set
+the reply-to address to anything different than the sender</p></li><li class="listitem"><p>Notifications: proper cleanup of acs_objects resulting from the
+deletion of dynamic notification requests</p></li>
+</ul></div>
+</li><li class="listitem"><p>User/Person/Party API: rework and rationalize caching of all
+party, person and user API, create separate caches for each of
+these types, make the API and return dicts. acs_user::get will not
+fail anymore with non-existing user.</p></li><li class="listitem"><p>User Portrait: created API to retrieve and create, store and
+delete the user&#39;s portrait. Also address leftover child
+relationships from the past and delete them properly.</p></li>
+</ul></div>
+</li>
+</ul></div>
+</li><li class="listitem">
+<p>Non-functional Changes</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle;">
+<li class="listitem">
+<p>Improved automated regression test infrastructure and test
+coverage</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>All packages in the <code class="computeroutput">oacs-5-10</code> branch pass regression test</p></li><li class="listitem"><p>Web testing was separated from non-maintained tcltest and was
+built on the standard OpenACS infrastructure</p></li><li class="listitem"><p>Include web testing per default in standard regression
+testing</p></li><li class="listitem"><p>Introduced new test authentication authority, allowing to run
+many user administration tests outside the context of a "real
+authority": in cases where the real authority depends on
+external services to proof identity, (e.g. Kerberos), those tests
+would just fail.</p></li><li class="listitem"><p>Introduce the display of warnings in the UI</p></li><li class="listitem"><p>Added test coverage information in the automated testing pages,
+using the new proc-coverage API and providing test coverage
+information for packages and system wide.</p></li><li class="listitem"><p>Increased overall coverage of public API</p></li><li class="listitem"><p>New tests checking various data-model properties and smells</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Improved scalability:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>Provided lock-free implementation of <code class="computeroutput">ad_page_contract_filters</code> and <code class="computeroutput">ad_page_contract_filter_rules</code>. This change
+improves parallel processing of requests and is primarily
+interesting for sites with a few mio page views per days. These
+locks were among the most frequent nsv locks</p></li><li class="listitem"><p>Reduced locks on util_memoize_cache my more invariants values
+into per-thread caching (<code class="computeroutput">acs_lookup_magic_object</code>, <code class="computeroutput">ad_acs_version</code>, .... ) and by avoiding
+specialized calls, which can be realized by already optimized ones
+(<code class="computeroutput">apm_package_installed_p_not_cached
+ref-timezones</code> was most frequently used util_memoize_cache
+entry). These changes are necessary to avoid full still-stand on
+the unfortunate long-time locks on util_memoize_cache stemming from
+permission and user management with wild-card flush operations,
+which require to iterate over all cache entries (which might be on
+a busy server several hundred thousands)</p></li><li class="listitem"><p>Added new interface for cache partitioning to reduce lock
+latencies on high load websites</p></li><li class="listitem"><p>Added new interface for lock-free per-thread and per-request
+caching to avoid scattered ad-hoc implementations</p></li><li class="listitem"><p>Better reuse of DB handles (reduced expiring/reopen/etc.),
+faster access to handles</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Improved startup time:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>When the package acs-automated-testing is disabled, startup time
+is reduced by avoiding loading of support functions and tests; the
+size of the blueprint is reduced</p></li><li class="listitem"><p>xowf: loading of at-jobs is significantly improved.</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Security improvements:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>Strengthened page contracts</p></li><li class="listitem"><p>CSP support for application packages</p></li><li class="listitem"><p>CSP fine tuning  </p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Better exception handling based on Tcl 8.6 exception handlers
+(<code class="computeroutput">try</code> and <code class="computeroutput">throw</code>, also available in Tcl 8.5)</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>Provided a new <code class="computeroutput">ad_try</code>
+implementation based on Tcl&#39;s <code class="computeroutput">try</code> replaces now the old <code class="computeroutput">ad_try</code>, <code class="computeroutput">with_catch</code> and <code class="computeroutput">with_finally</code>, which are marked as
+deprecated</p></li><li class="listitem"><p>The new <code class="computeroutput">ad_try</code> is in essence
+Tcl&#39;s <code class="computeroutput">try</code> but with
+predefined handling of <code class="computeroutput">ad_script_abort</code> and should be also used
+instead of <code class="computeroutput">catch</code>, when the
+OpenACS API is used (which might use script aborts)</p></li><li class="listitem"><p>All core packages use the new <code class="computeroutput">ad_try</code> instead of the deprecated
+versions.</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Connection close reform:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>NaviServer/AOLserver continue after connection closing commands
+to execute a script. This is in many situations not desired,
+especially, when for the page as well a .adp file exists, which
+will try to deliver this on the already closed connection. This can
+lead to errors in the error.log file, which are sometimes hard to
+analyze</p></li><li class="listitem"><p>Due to this cleanup, developers should use in most such cases
+cases <code class="computeroutput">ad_script_abort</code>
+</p></li><li class="listitem"><p>Connection closing commands are e.g. <code class="computeroutput">ad_returnredirect</code>, <code class="computeroutput">ad_redirect_for_registration</code>, <code class="computeroutput">cr_write_content</code>, <code class="computeroutput">ad_page_contract_handle_datasource_error</code>,
+<code class="computeroutput">ad_return_string_as_file</code>,
+<code class="computeroutput">ad_return_complaint</code>,
+<code class="computeroutput">ad_return_error</code>, <code class="computeroutput">ad_return_forbidden</code>, <code class="computeroutput">ad_return_warning</code>, <code class="computeroutput">ad_return_exception_page</code>, <code class="computeroutput">ns_returnredirect</code>, <code class="computeroutput">ns_return</code>, <code class="computeroutput">ns_returnerror</code>
+</p></li><li class="listitem"><p>The new version has made on most occasions explicit, when the
+script should abort.</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>API changes (new and extended API calls):</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>New API call <code class="computeroutput">category::get</code>
+to obtain category description for a category_id and locale</p></li><li class="listitem"><p>New utility <code class="computeroutput">ad_pad</code> emulating
+both lpad and rpad typically available in DBMSs</p></li><li class="listitem"><p>New proc lc_content_size_pretty, prettify data size given in
+bytes. It supports three different standards (SI base-10, IEC
+base-2 and the old JEDEC base-2), default is SI base-10.</p></li><li class="listitem"><p>New flag <code class="computeroutput">-export</code> for
+<code class="computeroutput">ad_form</code>: this flag uses
+<code class="computeroutput">export_vars</code> under the hood and
+supports all of this API&#39;s features (e.g. :multiple, :sign,
+:array). This addresses a long standing TODO</p></li><li class="listitem"><p>
+<code class="computeroutput">util::pdfinfo</code>: simple
+poppler-utils wrapper to extract pdf information</p></li><li class="listitem"><p>util::http: leverage new ns_http features such as request file
+spooling. Native implementation will now be used only on NaviServer
+&gt;= 4.99.15.</p></li><li class="listitem">
+<p>Database API:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>
+<code class="computeroutput">db_foreach</code>: queries executed
+inside of a db_foreach will not be issued using a different handle
+and will therefore be safe to use in a transaction</p></li><li class="listitem"><p>
+<code class="computeroutput">db_list_of_lists</code>: new
+<code class="computeroutput">-with_headers</code> flag, which will
+make the first element of the returned list to be the column names
+as defined in the query</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Groups API:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>Logics to delete a group type have now been included in the
+API</p></li><li class="listitem"><p>Allow to filter group members by member_state in the API</p></li>
+</ul></div>
+</li>
+</ul></div>
+</li><li class="listitem">
+<p>Deprecated commands:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>Many deprecated API calls were included in the code (and
+sometimes still in use) sometimes more than 10 years after these
+calls have been deprecated. In case a site modification still uses
+deprecated code, the user is warned about this. The OpenACS 5.10
+code base does not depend on deprecated code.</p></li><li class="listitem"><p>Move deprecated code into separate files</p></li><li class="listitem"><p>Made loading of deprecated code optional (can be controlled via
+parameter "WithDeprecatedCode" in section
+"ns_section ns/server/${server}/acs" of the config file.
+By default, deprecated procs are still loaded</p></li><li class="listitem">
+<p>When deprecated code is not loaded, the blueprint of the
+interpreter is smaller. The following number of lines of code can
+be omitted when loading without the deprecated procs:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>acs-tcl: 3178</p></li><li class="listitem"><p>acs-templating: 450</p></li><li class="listitem"><p>xotcl-core http-client-procs: 830</p></li><li class="listitem"><p>acs-content-repository: 1717 (including .xql files)</p></li>
+</ul></div>
+</li>
+</ul></div>
+</li><li class="listitem">
+<p>Bugfix and Code Maintenance:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>Made sure all party emails are stored as lowercase through the
+API</p></li><li class="listitem"><p>Fixed long standing regression in template::list: we were
+looping through the list "elements", rather than the
+"display_elements". This prevents specifying different
+sets of columns to be returned depending on the <code class="computeroutput">-formats</code> and <code class="computeroutput">-selected_format</code> options in
+template::list::create.</p></li><li class="listitem"><p>acs-content-repository: New HEIC and HEIF mimetypes</p></li><li class="listitem"><p>acs-mail-lite: handle <code class="computeroutput">to_addr</code> specified as "DisplayName
+&lt;email&gt;" without errors</p></li><li class="listitem"><p>Fixed invalidating of all existing user logins, (aka)
+"Logout from everywhere" feature, useful e.g. to make
+sure no device still holds a valid login when we change our
+password on a device</p></li><li class="listitem"><p>Don&#39;t lose the return URL when one tries to join a subsite
+before being logged in</p></li><li class="listitem"><p>Added <code class="computeroutput">doc(base_href)</code> and
+<code class="computeroutput">doc(base_target)</code> for setting
+&lt;base&gt; element via blank-baster (see issue #3435)</p></li><li class="listitem">
+<p>Groups:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>When a new group is created, flush all the group::get_id caches
+with the same name so that the new group can be fetched correctly
+in case it replaces a previously deleted one</p></li><li class="listitem"><p>Cleanup message keys coming from groups in acs-translations when
+a group is deleted</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>acs-lang:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>
+<code class="computeroutput">lang::util::convert_to_i18n</code>:
+do not always register a en_US translation, which would be always
+overridden. Instead, let <code class="computeroutput">lang::message::register</code> make sure that a
+en_US message exists and create one only as a fallback.</p></li><li class="listitem"><p>
+<code class="computeroutput">lc_time_fmt</code>: leverage Tcl
+clock to address shortcomings such as handling of dates in
+Julian/Gregorian calendar and impossible dates such as 1999-02-29,
+implement missing formats, support previously undocumented formats
+explicitly</p></li>
+</ul></div>
+</li><li class="listitem"><p>search: make sure objects in the search indexer queue still
+exist by the time they are swept by the indexer (e.g. items deleted
+before the indexer could sweep them)</p></li><li class="listitem"><p>
+<code class="computeroutput">attribute::delete</code>: fix proc
+so it leverages stored procedure capability of dropping the
+database table as well</p></li><li class="listitem"><p>
+<code class="computeroutput">util::http</code>: fix UTF-8
+encoding issues for some cornercases</p></li><li class="listitem"><p>Localization: Complete Italian and Spanish localization for the
+whole .LRN set of packages (including themes). Message keys for new
+and previously localized packages have also been updated</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>General cleanup/maintenance</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>Improved handling of server implementation-specific code:
+server-specific code can be optionally loaded via specifying the
+server family in the filename. Provided <code class="computeroutput">*-procs-aolserver.tcl</code> and <code class="computeroutput">*-procs-naviserver.tcl</code> similar to
+*.postgresql.xql and *.oracle.xql where appropriate</p></li><li class="listitem"><p>Modernization of Tcl idioms.</p></li><li class="listitem"><p>Compliance of files, proc names, ... to the naming
+conventions.</p></li><li class="listitem"><p>White space cleanup, indentation changes.</p></li><li class="listitem"><p>Improvement of public API documentation</p></li><li class="listitem"><p>Adjustment of proc protection levels (public, private)</p></li><li class="listitem"><p>Adjustment of log severity</p></li><li class="listitem"><p>Cleanup of obsolete files</p></li><li class="listitem"><p>Replacement of handcrafted forms by ad_form</p></li><li class="listitem"><p>Typo fixing</p></li><li class="listitem"><p>Editor hints</p></li><li class="listitem"><p>Replacement of deprecated calls</p></li><li class="listitem"><p>Addition of missing contracts</p></li><li class="listitem"><p>...</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>SQL cleanup:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem">
+<p>Cleanup of obsolete nonportable SQL constructs in a way Oracle
+and PostgreSQL code base divergency is reduced:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>"nvl" -&gt; "coalesce"</p></li><li class="listitem"><p>"sysdate" / "now()" -&gt; standard
+"current_date" or "current_timestamp"</p></li><li class="listitem"><p>Use standard-compliant "dual" table where appropriate
+(required by Oracle, supported by PostgreSQL)</p></li><li class="listitem"><p>Use non-dialectal cast idioms when appropriate</p></li><li class="listitem"><p>Adopt CTE idioms in Oracle codebase as well (e.g. connect -&gt;
+with recursive)</p></li><li class="listitem"><p>... (reference Oracle version will be 11gr2 as is oldest version
+officially supported by Oracle (See <a class="ulink" href="http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf" target="_top">here</a> and <a class="ulink" href="https://n4stack.io/oracle-11g-end-of-life/" target="_top">here</a>)</p></li>
+</ul></div>
+</li><li class="listitem">
+<p>Reduced superfluous .xql queries</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<li class="listitem"><p>acs-subsite: delete 21 files with un-referenced .xql queries</p></li><li class="listitem"><p>acs-tcl: delete 4 files</p></li><li class="listitem"><p>news: 3 files</p></li><li class="listitem"><p>file-storage: 1 file</p></li><li class="listitem"><p>dotlrn: 9 files</p></li>
+</ul></div>
+</li>
+</ul></div>
+</li><li class="listitem">
+<p>New Packages:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square;">
+<li class="listitem"><p>cookie-consent: alerting users about the use of cookies on a
+website</p></li><li class="listitem"><p>boomerang: performance of your website from your end user’s
+point of view</p></li><li class="listitem"><p>xooauth: OAuth implementation, including LTI (Learning Tools
+Interoperability)</p></li><li class="listitem"><p>dotlrn-bootstrap3-theme: Bootstrap 3 theme for DotLRN</p></li><li class="listitem"><p>xowf-monaco-plugin: Integration of Monaco editor with for code
+exercise types in xowf</p></li><li class="listitem"><p>proctoring-support: utilities and user interfaces to implement
+proctoring of the user session, mainly intended in the context of
+distance education and online exams. The main proctoring feature
+relies only on web technologies and does not require any plugin or
+additional software. Optional support for the Safe Exam Browser has
+also been introduced. The package is currently at the core of WU
+Online Exam infrastructure and is integrated in the inclass exam
+implementation for xowf</p></li>
+</ul></div>
+</li>
+</ul></div>
+</li><li class="listitem"><p>Require Tcl 8.6, XOTcl 2.1, PostgreSQL 9.6 (PostgreSQL 9.5 EOL:
+<a class="ulink" href="https://www.postgresql.org/support/versioning/" target="_top">February 2021</a>), tdom 0.9</p></li>
+</ul></div><p>Altogether, OpenACS 5.10.0 differs from OpenACS 5.9.1 by the
 following statistics</p><pre class="programlisting">
-      xxx files changed, xxx insertions(+), xxx deletions(-)
-    </pre><p>contributed by xxxx committers (...) and xxxx patch/bugfix
-providers (...). All packages of the release were tested with
-PostgreSQL 10.* and Tcl 8.6.*.</p><p>For more details, consult the <a class="ulink" href="" target="_top">raw ChangeLog</a>.</p>
+ 3442 files changed, 120847 insertions(+), 92002 deletions(-) 
+</pre><p>contributed by 7 committers (Antonio Pisano, Gustaf Neumann,
+Günter Ernst, Hector Romojaro, Michael Aram, Stefan Sobernig,
+Thomas Renner) and additional 13 patch/bugfix providers (Felix
+Mödritscher, Florian Mosböck, Frank Bergmann, Franz Penz, Hanifa
+Hasan, Keith Paskett, Markus Moser, Maurizio Martignano, Monika
+Andergassen, Nathan Coulter, Rainer Bachleitner, Stephan
+Adelsberger, Tony Kirkham). All packages of the release were tested
+with PostgreSQL 13.* and Tcl 8.6.*.</p><p>For more details, consult the <a class="ulink" href="http://openacs.org/changelogs/ChangeLog-5.10.0" target="_top">raw
+ChangeLog</a>.</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
 <a name="release-notes-5-9-1" id="release-notes-5-9-1"></a>Release 5.9.1</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
@@ -531,7 +909,7 @@
       3658 files changed, 120800 insertions(+), 97617 deletions(-)
     </pre><p>contributed by 4 committers (Michael Aram, Victor Guerra, Gustaf
 Neumann, Antonio Pisano) and patch/bugfix providers (Frank
-Bergmann, Andrew Helsley, Felix Mödritscher, Marcos Moser, Franz
+Bergmann, Andrew Helsley, Felix Mödritscher, Markus Moser, Franz
 Penz, Thomas Renner). These are significantly more changes as the
 differences in the last releases. All packages of the release were
 tested with PostgreSQL 9.4.* and Tcl 8.5.*.</p><p>For more details, consult the <a class="ulink" href="" target="_top">raw ChangeLog</a>.</p>
@@ -823,20 +1201,20 @@
 turned off by default via the acs-kernel parameter ExcludedFiles in
 section request-processor (The variable provides a string match
 glob list of files and is defaulted to "*/CVS/* *~")</p></li>
-</ul></div><div class="cvstag">($&zwnj;Id: release-notes.xml,v 1.39.2.4 2021/09/02
-18:42:46 gustafn Exp $)</div>
+</ul></div><div class="cvstag">($&zwnj;Id: release-notes.xml,v 1.39.2.5 2021/09/06
+17:42:35 gustafn Exp $)</div>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665973421504" id="idp140665973421504"></a>Release 4.6.3</h3></div></div></div><p><a class="ulink" href="release-notes-4-6-3" target="_top">Release Notes for 4.6.3</a></p>
+<a name="idp140698012445936" id="idp140698012445936"></a>Release 4.6.3</h3></div></div></div><p><a class="ulink" href="release-notes-4-6-3" target="_top">Release Notes for 4.6.3</a></p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665973423008" id="idp140665973423008"></a>Release 4.6.2</h3></div></div></div><p><a class="ulink" href="release-notes-4-6-2" target="_top">Release Notes for 4.6.2</a></p>
+<a name="idp140698012447440" id="idp140698012447440"></a>Release 4.6.2</h3></div></div></div><p><a class="ulink" href="release-notes-4-6-2" target="_top">Release Notes for 4.6.2</a></p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665973424512" id="idp140665973424512"></a>Release 4.6</h3></div></div></div><p><a class="ulink" href="release-notes-4-6" target="_top">Release Notes for 4.6</a></p>
+<a name="idp140698012448944" id="idp140698012448944"></a>Release 4.6</h3></div></div></div><p><a class="ulink" href="release-notes-4-6" target="_top">Release Notes for 4.6</a></p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665973426016" id="idp140665973426016"></a>Release 4.5</h3></div></div></div><p><a class="ulink" href="release-notes-4-5" target="_top">Release Notes for 4.5</a></p>
+<a name="idp140698012450448" id="idp140698012450448"></a>Release 4.5</h3></div></div></div><p><a class="ulink" href="release-notes-4-5" target="_top">Release Notes for 4.5</a></p>
 </div>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"
Index: openacs-4/packages/acs-core-docs/www/release-notes.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/release-notes.html,v
diff -u -r1.61.2.4 -r1.61.2.5
--- openacs-4/packages/acs-core-docs/www/release-notes.html	3 Sep 2021 09:15:25 -0000	1.61.2.4
+++ openacs-4/packages/acs-core-docs/www/release-notes.html	7 Sep 2021 09:39:36 -0000	1.61.2.5
@@ -1,18 +1,123 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>OpenACS Release Notes</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="general-documents.html" title="Chapter 1. High level information: What is OpenACS?"><link rel="previous" href="openacs-overview.html" title="Overview"><link rel="next" href="acs-admin.html" title="Part II. Administrator's Guide"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="openacs-overview.html">Prev</a> </td><th width="60%" align="center">Chapter 1. High level information: What is OpenACS?</th><td width="20%" align="right"> <a accesskey="n" href="acs-admin.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="release-notes"></a>OpenACS Release Notes</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="release-notes-5-10-0"></a>Release 5.10.0</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
-        ... to be completed ....
-      </p></li></ul></div><p> Altogether, OpenACS 5.10.0 differs from OpenACS 5.9.1 by the
-    following statistics
-    </p><pre class="programlisting">
-      xxx files changed, xxx insertions(+), xxx deletions(-)
-    </pre><p>
-    contributed by xxxx committers (...) and xxxx patch/bugfix providers
-    (...). All packages of
-    the release were tested with PostgreSQL 10.* and Tcl 8.6.*.
-  </p><p>
-    For more details, consult the
-    <a class="ulink" href="" target="_top">raw ChangeLog</a>.
-  </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="release-notes-5-9-1"></a>Release 5.9.1</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+      The release of OpenACS 5.10.0 contains the 93 packages of the oacs-5-10
+      branch.  These packages include the OpenACS core packages, the major
+      application packages (e.g. most the ones used on OpenACS.org), and
+      DotLRN 2.10.0. 
+    </p></li><li class="listitem"><p>Functional improvements
+	</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>Features:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>Added additional page_contract filter: oneof(red|green|blue)</p></li><li class="listitem"><p><code class="computeroutput">template::add_event_listener</code> and <code class="computeroutput">template::add_confirm_handler</code> now can target elements by CSS selector</p></li><li class="listitem"><p>Added text/markdown to the accepted text formats or rich-text widget</p></li><li class="listitem"><p>Support for range types in .xql files:
+			</p><p>PostgreSQL supports range types since 9.5. When using range types, square braces have to be used in SQL statements. Since OpenACS uses always Tcl substitution in .xql files, and OpenACS does NOT allow backslash substitution in these files, square brackets could not be escaped and therefore not be used in .xql files so far. This change allows now a developer to deactivate the substitution by passing e.g. <code class="computeroutput">-subst none</code> to the db_* command using the .xql file. Valid values for <code class="computeroutput">-subst</code> are <code class="computeroutput">all</code>, <code class="computeroutput">none</code>, <code class="computeroutput">vars</code>, and <code class="computeroutput">commands</code>, default is <code class="computeroutput">all</code> which is exactly the behavior of previous releases. Therefore, this change is fully backward compatible.</p><p>
+			</p></li><li class="listitem"><p>Improved API browser: Visualization for code dependencies (which procs calls what, from where is a proc being called) and test-coverage</p></li><li class="listitem"><p>Warn site administrators about expiring certificates</p></li><li class="listitem"><p>Additional input types (and widgets) for <code class="computeroutput">ad_form</code>:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>checkbox_text</p></li><li class="listitem"><p>color</p></li><li class="listitem"><p>email</p></li><li class="listitem"><p>tel</p></li><li class="listitem"><p>url</p></li><li class="listitem"><p>number</p></li><li class="listitem"><p>file (multiple)</p></li><li class="listitem"><p>h5date and h5time: date and time fields using native HTML5 visualization and input normalization</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>Registry for .js and .css libraries: allow besides classical URLs symbolic names for loading external resources (e.g. jquery), this makes it easier to upgrade libraries in multiple packages (without running into problems with duplicate versions) and supports switching between CDN and local pathsURN. The existing implementation is based on URNs and extends the existing template-head API to support registration for URNs. A URN provides an abstraction and a single place for e.g. updating references to external resources when switching between a CDN and a locally stored resource, or when a resource should be updated. Instead of adding e.g. a CDN URL via template::head::add_script, one can add an URN and control its content from a single place. Use common namespaces for OpenACS such as <code class="computeroutput">urn:ad:css:* </code>and <code class="computeroutput">urn:ad:js:*</code>.
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
+				</p><p>Register URNs:</p><p>
+				Example provider (e.g. in some theme):
+
+				</p><pre class="programlisting">
+   template::register_urn \ 
+       -urn urn:ad:js:jquery \ 
+       -resource /resources/xowiki/jquery/jquery.min.js
+</pre><p>
+				</p></li><li class="listitem"><p>
+				</p><p>The registered URN can be used like classical URL after registration.</p><p>
+
+				</p><p>Example consumer:</p><p>
+
+				</p><pre class="programlisting">
+   template::head::add_javascript -src urn:ad:js:jquery</pre><p>
+				</p></li><li class="listitem"><p>Declare composite files: Provide an interface to define that a .js file or a .css file contains multiple other .js/.css files in order to reduce the number of requests.
+				</p><pre class="programlisting">
+   template::head::includes -container urn:js::style.js -parts {urn:ad:js:jquery ...}</pre><p>
+				</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>
+			</p><p>Improved support for streaming HTML: The new API function <code class="computeroutput">template::collect_body_scripts</code> can be used to get the content of template::script or CSP calls (<code class="computeroutput">template::add_body_script</code>, <code class="computeroutput">template::add_event_listener</code>, <code class="computeroutput">template::add_body_handler</code>, <code class="computeroutput">template::add_script</code>) when streaming HTML (incremental HTML) is used. Before, these call could bot be used for streaming HTML.</p><p>
+			</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>Reforms:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>Dynamic blueprint reloading:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>When reloading apm packages, watched files, etc. the NaviServer blueprint is now updated correctly. This solves the long-standing problem that changes for scheduled procedures required a restart of the server. Furthermore, the old-style reloading was based on a ever-growing list of reload operations each time a new reload was requested, causing slow-downs in long running server instances, especially, when new threads are started.</p></li><li class="listitem"><p>Now changes are applied to all NaviServer threads, including threads for schedules procedures, ns_jobs and the like. Note that the current job has to be finished before the changes can be applied.</p></li><li class="listitem"><p>For the transition, it is possible to switch between the classical reloading style and blueprint reloading by changing a variable in acs-tcl/tcl/apm-procs.tcl</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>Login:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Get rid of bugging "login page expired" messages. The 17 years old construct was replaced by newer means to avoid caching of form values from the login form. Admins of existing sites should set the kernel parameter <code class="computeroutput">LoginPageExpirationTime</code> to 0</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>Forums:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Removed hard-coded dependency with registered_users group when checking forum permissions</p></li><li class="listitem"><p>Don't rely so heavily on acs_permissions to model forum configuration, as this can have unexpected consequences in convoluted multi-group/multi-subsite scenarios. Prefer simpler table attributes instead</p></li><li class="listitem"><p>New style of attachments to the forums, allowing multiple attachments to a single message directly from the message post page, using the multiple file input widget. Retain compatibility with old style attachments, using the new 'AttachmentStyle' package instance parameter. Currently, this supports two values: 'simple' (new behavior) and 'complex' previous behavior.</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>Chat:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Revamping of the GUI</p></li><li class="listitem"><p>Responsiveness</p></li><li class="listitem"><p>Full screen mode</p></li><li class="listitem"><p>Skins support (minimal, classic and bubbles, included): Skins are located in the new /packages/xowiki/www/resources/chat-skins/ directory. New skins can be created by just adding the css and js files in the skins directory, and naming them accordingly (chat-$SKIN_NAME.{js|css}).</p></li><li class="listitem"><p>Avatars (can be enabled per room)</p></li><li class="listitem"><p>Number of active users in chat</p></li><li class="listitem"><p>Tab notifications of new messages</p></li><li class="listitem"><p>Web Notifications:
+				</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>https://www.w3.org/TR/notifications/</p></li><li class="listitem"><p>https://developer.mozilla.org/en-US/docs/Web/API/Notifications_API/Using_the_Notifications_API</p></li></ul></div><p>
+				</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>acs-lang:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>admin pages:
+				</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>Added the option to unregister (delete permanently the message key from all locales) a message key that has been already marked as deleted. Useful for cleaning up old message keys.</p></li><li class="listitem"><p>Added the option to undelete, using the new ::message::undelete proc.</p></li><li class="listitem"><p>Made number and category (untranslated/deleted/...) of messages coherent in all pages.</p></li><li class="listitem"><p>Added the columns 'total' and 'deleted' to the index page.</p></li></ul></div><p>
+				</p></li><li class="listitem"><p>object_id reference: it is now possible to associate a message key to an object_id in a way that e.g. when the object is deleted, so is the message key. This addresses cases such as the message keys generated by group creation or by the new XoWiki localized fields</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>Notifications:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Improved scalability for notifications: One of the most expensive operations in large site is the cleanup for notification_requests in situations, where the user has lost permissions on an object, on which the user wanted to receive notifications. This check was performed previously in <code class="computeroutput">notification::sweep::cleanup_notifications</code> via a permission check over all notification requests, which can be very costly on large sites. This change moves this cleanup into the actual notification sending, where the permissions have to be sent anyhow.</p></li><li class="listitem"><p>When sending a notification on behalf of a person, if the system is not configured to process replies to notification, do not set the reply-to address to anything different than the sender</p></li><li class="listitem"><p>Notifications: proper cleanup of acs_objects resulting from the deletion of dynamic notification requests</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>User/Person/Party API: rework and rationalize caching of all party, person and user API, create separate caches for each of these types, make the API and return dicts. acs_user::get will not fail anymore with non-existing user.</p></li><li class="listitem"><p>User Portrait: created API to retrieve and create, store and delete the user's portrait. Also address leftover child relationships from the past and delete them properly.</p></li></ul></div><p>
+		</p></li></ul></div><p>
+	</p></li><li class="listitem"><p>Non-functional Changes
+	</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>Improved automated regression test infrastructure and test coverage
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>All packages in the <code class="computeroutput">oacs-5-10</code> branch pass regression test</p></li><li class="listitem"><p>Web testing was separated from non-maintained tcltest and was built on the standard OpenACS infrastructure</p></li><li class="listitem"><p>Include web testing per default in standard regression testing</p></li><li class="listitem"><p>Introduced new test authentication authority, allowing to run many user administration tests outside the context of a "real authority": in cases where the real authority depends on external services to proof identity, (e.g. Kerberos), those tests would just fail.</p></li><li class="listitem"><p>Introduce the display of warnings in the UI</p></li><li class="listitem"><p>Added test coverage information in the automated testing pages, using the new proc-coverage API and providing test coverage information for packages and system wide.</p></li><li class="listitem"><p>Increased overall coverage of public API</p></li><li class="listitem"><p>New tests checking various data-model properties and smells
+			</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>Improved scalability:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>
+			</p><p>Provided lock-free implementation of <code class="computeroutput">ad_page_contract_filters</code> and <code class="computeroutput">ad_page_contract_filter_rules</code>. This change improves parallel processing of requests and is primarily interesting for sites with a few mio page views per days. These locks were among the most frequent nsv locks</p><p>
+			</p></li><li class="listitem"><p>
+			</p><p>Reduced locks on util_memoize_cache my more invariants values into per-thread caching (<code class="computeroutput">acs_lookup_magic_object</code>, <code class="computeroutput">ad_acs_version</code>, .... ) and by avoiding specialized calls, which can be realized by already optimized ones (<code class="computeroutput">apm_package_installed_p_not_cached ref-timezones</code> was most frequently used util_memoize_cache entry). These changes are necessary to avoid full still-stand on the unfortunate long-time locks on util_memoize_cache stemming from permission and user management with wild-card flush operations, which require to iterate over all cache entries (which might be on a busy server several hundred thousands)</p><p>
+			</p></li><li class="listitem"><p>
+			</p><p>Added new interface for cache partitioning to reduce lock latencies on high load websites</p><p>
+			</p></li><li class="listitem"><p>
+			</p><p>Added new interface for lock-free per-thread and per-request caching to avoid scattered ad-hoc implementations</p><p>
+			</p></li><li class="listitem"><p>
+			</p><p>Better reuse of DB handles (reduced expiring/reopen/etc.), faster access to handles</p><p>
+			</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>Improved startup time:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>When the package acs-automated-testing is disabled, startup time is reduced by avoiding loading of support functions and tests; the size of the blueprint is reduced</p></li><li class="listitem"><p>xowf: loading of at-jobs is significantly improved.</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>Security improvements:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>Strengthened page contracts</p></li><li class="listitem"><p>CSP support for application packages</p></li><li class="listitem"><p>CSP fine tuning
+			 </p></li></ul></div><p>
+		</p></li><li class="listitem"><p>Better exception handling based on Tcl 8.6 exception handlers (<code class="computeroutput">try</code> and <code class="computeroutput">throw</code>, also available in Tcl 8.5)
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>Provided a new <code class="computeroutput">ad_try</code> implementation based on Tcl's <code class="computeroutput">try</code> replaces now the old <code class="computeroutput">ad_try</code>, <code class="computeroutput">with_catch</code> and <code class="computeroutput">with_finally</code>, which are marked as deprecated</p></li><li class="listitem"><p>The new <code class="computeroutput">ad_try</code> is in essence Tcl's <code class="computeroutput">try</code> but with predefined handling of <code class="computeroutput">ad_script_abort</code> and should be also used instead of <code class="computeroutput">catch</code>, when the OpenACS API is used (which might use script aborts)</p></li><li class="listitem"><p>All core packages use the new <code class="computeroutput">ad_try</code> instead of the deprecated versions.</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>Connection close reform:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>NaviServer/AOLserver continue after connection closing commands to execute a script. This is in many situations not desired, especially, when for the page as well a .adp file exists, which will try to deliver this on the already closed connection. This can lead to errors in the error.log file, which are sometimes hard to analyze</p></li><li class="listitem"><p>Due to this cleanup, developers should use in most such cases cases <code class="computeroutput">ad_script_abort</code></p></li><li class="listitem"><p>Connection closing commands are e.g. <code class="computeroutput">ad_returnredirect</code>, <code class="computeroutput">ad_redirect_for_registration</code>, <code class="computeroutput">cr_write_content</code>, <code class="computeroutput">ad_page_contract_handle_datasource_error</code>, <code class="computeroutput">ad_return_string_as_file</code>, <code class="computeroutput">ad_return_complaint</code>, <code class="computeroutput">ad_return_error</code>, <code class="computeroutput">ad_return_forbidden</code>, <code class="computeroutput">ad_return_warning</code>, <code class="computeroutput">ad_return_exception_page</code>, <code class="computeroutput">ns_returnredirect</code>, <code class="computeroutput">ns_return</code>, <code class="computeroutput">ns_returnerror</code></p></li><li class="listitem"><p>The new version has made on most occasions explicit, when the script should abort.</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>API changes (new and extended API calls):
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>New API call <code class="computeroutput">category::get</code> to obtain category description for a category_id and locale</p></li><li class="listitem"><p>New utility <code class="computeroutput">ad_pad</code> emulating both lpad and rpad typically available in DBMSs</p></li><li class="listitem"><p>New proc lc_content_size_pretty, prettify data size given in bytes. It supports three different standards (SI base-10, IEC base-2 and the old JEDEC base-2), default is SI base-10.</p></li><li class="listitem"><p>New flag <code class="computeroutput">-export</code> for <code class="computeroutput">ad_form</code>: this flag uses <code class="computeroutput">export_vars</code> under the hood and supports all of this API's features (e.g. :multiple, :sign, :array). This addresses a long standing TODO</p></li><li class="listitem"><p><code class="computeroutput">util::pdfinfo</code>: simple poppler-utils wrapper to extract pdf information</p></li><li class="listitem"><p>util::http: leverage new ns_http features such as request file spooling. Native implementation will now be used only on NaviServer &gt;= 4.99.15.</p></li><li class="listitem"><p>Database API:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><code class="computeroutput">db_foreach</code>: queries executed inside of a db_foreach will not be issued using a different handle and will therefore be safe to use in a transaction</p></li><li class="listitem"><p><code class="computeroutput">db_list_of_lists</code>: new <code class="computeroutput">-with_headers</code> flag, which will make the first element of the returned list to be the column names as defined in the query</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>Groups API:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Logics to delete a group type have now been included in the API</p></li><li class="listitem"><p>Allow to filter group members by member_state in the API</p></li></ul></div><p>
+			</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>Deprecated commands:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>Many deprecated API calls were included in the code (and sometimes still in use) sometimes more than 10 years after these calls have been deprecated. In case a site modification still uses deprecated code, the user is warned about this. The OpenACS 5.10 code base does not depend on deprecated code.</p></li><li class="listitem"><p>Move deprecated code into separate files</p></li><li class="listitem"><p>Made loading of deprecated code optional (can be controlled via parameter "WithDeprecatedCode" in section "ns_section ns/server/${server}/acs" of the config file. By default, deprecated procs are still loaded</p></li><li class="listitem"><p>When deprecated code is not loaded, the blueprint of the interpreter is smaller. The following number of lines of code can be omitted when loading without the deprecated procs:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>acs-tcl: 3178</p></li><li class="listitem"><p>acs-templating: 450</p></li><li class="listitem"><p>xotcl-core http-client-procs: 830</p></li><li class="listitem"><p>acs-content-repository: 1717 (including .xql files)</p></li></ul></div><p>
+			</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>Bugfix and Code Maintenance:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>Made sure all party emails are stored as lowercase through the API</p></li><li class="listitem"><p>Fixed long standing regression in template::list: we were looping through the list "elements", rather than the "display_elements". This prevents specifying different sets of columns to be returned depending on the <code class="computeroutput">-formats</code> and <code class="computeroutput">-selected_format</code> options in template::list::create.</p></li><li class="listitem"><p>acs-content-repository: New HEIC and HEIF mimetypes</p></li><li class="listitem"><p>acs-mail-lite: handle <code class="computeroutput">to_addr</code> specified as "DisplayName &lt;email&gt;" without errors</p></li><li class="listitem"><p>Fixed invalidating of all existing user logins, (aka) "Logout from everywhere" feature, useful e.g. to make sure no device still holds a valid login when we change our password on a device</p></li><li class="listitem"><p>Don't lose the return URL when one tries to join a subsite before being logged in</p></li><li class="listitem"><p>Added <code class="computeroutput">doc(base_href) </code>and <code class="computeroutput">doc(base_target)</code> for setting &lt;base&gt; element via blank-baster (see issue #3435)</p></li><li class="listitem"><p>Groups:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>When a new group is created, flush all the group::get_id caches with the same name so that the new group can be fetched correctly in case it replaces a previously deleted one</p></li><li class="listitem"><p>Cleanup message keys coming from groups in acs-translations when a group is deleted</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>acs-lang:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><code class="computeroutput">lang::util::convert_to_i18n</code>: do not always register a en_US translation, which would be always overridden. Instead, let <code class="computeroutput">lang::message::register</code> make sure that a en_US message exists and create one only as a fallback.</p></li><li class="listitem"><p><code class="computeroutput">lc_time_fmt</code>: leverage Tcl clock to address shortcomings such as handling of dates in Julian/Gregorian calendar and impossible dates such as 1999-02-29, implement missing formats, support previously undocumented formats explicitly</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>search: make sure objects in the search indexer queue still exist by the time they are swept by the indexer (e.g. items deleted before the indexer could sweep them)</p></li><li class="listitem"><p><code class="computeroutput">attribute::delete</code>: fix proc so it leverages stored procedure capability of dropping the database table as well</p></li><li class="listitem"><p><code class="computeroutput">util::http</code>: fix UTF-8 encoding issues for some cornercases</p></li><li class="listitem"><p>Localization: Complete Italian and Spanish localization for the whole .LRN set of packages (including themes). Message keys for new and previously localized packages have also been updated</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>General cleanup/maintenance
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>Improved handling of server implementation-specific code: server-specific code can be optionally loaded via specifying the server family in the filename. Provided <code class="computeroutput">*-procs-aolserver.tcl</code> and <code class="computeroutput">*-procs-naviserver.tcl</code> similar to *.postgresql.xql and *.oracle.xql where appropriate</p></li><li class="listitem"><p>Modernization of Tcl idioms.</p></li><li class="listitem"><p>Compliance of files, proc names, ... to the naming conventions.</p></li><li class="listitem"><p>White space cleanup, indentation changes.</p></li><li class="listitem"><p>Improvement of public API documentation</p></li><li class="listitem"><p>Adjustment of proc protection levels (public, private)</p></li><li class="listitem"><p>Adjustment of log severity</p></li><li class="listitem"><p>Cleanup of obsolete files</p></li><li class="listitem"><p>Replacement of handcrafted forms by ad_form</p></li><li class="listitem"><p>Typo fixing</p></li><li class="listitem"><p>Editor hints</p></li><li class="listitem"><p>Replacement of deprecated calls</p></li><li class="listitem"><p>Addition of missing contracts</p></li><li class="listitem"><p>...</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>SQL cleanup:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>Cleanup of obsolete nonportable SQL constructs in a way Oracle and PostgreSQL code base divergency is reduced:
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>"nvl" -&gt; "coalesce"</p></li><li class="listitem"><p>"sysdate" / "now()" -&gt; standard "current_date" or "current_timestamp"</p></li><li class="listitem"><p>Use standard-compliant "dual" table where appropriate (required by Oracle, supported by PostgreSQL)</p></li><li class="listitem"><p>Use non-dialectal cast idioms when appropriate</p></li><li class="listitem"><p>Adopt CTE idioms in Oracle codebase as well (e.g. connect -&gt; with recursive)</p></li><li class="listitem"><p>... (reference Oracle version will be 11gr2 as is oldest version officially supported by Oracle (See <a class="ulink" href="http://www.oracle.com/us/support/library/lifetime-support-technology-069183.pdf" target="_top">here</a> and <a class="ulink" href="https://n4stack.io/oracle-11g-end-of-life/" target="_top">here</a>)</p></li></ul></div><p>
+			</p></li><li class="listitem"><p>Reduced superfluous .xql queries
+			</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>acs-subsite: delete 21 files with un-referenced .xql queries</p></li><li class="listitem"><p>acs-tcl: delete 4 files</p></li><li class="listitem"><p>news: 3 files</p></li><li class="listitem"><p>file-storage: 1 file</p></li><li class="listitem"><p>dotlrn: 9 files</p></li></ul></div><p>
+			</p></li></ul></div><p>
+		</p></li><li class="listitem"><p>New Packages:
+		</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: square; "><li class="listitem"><p>cookie-consent: alerting users about the use of cookies on a website</p></li><li class="listitem"><p>boomerang: performance of your website from your end user’s point of view</p></li><li class="listitem"><p>xooauth: OAuth implementation, including LTI (Learning Tools Interoperability)</p></li><li class="listitem"><p>dotlrn-bootstrap3-theme: Bootstrap 3 theme for DotLRN</p></li><li class="listitem"><p>xowf-monaco-plugin: Integration of Monaco editor with for code exercise types in xowf</p></li><li class="listitem"><p>proctoring-support: utilities and user interfaces to implement proctoring of the user session, mainly intended in the context of distance education and online exams. The main proctoring feature relies only on web technologies and does not require any plugin or additional software. Optional support for the Safe Exam Browser has also been introduced. The package is currently at the core of WU Online Exam infrastructure and is integrated in the inclass exam implementation for xowf</p></li></ul></div><p>
+		</p></li></ul></div><p>
+	</p></li><li class="listitem"><p>Require Tcl 8.6, XOTcl 2.1, PostgreSQL 9.6 (PostgreSQL 9.5 EOL: <a class="ulink" href="https://www.postgresql.org/support/versioning/" target="_top">February 2021</a>), tdom 0.9</p></li></ul></div><p> Altogether, OpenACS 5.10.0 differs from OpenACS 5.9.1 by the
+following statistics
+</p><pre class="programlisting">
+ 3442 files changed, 120847 insertions(+), 92002 deletions(-) 
+</pre><p>
+contributed by 7 committers (Antonio Pisano, Gustaf Neumann, Günter Ernst, Hector Romojaro, Michael Aram, Stefan Sobernig, Thomas Renner) and additional 13 patch/bugfix providers (Felix Mödritscher, Florian Mosböck, Frank Bergmann, Franz Penz, Hanifa Hasan, Keith Paskett, Markus Moser, Maurizio Martignano, Monika Andergassen, Nathan Coulter, Rainer Bachleitner, Stephan Adelsberger, Tony Kirkham).
+
+All packages of
+the release were tested with PostgreSQL 13.* and Tcl 8.6.*.
+</p><p>
+  For more details, consult the
+  <a class="ulink" href="http://openacs.org/changelogs/ChangeLog-5.10.0" target="_top">raw ChangeLog</a>.
+</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="release-notes-5-9-1"></a>Release 5.9.1</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
 	The release of OpenACS 5.9.1 contains the 88 packages of the oacs-5-9
 	branch.  These packages include the OpenACS core packages, the major
 	application packages (e.g. most the ones used on OpenACS.org), and
@@ -875,7 +980,7 @@
     </pre><p>
     contributed by 4 committers (Michael Aram, Victor Guerra, Gustaf Neumann, Antonio Pisano) and
     patch/bugfix providers (Frank Bergmann, Andrew Helsley, Felix
-    Mödritscher, Marcos Moser, Franz Penz, Thomas Renner).
+    Mödritscher, Markus Moser, Franz Penz, Thomas Renner).
     These are significantly more  changes as the differences
     in the last releases. All packages of the release were tested with
     PostgreSQL 9.4.* and Tcl 8.5.*.
@@ -1181,4 +1286,4 @@
         </p></li><li class="listitem"><p>
           Serving backup files and files from the CVS directories is turned off by default via the acs-kernel parameter
           ExcludedFiles in section request-processor (The variable provides a string match glob list of files and is defaulted to "*/CVS/* *~")
-        </p></li></ul></div><div class="cvstag">($Id$)</div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665973421504"></a>Release 4.6.3</h3></div></div></div><p><a class="ulink" href="release-notes-4-6-3.html" target="_top">Release Notes for 4.6.3</a></p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665973423008"></a>Release 4.6.2</h3></div></div></div><p><a class="ulink" href="release-notes-4-6-2.html" target="_top">Release Notes for 4.6.2</a></p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665973424512"></a>Release 4.6</h3></div></div></div><p><a class="ulink" href="release-notes-4-6.html" target="_top">Release Notes for 4.6</a></p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665973426016"></a>Release 4.5</h3></div></div></div><p><a class="ulink" href="release-notes-4-5.html" target="_top">Release Notes for 4.5</a></p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="openacs-overview.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="acs-admin.html">Next</a></td></tr><tr><td width="40%" align="left">Overview </td><td width="20%" align="center"><a accesskey="u" href="general-documents.html">Up</a></td><td width="40%" align="right"> Part II. Administrator's Guide</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
+        </p></li></ul></div><div class="cvstag">($Id$)</div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698012445936"></a>Release 4.6.3</h3></div></div></div><p><a class="ulink" href="release-notes-4-6-3.html" target="_top">Release Notes for 4.6.3</a></p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698012447440"></a>Release 4.6.2</h3></div></div></div><p><a class="ulink" href="release-notes-4-6-2.html" target="_top">Release Notes for 4.6.2</a></p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698012448944"></a>Release 4.6</h3></div></div></div><p><a class="ulink" href="release-notes-4-6.html" target="_top">Release Notes for 4.6</a></p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698012450448"></a>Release 4.5</h3></div></div></div><p><a class="ulink" href="release-notes-4-5.html" target="_top">Release Notes for 4.5</a></p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="openacs-overview.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="acs-admin.html">Next</a></td></tr><tr><td width="40%" align="left">Overview </td><td width="20%" align="center"><a accesskey="u" href="general-documents.html">Up</a></td><td width="40%" align="right"> Part II. Administrator's Guide</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/tutorial-css-layout.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-css-layout.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/tutorial-css-layout.adp	3 Sep 2021 09:15:31 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/tutorial-css-layout.adp	7 Sep 2021 09:39:39 -0000	1.4.2.6
@@ -12,7 +12,7 @@
 <a name="tutorial-css-layout" id="tutorial-css-layout"></a>Laying out a page with CSS instead of
 tables</h2></div></div></div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665975834128" id="idp140665975834128"></a>.LRN home page with table-based
+<a name="idp140697194135744" id="idp140697194135744"></a>.LRN home page with table-based
 layout</h3></div></div></div><div class="mediaobject" align="center"><img src="images/dotlrn-style-1.png" align="middle"></div><p>A sample of the HTML code (<a class="ulink" href="files/dotlrn-style-1" target="_top">full source</a>)</p><pre class="programlisting">&lt;table border="0" width="100%"&gt;
   &lt;tr&gt;
     &lt;td valign="top" width="50%"&gt;
@@ -38,7 +38,7 @@
                         MBA 101</pre>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665975839488" id="idp140665975839488"></a>.LRN Home with CSS-based layout</h3></div></div></div><div class="mediaobject" align="center"><img src="images/dotlrn-style-3.png" align="middle"></div><p>A sample of the HTML code (<a class="ulink" href="files/dotlrn-style-2" target="_top">full source</a>)</p><pre class="programlisting">&lt;div class="left"&gt;
+<a name="idp140697194140752" id="idp140697194140752"></a>.LRN Home with CSS-based layout</h3></div></div></div><div class="mediaobject" align="center"><img src="images/dotlrn-style-3.png" align="middle"></div><p>A sample of the HTML code (<a class="ulink" href="files/dotlrn-style-2" target="_top">full source</a>)</p><pre class="programlisting">&lt;div class="left"&gt;
   &lt;div class="portlet-wrap-shadow"&gt;
     &lt;div class="portlet-wrap-bl"&gt;
       &lt;div class="portlet-wrap-tr"&gt;
Index: openacs-4/packages/acs-core-docs/www/tutorial-css-layout.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-css-layout.html,v
diff -u -r1.15.2.4 -r1.15.2.5
--- openacs-4/packages/acs-core-docs/www/tutorial-css-layout.html	3 Sep 2021 09:15:31 -0000	1.15.2.4
+++ openacs-4/packages/acs-core-docs/www/tutorial-css-layout.html	7 Sep 2021 09:39:39 -0000	1.15.2.5
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Laying out a page with CSS instead of tables</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="tutorial-advanced.html" title="Chapter 10. Advanced Topics"><link rel="previous" href="tutorial-vuh.html" title="Using .vuh files for pretty URLs"><link rel="next" href="tutorial-html-email.html" title="Sending HTML email from your application"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="tutorial-vuh.html">Prev</a> </td><th width="60%" align="center">Chapter 10. Advanced Topics</th><td width="20%" align="right"> <a accesskey="n" href="tutorial-html-email.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tutorial-css-layout"></a>Laying out a page with CSS instead of tables</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665975834128"></a>.LRN home page with table-based layout</h3></div></div></div><div class="mediaobject" align="center"><img src="images/dotlrn-style-1.png" align="middle"></div><p>A sample of the HTML code (<a class="ulink" href="files/dotlrn-style-1.html" target="_top">full source</a>)</p><pre class="programlisting">&lt;table border="0" width="100%"&gt;
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Laying out a page with CSS instead of tables</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="tutorial-advanced.html" title="Chapter 10. Advanced Topics"><link rel="previous" href="tutorial-vuh.html" title="Using .vuh files for pretty URLs"><link rel="next" href="tutorial-html-email.html" title="Sending HTML email from your application"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="tutorial-vuh.html">Prev</a> </td><th width="60%" align="center">Chapter 10. Advanced Topics</th><td width="20%" align="right"> <a accesskey="n" href="tutorial-html-email.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tutorial-css-layout"></a>Laying out a page with CSS instead of tables</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697194135744"></a>.LRN home page with table-based layout</h3></div></div></div><div class="mediaobject" align="center"><img src="images/dotlrn-style-1.png" align="middle"></div><p>A sample of the HTML code (<a class="ulink" href="files/dotlrn-style-1.html" target="_top">full source</a>)</p><pre class="programlisting">&lt;table border="0" width="100%"&gt;
   &lt;tr&gt;
     &lt;td valign="top" width="50%"&gt;
       &lt;table class="element" border="0" cellpadding="0" cellspacing="0" width="100%"&gt;
@@ -21,7 +21,7 @@
                   &lt;table border="0" bgcolor="white" cellpadding="0" cellspacing="0" width="100%"&gt;
                     &lt;tr&gt;
                       &lt;td class=element-text&gt;
-                        MBA 101</pre></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665975839488"></a>.LRN Home with CSS-based layout</h3></div></div></div><div class="mediaobject" align="center"><img src="images/dotlrn-style-3.png" align="middle"></div><p>A sample of the HTML code (<a class="ulink" href="files/dotlrn-style-2.html" target="_top">full source</a>)</p><pre class="programlisting">&lt;div class="left"&gt;
+                        MBA 101</pre></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697194140752"></a>.LRN Home with CSS-based layout</h3></div></div></div><div class="mediaobject" align="center"><img src="images/dotlrn-style-3.png" align="middle"></div><p>A sample of the HTML code (<a class="ulink" href="files/dotlrn-style-2.html" target="_top">full source</a>)</p><pre class="programlisting">&lt;div class="left"&gt;
   &lt;div class="portlet-wrap-shadow"&gt;
     &lt;div class="portlet-wrap-bl"&gt;
       &lt;div class="portlet-wrap-tr"&gt;
Index: openacs-4/packages/acs-core-docs/www/tutorial-cvs.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-cvs.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/tutorial-cvs.adp	3 Sep 2021 09:15:31 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/tutorial-cvs.adp	7 Sep 2021 09:39:39 -0000	1.4.2.6
@@ -69,7 +69,7 @@
 done
 <span class="emphasis"><em>(many lines omitted)</em></span>
 [$OPENACS_SERVICE_NAME myfirstpackage]$</pre><div class="figure">
-<a name="idp140665976169280" id="idp140665976169280"></a><p class="title"><strong>Figure 10.1. Upgrading a local
+<a name="idp140697193935072" id="idp140697193935072"></a><p class="title"><strong>Figure 10.1. Upgrading a local
 CVS repository</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/development-with-cvs.png" align="middle" alt="Upgrading a local CVS repository"></div></div>
 </div><br class="figure-break">
 </div>
Index: openacs-4/packages/acs-core-docs/www/tutorial-cvs.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-cvs.html,v
diff -u -r1.29.2.4 -r1.29.2.5
--- openacs-4/packages/acs-core-docs/www/tutorial-cvs.html	3 Sep 2021 09:15:31 -0000	1.29.2.4
+++ openacs-4/packages/acs-core-docs/www/tutorial-cvs.html	7 Sep 2021 09:39:39 -0000	1.29.2.5
@@ -59,4 +59,4 @@
 initial revision: 1.1
 done
 <span class="emphasis"><em>(many lines omitted)</em></span>
-[$OPENACS_SERVICE_NAME myfirstpackage]$</pre><div class="figure"><a name="idp140665976169280"></a><p class="title"><b>Figure 10.1. Upgrading a local CVS repository</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/development-with-cvs.png" align="middle" alt="Upgrading a local CVS repository"></div></div></div><br class="figure-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="tutorial-specs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="tutorial-etp-templates.html">Next</a></td></tr><tr><td width="40%" align="left">Write the Requirements and Design Specs </td><td width="20%" align="center"><a accesskey="u" href="tutorial-advanced.html">Up</a></td><td width="40%" align="right"> OpenACS Edit This Page Templates</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
+[$OPENACS_SERVICE_NAME myfirstpackage]$</pre><div class="figure"><a name="idp140697193935072"></a><p class="title"><b>Figure 10.1. Upgrading a local CVS repository</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/development-with-cvs.png" align="middle" alt="Upgrading a local CVS repository"></div></div></div><br class="figure-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="tutorial-specs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="tutorial-etp-templates.html">Next</a></td></tr><tr><td width="40%" align="left">Write the Requirements and Design Specs </td><td width="20%" align="center"><a accesskey="u" href="tutorial-advanced.html">Up</a></td><td width="40%" align="right"> OpenACS Edit This Page Templates</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
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 -r1.4.2.6 -r1.4.2.7
--- openacs-4/packages/acs-core-docs/www/tutorial-database.adp	3 Sep 2021 09:15:31 -0000	1.4.2.6
+++ openacs-4/packages/acs-core-docs/www/tutorial-database.adp	7 Sep 2021 09:39:39 -0000	1.4.2.7
@@ -15,7 +15,7 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823261808" id="idp140665823261808"></a>Code the data model</h3></div></div></div><p>We create all database objects with scripts in the <code class="computeroutput">myfirstpackage/sql/</code> directory. All database
+<a name="idp140698007115040" id="idp140698007115040"></a>Code the data model</h3></div></div></div><p>We create all database objects with scripts in the <code class="computeroutput">myfirstpackage/sql/</code> directory. All database
 scripts are database-specific and are thus in either the
 <code class="computeroutput">myfirstpackage/sql/oracle</code> or
 <code class="computeroutput">myfirstpackage/sql/postgresql</code>
@@ -42,15 +42,15 @@
 simplify our database creation. (<a class="ulink" href="objects" target="_top">More information about ACS
 Objects</a>. <a class="ulink" href="/doc/acs-content-repository" target="_top">More information about the Content
 Repository</a>.)</p><div class="figure">
-<a name="idp140665823975504" id="idp140665823975504"></a><p class="title"><strong>Figure 9.2. Tutorial Data
+<a name="idp140698002449680" id="idp140698002449680"></a><p class="title"><strong>Figure 9.2. Tutorial Data
 Model</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/tutorial-data-model.png" align="middle" alt="Tutorial Data Model"></div></div>
 </div><br class="figure-break"><p>The top of each SQL file has some standard comments, including
 doc tags such as <code class="computeroutput">\@author</code> which
 will be picked up by the API browser. The string <code class="computeroutput">$&zwnj;Id:$</code> will automatically be expanded when
 the file is checked in to cvs.</p><pre class="screen">[$OPENACS_SERVICE_NAME ~]$ <strong class="userinput"><code>cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/myfirstpackage/sql/postgresql</code></strong>
 [$OPENACS_SERVICE_NAME postgresql]$ <strong class="userinput"><code>emacs myfirstpackage-create.sql</code></strong>
 </pre><p>Paste the text below into the file, save, and close.</p><div class="figure">
-<a name="idp140665822795008" id="idp140665822795008"></a><p class="title"><strong>Figure 9.3. The Database
+<a name="idp140698006946784" id="idp140698006946784"></a><p class="title"><strong>Figure 9.3. The Database
 Creation Script</strong></p><div class="figure-contents"><pre class="programlisting">-- creation script
 --
 -- \@author joel\@aufrecht.org
@@ -79,7 +79,7 @@
 uninstalled.</p><pre class="screen">
 [$OPENACS_SERVICE_NAME postgresql]$ <strong class="userinput"><code>emacs myfirstpackage-drop.sql</code></strong>
 </pre><div class="figure">
-<a name="idp140665823594672" id="idp140665823594672"></a><p class="title"><strong>Figure 9.4. Database Deletion
+<a name="idp140698007213488" id="idp140698007213488"></a><p class="title"><strong>Figure 9.4. Database Deletion
 Script</strong></p><div class="figure-contents"><pre class="programlisting">-- drop script
 --
 -- \@author joel\@aufrecht.org
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 -r1.47.2.4 -r1.47.2.5
--- openacs-4/packages/acs-core-docs/www/tutorial-database.html	3 Sep 2021 09:15:32 -0000	1.47.2.4
+++ openacs-4/packages/acs-core-docs/www/tutorial-database.html	7 Sep 2021 09:39:39 -0000	1.47.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Setting Up Database Objects</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="tutorial.html" title="Chapter 9. Development Tutorial"><link rel="previous" href="tutorial-newpackage.html" title="Creating an Application Package"><link rel="next" href="tutorial-pages.html" title="Creating Web Pages"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="tutorial-newpackage.html">Prev</a> </td><th width="60%" align="center">Chapter 9. Development Tutorial</th><td width="20%" align="right"> <a accesskey="n" href="tutorial-pages.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tutorial-database"></a>Setting Up Database Objects</h2></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:joel@aufrecht.org" target="_top">Joel Aufrecht</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823261808"></a>Code the data model</h3></div></div></div><p>We create all database objects with scripts in the
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698007115040"></a>Code the data model</h3></div></div></div><p>We create all database objects with scripts in the
       <code class="computeroutput">myfirstpackage/sql/</code> directory.  All
       database scripts are database-specific and are thus in either
       the <code class="computeroutput">myfirstpackage/sql/oracle</code> or
@@ -32,13 +32,13 @@
       repository functions to simplify our database creation.  (<a class="ulink" href="objects.html" target="_top">More
       information about ACS Objects</a>.  <a class="ulink" href="/doc/acs-content-repository" target="_top">More information about the
       Content Repository</a>.)
-</p><div class="figure"><a name="idp140665823975504"></a><p class="title"><b>Figure 9.2. Tutorial Data Model</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/tutorial-data-model.png" align="middle" alt="Tutorial Data Model"></div></div></div><br class="figure-break"><p>The top of each SQL file has some
+</p><div class="figure"><a name="idp140698002449680"></a><p class="title"><b>Figure 9.2. Tutorial Data Model</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/tutorial-data-model.png" align="middle" alt="Tutorial Data Model"></div></div></div><br class="figure-break"><p>The top of each SQL file has some
       standard comments, including doc tags such as
       <code class="computeroutput">@author</code> which will be picked up
       by the API browser.  The string
       <code class="computeroutput">$Id$</code> will automatically be
       expanded when the file is checked in to cvs.</p><pre class="screen">[$OPENACS_SERVICE_NAME ~]$ <strong class="userinput"><code>cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/myfirstpackage/sql/postgresql</code></strong>
-[$OPENACS_SERVICE_NAME postgresql]$ <strong class="userinput"><code>emacs myfirstpackage-create.sql</code></strong></pre><p>Paste the text below into the file, save, and close.</p><div class="figure"><a name="idp140665822795008"></a><p class="title"><b>Figure 9.3. The Database Creation Script</b></p><div class="figure-contents"><pre class="programlisting">-- creation script
+[$OPENACS_SERVICE_NAME postgresql]$ <strong class="userinput"><code>emacs myfirstpackage-create.sql</code></strong></pre><p>Paste the text below into the file, save, and close.</p><div class="figure"><a name="idp140698006946784"></a><p class="title"><b>Figure 9.3. The Database Creation Script</b></p><div class="figure-contents"><pre class="programlisting">-- creation script
 --
 -- @author joel@aufrecht.org
 -- @cvs-id &amp;Id:$
@@ -62,7 +62,7 @@
     object.  Notice the use of "mfp."  This is derived from "My
     First Package" and ensures that our object is unlikely to conflict
     with objects from other packages.</p><p>Create a database file to drop everything if the package is uninstalled.</p><pre class="screen">
-[$OPENACS_SERVICE_NAME postgresql]$ <strong class="userinput"><code>emacs myfirstpackage-drop.sql</code></strong></pre><div class="figure"><a name="idp140665823594672"></a><p class="title"><b>Figure 9.4. Database Deletion Script</b></p><div class="figure-contents"><pre class="programlisting">-- drop script
+[$OPENACS_SERVICE_NAME postgresql]$ <strong class="userinput"><code>emacs myfirstpackage-drop.sql</code></strong></pre><div class="figure"><a name="idp140698007213488"></a><p class="title"><b>Figure 9.4. Database Deletion Script</b></p><div class="figure-contents"><pre class="programlisting">-- drop script
 --
 -- @author joel@aufrecht.org
 -- @cvs-id &amp;Id:$
Index: openacs-4/packages/acs-core-docs/www/tutorial-debug.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-debug.adp,v
diff -u -r1.4.2.6 -r1.4.2.7
--- openacs-4/packages/acs-core-docs/www/tutorial-debug.adp	3 Sep 2021 09:15:32 -0000	1.4.2.6
+++ openacs-4/packages/acs-core-docs/www/tutorial-debug.adp	7 Sep 2021 09:39:40 -0000	1.4.2.7
@@ -15,7 +15,7 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665976225984" id="idp140665976225984"></a>Debugging</h3></div></div></div><p>
+<a name="idp140698454688112" id="idp140698454688112"></a>Debugging</h3></div></div></div><p>
 <strong>Developer Support. </strong>The Developer Support
 package adds several goodies: debug information for every page; the
 ability to log comments to the page instead of the error log, and
@@ -41,7 +41,7 @@
           </p></div>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665975334544" id="idp140665975334544"></a>Manual testing</h3></div></div></div><p>Make a list of basic tests to make sure it works</p><div class="segmentedlist"><table border="0">
+<a name="idp140698013069520" id="idp140698013069520"></a>Manual testing</h3></div></div></div><p>Make a list of basic tests to make sure it works</p><div class="segmentedlist"><table border="0">
 <thead><tr class="segtitle">
 <th>Test Num</th><th>Action</th><th>Expected Result</th>
 </tr></thead><tbody>
@@ -69,11 +69,11 @@
 to delete your own note. Edit your own note. Search for a note.</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665976136896" id="idp140665976136896"></a>Write automated tests</h3></div></div></div><div class="authorblurb">
+<a name="idp140698012904112" id="idp140698012904112"></a>Write automated tests</h3></div></div></div><div class="authorblurb">
 <p>by <a class="ulink" href="mailto:simon\@collaboraid.net" target="_top">Simon Carstensen</a> and Joel Aufrecht</p>
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><p>
-<a class="indexterm" name="idp140665976138944" id="idp140665976138944"></a> It seems to me that a lot of people have
+<a class="indexterm" name="idp140698012906160" id="idp140698012906160"></a> It seems to me that a lot of people have
 been asking for some guidelines on how to write automated tests.
 I&#39;ve done several tests by now and have found the process to be
 extremely easy and useful. It&#39;s a joy to work with automated
@@ -139,7 +139,7 @@
 myfirstpackage. You should see your test case. Run it and examine
 the results.</p><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665975457184" id="idp140665975457184"></a>TCLWebtest tests</h4></div></div></div><p>API testing can only test part of our package - it doesn&#39;t
+<a name="idp140698012615728" id="idp140698012615728"></a>TCLWebtest tests</h4></div></div></div><p>API testing can only test part of our package - it doesn&#39;t
 test the code in our adp/tcl pairs. For this, we can use
 TCLwebtest. TCLwebtest must be <a class="link" href="install-tclwebtest" title="Install tclwebtest.">installed</a>
 for this test to work. This provides a <a class="ulink" href="http://tclwebtest.sourceforge.net/doc/api_public.html" target="_top">library of functions</a> that make it easy to call a page
@@ -149,7 +149,7 @@
 integrating them.</p>
 </div><div class="sect3">
 <div class="titlepage"><div><div><h4 class="title">
-<a name="idp140665975459744" id="idp140665975459744"></a>Example</h4></div></div></div><p>Now we can add the rest of the API tests, including a test with
+<a name="idp140698012995552" id="idp140698012995552"></a>Example</h4></div></div></div><p>Now we can add the rest of the API tests, including a test with
 deliberately bad data. The complete test looks like:</p><pre class="programlisting">ad_library {
     Test cases for my first package.
 }
Index: openacs-4/packages/acs-core-docs/www/tutorial-debug.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-debug.html,v
diff -u -r1.46.2.4 -r1.46.2.5
--- openacs-4/packages/acs-core-docs/www/tutorial-debug.html	3 Sep 2021 09:15:32 -0000	1.46.2.4
+++ openacs-4/packages/acs-core-docs/www/tutorial-debug.html	7 Sep 2021 09:39:40 -0000	1.46.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Debugging and Automated Testing</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="tutorial.html" title="Chapter 9. Development Tutorial"><link rel="previous" href="tutorial-pages.html" title="Creating Web Pages"><link rel="next" href="tutorial-advanced.html" title="Chapter 10. Advanced Topics"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="tutorial-pages.html">Prev</a> </td><th width="60%" align="center">Chapter 9. Development Tutorial</th><td width="20%" align="right"> <a accesskey="n" href="tutorial-advanced.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tutorial-debug"></a>Debugging and Automated Testing</h2></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:joel@aufrecht.org" target="_top">Joel Aufrecht</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665976225984"></a>Debugging</h3></div></div></div><p><b>Developer Support. </b>The Developer Support package adds several goodies: debug
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698454688112"></a>Debugging</h3></div></div></div><p><b>Developer Support. </b>The Developer Support package adds several goodies: debug
       information for every page; the ability to log comments to the
       page instead of the error log, and fast user switching so that you
       can test pages as anonymous and as dummy users without logging
@@ -23,16 +23,16 @@
 ? searches backward <br>
 / searches forward. <br>
           </p></div><p>
-    </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665975334544"></a>Manual testing</h3></div></div></div><p>Make a list of basic tests to make sure it works</p><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Test Num</th><th>Action</th><th>Expected Result</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">001</td><td class="seg">Browse to the index page while not logged in and
+    </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698013069520"></a>Manual testing</h3></div></div></div><p>Make a list of basic tests to make sure it works</p><div class="segmentedlist"><table border="0"><thead><tr class="segtitle"><th>Test Num</th><th>Action</th><th>Expected Result</th></tr></thead><tbody><tr class="seglistitem"><td class="seg">001</td><td class="seg">Browse to the index page while not logged in and
             while one or more notes exist.</td><td class="seg">No edit or delete or add links should appear.</td></tr><tr class="seglistitem"><td class="seg">002</td><td class="seg">Browse to the index page while logged in.  An Edit
             link should appear.  Click on it.  Fill out the form and
             click Submit.</td><td class="seg">The text added in the form should be visible on the
             index page.</td></tr><tr class="seglistitem"><td class="seg">API-001</td><td class="seg">Invoke mfp::note::create with a specific word as the title.</td><td class="seg">Proc should return an object id.</td></tr><tr class="seglistitem"><td class="seg">API-002</td><td class="seg">Given an object id from API-001, invoke mfp::note::get.</td><td class="seg">Proc should return the specific word in the title.</td></tr><tr class="seglistitem"><td class="seg">API-003</td><td class="seg">Given the object id from API-001, invoke mfp::note::delete.</td><td class="seg">Proc should return 0 for success.</td></tr></tbody></table></div><p>Other things to test: try to delete someone else's
         note.  Try to delete your own note.  Edit your own note.
-        Search for a note.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665976136896"></a>Write automated tests</h3></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:simon@collaboraid.net" target="_top">Simon Carstensen</a> and Joel Aufrecht</p>
+        Search for a note.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698012904112"></a>Write automated tests</h3></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:simon@collaboraid.net" target="_top">Simon Carstensen</a> and Joel Aufrecht</p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><p><a class="indexterm" name="idp140665976138944"></a>
+        </div><p><a class="indexterm" name="idp140698012906160"></a>
     It seems to me that a lot of people have been asking for some guidelines on how to write automated tests. I've done several tests by now and have found the process to be extremely easy and useful. It's a joy to work with automated testing once you get the hang of it.</p><p>Create the directory that will contain the test
     script and edit the script file.  The directory location and filename are standards which are recognized by the automated testing package:</p><pre class="screen">[$OPENACS_SERVICE_NAME www]$<strong class="userinput"><code> mkdir /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/myfirstpackage/tcl/test</code></strong>
 [$OPENACS_SERVICE_NAME www]$<strong class="userinput"><code> cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/myfirstpackage/tcl/test</code></strong>
@@ -68,7 +68,7 @@
 goes inside <code class="computeroutput">-test_code {}</code>.  We want to implement test case API-001, "Given an object id from API-001, invoke mfp::note::get.  Proc should return the specific word in the title."</p><pre class="programlisting">
       set name [ad_generate_random_string]
       set new_id [mfp::note::add -title $name]
-      aa_true "Note add succeeded" {$new_id ne ""}</pre><p>To test our simple case, we must load the test file into the system (just as with the /tcl file in the basic tutorial, since the file didn't exist when the system started, the system doesn't know about it.)  To make this file take effect, go to the <a class="ulink" href="/acs-admin/apm" target="_top">APM</a> and choose "Reload changed" for "MyFirstPackage".  Since we'll be changing it frequently, select "watch this file" on the next page.  This will cause the system to check this file every time any page is requested, which is bad for production systems but convenient for developing.  We can also add some aa_register_case flags to make it easier to run the test.  The <code class="computeroutput">-procs</code> flag, which indicates which procs are tested by this test case, makes it easier to find procs in your package that aren't tested at all.  The <code class="computeroutput">-cats</code> flag, setting categories, makes it easier to control which tests to run.  The <code class="computeroutput">smoke</code> test setting means that this is a basic test case that can and should be run any time you are doing any test. (<a class="ulink" href="http://www.nedbatchelder.com/blog/20030408T062805.html" target="_top">a definition of "smoke test"</a>)</p><p>Once the file is loaded, go to <a class="ulink" href="/test" target="_top">ACS Automated Testing</a> and click on myfirstpackage.  You should see your test case.  Run it and examine the results.</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665975457184"></a>TCLWebtest tests</h4></div></div></div><p>API testing can only test part of our package - it doesn't test the code in our adp/tcl pairs.  For this, we can use TCLwebtest.  TCLwebtest must be <a class="link" href="install-tclwebtest.html" title="Install tclwebtest.">installed</a> for this test to work.  This provides a <a class="ulink" href="http://tclwebtest.sourceforge.net/doc/api_public.html" target="_top">library of functions</a> that make it easy to call a page through HTTP, examine the results, and drive forms.  TCLwebtest's functions overlap slightly with acs-automated-testing; see the example provided for one approach on integrating them.</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140665975459744"></a>Example</h4></div></div></div><p>Now we can add the rest of the API tests, including a test with deliberately bad data.  The complete test looks like:</p><pre class="programlisting">ad_library {
+      aa_true "Note add succeeded" {$new_id ne ""}</pre><p>To test our simple case, we must load the test file into the system (just as with the /tcl file in the basic tutorial, since the file didn't exist when the system started, the system doesn't know about it.)  To make this file take effect, go to the <a class="ulink" href="/acs-admin/apm" target="_top">APM</a> and choose "Reload changed" for "MyFirstPackage".  Since we'll be changing it frequently, select "watch this file" on the next page.  This will cause the system to check this file every time any page is requested, which is bad for production systems but convenient for developing.  We can also add some aa_register_case flags to make it easier to run the test.  The <code class="computeroutput">-procs</code> flag, which indicates which procs are tested by this test case, makes it easier to find procs in your package that aren't tested at all.  The <code class="computeroutput">-cats</code> flag, setting categories, makes it easier to control which tests to run.  The <code class="computeroutput">smoke</code> test setting means that this is a basic test case that can and should be run any time you are doing any test. (<a class="ulink" href="http://www.nedbatchelder.com/blog/20030408T062805.html" target="_top">a definition of "smoke test"</a>)</p><p>Once the file is loaded, go to <a class="ulink" href="/test" target="_top">ACS Automated Testing</a> and click on myfirstpackage.  You should see your test case.  Run it and examine the results.</p><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698012615728"></a>TCLWebtest tests</h4></div></div></div><p>API testing can only test part of our package - it doesn't test the code in our adp/tcl pairs.  For this, we can use TCLwebtest.  TCLwebtest must be <a class="link" href="install-tclwebtest.html" title="Install tclwebtest.">installed</a> for this test to work.  This provides a <a class="ulink" href="http://tclwebtest.sourceforge.net/doc/api_public.html" target="_top">library of functions</a> that make it easy to call a page through HTTP, examine the results, and drive forms.  TCLwebtest's functions overlap slightly with acs-automated-testing; see the example provided for one approach on integrating them.</p></div><div class="sect3"><div class="titlepage"><div><div><h4 class="title"><a name="idp140698012995552"></a>Example</h4></div></div></div><p>Now we can add the rest of the API tests, including a test with deliberately bad data.  The complete test looks like:</p><pre class="programlisting">ad_library {
     Test cases for my first package.
 }
 
Index: openacs-4/packages/acs-core-docs/www/tutorial-distribute.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-distribute.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/tutorial-distribute.adp	3 Sep 2021 09:15:32 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/tutorial-distribute.adp	7 Sep 2021 09:39:40 -0000	1.4.2.6
@@ -13,7 +13,7 @@
 distribution.</h2></div></div></div><p>Browse to the package manager. Click on <code class="computeroutput"><span class="guilabel"><span class="guilabel">tutorialapp</span></span></code>.</p><p>Click on <code class="computeroutput"><span class="guilabel"><span class="guilabel">Generate a distribution file for
 this package from the filesystem</span></span></code>.</p><p>Click on the file size (<code class="computeroutput"><span class="guilabel"><span class="guilabel">37.1KB</span></span></code>) after the label
 <code class="computeroutput"><span class="guilabel"><span class="guilabel">Distribution File:</span></span></code> and save the
-file to /var/tmp.</p><p><a class="indexterm" name="idp140665976049392" id="idp140665976049392"></a></p><p><a class="ulink" href="http://openacs.org/forums/message-view?message_id=192919" target="_top">Package development guidelines</a></p>
+file to /var/tmp.</p><p><a class="indexterm" name="idp140697194080608" id="idp140697194080608"></a></p><p><a class="ulink" href="http://openacs.org/forums/message-view?message_id=192919" target="_top">Package development guidelines</a></p>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"
 			leftLink="profile-code" leftLabel="Prev" leftTitle="Profile your code"
Index: openacs-4/packages/acs-core-docs/www/tutorial-distribute.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-distribute.html,v
diff -u -r1.29.2.4 -r1.29.2.5
--- openacs-4/packages/acs-core-docs/www/tutorial-distribute.html	3 Sep 2021 09:15:32 -0000	1.29.2.4
+++ openacs-4/packages/acs-core-docs/www/tutorial-distribute.html	7 Sep 2021 09:39:40 -0000	1.29.2.5
@@ -7,5 +7,5 @@
         (<code class="computeroutput"><span class="guilabel"><span class="guilabel">37.1KB</span></span></code>)
         after the label <code class="computeroutput"><span class="guilabel"><span class="guilabel">Distribution
         File:</span></span></code> and save the file to
-        /var/tmp.</p><p><a class="indexterm" name="idp140665976049392"></a>
+        /var/tmp.</p><p><a class="indexterm" name="idp140697194080608"></a>
 </p><p><a class="ulink" href="http://openacs.org/forums/message-view?message_id=192919" target="_top">Package development guidelines</a></p></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="profile-code.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="tutorial-upgrades.html">Next</a></td></tr><tr><td width="40%" align="left">Profile your code </td><td width="20%" align="center"><a accesskey="u" href="tutorial-advanced.html">Up</a></td><td width="40%" align="right"> Distributing upgrades of your package</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/tutorial-etp-templates.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-etp-templates.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/tutorial-etp-templates.adp	3 Sep 2021 09:15:32 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/tutorial-etp-templates.adp	7 Sep 2021 09:39:41 -0000	1.4.2.6
@@ -80,7 +80,7 @@
 </li><li class="listitem">
 <p>The template should provide us with the following ETP
 layout:</p><div class="table">
-<a name="idp140665975851424"></a><p class="title"><strong>Table 10.1. table showing ETP
+<a name="idp140697193965744"></a><p class="title"><strong>Table 10.1. table showing ETP
 layout</strong></p><div class="table-contents"><table class="table" summary="table showing ETP layout" cellspacing="0" border="1" width="250">
 <colgroup>
 <col align="left" class="c1"><col width="2" align="left" class="c2">
Index: openacs-4/packages/acs-core-docs/www/tutorial-etp-templates.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-etp-templates.html,v
diff -u -r1.12.2.4 -r1.12.2.5
--- openacs-4/packages/acs-core-docs/www/tutorial-etp-templates.html	3 Sep 2021 09:15:33 -0000	1.12.2.4
+++ openacs-4/packages/acs-core-docs/www/tutorial-etp-templates.html	7 Sep 2021 09:39:41 -0000	1.12.2.5
@@ -13,5 +13,5 @@
             cvs -d:pserver:anonymous@openacs.org:/cvsroot co edit-this-page</pre></li><li class="listitem"><p>Go to the package manager at http://yoursite/acs-admin/apm. And install  the new package: edit-this-page.</p></li><li class="listitem"><p>Or use the "Add Application" form available on the Main site.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="exercise3"></a>Change ETP Application</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Work out how to change the ETP application.</p></li><li class="listitem"><p>Investigate each of the available ETP templates:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>Default</p></li><li class="listitem"><p>News</p></li><li class="listitem"><p>FAQ</p></li></ul></div></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="exercise4"></a>Exercise 4: Create a New ETP Template</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Browse the files for each of the above ETP templates at:</p><pre class="screen">cd ~/openacs/packages/edit-this-page/templates</pre></li><li class="listitem"><p>Use the article template as the basis of our new col2 template.</p><pre class="screen">cp article-content.adp col2-content.adp
             cp article-content.tcl col2-content.tcl
             cp article-index.adp col2-index.adp
-            cp article-index.tcl col2-index.tcl</pre></li><li class="listitem"><p>The template should provide us with the following ETP layout:</p><div class="table"><a name="idp140665975851424"></a><p class="title"><b>Table 10.1. table showing ETP layout</b></p><div class="table-contents"><table class="table" summary="table showing ETP layout" cellspacing="0" border="1" width="250"><colgroup><col align="left" class="c1"><col width="2" align="left" class="c2"></colgroup><tbody><tr><td colspan="2" align="center">Header</td></tr><tr height="200"><td align="left">Sidebar</td><td align="left">Main Content Pane</td></tr></tbody></table></div></div><br class="table-break"></li><li class="listitem"><p>The "Main Content" pane should contain the editable content that ETP provides.</p></li><li class="listitem"><p>The "Header" should display the title of the page that you set in ETP.</p></li><li class="listitem"><p>The "Sidebar" should display the extlinks that you add as a content item in ETP.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="exercise5"></a>Exercise 5: Register the col2 Template with ETP</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Need to register your template with ETP so that it appears in the drop-down menu that you would have seen in Exercise 3.</p><pre class="screen">cd ~/openacs/packages/edit-this-page/tcl
+            cp article-index.tcl col2-index.tcl</pre></li><li class="listitem"><p>The template should provide us with the following ETP layout:</p><div class="table"><a name="idp140697193965744"></a><p class="title"><b>Table 10.1. table showing ETP layout</b></p><div class="table-contents"><table class="table" summary="table showing ETP layout" cellspacing="0" border="1" width="250"><colgroup><col align="left" class="c1"><col width="2" align="left" class="c2"></colgroup><tbody><tr><td colspan="2" align="center">Header</td></tr><tr height="200"><td align="left">Sidebar</td><td align="left">Main Content Pane</td></tr></tbody></table></div></div><br class="table-break"></li><li class="listitem"><p>The "Main Content" pane should contain the editable content that ETP provides.</p></li><li class="listitem"><p>The "Header" should display the title of the page that you set in ETP.</p></li><li class="listitem"><p>The "Sidebar" should display the extlinks that you add as a content item in ETP.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="exercise5"></a>Exercise 5: Register the col2 Template with ETP</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Need to register your template with ETP so that it appears in the drop-down menu that you would have seen in Exercise 3.</p><pre class="screen">cd ~/openacs/packages/edit-this-page/tcl
             emacs etp-custom-init.tcl</pre></li><li class="listitem"><p>Use the function etp::define_application to register your template with ETP</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p>Uncomment the "asc" definition</p></li><li class="listitem"><p>Set allow_extlinks to true, the rest should be false.</p></li></ul></div></li><li class="listitem"><p>Restart your server for the changes to take effect.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="exercise6"></a>Exercise 6: Configure ETP to use the col2 Template</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Configure your ETP instance at /lab4/index to use the col2 template.</p></li><li class="listitem"><p>Create external links to link to other mounted ETP instances.</p></li><li class="listitem"><p>Check that your external links show up in the sidebar when you view your ETP application using the col2 template.</p></li></ul></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="end"></a>Who Wrote This and When</h3></div></div></div><p>This problem set was originally written by Nick Carroll in August 2004 for the <a class="ulink" href="http://www.usyd.edu.au" target="_top">University of Sydney</a> Course EBUS5002.</p><p>This material is copyright 2004 by Nick Carroll.  It may be copied, reused, and modified, provided credit is given to the original author.</p><div class="cvstag">($Id$)</div></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="tutorial-cvs.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="tutorial-comments.html">Next</a></td></tr><tr><td width="40%" align="left">Add the new package to CVS </td><td width="20%" align="center"><a accesskey="u" href="tutorial-advanced.html">Up</a></td><td width="40%" align="right"> Adding Comments</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/tutorial-newpackage.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-newpackage.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/tutorial-newpackage.adp	3 Sep 2021 09:15:33 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/tutorial-newpackage.adp	7 Sep 2021 09:39:41 -0000	1.4.2.6
@@ -18,7 +18,7 @@
 <a name="tutorial-picture" id="tutorial-picture"></a>The intended page map</h3></div></div></div><div class="mediaobject"><img src="images/openacs-best-practice.png"></div>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823909680" id="idp140665823909680"></a>Overview</h3></div></div></div><p>To start developing new code in OpenACS, we build a new package.
+<a name="idp140697731927376" id="idp140697731927376"></a>Overview</h3></div></div></div><p>To start developing new code in OpenACS, we build a new package.
 A package is a discrete collection of web pages, Tcl code, and
 database tables and procedures. A package with user interface is
 called an <span class="strong"><strong>application</strong></span>;
@@ -36,14 +36,14 @@
 displaying a list of text notes.</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665824084928" id="idp140665824084928"></a>Before you begin</h3></div></div></div><p>You will need:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<a name="idp140697731647888" id="idp140697731647888"></a>Before you begin</h3></div></div></div><p>You will need:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem"><p>A computer with a working installation of OpenACS. If you
 don&#39;t have this, see <a class="xref" href="install-overview" title="Chapter 2. Installation Overview">Chapter 2,
 <em>Installation Overview</em>
 </a>.</p></li><li class="listitem"><p>Example files, which are included in the standard OpenACS 5.9.0
 distribution.</p></li>
 </ul></div><div class="figure">
-<a name="idp140665823728864" id="idp140665823728864"></a><p class="title"><strong>Figure 9.1. Assumptions in this
+<a name="idp140697463252912" id="idp140697463252912"></a><p class="title"><strong>Figure 9.1. Assumptions in this
 section</strong></p><div class="figure-contents"><div class="informaltable"><table class="informaltable" cellspacing="0" border="1">
 <colgroup>
 <col><col>
@@ -62,7 +62,7 @@
 </div><br class="figure-break">
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823926368" id="idp140665823926368"></a>Use the APM to initialize a new
+<a name="idp140697463260336" id="idp140697463260336"></a>Use the APM to initialize a new
 package</h3></div></div></div><p>We use the <a class="ulink" href="packages" target="_top">ACS Package Manager</a> (APM) to add, remove, and upgrade
 packages. It handles package meta-data, such as lists of files that
 belong in the package. Each package is uniquely identified by a
@@ -102,7 +102,7 @@
 packages</a>).</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823368256" id="idp140665823368256"></a>Add an Application Instance to the
+<a name="idp140697463280752" id="idp140697463280752"></a>Add an Application Instance to the
 Server</h3></div></div></div><p>In order to see your work in progress, you must create a map
 between the URL space of incoming requests and the package
 application instance. You do this by adding the application in the
@@ -121,7 +121,7 @@
 to be satisfied from the files at <code class="computeroutput">/var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/www</code>.</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140665823291280" id="idp140665823291280"></a>Quick start</h3></div></div></div><p>The remainder of the tutorial walks you through each file one at
+<a name="idp140697463288560" id="idp140697463288560"></a>Quick start</h3></div></div></div><p>The remainder of the tutorial walks you through each file one at
 a time as you create the package. You can skip all this, and get a
 working package, by doing the following:</p><pre class="screen">cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/acs-core-docs/www/files/tutorial
 psql <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span> -f myfirstpackage-create.sql
Index: openacs-4/packages/acs-core-docs/www/tutorial-newpackage.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/tutorial-newpackage.html,v
diff -u -r1.46.2.4 -r1.46.2.5
--- openacs-4/packages/acs-core-docs/www/tutorial-newpackage.html	3 Sep 2021 09:15:33 -0000	1.46.2.4
+++ openacs-4/packages/acs-core-docs/www/tutorial-newpackage.html	7 Sep 2021 09:39:41 -0000	1.46.2.5
@@ -2,7 +2,7 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Creating an Application Package</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="tutorial.html" title="Chapter 9. Development Tutorial"><link rel="previous" href="tutorial.html" title="Chapter 9. Development Tutorial"><link rel="next" href="tutorial-database.html" title="Setting Up Database Objects"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="tutorial.html">Prev</a> </td><th width="60%" align="center">Chapter 9. Development Tutorial</th><td width="20%" align="right"> <a accesskey="n" href="tutorial-database.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tutorial-newpackage"></a>Creating an Application Package</h2></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:joel@aufrecht.org" target="_top">Joel Aufrecht</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="tutorial-picture"></a>The intended page map</h3></div></div></div><div class="mediaobject"><img src="images/openacs-best-practice.png"></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823909680"></a>Overview</h3></div></div></div><p>To start developing new code in OpenACS, we build a new package. A package 
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="tutorial-picture"></a>The intended page map</h3></div></div></div><div class="mediaobject"><img src="images/openacs-best-practice.png"></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697731927376"></a>Overview</h3></div></div></div><p>To start developing new code in OpenACS, we build a new package. A package 
       is a discrete collection of web pages, Tcl code, and database tables and procedures.
       A package with user interface is called an <span class="strong"><strong>application</strong></span>; 
       a package which provides functions to other packages and has no direct interface, a
@@ -18,11 +18,11 @@
         right now.  Code that is temporary hackage is clearly marked.
       </p><p>In this tutorial, we will make an application package for
     displaying a list of text notes.
-</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665824084928"></a>Before you begin</h3></div></div></div><p>You will need:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>A computer with a working installation of
+</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697731647888"></a>Before you begin</h3></div></div></div><p>You will need:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>A computer with a working installation of
 	  OpenACS.  If you don't have this, see <a class="xref" href="install-overview.html" title="Chapter 2. Installation Overview">Chapter 2, <i>Installation Overview</i></a>.
 	  </p></li><li class="listitem"><p>Example files, which are included in the
 standard OpenACS 5.9.0 distribution.
-	  </p></li></ul></div><div class="figure"><a name="idp140665823728864"></a><p class="title"><b>Figure 9.1. Assumptions in this section</b></p><div class="figure-contents"><div class="informaltable"><table class="informaltable" cellspacing="0" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Fully qualified domain name of your server</td><td><span class="replaceable"><span class="replaceable">yourserver.test</span></span></td></tr><tr><td>URL of your server</td><td><span class="replaceable"><span class="replaceable">http://yourserver.test:8000</span></span></td></tr><tr><td>Name of development account</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>New Package key</td><td><span class="replaceable"><span class="replaceable">myfirstpackage</span></span></td></tr></tbody></table></div></div></div><br class="figure-break"></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823926368"></a>Use the APM to initialize a new package</h3></div></div></div><p>We use the <a class="ulink" href="packages.html" target="_top">ACS Package Manager</a> (APM) to add, remove, and
+	  </p></li></ul></div><div class="figure"><a name="idp140697463252912"></a><p class="title"><b>Figure 9.1. Assumptions in this section</b></p><div class="figure-contents"><div class="informaltable"><table class="informaltable" cellspacing="0" border="1"><colgroup><col><col></colgroup><tbody><tr><td>Fully qualified domain name of your server</td><td><span class="replaceable"><span class="replaceable">yourserver.test</span></span></td></tr><tr><td>URL of your server</td><td><span class="replaceable"><span class="replaceable">http://yourserver.test:8000</span></span></td></tr><tr><td>Name of development account</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>New Package key</td><td><span class="replaceable"><span class="replaceable">myfirstpackage</span></span></td></tr></tbody></table></div></div></div><br class="figure-break"></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697463260336"></a>Use the APM to initialize a new package</h3></div></div></div><p>We use the <a class="ulink" href="packages.html" target="_top">ACS Package Manager</a> (APM) to add, remove, and
     upgrade packages.  It handles package meta-data, such as lists of
     files that belong in the package.  Each package is uniquely
     identified by a package key.  To start developing a new
@@ -55,7 +55,7 @@
           <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/<span class="replaceable"><span class="replaceable">myfirstpackage</span></span></code>.
           This is the "home directory" of our new package, and all
           files in the package will be within this directory. <a class="ulink" href="packages.html" target="_top">More on the structure of
-          packages</a>). </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823368256"></a>Add an Application Instance to the Server</h3></div></div></div><p>In order to see your work in progress, you must create a
+          packages</a>). </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697463280752"></a>Add an Application Instance to the Server</h3></div></div></div><p>In order to see your work in progress, you must create a
       map between the URL space of incoming requests and the package application instance.
       You do this by adding the application in the main site administration).  This
       creates a link between the incoming URL requests and an
@@ -66,7 +66,7 @@
       in this tutorial.</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Browse to
 <code class="computeroutput"><span class="replaceable"><span class="replaceable">http://yourserver.test:8000</span></span><a class="ulink" href="/admin/applications/application-add" target="_top">/admin/applications/application-add/</a></code>.</p></li><li class="listitem"><p>Choose "My First Package" from the list and click OK (the other fields are optional).</p></li></ol></div><p>By mounting the package, we've caused all requests to
       <code class="computeroutput">http://yourserver.test:8000/myfirstpackage</code>
-      to be satisfied from the files at <code class="computeroutput">/var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/www</code>.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140665823291280"></a>Quick start</h3></div></div></div><p>The remainder of the tutorial walks you through each file one at a time as you create the package.  You can skip all this, and get a working package, by doing the following:</p><pre class="screen">cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/acs-core-docs/www/files/tutorial
+      to be satisfied from the files at <code class="computeroutput">/var/lib/aolserver/$OPENACS_SERVICE_NAME/packages/myfirstpackage/www</code>.</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697463288560"></a>Quick start</h3></div></div></div><p>The remainder of the tutorial walks you through each file one at a time as you create the package.  You can skip all this, and get a working package, by doing the following:</p><pre class="screen">cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/acs-core-docs/www/files/tutorial
 psql <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span> -f myfirstpackage-create.sql
 cp note-edit.* note-delete.tcl index.* ../../../../myfirstpackage/www/
 mkdir ../../../../myfirstpackage/lib
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 -r1.6.2.5 -r1.6.2.6
--- openacs-4/packages/acs-core-docs/www/tutorial-pages.adp	3 Sep 2021 09:15:34 -0000	1.6.2.5
+++ openacs-4/packages/acs-core-docs/www/tutorial-pages.adp	7 Sep 2021 09:39:41 -0000	1.6.2.6
@@ -15,23 +15,23 @@
 OpenACS docs are written by the named authors, and may be edited by
 OpenACS documentation staff.</div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140666274138304" id="idp140666274138304"></a>Install some API</h3></div></div></div><p>As a workaround for missing content-repository functionality,
+<a name="idp140697730234592" id="idp140697730234592"></a>Install some API</h3></div></div></div><p>As a workaround for missing content-repository functionality,
 copy a provided file into the directory for Tcl files:</p><pre class="screen"><span class="action"><span class="action">cp /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/acs-core-docs/www/files/tutorial/note-procs.tcl /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/myfirstpackage/tcl/</span></span></pre><p>To make this file take effect, go to the <a class="ulink" href="/acs-admin/apm" target="_top">APM</a> and choose "Reload
 changed" for "MyFirstPackage".</p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140666274142960" id="idp140666274142960"></a>Page Map</h3></div></div></div><p>Our package will have two visible pages. The first shows a list
+<a name="idp140697731406448" id="idp140697731406448"></a>Page Map</h3></div></div></div><p>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&#39;ll put it in a separate file and include it on the index
 page.</p><div class="figure">
-<a name="idp140666274144384" id="idp140666274144384"></a><p class="title"><strong>Figure 9.5. Page
+<a name="idp140697731362544" id="idp140697731362544"></a><p class="title"><strong>Figure 9.5. Page
 Map</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/tutorial-page-map.png" align="middle" alt="Page Map"></div></div>
 </div><br class="figure-break">
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140666274147440" id="idp140666274147440"></a>Build the "Index" page</h3></div></div></div><p>Each user-visible page in your package has, typically, three
+<a name="idp140697193479920" id="idp140697193479920"></a>Build the "Index" page</h3></div></div></div><p>Each user-visible page in your package has, typically, three
 parts. The <code class="computeroutput">tcl</code> file holds the
 procedural logic for the page, including Tcl and
 database-independent SQL code, and does things like check
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 -r1.49.2.4 -r1.49.2.5
--- openacs-4/packages/acs-core-docs/www/tutorial-pages.html	3 Sep 2021 09:15:34 -0000	1.49.2.4
+++ openacs-4/packages/acs-core-docs/www/tutorial-pages.html	7 Sep 2021 09:39:42 -0000	1.49.2.5
@@ -2,8 +2,8 @@
 <html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Creating Web Pages</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="tutorial.html" title="Chapter 9. Development Tutorial"><link rel="previous" href="tutorial-database.html" title="Setting Up Database Objects"><link rel="next" href="tutorial-debug.html" title="Debugging and Automated Testing"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="tutorial-database.html">Prev</a> </td><th width="60%" align="center">Chapter 9. Development Tutorial</th><td width="20%" align="right"> <a accesskey="n" href="tutorial-debug.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="tutorial-pages"></a>Creating Web Pages</h2></div></div></div><div class="authorblurb"><p>by <a class="ulink" href="mailto:joel@aufrecht.org" target="_top">Joel Aufrecht</a></p>
           OpenACS docs are written by the named authors, and may be edited
           by OpenACS documentation staff.
-        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140666274138304"></a>Install some API</h3></div></div></div><p>As a workaround for missing content-repository functionality, copy a provided file into the directory for Tcl files:</p><pre class="screen">
-    <span class="action"><span class="action">cp /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/acs-core-docs/www/files/tutorial/note-procs.tcl /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/myfirstpackage/tcl/</span></span></pre><p>To make this file take effect, go to the <a class="ulink" href="/acs-admin/apm" target="_top">APM</a> and choose "Reload changed" for "MyFirstPackage".</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140666274142960"></a>Page Map</h3></div></div></div><p>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.</p><div class="figure"><a name="idp140666274144384"></a><p class="title"><b>Figure 9.5. Page Map</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/tutorial-page-map.png" align="middle" alt="Page Map"></div></div></div><br class="figure-break"></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140666274147440"></a>Build the "Index" page</h3></div></div></div><p>Each user-visible page in your package has, typically,
+        </div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697730234592"></a>Install some API</h3></div></div></div><p>As a workaround for missing content-repository functionality, copy a provided file into the directory for Tcl files:</p><pre class="screen">
+    <span class="action"><span class="action">cp /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/acs-core-docs/www/files/tutorial/note-procs.tcl /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/packages/myfirstpackage/tcl/</span></span></pre><p>To make this file take effect, go to the <a class="ulink" href="/acs-admin/apm" target="_top">APM</a> and choose "Reload changed" for "MyFirstPackage".</p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697731406448"></a>Page Map</h3></div></div></div><p>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.</p><div class="figure"><a name="idp140697731362544"></a><p class="title"><b>Figure 9.5. Page Map</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/tutorial-page-map.png" align="middle" alt="Page Map"></div></div></div><br class="figure-break"></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140697193479920"></a>Build the "Index" page</h3></div></div></div><p>Each user-visible page in your package has, typically,
       three parts.  The  <code class="computeroutput">tcl</code> 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/upgrade-4.5-to-4.6.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.adp,v
diff -u -r1.4.2.6 -r1.4.2.7
--- openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.adp	3 Sep 2021 09:15:36 -0000	1.4.2.6
+++ openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.adp	7 Sep 2021 09:39:42 -0000	1.4.2.7
@@ -8,7 +8,7 @@
 			rightLink="upgrade-4.6.3-to-5" rightLabel="Next">
 		    <div class="sect1">
 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
-<a name="upgrade-4.5-to-4.6" id="upgrade-4.5-to-4.6"></a>Upgrading 4.5 or higher to 4.6.3</h2></div></div></div><a class="indexterm" name="idp140666101895040" id="idp140666101895040"></a><p>The required platform for OpenACS 4.6 is the same as 4.5, with
+<a name="upgrade-4.5-to-4.6" id="upgrade-4.5-to-4.6"></a>Upgrading 4.5 or higher to 4.6.3</h2></div></div></div><a class="indexterm" name="idp140698012076496" id="idp140698012076496"></a><p>The required platform for OpenACS 4.6 is the same as 4.5, with
 the exception of OpenFTS. OpenACS 4.6 and later require OpenFTS
 0.3.2 for full text search on PostGreSQL. If you have OpenFTS 0.2,
 you&#39;ll need to upgrade.</p><p>If upgrading from 4.4, you need to manually run
Index: openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html,v
diff -u -r1.30.2.4 -r1.30.2.5
--- openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html	3 Sep 2021 09:15:36 -0000	1.30.2.4
+++ openacs-4/packages/acs-core-docs/www/upgrade-4.5-to-4.6.html	7 Sep 2021 09:39:42 -0000	1.30.2.5
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Upgrading 4.5 or higher to 4.6.3</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="upgrade.html" title="Chapter 5. Upgrading"><link rel="previous" href="upgrade-overview.html" title="Overview"><link rel="next" href="upgrade-4.6.3-to-5.html" title="Upgrading OpenACS 4.6.3 to 5.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="upgrade-overview.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Upgrading</th><td width="20%" align="right"> <a accesskey="n" href="upgrade-4.6.3-to-5.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="upgrade-4.5-to-4.6"></a>Upgrading 4.5 or higher to 4.6.3</h2></div></div></div><a class="indexterm" name="idp140666101895040"></a><p>The required platform for OpenACS 4.6 is the same as
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Upgrading 4.5 or higher to 4.6.3</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="upgrade.html" title="Chapter 5. Upgrading"><link rel="previous" href="upgrade-overview.html" title="Overview"><link rel="next" href="upgrade-4.6.3-to-5.html" title="Upgrading OpenACS 4.6.3 to 5.0"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="upgrade-overview.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Upgrading</th><td width="20%" align="right"> <a accesskey="n" href="upgrade-4.6.3-to-5.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="upgrade-4.5-to-4.6"></a>Upgrading 4.5 or higher to 4.6.3</h2></div></div></div><a class="indexterm" name="idp140698012076496"></a><p>The required platform for OpenACS 4.6 is the same as
       4.5, with the exception of OpenFTS.  OpenACS 4.6 and later require OpenFTS 0.3.2 for full text search on PostGreSQL.  If you have OpenFTS 0.2, you'll need to upgrade.  </p><p>If upgrading from 4.4, you need to manually run acs-kernel/sql/postgres/upgrade-4.4-4.5.sql.  See <a class="ulink" href="http://openacs.org/bugtracker/openacs/bug?bug_number=632" target="_top">Bug #632</a></p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem" style="list-style-type: circle"><p>A computer with OpenACS 4.5.</p></li><li class="listitem" style="list-style-type: circle"><p><a class="ulink" href="http://openacs.org/projects/openacs/download/" target="_top">OpenACS 4.6 tarball</a> or CVS checkout/export.</p></li><li class="listitem" style="list-style-type: circle"><p>Required for Full Text Search on PostgreSQL: <a class="ulink" href="http://openfts.sourceforge.net" target="_top">OpenFTS 0.3.2</a></p></li></ul></div><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p><b>Make a Backup. </b>Back up the database and filesystem (see <a class="xref" href="snapshot-backup.html" title="Manual backup and recovery">the section called “Manual backup and recovery”</a>).</p></li><li class="listitem"><p><b>OPTIONAL: Upgrade OpenFTS. </b><a class="xref" href="upgrade-supporting.html#upgrade-openfts-0.2-to-0.3.2" title="Upgrading OpenFTS from 0.2 to 0.3.2">the section called “Upgrading OpenFTS from 0.2 to 0.3.2”</a></p></li><li class="listitem"><p>
             Stop the server
           </p><pre class="screen">[root root]# <strong class="userinput"><code>svc -d /service/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></code></strong></pre></li><li class="listitem"><p><b>Upgrade the filesystem. </b><a class="xref" href="upgrade-openacs-files.html" title="Upgrading the OpenACS files">the section called “Upgrading the OpenACS files”</a></p></li><li class="listitem"><p>
Index: openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.adp,v
diff -u -r1.5.2.6 -r1.5.2.7
--- openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.adp	3 Sep 2021 09:15:37 -0000	1.5.2.6
+++ openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.adp	7 Sep 2021 09:39:42 -0000	1.5.2.7
@@ -11,7 +11,7 @@
 <a name="upgrade-openacs-files" id="upgrade-openacs-files"></a>Upgrading
 the OpenACS files</h2></div></div></div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140666101984976" id="idp140666101984976"></a>Choosing a Method to Upgrade your
+<a name="idp140698011955248" id="idp140698011955248"></a>Choosing a Method to Upgrade your
 Files</h3></div></div></div><p>OpenACS is distributed in many different ways:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem"><p>as a collection of files</p></li><li class="listitem"><p>as one big tarball</p></li><li class="listitem"><p>via CVS</p></li><li class="listitem"><p>via automatic download from within the APM (package manager)</p></li>
 </ul></div><p>Upgrades work by first changing the filesystem (via any of the
@@ -25,7 +25,7 @@
 </p>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140666101990400" id="idp140666101990400"></a>Methods of upgrading OpenACS files</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
+<a name="idp140698011950704" id="idp140698011950704"></a>Methods of upgrading OpenACS files</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc;">
 <li class="listitem">
 <p>
 <strong>Upgrading files for a site which is not in a CVS
@@ -53,7 +53,7 @@
 version, without overriding your own local customizations.</p><p>This diagram explains the basic idea. However, the labels are
 incorrect. Step 1(a) has been removed, and Step 1(b) should be
 labelled Step 1.</p><div class="figure">
-<a name="idp140666102001360" id="idp140666102001360"></a><p class="title"><strong>Figure 5.2. Upgrading a local
+<a name="idp140698011926320" id="idp140698011926320"></a><p class="title"><strong>Figure 5.2. Upgrading a local
 CVS repository</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/upgrade-cvs.png" align="middle" alt="Upgrading a local CVS repository"></div></div>
 </div><br class="figure-break"><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle;">
 <li class="listitem">
@@ -180,7 +180,7 @@
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$</pre></li></ol></div>
 </div><div class="sect2">
 <div class="titlepage"><div><div><h3 class="title">
-<a name="idp140666102063872" id="idp140666102063872"></a>Upgrading a Production Site Safely</h3></div></div></div><p>If you are upgrading a production OpenACS site which is on a
+<a name="idp140698011786016" id="idp140698011786016"></a>Upgrading a Production Site Safely</h3></div></div></div><p>If you are upgrading a production OpenACS site which is on a
 private CVS tree, this process lets you do the upgrade without
 risking extended downtime or an unusable site:</p><div class="orderedlist"><ol class="orderedlist" type="1">
 <li class="listitem"><p>Declare a freeze on new cvs updates - ie, you cannot run cvs
Index: openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html,v
diff -u -r1.31.2.4 -r1.31.2.5
--- openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html	3 Sep 2021 09:15:37 -0000	1.31.2.4
+++ openacs-4/packages/acs-core-docs/www/upgrade-openacs-files.html	7 Sep 2021 09:39:42 -0000	1.31.2.5
@@ -1,5 +1,5 @@
 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" 'http://www.w3.org/TR/html4/loose.dtd"'>
-<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Upgrading the OpenACS files</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="upgrade.html" title="Chapter 5. Upgrading"><link rel="previous" href="upgrade-5-0-dot.html" title="Upgrading an OpenACS 5.0.0 or greater installation"><link rel="next" href="upgrade-supporting.html" title="Upgrading Platform components"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="upgrade-5-0-dot.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Upgrading</th><td width="20%" align="right"> <a accesskey="n" href="upgrade-supporting.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="upgrade-openacs-files"></a>Upgrading the OpenACS files</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140666101984976"></a>Choosing a Method to Upgrade your Files</h3></div></div></div><p>OpenACS is distributed in many different ways:
+<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"><title>Upgrading the OpenACS files</title><link rel="stylesheet" type="text/css" href="openacs.css"><meta name="generator" content="DocBook XSL Stylesheets Vsnapshot"><link rel="home" href="index.html" title="OpenACS Core Documentation"><link rel="up" href="upgrade.html" title="Chapter 5. Upgrading"><link rel="previous" href="upgrade-5-0-dot.html" title="Upgrading an OpenACS 5.0.0 or greater installation"><link rel="next" href="upgrade-supporting.html" title="Upgrading Platform components"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><a href="http://openacs.org"><img src="/doc/images/alex.jpg" style="border:0" alt="Alex logo"></a><table width="100%" summary="Navigation header" border="0"><tr><td width="20%" align="left"><a accesskey="p" href="upgrade-5-0-dot.html">Prev</a> </td><th width="60%" align="center">Chapter 5. Upgrading</th><td width="20%" align="right"> <a accesskey="n" href="upgrade-supporting.html">Next</a></td></tr></table><hr></div><div class="sect1"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a name="upgrade-openacs-files"></a>Upgrading the OpenACS files</h2></div></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011955248"></a>Choosing a Method to Upgrade your Files</h3></div></div></div><p>OpenACS is distributed in many different ways:
         </p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>as a collection of files</p></li><li class="listitem"><p> as one big tarball</p></li><li class="listitem"><p> via CVS</p></li><li class="listitem"><p> via automatic download from within the APM
             (package manager)</p></li></ul></div><p>
       </p><p>Upgrades work by first changing the filesystem (via any
@@ -11,7 +11,7 @@
         describes whether or not you need to be upgrading using this
         page or not:
         <a class="xref" href="upgrade-5-0-dot.html" title="Upgrading an OpenACS 5.0.0 or greater installation">the section called “Upgrading an OpenACS 5.0.0 or greater installation”</a>
-      </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140666101990400"></a>Methods of upgrading OpenACS files</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><b>Upgrading files for a site which is not in a CVS repository. </b>Unpack the tarball into a new directory and copy its
+      </p></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011950704"></a>Methods of upgrading OpenACS files</h3></div></div></div><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p><b>Upgrading files for a site which is not in a CVS repository. </b>Unpack the tarball into a new directory and copy its
           contents on top of your working directory. Or just 'install
           software', select remote repository, and upgrade your files
           from there.</p><pre class="screen">[root root]# <strong class="userinput"><code>su - <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></code></strong>
@@ -32,7 +32,7 @@
         with the latest OpenACS version, without overriding your own
         local customizations. </p><p>This diagram explains the basic idea. However, the
         labels are incorrect. Step 1(a) has been removed, and Step
-        1(b) should be labelled Step 1.</p><div class="figure"><a name="idp140666102001360"></a><p class="title"><b>Figure 5.2. Upgrading a local CVS repository</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/upgrade-cvs.png" align="middle" alt="Upgrading a local CVS repository"></div></div></div><br class="figure-break"><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p><b>Step 0: Set up a working CVS checkout. </b>To get your OpenACS code into your local CVS
+        1(b) should be labelled Step 1.</p><div class="figure"><a name="idp140698011926320"></a><p class="title"><b>Figure 5.2. Upgrading a local CVS repository</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/upgrade-cvs.png" align="middle" alt="Upgrading a local CVS repository"></div></div></div><br class="figure-break"><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: circle; "><li class="listitem"><p><b>Step 0: Set up a working CVS checkout. </b>To get your OpenACS code into your local CVS
                 repository, you will set up a working CVS checkout of
                 OpenACS. When you want to update your site, you'll
                 update the working CVS checkout, import those changes
@@ -97,7 +97,7 @@
       </p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><pre class="screen">[$OPENACS_SERVICE_NAME ~]$ <strong class="userinput"><code>cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></code></strong>
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>cvs up -Pd</code></strong>
 (CVS feedback)
-[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$</pre></li></ol></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140666102063872"></a>Upgrading a Production Site Safely</h3></div></div></div><p>If you are upgrading a production OpenACS site which is on a private CVS tree, this process lets you do the upgrade without risking extended downtime or an unusable site:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Declare a freeze on new cvs updates - ie, you cannot run cvs update
+[$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$</pre></li></ol></div></div><div class="sect2"><div class="titlepage"><div><div><h3 class="title"><a name="idp140698011786016"></a>Upgrading a Production Site Safely</h3></div></div></div><p>If you are upgrading a production OpenACS site which is on a private CVS tree, this process lets you do the upgrade without risking extended downtime or an unusable site:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Declare a freeze on new cvs updates - ie, you cannot run cvs update
    on the production site</p></li><li class="listitem"><p>
             Make a manual backup of the production site in addition to the
    automated backups</p></li><li class="listitem"><p>Import the new code (for example, OpenACS 5.0.4, openacs-5-0-compat versions of
Index: openacs-4/packages/acs-core-docs/www/upgrade-overview.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-overview.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/upgrade-overview.adp	3 Sep 2021 09:15:37 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/upgrade-overview.adp	7 Sep 2021 09:39:43 -0000	1.4.2.6
@@ -25,11 +25,11 @@
 upgrade scripts, and prompt you to restart the server. After
 restarting the server again, the upgrade is complete.</p></li>
 </ol></div><div class="figure">
-<a name="idp140666101883488" id="idp140666101883488"></a><p class="title"><strong>Figure 5.1. Upgrading with the
+<a name="idp140698011417872" id="idp140698011417872"></a><p class="title"><strong>Figure 5.1. Upgrading with the
 APM</strong></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/upgrade-apm.png" align="middle" alt="Upgrading with the APM"></div></div>
 </div><br class="figure-break"><p>It&#39;s always a good idea to precede an upgrade attempt with a
 <a class="link" href="snapshot-backup" title="Manual backup and recovery">snapshot backup</a>.</p><div class="table">
-<a name="idp140666101887168" id="idp140666101887168"></a><p class="title"><strong>Table 5.1. Assumptions in this
+<a name="idp140698012084400" id="idp140698012084400"></a><p class="title"><strong>Table 5.1. Assumptions in this
 section</strong></p><div class="table-contents"><table class="table" summary="Assumptions in this section" cellspacing="0" border="1">
 <colgroup>
 <col><col>
Index: openacs-4/packages/acs-core-docs/www/upgrade-overview.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/upgrade-overview.html,v
diff -u -r1.30.2.4 -r1.30.2.5
--- openacs-4/packages/acs-core-docs/www/upgrade-overview.html	3 Sep 2021 09:15:38 -0000	1.30.2.4
+++ openacs-4/packages/acs-core-docs/www/upgrade-overview.html	7 Sep 2021 09:39:43 -0000	1.30.2.5
@@ -4,4 +4,4 @@
     or better, you should always be able to upgrade all of your core
     packages automatically.  If you haven't changed anything, no
     manual intervention should be required.  If you are running
-    OpenACS prior to 4.5, upgrading will require manual effort.</p><p>If all of these conditions are true:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Your OpenACS Core is 5.0.0 or later</p></li><li class="listitem"><p>You do not keep your OpenACS site in a local CVS repository</p></li><li class="listitem"><p>You do not have any custom code</p></li></ul></div><p>then you can upgrade automatically using the automated installer in the OpenACS Package Manager (APM), and you can probably skip the rest of this chapter.  To upgrade directly from the OpenACS repository using the APM:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Browse to the <a class="ulink" href="/acs-admin/install/" target="_top">Installer</a>.</p></li><li class="listitem"><p>Click install or upgrade under "Install from OpenACS Repository" and select the packages to install or upgrade.</p></li><li class="listitem"><p>The APM will download the requested packages from OpenACS.org, install the files on your hard drive, run any appropriate database upgrade scripts, and prompt you to restart the server.  After restarting the server again, the upgrade is complete.</p></li></ol></div><div class="figure"><a name="idp140666101883488"></a><p class="title"><b>Figure 5.1. Upgrading with the APM</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/upgrade-apm.png" align="middle" alt="Upgrading with the APM"></div></div></div><br class="figure-break"><p>It's always a good idea to precede an upgrade attempt with a <a class="link" href="snapshot-backup.html" title="Manual backup and recovery">snapshot backup</a>.</p><div class="table"><a name="idp140666101887168"></a><p class="title"><b>Table 5.1. Assumptions in this section</b></p><div class="table-contents"><table class="table" summary="Assumptions in this section" cellspacing="0" border="1"><colgroup><col><col></colgroup><tbody><tr><td>name of OpenACS user</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>OpenACS server name</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>Root of OpenACS file tree</td><td><span class="replaceable"><span class="replaceable">/var/lib/aolserver/$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>Database backup directory</td><td><span class="replaceable"><span class="replaceable">/var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup</span></span></td></tr></tbody></table></div></div><br class="table-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="upgrade.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrade-4.5-to-4.6.html">Next</a></td></tr><tr><td width="40%" align="left">Chapter 5. Upgrading </td><td width="20%" align="center"><a accesskey="u" href="upgrade.html">Up</a></td><td width="40%" align="right"> Upgrading 4.5 or higher to 4.6.3</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
+    OpenACS prior to 4.5, upgrading will require manual effort.</p><p>If all of these conditions are true:</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>Your OpenACS Core is 5.0.0 or later</p></li><li class="listitem"><p>You do not keep your OpenACS site in a local CVS repository</p></li><li class="listitem"><p>You do not have any custom code</p></li></ul></div><p>then you can upgrade automatically using the automated installer in the OpenACS Package Manager (APM), and you can probably skip the rest of this chapter.  To upgrade directly from the OpenACS repository using the APM:</p><div class="orderedlist"><ol class="orderedlist" type="1"><li class="listitem"><p>Browse to the <a class="ulink" href="/acs-admin/install/" target="_top">Installer</a>.</p></li><li class="listitem"><p>Click install or upgrade under "Install from OpenACS Repository" and select the packages to install or upgrade.</p></li><li class="listitem"><p>The APM will download the requested packages from OpenACS.org, install the files on your hard drive, run any appropriate database upgrade scripts, and prompt you to restart the server.  After restarting the server again, the upgrade is complete.</p></li></ol></div><div class="figure"><a name="idp140698011417872"></a><p class="title"><b>Figure 5.1. Upgrading with the APM</b></p><div class="figure-contents"><div class="mediaobject" align="center"><img src="images/upgrade-apm.png" align="middle" alt="Upgrading with the APM"></div></div></div><br class="figure-break"><p>It's always a good idea to precede an upgrade attempt with a <a class="link" href="snapshot-backup.html" title="Manual backup and recovery">snapshot backup</a>.</p><div class="table"><a name="idp140698012084400"></a><p class="title"><b>Table 5.1. Assumptions in this section</b></p><div class="table-contents"><table class="table" summary="Assumptions in this section" cellspacing="0" border="1"><colgroup><col><col></colgroup><tbody><tr><td>name of OpenACS user</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>OpenACS server name</td><td><span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>Root of OpenACS file tree</td><td><span class="replaceable"><span class="replaceable">/var/lib/aolserver/$OPENACS_SERVICE_NAME</span></span></td></tr><tr><td>Database backup directory</td><td><span class="replaceable"><span class="replaceable">/var/lib/aolserver/$OPENACS_SERVICE_NAME/database-backup</span></span></td></tr></tbody></table></div></div><br class="table-break"></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="upgrade.html">Prev</a> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right"> <a accesskey="n" href="upgrade-4.5-to-4.6.html">Next</a></td></tr><tr><td width="40%" align="left">Chapter 5. Upgrading </td><td width="20%" align="center"><a accesskey="u" href="upgrade.html">Up</a></td><td width="40%" align="right"> Upgrading 4.5 or higher to 4.6.3</td></tr></table><hr><address><a href="mailto:docs@openacs.org">docs@openacs.org</a></address></div><a name="comments"></a></body></html>
Index: openacs-4/packages/acs-core-docs/www/variables.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/variables.adp,v
diff -u -r1.4.2.5 -r1.4.2.6
--- openacs-4/packages/acs-core-docs/www/variables.adp	3 Sep 2021 09:15:38 -0000	1.4.2.5
+++ openacs-4/packages/acs-core-docs/www/variables.adp	7 Sep 2021 09:39:43 -0000	1.4.2.6
@@ -19,7 +19,7 @@
 OpenACS documentation staff.</div><p>Starting with OpenACS 5.0 and the introduction of acs-lang, we
 recommend retrieving date/time information from the database in
 ANSI format and then using <a class="ulink" href="/api-doc/proc-view?proc=lc%5ftime%5ffmt" target="_top">lc_time_fmt</a> to format it for display.</p><div class="example">
-<a name="idp140665014998576" id="idp140665014998576"></a><p class="title"><strong>Example 12.1. Getting datetime
+<a name="idp140696927585168" id="idp140696927585168"></a><p class="title"><strong>Example 12.1. Getting datetime
 from the database ANSI-style</strong></p><div class="example-contents"><pre class="programlisting">db_multirow -extend { mydate_pretty } {
     select to_char(mydate, 'YYYY-MM-DD HH24:MI:SS') as mydate_ansi,
           ...
Index: openacs-4/packages/acs-core-docs/www/variables.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/variables.html,v
diff -u -r1.33.2.4 -r1.33.2.5
--- openacs-4/packages/acs-core-docs/www/variables.html	3 Sep 2021 09:15:38 -0000	1.33.2.4
+++ openacs-4/packages/acs-core-docs/www/variables.html	7 Sep 2021 09:39:43 -0000	1.33.2.5
@@ -4,7 +4,7 @@
           by OpenACS documentation staff.
         </div><p>Starting with OpenACS 5.0 and the introduction of acs-lang,
     we recommend retrieving date/time information from the database in
-    ANSI format and then using <a class="ulink" href="/api-doc/proc-view?proc=lc%5ftime%5ffmt" target="_top">lc_time_fmt</a> to format it for display.</p><div class="example"><a name="idp140665014998576"></a><p class="title"><b>Example 12.1. Getting datetime from the database ANSI-style</b></p><div class="example-contents"><pre class="programlisting">db_multirow -extend { mydate_pretty } {
+    ANSI format and then using <a class="ulink" href="/api-doc/proc-view?proc=lc%5ftime%5ffmt" target="_top">lc_time_fmt</a> to format it for display.</p><div class="example"><a name="idp140696927585168"></a><p class="title"><b>Example 12.1. Getting datetime from the database ANSI-style</b></p><div class="example-contents"><pre class="programlisting">db_multirow -extend { mydate_pretty } {
     select to_char(mydate, 'YYYY-MM-DD HH24:MI:SS') as mydate_ansi,
           ...
     ...
Index: openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes-5-10.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes-5-10.xml,v
diff -u -r1.1.2.1 -r1.1.2.2
--- openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes-5-10.xml	6 Sep 2021 17:42:35 -0000	1.1.2.1
+++ openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes-5-10.xml	7 Sep 2021 09:39:43 -0000	1.1.2.2
@@ -322,7 +322,7 @@
 <para> Altogether, OpenACS 5.10.0 differs from OpenACS 5.9.1 by the
 following statistics
 <programlisting>
-  xxx files changed, xxx insertions(+), xxx deletions(-)
+ 3442 files changed, 120847 insertions(+), 92002 deletions(-) 
 </programlisting>
 contributed by 7 committers (Antonio Pisano, Gustaf Neumann, Günter Ernst, Hector Romojaro, Michael Aram, Stefan Sobernig, Thomas Renner) and additional 13 patch/bugfix providers (Felix Mödritscher, Florian Mosböck, Frank Bergmann, Franz Penz, Hanifa Hasan, Keith Paskett, Markus Moser, Maurizio Martignano, Monika Andergassen, Nathan Coulter, Rainer Bachleitner, Stephan Adelsberger, Tony Kirkham).
 
Index: openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml,v
diff -u -r1.39.2.5 -r1.39.2.6
--- openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml	6 Sep 2021 17:42:35 -0000	1.39.2.5
+++ openacs-4/packages/acs-core-docs/www/xml/for-everyone/release-notes.xml	7 Sep 2021 09:39:44 -0000	1.39.2.6
@@ -1366,7 +1366,7 @@
     </programlisting>
     contributed by 4 committers (Michael Aram, Victor Guerra, Gustaf Neumann, Antonio Pisano) and
     patch/bugfix providers (Frank Bergmann, Andrew Helsley, Felix
-    Mödritscher, Marcos Moser, Franz Penz, Thomas Renner).
+    Mödritscher, Markus Moser, Franz Penz, Thomas Renner).
     These are significantly more  changes as the differences
     in the last releases. All packages of the release were tested with
     PostgreSQL 9.4.* and Tcl 8.5.*.