-[[RenameTopic]] can also be used to delete a topic. This is done by moving the topic to the Trash Web. If this Web does not exist ask your to add it.
+[[ManagingTopics]] can also be used to delete a topic. This is done by moving the topic to the Trash Web. If this Web does not exist ask your to add it.
<div>
<ul>
- <li><a href="#Modifying Topics"> Modifying Topics</a><ul>
- <li><a href="#Referring topics"> Referring topics</a></li>
- <li><a href="#Deleting a topic"> Deleting a topic</a></li>
- <li><a href="#Redirection from old topic"> Redirection from old topic</a></li>
+ <li><a href="#Managing Topics"> Managing Topics</a><ul>
+ <li><a href="#Referring Topics"> Referring Topics</a></li>
+ <li><a href="#Deleting a Topic"> Deleting a Topic</a></li>
+ <li><a href="#Redirecting from an Old Topic"> Redirecting from an Old Topic</a></li>
<li><a href="#Permissions"> Permissions</a></li>
- <li><a href="#Approach"> Approach</a></li>
- <li><a href="#Limitations"> Limitations</a></li>
+ <li><a href="#Procedure"> Procedure</a></li>
+ <li><a href="#Known Limitations"> Known Limitations</a></li>
</ul>
</li>
</ul>
</div>
-## <a name="Modifying Topics"></a> Modifying Topics
+## <a name="Managing Topics"></a> Managing Topics
-Select rename/move when viewing a topic to change its name, delete it or move it
+Select [Rename/move] when viewing a topic to change its name, delete it or move it
1. Select target Web if other than existing Web
2. Fill in new name - defaults to current name
- If any of the referring pages are locked then they will be listed
- You can correct these later by again pressing Rename/Move
-### <a name="Referring topics"></a> Referring topics
+### <a name="Referring Topics"></a> Referring Topics
Referring topics are found using the the %SEARCH% variable, see the template <code>**searchrenameview.tmpl**</code>. First, matching topics in the current Web are listed - matches are to _topic_. Next, all Webs (including the current one) are listed that match _web.topic_. Because %SEARCH% is used, Webs marked in [[WebPreferences]] as NOSEARCHALL will not show up in the search for refernces to the _topic_ being changed.
Changed references are kept are as short as possible, i.e. _topic_ is used in preference to _web.topic_.
-### <a name="Deleting a topic"></a> Deleting a topic
+### <a name="Deleting a Topic"></a> Deleting a Topic
Topics can be _deleted_ by moving them to the <code>**Trash Web**</code>. Note that topics from all Webs go into this, so there could be name clashes, the user is warned of this and asked to choose a new name. When TWiki support sub-webs, these could be created on demand in the Trash Web, which would avoid this name clash problem.
It is up to the administrator of a TWiki installation to clean the Trash Web periodically e.g. by archiving to tape of CDROM entries older than 6 months.
-### <a name="Redirection from old topic"></a> Redirection from old topic
+### <a name="Redirecting from an Old Topic"></a> Redirecting from an Old Topic
Something like the following can be put in [[WebTopicViewTemplate]] and [[WebTopicNonWikiTemplate]] to show if a topic has moved. It does this by searching for the tag %META:TOPICMOVED\{...\}%.
Permissions affect rename in various ways. To rename a topic you need both change and rename permissions. To alter refering topics, you need change permission. See [[TWikiDocumentation#TWiki_Access_Control]] for information on setting up permissions.
-### <a name="Approach"></a> Approach
+### <a name="Procedure"></a> Procedure
- %SEARCH% is used with a special template to show text in topics that requires alteration to point to the new topic name. This includes relavent [[meta data|Main/TWikiDocumentation#Meta_Data_Definition]]
- User chooses which topics will be altered
- References are changed (locks and permissions allowing)
- Any refering topics that can't be changed due to locks are listed - user can try getting these references changed at any time.
-### <a name="Limitations"></a> Limitations
+### <a name="Known Limitations"></a> Known Limitations
Rename in TWiki is fairly complicated due to the dynamic generation of links. Ideally it would be possible to run the required part of rendering in a way that would allow identification of the text to be changed. Unfortunately, these hooks don't exist in TWiki at present. Instead, %SEARCH% is used with a special template to show the text to be changed. And the selected topics and then altered. Search can show matches that will not be updated e.g. because of case differences. Other mis-matches to actual rendered output are also possible as the approaches are so different.
The following shows some limitations of square bracket processing.
- [[Old Topic]] => [[NewTopic][Old Topic]]
- [[old topic]] => [[NewTopic][old topic]]
- [[old t opic]] => not changed
- [[OldTopic]] => [[NewTopic]]
+> [[Old Topic]] => [[NewTopic][Old Topic]]
+> [[old topic]] => [[NewTopic][old topic]]
+> [[old t opic]] => not changed
+> [[OldTopic]] => [[NewTopic]]
<div>
<ul>
- <li><a href="#Modifying Webs"> Modifying Webs</a><ul>
+ <li><a href="#Managing Webs"> Managing Webs</a><ul>
<li><a href="#How to Add a New Web"> How to Add a New Web</a></li>
<li><a href="#How to Rename or Delete a Web"> How to Rename or Delete a Web</a></li>
</ul>
</ul>
</div>
-## <a name="Modifying Webs"></a> Modifying Webs
+## <a name="Managing Webs"></a> Managing Webs
-To work with entire TWiki webs, you need direct access to the installation files on the host server. Connecting by Telnet or FTP is the usual approach. Before making changes to a web, you can move individual topics through your browser (see [[ModifyTopics|TWiki/RenameTopic]]). No similar web controls are available through the browser interface.
+To work with entire TWiki webs, you need direct access to the installation files on the host server. Connecting by Telnet or FTP is the usual approach. Before making changes to a web, you can move individual topics through your browser (see [[ModifyTopics|TWiki/ManagingTopics]]). No similar web controls are available through the browser interface.
### <a name="How to Add a New Web"></a> How to Add a New Web
-[[RenameTopic]] can be used to move a topic from one Web to another. One specialised use of this is [[DeleteWeb]].
+[[ManagingTopics]] can be used to move a topic from one Web to another. One specialised use of this is [[DeleteWeb]].
<div>
<ul>
<li><a href="#TWiki Installation Guide"> TWiki Installation Guide</a><ul>
- <li><a href="#Standard Installation Steps"> Standard Installation Steps</a></li>
- <li><a href="#Adding Variables Rendering Rule"> Adding Variables & Rendering Rules </a></li>
- <li><a href="#Enabling Basic Authentication (."> Enabling Basic Authentication (.htaccess)</a></li>
- <li><a href="#Generating Site Usage Statistics"> Generating Site Usage Statistics</a></li>
- <li><a href="#Creating a New Web"> Creating a New Web</a></li>
+ <li><a href="#Standard Installation"> Standard Installation</a><ul>
+ <li><a href="#Step 1: Create Configure the Di"> Step 1: Create & Configure the Directories</a></li>
+ <li><a href="#Step 2: Check the Server Directo"> Step 2: Check the Server Directory Settings</a></li>
+ <li><a href="#Step 3: Enable Perl File Permiss"> Step 3: Enable Perl File Permissions</a></li>
+ <li><a href="#Step 4: Set the Main Configurati"> Step 4: Set the Main Configuration File</a></li>
+ <li><a href="#Step 5: Finish Up from Your Brow"> Step 5: Finish Up from Your Browser</a></li>
+ </ul>
+ </li>
+ <li><a href="#Extra Server-Level Options"> Extra Server-Level Options</a><ul>
+ <li><a href="#Creating a New Web"> Creating a New Web</a></li>
+ <li><a href="#Adding Variables Rendering Rule"> Adding Variables & Rendering Rules </a></li>
+ <li><a href="#Enabling Basic Authentication (."> Enabling Basic Authentication (.htaccess)</a></li>
+ </ul>
+ </li>
<li><a href="#TWiki File System Snapshot"> TWiki File System Snapshot</a></li>
</ul>
</li>
**_Note:_** Below installation steps assume user `nobody` for all files manupulated by the cgi scripts (executed by the web server), and user `twiki` for all other files. You need to replace user `nobody` with an other user in case the web server executes the script with a different user ( default for Debian is `www-data` ). Also, you can substitute user `twiki` with your own user name.
-**_Note:_** Below installation steps assume that you have control over the web server configuraton files. In case you don't (i.e. if you are installing it on a hosted server) follow the steps but use these directories instead:
+**_Note:_** Below installation steps assume that you have control over the web server configuraton files. In case you don't - you may be installing on an ISP-hosted server - follow the steps but use these directories instead:
<table border="1" cellpadding="0" cellspacing="0">
<tr>
Read <http://TWiki.org/cgi-bin/view/Codev/SourceForgeHowTo> in case you want to install TWiki on SourceForge.
-### <a name="Standard Installation Steps"></a> Standard Installation Steps
+### <a name="Standard Installation"></a> Standard Installation
+
+Request and download the TWiki %VERSION% distribution in Unix ZIP format from <http://TWiki.org/download.html>.
+
+#### <a name="Step 1: Create Configure the Di"></a> Step 1: Create & Configure the Directories
-- Request the TWiki distribution (in Unix ZIP format) from <http://TWiki.org/download.html> .
- Create directory `/home/httpd/twiki` and unzip the TWiki distribution into this directory.
- The `twiki/bin` directory of TWiki must be set as a cgi-bin directory. Add `/home/httpd/twiki/bin` to file `/etc/httpd/httpd.conf` with only `ExecCGI` option.
- The `twiki/pub` directory of TWiki must be set so that it is visible as a URL. Add `/home/httpd/twiki` to file `httpd.conf` with normal access options (copy from `/home/httpd/html` ).
- Now add `ScriptAlias` for `/twiki/bin` and `Alias` for `/twiki` to file `httpd.conf` . <br />**_Note:_** The `ScriptAlias` **must** come before the `Alias` in Apache, otherwise it will fail to correctly set up `/twiki/bin/` , due to the fact that it sees that as being just another subdirectory of the `/twiki/` alias. <br />
-- Here are example `httpd.conf` entries: ScriptAlias /twiki/bin/ "/home/httpd/twiki/bin/"
- Alias /twiki/ "/home/httpd/twiki/"
- <Directory "/home/httpd/twiki/bin">
- Options +ExecCGI
- SetHandler cgi-script
- Allow from all
- </Directory>
- <Directory "/home/httpd/twiki/pub">
- Options FollowSymLinks +Includes
- AllowOverride None
- Allow from all
- </Directory>
+
+> **Example `httpd.conf` entries:**
+>
+> ScriptAlias /twiki/bin/ "/home/httpd/twiki/bin/"
+> Alias /twiki/ "/home/httpd/twiki/"
+> <Directory "/home/httpd/twiki/bin">
+> Options +ExecCGI
+> SetHandler cgi-script
+> Allow from all
+> </Directory>
+> <Directory "/home/httpd/twiki/pub">
+> Options FollowSymLinks +Includes
+> AllowOverride None
+> Allow from all
+> </Directory>
+
+#### <a name="Step 2: Check the Server Directo"></a> Step 2: Check the Server Directory Settings
+
- Restart Apache by `/etc/rc.d/rc5.d/S85httpd restart` .
- Test if the `twiki/bin` directory is cgi-enabled:
- Enter the URL of that directory into your browser ( `http://your.domain.com/twiki/bin` ). It is not set correctly as cgi-bin in case you get something like `"Index of /twiki/bin"` . It is OK if you get a message like `"Forbidden. You don't have permission to access /twiki/bin/ on this server."`
- - Execute the `testenv` script from your browser ( `http://your.domain.com/twiki/bin/testenv` ). It shows a table with all CGI environment variables and tests the settings in your `twiki/bin/wikicfg.pm` configuration file.
-- Make sure PERL 5 and the PERL CGI library is installed on your system. Default location of PERL executable is `/usr/bin/perl` . In case PERL is installed in a different location, the first line of all perl scripts in the `twiki/bin` directory need to be changed (alternatively you can create a symbolic link from `/usr/bin/perl` ).
-- To be able to edit the perl scripts and .tmpl files it is necessary to `chown` and `chgrp -R twiki` so all the files have the owner you want.
-- The scripts execute as `nobody` . Set the file permission of all Perl scripts in the `twiki/bin` directory as executable to `-rwxr-xr-x` .
-- Set the permission of all files below `twiki/data` so that they are writable by user `nobody`. A simple way is to chmod them to 666 ( `-rw-rw-rw-` ).
-- Set the permission of the `twiki/data` directory and all its subdirectories so that files in there are writable by user `nobody`. A simple way is to chmod them to 777 ( `drwxrwxrwx` ).
-- Set the permission of the `twiki/pub` directory and all its subdirectories so that files in there are writable by user `nobody`. A simple way is to chmod them to 777 ( `drwxrwxrwx` ).
-- Edit the file `twiki/bin/wikicfg.pm` and set the variables at the beginning of the file to your needs.
-- Make sure RCS is installed. Set `$rcsDir` in `twiki/bin/wikicfg.pm` to mach the location of your RCS binaries.
-- Point your browser at <http://your.domain.com/twiki/bin/view> and start TWiki-ing away!
-- Using your browser, edit the [[TWikiPreferences]] topic in the TWiki.TWiki web to set the WIKIWEBMASTER email address, the WEBCOPYRIGHT message and other preferences.
-- Note in case the cgi scripts must have a file extension like `.pl` or `.cgi`:
- - Add the extension to all the scripts (except for the `.pm` ones) in `twiki/bin`
- - Edit `wikicfg.pm` and set the file extension in the `$scriptSuffix` variable.
- - If you use `.htaccess`, edit the file and add the file extension to `edit`, `view`, `preview`, etc.
+ - Execute the `testenv` script from your browser ( `http://your.domain.com/twiki/bin/testenv` ). It shows a table with all CGI environment variables and tests the settings in your <code>**twiki/bin/wikicfg.pm**</code> configuration file.
+
+#### <a name="Step 3: Enable Perl File Permiss"></a> Step 3: Enable Perl File Permissions
+
+- Make sure Perl 5 and the Perl CGI library is installed on your system. Default location of Perl executable is `/usr/bin/perl` . In case Perl is installed in a different location, the first line of all perl scripts in the <code>**twiki/bin**</code> directory need to be changed (alternatively you can create a symbolic link from <code>**/usr/bin/perl**</code> ).
+ - **IMPORTANT:** On most ISP virtual domain accounts, Perl CGI scripts require a <code>**.cgi**</code> extension to run. Some systems need <code>**.pl**</code>, the regular Perl extension. Change all <code>**twiki/bin**</code> scripts appropriately if necssary.
+- To be able to edit the Perl scripts and <code>**.tmpl**</code> files it is necessary to <code>**chown**</code> and <code>**chgrp -R twiki**</code> so all the files have the owner you want.
+- The scripts execute as <code>**nobody**</code>. Set the file permission of all Perl scripts in the <code>**twiki/bin**</code> directory as executable to <code>**-rwxr-xr-x**</code> (755).
+- Set the permission of all files below `twiki/data` so that they are writable by user `nobody`. A simple way is to <code>**chmod**</code> them to <code>**-rw-rw-rw-**</code> (666).
+- Set the permission of the <code>**twiki/data**</code> directory and its subdirectories so that files in there are writable by user <code>**nobody**</code>. A simple way is to chmod them to <code>**drwxrwxrwx**</code> (777).
+- Set the permission of the `twiki/pub` directory and all its subdirectories so that files in there are writable by user `nobody`. A simple way is to chmod them to <code>**drwxrwxrwx**</code> (777).
+
+#### <a name="Step 4: Set the Main Configurati"></a> Step 4: Set the Main Configuration File
+
+- Edit the file <code>**twiki/bin/wikicfg.pm**</code> and set the variables at the beginning of the file to your needs.
+ - Set the file extension in the `$scriptSuffix` variable to <code>**cgi**</code> or <code>**pl**</code> if required.
+ - Make sure RCS is installed. Set `$rcsDir` in `twiki/bin/wikicfg.pm` to mach the location of your RCS binaries.
- Note in case the cgi scripts are **_not_** running as user `nobody`: The `*,v` RCS repository files delivered with the installation package are locked by user `nobody` . In case the user is different (e.g. `www-data` ), it is not possible to check in files, this has the effect that the topic version number does not increase when saving a topic. In this case you need to unlock all repository files and lock them as user `www-data` (check the rcs man pages), or simply delete all the repository files. A simple way to switch the locker of the RCS files is to use sed: <br />`for f in *,v; do sed 's/nobody\:/www-data\:/' $f > x; mv x $f; done`
-- Security issue: Directories `twiki/data` , `twiki/templates` and all its subdirectories should be set so that they are **not** visible as a URL. (Alternatively, move the directries to a place where they are not visible, and change the variables in `twiki/bin/wikicfg.pm` accordingly)
-- Enable email notification of topic changes, [[Notification of Changes|Main/TWikiDocumentation#TWiki_Notification_of_Changes]] has more. Using your browser, edit also the [[WebNotify]] topic in all webs and set the users you want to notify.
+- **Security issue:** Directories `twiki/data` , `twiki/templates` and all its subdirectories should be set so that they are **not** visible as a URL. (Alternatively, move the directries to a place where they are not visible, and change the variables in `twiki/bin/wikicfg.pm` accordingly)
+- Enable email notification of topic changes, [[Notification of Changes|Main/TWikiDocumentation#TWiki_Notification_of_Changes]] has more.
- Add the [TWiki:Main.PoweredByTWikiLogo](http://TWiki.org/cgi-bin/view/Main/PoweredByTWikiLogo) to your [[WebHome]] topic.
-### <a name="Adding Variables Rendering Rule"></a> Adding Variables & Rendering Rules
+#### <a name="Step 5: Finish Up from Your Brow"></a> Step 5: Finish Up from Your Browser
-- Optional: You can add new rendering rules or new %VARIABLES%. To insure an easy upgrade of TWiki it is recommended to do this customization in `twiki/bin/wikicfg.pm` , not `twiki/bin/wiki.pm` .
+- Point your Web browser at <code>**http://your.domain.com/twiki/bin/view**</code> and start TWiki-ing away!
+- Edit the [[TWikiPreferences]] topic in the TWiki:TWiki web to set the WIKIWEBMASTER email address, the WEBCOPYRIGHT message and other preferences.
+- If you use `.htaccess`, edit the file and add the file extension to `edit`, `view`, `preview`, etc.
+- Edit the [[WebNotify]] topic in all webs and set the users you want to notify.
-### <a name="Enabling Basic Authentication (."></a> Enabling Basic Authentication (.htaccess)
+That's it for the standard virgin installation of TWiki. Read on to learn how to customize TWiki.
-- Optional: If you are on a non authenticated server (i.e. not using SSL) and you would like to authenticate users:
- - Rename file `.htaccess.txt` in the `twiki/bin` directory to `.htaccess` and change it to your needs. For details consult the HTTP server documentation (for Apache server: [[1]](http://www.apache.org/docs/mod/directives.html), [[2]](http://www.mcs.kent.edu/system/web_help/htaccess/introduction.html)). In particular, the following <font>red</font> part needs to be configured correctly: <br /><code>Redirect <font>/urlpath/to/TWiki/index.html</font> http://<font>your.domain.com/urlpath/to/TWiki/bin/</font>view</code><br /><code>AuthUserFile <font>/filepath/to/TWiki/data/</font>.htpasswd</code><br /><code>ErrorDocument 401 <font>/urlpath/to/TWiki/bin/</font>oops/TWiki/TWikiRegistration?template=oopsauth</code>
- - **_Note:_** The browser should ask for login name and password when you click on the <u>Edit</u> link. In case `.htaccess` does not have the desired effect you need to enable it: Add "AllowOverride All" to the Directory section of `access.conf` for your `twiki/bin` directory.
- - Copy the [[TWikiRegistrationPub]] topic to [[TWikiRegistration]]. Do that by either editing the topics in theTWiki web, or by renaming the `.txt` and `.txt,v` files in the `twiki/data/TWiki` directory.
- - **_Note:_** You can customize the registration form if needed, like deleting or adding input tags. The `name=""` parameter of the input tags must start with: `"Twk0..."` (if this is an optional entry), or `"Twk1..."` (if this is a required entry). This will ensure that the fields are processed correctly.
- - A new line containing user name and encrypted password gets added to the `data/.htpasswd` file when a users registers. The file that comes with the TWiki installation contains a few user accounts of TWiki core team members (needed for testing). You can edit the file and delete those lines.
-
-### <a name="Generating Site Usage Statistics"></a> Generating Site Usage Statistics
+### <a name="Extra Server-Level Options"></a> Extra Server-Level Options
-- Optional: You can automatically generate usage statistics for all webs. To enable this:
- - Make sure variable `$doLogTopicView, $doLogTopicSave and $doLogTopicUpload` in `wikicfg.pm` are set. This will generate log entries in file `twiki/data/log<date>.txt` .
- - Topic [[WebStatistics]] must be present in all webs where you want to have statistics. You can use the topic in the Main web as a template.
- - Call the `twiki/bin/statistics` script from a cron job, once a day is recommended. This will update the [[WebStatistics]] topics in all webs.
- - **_Attention:_** The script must run as the same user as the CGI scripts are running, which is user `nobody` on most systems. Example crontab entry: <br />`0 0 * * * (cd /path/to/TWiki/bin; ./statistics >/dev/null 2>&1)`
- - There is a workaround in case you can't run the script as user `nobody` : Run the utility `twiki/bin/geturl` in your cron job and specify the URL of the `twiki/bin/statistics` script as a parameter. Example: <br />`0 0 * * * (cd /path/to/TWiki/bin; ./geturl mydomain.com /urlpath/to/TWiki/bin/statistics >/dev/null 2>&1)`
- - The `twiki/bin/statistics` script can also be executed as a CGI script, just enter the URL in your browser. Examples:
- - Update current month for all webs: <br />`http://mydomain.com/twiki/bin/statistics`
- - Update current month for Main web only: <br />`http://mydomain.com/twiki/bin/statistics/Main`
- - Update January 2000 for Main web: <br />`http://mydomain.com/twiki/bin/statistics/Main?logdate=200001`
+Complete a Standard Installation and your new TWiki site should be up and running. You can develop and manage most aspects of your site from the browser interface. Core set-up functions require direct access to the server file system, via Telnet or FTP. You can make server-level site changes during installation, or at any time afterwards.
<a name="CreateWeb"></a>
-### <a name="Creating a New Web"></a> Creating a New Web
+#### <a name="Creating a New Web"></a> Creating a New Web
- To create a new web:
- Use a name for the web consisting of characters `A..Z` , `a..z` but **not** in [[WikiNotation]].
- In case you want usage statistics for this web: Copy file `WebStatistics.txt` from the `twiki/data/Main` directory to the new data directory. Edit topic WebStatistics in the new web and delete old usage entries.
- Note that user home topics are only located in the %WIKITOOLNAME%.Main web, so don't try to move them or create them in other webs. From any web you can refer to users located in the %WIKITOOLNAME%.Main web like `Main.UserName` or `%MAINWEB%.UserName`.
+#### <a name="Adding Variables Rendering Rule"></a> Adding Variables & Rendering Rules
+
+- You can add new rendering rules or new %VARIABLES%. To insure an easy upgrade of TWiki it is recommended to do this customization in `twiki/bin/wikicfg.pm` , not `twiki/bin/wiki.pm` .
+
+#### <a name="Enabling Basic Authentication (."></a> Enabling Basic Authentication (.htaccess)
+
+- If you are on a non authenticated server (i.e. not using SSL) and you would like to authenticate users:
+ - Rename file `.htaccess.txt` in the `twiki/bin` directory to `.htaccess` and change it to your needs. For details consult the HTTP server documentation (for Apache server: [[1]](http://www.apache.org/docs/mod/directives.html), [[2]](http://www.mcs.kent.edu/system/web_help/htaccess/introduction.html)). In particular, the following <font>red</font> part needs to be configured correctly: <br /><code>Redirect <font>/urlpath/to/TWiki/index.html</font> http://<font>your.domain.com/urlpath/to/TWiki/bin/</font>view</code><br /><code>AuthUserFile <font>/filepath/to/TWiki/data/</font>.htpasswd</code><br /><code>ErrorDocument 401 <font>/urlpath/to/TWiki/bin/</font>oops/TWiki/TWikiRegistration?template=oopsauth</code>
+ - **_Note:_** The browser should ask for login name and password when you click on the <u>Edit</u> link. In case `.htaccess` does not have the desired effect you need to enable it: Add "AllowOverride All" to the Directory section of `access.conf` for your `twiki/bin` directory.
+ - Copy the [[TWikiRegistrationPub]] topic to [[TWikiRegistration]]. Do that by either editing the topics in theTWiki web, or by renaming the `.txt` and `.txt,v` files in the `twiki/data/TWiki` directory.
+ - **_Note:_** You can customize the registration form if needed, like deleting or adding input tags. The `name=""` parameter of the input tags must start with: `"Twk0..."` (if this is an optional entry), or `"Twk1..."` (if this is a required entry). This will ensure that the fields are processed correctly.
+ - A new line containing user name and encrypted password gets added to the `data/.htpasswd` file when a users registers. The file that comes with the TWiki installation contains a few user accounts of TWiki core team members (needed for testing). You can edit the file and delete those lines.
+
### <a name="TWiki File System Snapshot"></a> TWiki File System Snapshot
Here are partial directory listings showing typical file permissions and ownership. This is provided for general debugging use only and isn't an exact representation of the current distribution. There is also a complete file [[listing by directory|TWiki/TWikiImplementationNotes]], with individual file descriptions, for the current TWiki release.
- Wiki webmaster email address:
- Set WIKIWEBMASTER = <webmaster@your.company>
-- Mail host for outgoing mail. This is used for [[TWikiNotificationOfChanges]] if Perl module <code>**Net::SMTP**</code> is installed. If not, sendmail is used instead (defined by <code>**$mailProgram**</code> in <code>**TWiki.cfg**</code>). Examples: `mail.your.company` or `localhost`
+- Mail host for outgoing mail. This is used for [[WebNotification]] if Perl module <code>**Net::SMTP**</code> is installed. If not, sendmail is used instead (defined by <code>**$mailProgram**</code> in <code>**TWiki.cfg**</code>). Examples: `mail.your.company` or `localhost`
- Set SMTPMAILHOST = mail
- [[TWikiPlugins]] configuration: All plugin modules that exist in the `lib/TWiki/Plugins` directory are activated automatically unless disabled by DISABLEDPLUGINS. You can optionally list the installed plugins in INSTALLEDPLUGINS. This is useful to define the sequence of plugin execution, or to specify other webs then the TWiki web for the plugin topics. Specify plugins as a comma separated list of topics.
- [[TWikiPlannedFeatures]] has a list of planned features for upcoming TWiki versions.
- [[TWikiHistory]] shows TWiki's implementation history.
- [[TWikiDocumentation]] is the implementation documentation.
-- [[TWikiAdministration]] tells you how to do administrative stuff, like renaming or deleting a topic.
+- [[ManagingWebs]] tells you how to do administrative stuff, like renaming or deleting a topic.
- [[WikiCulture]] talks about the unique type of collaboration Wiki systems offer.
- [[WikiReferences]] has links to articles and books around collaboration and the Wiki technology in particular.
<div>
<ul>
- <li><a href="#TWiki Software Environment"> TWiki Software Environment</a><ul>
- <li><a href="#System Requirements"> System Requirements</a></li>
+ <li><a href="#TWiki Operating Environment"> TWiki Operating Environment</a><ul>
+ <li><a href="#Server-Side Requirements"> Server-Side Requirements</a></li>
+ </ul>
+ </li>
+ <li><a href="#Client-Side Requirements"> Client-Side Requirements</a><ul>
+ <li><a href="#Known Issues"> Known Issues</a></li>
<li><a href="#TWiki Directory Structure"> TWiki Directory Structure</a></li>
<li><a href="#File Descriptions"> File Descriptions</a><ul>
<li><a href="#Files in twiki"> Files in <code>twiki</code></a></li>
</ul>
</div>
-## <a name="TWiki Software Environment"></a> TWiki Software Environment
+## <a name="TWiki Operating Environment"></a> TWiki Operating Environment
+
+Low requirements on client-side and server-side environment, to keep TWiki deployment as broad as possible is a key element of the [[TWikiMission]]. Strict [[W3C]] and ECMA standards compliance is also a mandate. These requirements are amended from time to time as technology progresses.
-### <a name="System Requirements"></a> System Requirements
+### <a name="Server-Side Requirements"></a> Server-Side Requirements
-TWiki is written in **Perl 5** and also uses some **shell commands**. It also requires that **GNU RCS** (Revision Control System) is installed on the same system. The current implementation runs best on a Linux machine, but it can also run with Microsoft Windows.
+TWiki is written in **Perl 5** and uses a number of **shell commands**. It requires that **GNU RCS** (Revision Control System) be installed on the same system. Current development is on Linux. the recommended platform, but it can also work with Microsoft Windows and other OS.
<table border="1" cellpadding="0" cellspacing="0">
<tr>
- <th bgcolor="#99CCCC" colspan="3"><strong> Required Environment by Platform </strong></th>
+ <th bgcolor="#99CCCC" colspan="3"><strong> Required Server Environment by Platform </strong></th>
</tr>
<tr>
- <th bgcolor="#99CCCC"><strong> Packages: </strong></th>
- <th bgcolor="#99CCCC"><strong> Linux/Unix: </strong></th>
- <th bgcolor="#99CCCC"><strong> Windows: </strong></th>
+ <th bgcolor="#99CCCC"><strong> Resource </strong></th>
+ <th bgcolor="#99CCCC"><strong> Unix </strong></th>
+ <th bgcolor="#99CCCC"><strong> Windows </strong></th>
</tr>
<tr>
<td> Perl </td>
- <td align="center"> 5.x </td>
- <td align="center"> 5.x </td>
- </tr>
- <tr>
- <td> Non-standard Perl modules </td>
- <td align="center"> ??? </td>
- <td><code>MIME::Base64</code>, Digest::SHA1 (for password generation) </td>
+ <td align="center" colspan="2"> 5.005_03 or higher </td>
</tr>
<tr>
- <td> Optional Perl modules </td>
- <td><code>Net::SMTP</code> (or sendmail) </td>
+ <td> Non standard Perl modules </td>
+ <td align="center"><code>Net::SMTP</code> (or <code>sendmail</code>) </td>
<td align="center"><code>Net::SMTP</code></td>
</tr>
<tr>
<td> RCS </td>
- <td align="center"> 5.7 </td>
- <td align="center"> 5.7 (including <code>diff</code></td>
+ <td align="center" colspan="2"> 5.7 or higher </td>
</tr>
<tr>
<td> Other external programs </td>
- <td align="center"><code>ls</code>, <code>fgrep</code>, <code>egrep</code></td>
- <td align="center"><code>ls</code>, <code>fgrep</code>, <code>egrep</code></td>
+ <td align="center" colspan="2"><code>ls, fgrep, egrep</code></td>
</tr>
<tr>
<td> Web server </td>
- <td align="center"> Apache </td>
- <td align="center"> Apache, IIS </td>
+ <td align="center" colspan="2"> Apache and others (support for cgi, authentication, extended path) <strong>*</strong></td>
</tr>
<tr>
<td><em>OS versions</em></td>
<td align="center"><strong><em>Linux, Unix...</em></strong></td>
<td align="center"><strong><em>every last Win?!</em></strong></td>
</tr>
+ <tr>
+ <td> Required disk space </td>
+ <td> </td>
+ <td> </td>
+ </tr>
+</table>
+
+**_ISP INSTALLATION REQUIREMENTS: SSI, RCS local or sysadmin, same for perl modules for plugins, cron, basic authentication,..._**
+
+## <a name="Client-Side Requirements"></a> Client-Side Requirements
+
+The basic TWiki engine and templates have a low requirement on the browser:
+
+<table border="1" cellpadding="0" cellspacing="0">
+ <tr>
+ <th align="center" bgcolor="#99CCCC" colspan="3"><strong> Recommend PC Requirement </strong></th>
+ </tr>
+ <tr>
+ <th bgcolor="#99CCCC"><strong> Component </strong></th>
+ <th bgcolor="#99CCCC"><strong> Min/Rec </strong></th>
+ </tr>
+</table>
+
+<table border="1" cellpadding="0" cellspacing="0">
+ <tr>
+ <th align="center" bgcolor="#99CCCC" colspan="2"><strong> Browser Requirements </strong></th>
+ </tr>
+ <tr>
+ <th bgcolor="#99CCCC"><strong> Resource </strong></th>
+ <th bgcolor="#99CCCC"><strong> Details </strong></th>
+ </tr>
+ <tr>
+ <td> HTML 3.2 browser </td>
+ <td> </td>
+ </tr>
+ <tr>
+ <td>[[Main/JavaScript]] 1.? </td>
+ <td> Optional: JS degrades gracefully </td>
+ </tr>
+ <tr>
+ <td> Cookies </td>
+ <td> Not used </td>
+ </tr>
+ <tr>
+ <td> CSS1/2 </td>
+ <td> ???? </td>
+ </tr>
</table>
+- TWiki generates XHTML 1.0 code as long as it is compatible with HTML 3.2.
+
+**_WHAT ABOUT WEB STANDARDS PROJECT - CSS CONTROL_**
+
+### <a name="Known Issues"></a> Known Issues
+
+- Some [[TWikiSkins]] may require more, like cookies and [[JavaScript]]
+- At present, contributed Plugins are not checked against compatibility standards, and may require anything imaginable: browser-specific functions, Java, cookies, CSS, etc.
+
### <a name="TWiki Directory Structure"></a> TWiki Directory Structure
You can easily rename the root TWiki directory - <code>**twiki**</code> - to whatever you like by changing it in the <code>**twiki.cfg**</code> configuration file. However, to keep the current installation and future upgrades simple, you should leave the subdirectory structure intact:
<td> xxxx </td>
</tr>
<tr>
- <td><code><b>TWiki/RenameTopic.txt</b></code></td>
+ <td><code><b>TWiki/ManagingTopics.txt</b></code></td>
<td> xxxx </td>
</tr>
<tr>
- <td><code><b>TWiki/RenameTopic.txt,v</b></code></td>
+ <td><code><b>TWiki/ManagingTopics.txt,v</b></code></td>
<td> xxxx </td>
</tr>
<tr>
<td> xxxx </td>
</tr>
<tr>
- <td><code><b>TWiki/TWikiAdministration.txt</b></code></td>
+ <td><code><b>TWiki/ManagingWebs.txt</b></code></td>
<td> xxxx </td>
</tr>
<tr>
- <td><code><b>TWiki/TWikiAdministration.txt,v</b></code></td>
+ <td><code><b>TWiki/ManagingWebs.txt,v</b></code></td>
<td> xxxx </td>
</tr>
<tr>
<td> xxxx </td>
</tr>
<tr>
- <td><code><b>TWiki/TWikiNotificationOfChanges.txt</b></code></td>
+ <td><code><b>TWiki/WebNotification.txt</b></code></td>
<td> xxxx </td>
</tr>
<tr>
- <td><code><b>TWiki/TWikiNotificationOfChanges.txt,v</b></code></td>
+ <td><code><b>TWiki/WebNotification.txt,v</b></code></td>
<td> xxxx </td>
</tr>
<tr>
-## <a name="Monitoring Site Changes"></a> Monitoring Site Changes
+## <a name="Web Notification on Changes"></a> Web Notification on Changes
Each %WIKITOOLNAME% web does an automatic email notification of recent changes. Users can subscribe / unsubscribe themselves in [[WebNotify]] of each TWiki web. The Perl script <code>**mailnotify**</code> is called by a deamon in regular intervals. The script is sending an automated email to subscribed users in case some topics changed in a web within this interval.
9. [[TWikiMetaData]]
10. [[TWikiFormTemplate]]
11. [[TWikiPlugins]]
- 12. [[MonitoringSiteChanges|Main/TWikiNotificationOfChanges]]
- 13. [[ManagingTopics|Main/RenameTopic]]
- 14. [[ManagingWebs|Main/TWikiAdministration]]
+ 12. [[MonitoringSiteActivity]]
+ 13. [[ManagingTopics]]
+ 14. [[ManagingWebs]]
<form action="http://www.dementia.org/twiki//search/%WEB%/">
<ul>
git://git.openafs.org / openafs-wiki.git / commitdiff