Index: openacs-4/packages/acs-bootstrap-installer/installer/index.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-bootstrap-installer/installer/index.tcl,v diff -u -N -r1.32.2.3 -r1.32.2.4 --- openacs-4/packages/acs-bootstrap-installer/installer/index.tcl 17 May 2019 14:10:34 -0000 1.32.2.3 +++ openacs-4/packages/acs-bootstrap-installer/installer/index.tcl 17 May 2019 14:11:14 -0000 1.32.2.4 @@ -21,25 +21,25 @@ # (well, actually, /?done_p=1). This is so the user can just hit his/her # browser's Reload button to get the main OpenACS login page once (s)he's # restarted the OpenNSD. - + if { [ad_verify_install] } { install_return 200 "OpenACS Installation Complete" " You have successfully installed the Open Architecture Community System (OpenACS)!

Your server process has been terminated. Unless you have configured your -web server to restart automatically, as outlined in the -OpenACS 4.x Installation Guide, +web server to restart automatically, as outlined in the +OpenACS 4.x Installation Guide, you will need to start your web server again. -When the web server restarts, OpenACS will be fully functional and you can reload +When the web server restarts, OpenACS will be fully functional and you can reload this page to access the running web server. " ns_shutdown } else { install_return 200 "Error" " The installation program has encountered an error. Please drop your OpenACS tablespace and the OpenACS username, recreate them, and try again. You can log this as a bug -using the OpenACS Bug Tracker. +using the OpenACS Bug Tracker. " return } @@ -53,7 +53,7 @@ for collaborative commerce. This is the OpenACS Installer which performs all the steps necessary to get the OpenACS Community System running on your server.

-Please read the Release Notes +Please read the Release Notes before proceeding to better understand what is contained in this release. " @@ -80,7 +80,7 @@ append body [subst {

For more information about the $acs_application(pretty_name) application visit the $acs_application(pretty_name) home page - }] + }] } } else { set acs_application(name) openacs @@ -101,7 +101,7 @@

The first step involved in setting up your OpenACS installation is to configure your RDBMS, correctly install a database driver, -and configure AOLserver to use it. You can download +and configure AOLserver to use it. You can download and install the latest version of the AOLserver Oracle and PostgreSQL drivers from the OpenACS.org Software Page. @@ -110,7 +110,7 @@ " install_return 200 "Error" $body return -} +} # # Unset array errors, in case it exists @@ -141,7 +141,7 @@ " set error_p 1 } - + # AOLserver must support ns_cache. if {[llength [info commands ns_cache]] < 1} { append errors "

  • The ns_cache module is not installed. This is required for OpenACS." @@ -152,25 +152,25 @@ if {![xml_support_ok xml_status_msg]} { append errors "Problems with XML support for AOLserver:

    $xml_status_msg" set error_p 1 -} +} # AOLserver must support the "fancy" ADP parser. set adp_support [ns_config "ns/server/[ns_info server]/adp" DefaultParser] if {$adp_support ne "fancy" && [ns_info name] ne "NaviServer"} { - append errors "

  • The fancy ADP parser is not enabled. This is required to support + append errors "

  • The fancy ADP parser is not enabled. This is required to support the OpenACS Templating System. Without this templating system, none of the OpenACS pages installed by default -will display. Please add the following to your AOLserver configuration file (usually in -/home/aol30/yourservname.ini) or see the Installation Guide for +will display. Please add the following to your AOLserver configuration file (usually in +/home/aol30/yourservname.ini) or see the Installation Guide for more information.

    -\[ns/server/bquinn/adp\] 
    -Map=/*.adp 
    +\[ns/server/bquinn/adp\]
    +Map=/*.adp
     DefaultParser=fancy
     
    After adding support for the fancy ADP parser, please restart your web server.

    " set error_p 1 -} +} # The server must have a large stack size (at least 128K by default, or the value specified # in the install.xml file) @@ -179,7 +179,7 @@ if {[regexp {^([0-9.]+)([MKk])B} $stacksize . number multiplicator]} { switch $multiplicator { - "k" - "K" {set stacksize [expr {int($number * 1024.0)}]} + "k" - "K" {set stacksize [expr {int($number * 1024.0)}]} "M" {set stacksize [expr {int($number * 1024.0 * 1024.0)}]} default {ns_log warning "installer/index.tcl: invalid multiplicator $multiplicator"} } @@ -199,7 +199,7 @@ After adding support the larger stacksize, please restart your web server.

    " set error_p 1 -} +} # APM needs to check its permissions. @@ -220,8 +220,8 @@ # We have the workspace dir, but what about the package root? if { ![file writable [file join $::acs::rootdir packages]] } { append errors "
  • The $::acs::rootdir/packages directory has incorrect permissions. It must be owned by - the user executing the web server, normally nsadmin and the owner must have read and write - privileges on this directory and all of its subdirectories. You can correct this by running the following + the user executing the web server, normally nsadmin and the owner must have read and write + privileges on this directory and all of its subdirectories. You can correct this by running the following script as root. To give another user access to the files, add them to web group.

    @@ -238,16 +238,16 @@
     # correctly, let's check out the actual db.
     if {$error_p} {
         append body [subst {

    - At least one misconfiguration was discovered that must be corrected. + At least one misconfiguration was discovered that must be corrected. Please fix all of them, restart the web server, and try running the OpenACS installer again. - You can proceed without resolving these errors, but the system may not function - correctly. - -

    -

      - $errors -
    -

    + You can proceed without resolving these errors, but the system may not function + correctly. + +

    +

      + $errors +
    +

    }] } @@ -259,7 +259,7 @@ # Get the default for system_url. First try to get it from the nssock # hostname setting - if that is not available then try ns_info if { [catch { - set driversection [ns_driversection] + set driversection [ns_driversection] set system_url "http://[ns_config $driversection hostname [ns_info hostname]]" set system_port [ns_config $driversection port [ns_conn port]] @@ -369,14 +369,14 @@

    Once your server is installed, you can choose to have users login with username instead of email. - This is particularly useful if you're authenticating against other services, such as LDAP or the + This is particularly useful if you're authenticating against other services, such as LDAP or the local operating system, which may not use email as the basis of authentication.