TWiki Configuration

Use this page to set the configuration options for TWiki. Fill in the settings, and then press 'Next'.

If you are installing TWiki for the first time, and you just want to get up and running, the only section you need to worry about below is General path settings. You can always come back and configure other settings later.
Explanation of color codes:
SettingsClick the buttons below to open each sectionOpen all options
Environment variables(read only)
DOCUMENT_ROOT/www/data/ssec/
GATEWAY_INTERFACECGI/1.1
HTTP_ACCEPTAccept: application/xhtml+xml,text/html;q=0.9,text/plain;
HTTP_ACCEPT_CHARSETISO-8859-1,utf-8;q=0.7,*;q=0.7
HTTP_ACCEPT_ENCODINGgzip
HTTP_ACCEPT_LANGUAGEen-us,en;q=0.5
HTTP_CACHE_CONTROLno-cache
HTTP_CONNECTIONclose
HTTP_HOSTwww.socialscience-ed.org
HTTP_PRAGMAno-cache
HTTP_USER_AGENTCCBot/1.0 (+http://www.commoncrawl.org/bot.html)
PATH/usr/local/etc/rc.d:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin
QUERY_STRING
REMOTE_ADDR38.103.63.59
REMOTE_PORT46104
REQUEST_METHODGET
REQUEST_URI/pages/bin/configure
SCRIPT_FILENAME/www/data/ssec/pages/bin/configure
SCRIPT_NAME/pages/bin/configure
SERVER_ADDR207.59.156.131
SERVER_ADMINyou@your.address
SERVER_NAMEwww.socialscience-ed.org
SERVER_PORT80
SERVER_PROTOCOLHTTP/1.1
SERVER_SIGNATURE
Apache/1.3.26 Server at www.socialscience-ed.org Port 80
SERVER_SOFTWAREApache/1.3.26 (Unix) mod_ssl/2.8.10 OpenSSL/0.9.6e DAV/1.0.3 PHP/4.3.8 PHP/3.0.18
UNIQUE_IDSOK6JX8AAAEAAA3o03M
CGI Setup(read only) 1 warning
Operating systemUnix (freebsd)
Perl version5.8.7
@INC library path/www/data/ssec/pages/lib
/usr/local/lib/perl5/5.8.7/i386-freebsd
/usr/local/lib/perl5/5.8.7
/usr/local/lib/perl5/site_perl/5.8.7/i386-freebsd
/usr/local/lib/perl5/site_perl/5.8.7
/usr/local/lib/perl5/site_perl/5.8.2
/usr/local/lib/perl5/site_perl/5.8.0
/usr/local/lib/perl5/site_perl/5.6.1
/usr/local/lib/perl5/site_perl/5.005
/usr/local/lib/perl5/site_perl
.

This is the Perl library path, used to load TWiki modules, third-party modules used by some plugins, and Perl built-in modules.

CGI bin directory/www/data/ssec/pages/bin
TWiki module in @INC pathOK, TWiki.pm found (Version: Mon, 29 Aug 2005 build 6193)
Required Perl modules
Error0.15
File::Copy2.08
File::Spec3.05
CGI3.10
CGI::Carp1.29
Algorithm::Diff1.1901
FileHandle2.01
Optional Perl Modules
CGI::Cookie1.25
Digest::SHA12.10
Text::Diff0.35
CGI::Session3.95
Net::SMTP2.29
MIME::Base643.05
POSIX1.08
Digest::MD52.33
PATH_INFO

For a URL such as http://www.socialscience-ed.org/pages/bin/configure/foo/bar, the correct PATH_INFO is /foo/bar, without any prefixed path components. Test this now - particularly if you are using mod_perl, Apache or IIS, or are using a web hosting provider. The page resulting from the test link should have a PATH_INFO of /foo/bar

mod_perlNot used for this script

mod_perl is not loaded into Apache

CGI useruserid = nobody groups = nogroup,nogroup,nogroup

Your CGI scripts are executing as this user.

Original PATH/usr/local/etc/rc.d:/sbin:/bin:/usr/sbin:/usr/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin:/root/bin

This is the PATH value passed in from the web server to this script - it is reset by TWiki scripts to the PATH below, and is provided here for comparison purposes only.

Current PATH/bin:/usr/bin

This is the actual PATH setting that will be used by Perl to run programs. It is normally identical to {SafeEnvPath}, unless that variable is empty, in which case this will be the webserver users standard path..

patch
Warning: 'patch' program was found on the PATH but is not GNU patch - this may cause problems. Patch version 2.1

It is used by the UpgradeTwiki script to upgrade an existing TWiki installation

General path settings
If you are a first-time installer; once you have set up the next six paths below, your TWiki should work - try it. You can always come back and tweak other settings later.
This is the root of all TWiki URLs e.g. http://myhost.com:123.
{DefaultUrlHost}
This is the 'cgi-bin' part of URLs used to access the TWiki bin directory e.g. /twiki/bin
{ScriptUrlPath}
Attachments URL path e.g. /twiki/pub This is not set correctly if the link below is broken:
Go to "pub" directory
{PubUrlPath}
Attachments store (file path, not URL), must match /twiki/pub e.g. /usr/local/twiki/pub
{PubDir}
Template directory e.g. /usr/local/twiki/templates
{TemplateDir}
Topic files store (file path, not URL) e.g. /usr/local/twiki/data
{DataDir}
URL path to scripts used to render links. Defaults to {ScriptUrlPath}. May need to be set if using redirection to shorten URLs.
{DispScriptUrlPath}
Suffix of TWiki CGI scripts (e.g. .cgi or .pl). You may need to set this if your webserver requires an extension.
{ScriptSuffix}
Operating system
{OS} and {DetailedOS} are calculated in the TWiki code. You should only need to override if there is something badly wrong with those calculations.
{OS} may be one of UNIX WINDOWS VMS DOS MACINTOSH OS2
{OS}
The value of Perl $OS
{DetailedOS}
Security setup

Sessions

You can use persistent CGI session tracking even if you are not using login. This allows you to have persistant session variables - for example, skins. Client sessions are not required for logins to work, but TWiki will not be able to remember users unless there is some other mechanism - such as browser cacheing of authentication - available.
{UseClientSessions}
Absolute file path of the directory in which session files are stored. Usually /tmp. You should only have to change this if /tmp if not accessible for some reason. The directory should *not* be browseable from the web!
{SessionDir}

Authentication

TWiki supports different ways of responding when the user asks to log in (or is asked to log in as the result of an access control fault). They are:
  1. none - Don't support logging in, all users have access to everything.
  2. TWiki::Client::TemplateLogin - Redirect to the login template, which asks for a username and password in a form. Does not cache the ID in the browser, so requires client sessions to work.
  3. TWiki::Client::ApacheLogin - Redirect to an '...auth' script for which Apache can be configured to ask for authorization information. Does not require client sessions, but works best with them enabled.
{LoginManager}
Comma-separated list of scripts that require the user to authenticate. With TemplateLogin, if an unauthenticated user attempts to access one of these scripts, they will be redirected to the login script. With ApacheLogin, they will be redirected to the logon script (note login and logon; they are different scripts). This approach means that only the logon script needs to be specified as require valid-user when using Apache authentication.
{AuthScripts}
Authentication realm. This is normally only used in the login prompt screen by the TWiki::Client::TemplateLogin manager.
{AuthRealm}

Passwords

Name of the password handler implementation. The password handler manages the passwords database, and provides password lookup, and optionally password change, services. TWiki ships with two alternative implementations:
  1. TWiki::Users::HtPasswdUser - handles 'htpasswd' format files, with passwords encoded as per the HtpasswdEncoding
  2. TWiki::Users::ApacheHtPasswdUser - should behave identically to HtpasswdUser, but uses the CPAN:Apache::Htpasswd package to interact with Apache. It is shipped mainly as a demonstration of how to write a new password manager.
You can provide your own alternative by implementing a new subclass of TWiki::Users::Password, and pointing {PasswordManager} at it in lib/LocalSite.cfg.

If 'none' is selected, users will not be able to change passwords, and will always be authenticated by the TemplateLogin manager, regardless of what username or password they enter. This may be useful when you want to enable logins so TWiki can identify contributors, but you don't care about passwords.

{PasswordManager}
Path to the file that stores passwords, for the TWiki::Users::HtPasswdUser password manager. You can use the htpasswd Apache program to create a new password file with the right encoding.
{Htpasswd}{FileName}
Password encryption, for the TWiki::Users::HtPasswdUser password manager. You can use the htpasswd Apache program to create a new password file with the right encoding.
crypt
is the default, and should be used on Linux/Unix.
sha1
is recommended for use on Windows.
md5
may be useful on sites where password files are required to be portable. In this case, the {AuthRealm} is used with the username and password to generate the encrypted form of the password, thus: user:{AuthRealm}:password. Take note of this, because it means that if the {AuthRealm} changes, any existing MD5 encoded passwords will be invalidated by the change!
plain
stores passwords as plain text (no encryption).
{Htpasswd}{Encoding}
Hide password in registration email to the *user* Note that TWiki sends admins a separate confirmation.
{HidePasswdInRegistration}
Whether registrations must be verified by the user following a link sent in an email to the user's registered email address
{Register}{NeedVerification}
Map login name to Wiki name via the mapping in the topic named in {UsersTopicName}. Set this to $FALSE for .htpasswd authenticated sites where the user's wiki name is the name they use to log in, or if you have some other way of making the mapping to a Wiki name (e.g. a local Plugin).
{MapUserToWikiName}
Group of users that can use special action=repRev and action=delRev on =save= and ALWAYS have edit powers. See TWiki.TWikiDocumentation for an explanation of twiki groups. Make sure you edit this topic if you enable authentication
{SuperAdminGroup}
Name of topic in the {UsersWebName} web where registered users are listed. Automatically maintained by the standard registration scripts. If you change this setting you will have to use TWiki to manually rename the existing topic
{UsersTopicName}
Path control. If set, overrides the default PATH setting to control where TWiki looks for programs. Check notes for your operating system. NOTE: it is better to use full pathnames in the paths to external programs, rather than relying on this path.
  1. Unix or Linux
    • path separator is :
    • ensure diff and shell (Bourne or bash type) is found on the path.
  2. Windows ActiveState Perl, with non-Cygwin RCS, OR no PERL5SHELL setting.
    • path separator is ;
    • The Windows system directory (e.g. c:\winnt\system32) is required in this path.
    • Must NOT use '/' in pathnames as this upsets cmd.exe - single '' is OK using Perl single-quoted string.
  3. Windows: ActiveState Perl, with Cygwin RCS and PERL5SHELL set to 'c:/cygwin/bin/bash.exe -c'
    • path separator is ;
    • best to avoid 'c:/foo' type paths, because it can cause a Perl 'Insecure directory in $ENV{PATH}' error. The best approach is to convert 'c:/foo' to '/c/cygdrive/foo' - odd looking but it works! The Windows system directory (e.g. /cygdrive/c/winnt/system32) is required in this path. For example: /cygdrive/c/YOURCYGWINDIR/bin;/cygdrive/c/YOURWINDOWSDIR/system32
  4. Windows: ActiveState Perl, with non-Cygwin RCS, OR no PERL5SHELL setting.
    • path separator is ';'
    • The Windows system directory is required in this path. Must NOT use / in directories on the path as this upsets cmd.exe - single '\' is OK using Perl single quoted string.
{SafeEnvPath}
Remove .. from %INCLUDE{filename}%, to stop includes of relative paths.
{DenyDotDotInclude}
Allow the use of SCRIPT tags in content. if this is set false, all SCRIPT sections will be removed from the body of topics. They can still be used in the HEAD section, though. Note that this may prevent some plugins from functioning correctly.
{AllowInlineScript}
Filter-in regex for uploaded (attached) file names (Matching filenames will have .txt appended) WARNING: Be sure to update this list with any configuration or script filetypes that are automatically run by your web server
{UploadFilter}
Filter-in regex for webnames, topic names, usernames, include paths and skin names
{NameFilter}
If this is set, the the search module will use more relaxed rules governing regular expressions searches.
{ForceUnsafeRegexes}
Build the path to /twiki/bin from the URL that was used to get this far. This can be useful when rewriting rules or redirection are used to shorten URLs. Note that displayed links are incorrect after failed authentication if this is set, so unless you really know what you are doing, leave it alone.
{GetScriptUrlFromCgi}
Remove port number from URL. If set, and a URL is given with a port number e.g. http://my.server.com:8080/twiki/bin/view, this will strip off the port number before using the url in links.
{RemovePortNumber}
Anti-spam measures
Standard TWiki incorporates some simple anti-spam measures to protect e-mail addresses and control the activities of benign robots. These should be enough to handle intranet requirements. Administrators of public (internet) sites are strongly recommended to investigate the BlackListPlugin
Text added to email addresses to prevent spambots from grabbing addresses e.g. set to 'NOSPAM' to get fred@user.co.ru rendered as fred@user.co.NOSPAM.ru
{AntiSpam}{EmailPadding}
Options added to external links (links to URLs that do not match {AntiSpam}{Clean}. Public sites should set this to 'rel="nofollow"' to help prevent wiki spammers gaining any benefit from spamming your wiki.
{AntiSpam}{Options}
Regular expression that must match the start of any external links that are _not_ to have the {AntiSpam}{Options} added. The default is to leave links to twiki.org and to the server site untouched.
{AntiSpam}{Clean}
By default, a META tag is generated to tell robots not to index pages viewed in TWiki. You can ask for this tag to be removed in the event that you want topics to be indexed by robots, such as Google. Note that only "normal view" pages can be indexed. If there are any parameters to the view, then it can never be indexed. This is to help prevent inappropriate pages (like the raw view) from ever being spidered.
{AntiSpam}{RobotsAreWelcome}
Log files
Whether or not to to log different actions in the Access log (in order of how frequently they occur in a typical installation). Information in the Access log is used in gathering web statistics, and is useful as an audit trail of TWiki activity.
{Log}{view}
{Log}{search}
{Log}{changes}
{Log}{rdiff}
{Log}{edit}
{Log}{save}
{Log}{upload}
{Log}{attach}
{Log}{rename}
{Log}{register}
File for configuration messages generated by the configure script. (usually very very low volume).
{ConfigurationLogName}
File for debug messages (usually very low volume). %DATE% gets expanded to YYYYMM (year, month), allowing you to rotate logs.
{DebugFileName}
Warnings - low volume, hopefully! %DATE% gets expanded to YYYYMM (year, month), allowing you to rotate logs.
{WarningFileName}
Access log - high volume, depending on what you enabled in {Log} above. %DATE% gets expanded to YYYYMM (year, month), allowing you to rotate logs.
{LogFileName}
Localisation1 warning
Set the timezone (this only effects the display of times, all internal storage is still in GMT). May be gmtime or servertime
{DisplayTimeValues}
Internationalisation Set to enable internationalisation support for 8-bit character sets
{UseLocale}
Site-wide locale - used by TWiki and external programs such as grep, and to specify the character set for the user's web browser. The language part also prevents English plural handling for non-English languages. Ignored unless {UseLocale} is set.
Locale names are not standardised - check 'locale -a' on your system to see what's installed, and check this works using command line tools. You may also need to check what charsets your browsers accept - the 'preferred MIME names' at http://www.iana.org/assignments/character-sets are a good starting point.
WARNING: Topics are stored in site character set format, so data conversion of file names and contents will be needed if you change locales after creating topics whose names or contents include 8-bit characters.
Examples:
de_AT.ISO-8859-15 - Austria with ISO-8859-15 for Euro
ru_RU.KOI8-R - Russia
ja_JP.eucjp - Japan
C - English only; no I18N features
Warning: Unable to set locale to 'en_US.ISO-8859-1'. The actual locale is 'C' - please test your locale settings. This warning can be ignored if you are not planning to use locales (e.g. your site uses English only) - or you can set {Site}{Locale} to C, which should always work.
{Site}{Locale}
Disable to force explicit listing of national chars in regexes, rather than relying on locale-based regexes. Intended for Perl 5.6 or higher on platforms with broken locales: should only be disabled if you have locale problems.
{Site}{LocaleRegexes}
If a suitable working locale is not available (i.e. {UseLocale} is disabled), OR you are using Perl 5.005 (with or without working locales), OR {Site}{LocaleRegexes} is disabled, you can use WikiWords with accented national characters by putting any '8-bit' accented national characters within these strings - i.e. {UpperNational} should contain upper case non-ASCII letters. This is termed 'non-locale regexes' mode. If 'non-locale regexes' is in effect, WikiWord linking will work, but some features such as sorting of WikiWords in search results may not. These features depend on {UseLocale}, which can be set independently of {Site}{{LocaleRegexes}, so they will work with Perl 5.005 as long as {UseLocale} is set and you have working locales.
{UpperNational}
{LowerNational}
Change this only if you must match a specific locale (from 'locale -a') whose character set is not supported by your chosen conversion module (i.e. Encode for Perl 5.8 or higher, or Unicode::MapUTF8 for other Perl versions). For example, if the locale 'ja_JP.eucjp' exists on your system but only 'euc-jp' is supported by Unicode::MapUTF8, set this to 'euc-jp'. If you don't define it, it will automatically be defaulted from the {Site}{Locale}. Only used if {UseLocale} is set.
{Site}{CharSet}
Site language - change this from the default if it is incorrect. Only used if {UseLocale} is set.
{Site}{Lang}
Site language - change this from the default if it is incorrect. Only used if {UseLocale} is set.
{Site}{FullLang}
Store settings2 warnings
Default store implementation.
  • RcsWrap uses normal RCS executables.
  • RcsLite uses a 100% Perl simplified implementation of RCS. RcsLite is useful if you don't have, and can't install, RCS - for example, on a hosted platform. It will work, and is compatible with RCS, but is not quite as fast.
  • Subversive is a thin layer over the Subversion version control system. It is designed for use by developers in a subversion checkout area, and is probably not useful to anyone else.

Note: The 'diff' program found on the path is used by RcsWrap to compare revisions (diff is version 2.7).

{StoreImpl}
Perl regular expression matching suffixes valid on plain text files Defines which attachments will be treated as ASCII in RCS
{RCS}{asciiFileSuffixes}
File security for new directories. You may have to adjust these permissions to allow (or deny) users other than the webserver user access to directories that TWiki creates. This is an *octal* number representing the standard UNIX permissions (e.g. 755 == rwxr-xr-x)
{RCS}{dirPermission}
File security for new files. You may have to adjust these permissions to allow (or deny) users other than the webserver user access to files that TWiki creates. This is an *octal* number representing the standard UNIX permissions (e.g. 644 == rw-r--r--)
{RCS}{filePermission}
Set this if you want to use RCS subdirectories instead of storing ,v files alongside the topics. Not recommended.
{RCS}{useSubDir}
Set this if your RCS cannot check out using the -p option. May be needed in some windows installations (not required for cygwin)
{RCS}{coMustCopy}
Full path to GNU-compatible egrep program. This is used for searching. %CS{|-i}% will be expanded to -i for case-sensitive search or to the empty string otherwise. Similarly for %DET, which controls whether matching lines are required. (see the documentation on these options with GNU grep for details).
Warning: '/bin/egrep' program was not found on the current PATH.
{RCS}{EgrepCmd}
Full path to GNU-compatible fgrep program. This is used for searching.
Warning: '/bin/fgrep' program was not found on the current PATH.
{RCS}{FgrepCmd}
RcsWrap initialise a file as binary. %FILENAME|F% will be expanded to the filename. (/usr/bin/rcs is version 5.7)
{RCS}{initBinaryCmd}
RcsWrap initialise a topic file. (/usr/bin/rcs is version 5.7)
{RCS}{initTextCmd}
RcsWrap uses this on Windows to create temporary binary files during upload. (/usr/bin/rcs is version 5.7)
{RCS}{tmpBinaryCmd}
RcsWrap check-in. %USERNAME|S% will be expanded to the username. %COMMENT|U% will be expanded to the comment. (/usr/bin/ci is version 5.7)
{RCS}{ciCmd}
RcsWrap check in, forcing the date. %DATE|D% will be expanded to the date. (/usr/bin/ci is version 5.7)
{RCS}{ciDateCmd}
RcsWrap check out. %REVISION|N% will be expanded to the revision number (/usr/bin/co is version 5.7)
{RCS}{coCmd}
RcsWrap file history. (/usr/bin/rlog is version 5.7)
{RCS}{histCmd}
RcsWrap revision info about the file. (/usr/bin/rlog is version 5.7)
{RCS}{infoCmd}
RcsWrap revision info about the revision that existed at a given date. %REVISIONn|N% will be expanded to the revision number. %CONTEXT|N% will be expanded to the number of lines of context. (/usr/bin/rlog is version 5.7)
{RCS}{rlogDateCmd}
RcsWrap differences between two revisions. (/usr/bin/rcsdiff is version 5.7)
{RCS}{diffCmd}
RcsWrap lock a file. (/usr/bin/rcs is version 5.7)
{RCS}{lockCmd}
RcsWrap unlock a file. (/usr/bin/rcs is version 5.7)
{RCS}{unlockCmd}
RcsWrap delete a specific revision. (/usr/bin/rcs is version 5.7)
{RCS}{delRevCmd}
Mail and Proxies
Name of topic in each web that has notification registrations. If you change this setting you will have to use TWiki to manually rename the topic in all existing webs
{NotifyTopicName}
Remove IMG tags in notification mails.
{RemoveImgInMailnotify}
Mail program. If Net::SMTP is installed, it will be used in preference. Otherwise this needs to be a command-line program that accepts MIME format mail messages on standard input, and mails them. Net::SMTP is installed in this environment, so this setting will not be used.
{MailProgram}
Mail host for outgoing mail. This is only used if Net::SMTP is installed. Examples: mail.your.company CAUTION This setting can be overridden by a setting of SMTPMAILHOST in TWikiPreferences. Make sure you delete that setting if you are using a TWikiPreferences topic from a previous release of TWiki.
{SMTP}{MAILHOST}
Mail domain sending mail, required if you are using Net::SMTP. SMTP requires that you identify the server sending mail. If not set, Net::SMTP will guess it for you. Example: twiki.your.company. CAUTION This setting can be overridden by a setting of SMTPSENDERHOST in TWikiPreferences. Make sure you delete that setting if you are using a TWikiPreferences topic from a previous release of TWiki.
{SMTP}{SENDERHOST}
Some environments require outbound HTTP traffic to go through a proxy server. (e.g. proxy.your.company). CAUTION This setting can be overridden by a PROXYHOST setting in TWikiPreferences. Make sure you delete the setting from there if you are using a TWikiPreferences topic from a previous release of TWiki.
{PROXY}{HOST}
Some environments require outbound HTTP traffic to go through a proxy server. Set the port number here (e.g: 8080). CAUTION This setting can be overridden by a PROXYPORT setting in TWikiPreferences. Make sure you delete the setting from there if you are using a TWikiPreferences topic from a previous release of TWiki.
{PROXY}{HOST}
Miscellaneous settings
Guest user's login name (guest)
{DefaultUserLogin}
Guest user's wiki name (TWikiGuest)
{DefaultUserWikiName}
Set to enable experimental mirror-site support. If this name is different to MIRRORSITENAME, then this TWiki is assumed to be a mirror of another. You are highly recommended not to dabble with this experimental, undocumented feature!
{SiteWebTopicName}
Set to enable hierarchical webs. Without this setting, TWiki will only allow a single level of hierarchy (webs). If you set this, you can use multiple levels, like a directory tree, i.e. webs within webs. See TWiki.MultiLevelWikiWebs for more details.
{EnableHierarchicalWebs}
Name of the web where docs and site level preferences are held. If you change this setting, you must make sure the web exists and contains appropriate content, and upgrade scripts may no longer work (i.e. don't change it unless you are certain that you know what you are doing!)
{SystemWebName}
Name of the web used as a trashcan (where deleted topics are moved) If you change this setting, you must make sure the web exists.
{TrashWebName}
Name of site-level preferences topic in the system web If you change this setting you will have to use TWiki to manually rename the existing topic.
{SitePrefsTopicName}
Web.TopicName of the site-level local preferences topic. If this topic exists, any settings in it will override settings in {SitePrefsTopicName}.
You are strongly recommended to keep all your local changes in a {LocalSitePreferences} topic rather than changing TWikiPreferences, as it will make upgrading a lot easier.
{LocalSitePreferences}
Name of the web where usertopics are stored. If you change this setting, you must make sure the web exists and contains appropriate content, and upgrade scripts may no longer work (i.e. don't change it unless you are certain that you know what you are doing!)
{UsersWebName}
Name of main topic in a web. If you change this setting you will have to use TWiki to manually rename the topic in all existing webs
{HomeTopicName}
Name of preferences topic in a web. If you change this setting you will have to use TWiki to manually rename the topic in all existing webs
{WebPrefsTopicName}
Name of statistics topic
{Stats}{TopicName}
Number of top viewed topics to show in statistics topic
{Stats}{TopViews}
Number of top contributors to show in statistics topic
{Stats}{TopContrib}
How many links to other revisions to show, 0 for all
{NumberOfRevisions}
If this is set to a > 0 value, and the revision control system supports it (RCS does), then if a second edit of the same topic is done by the same user within this number of seconds, a new revision of the topic will NOT be created (the top revision will be replaced).
{ReplaceIfEditedAgainWithin}
When a topic is edited, the user takes a "lease" on that topic. If another user tries to also edit the topic while the lease is still active, they will get a warning. The warning text will be different depending on whether the lease has "expired" or not i.e. if it was taken out more than LeaseLength seconds ago.
{LeaseLength}
Change non-existant plural topic name to singular, e.g. TestPolicies to TestPolicy.
{PluralToSingular}
Pathname to file that maps file suffixes to MIME types : For Apache server set this to Apache's mime.types file pathname, for example /etc/httpd/mime.types, or use the default shipped in the TWiki data directory.
{MimeTypesFileName}
Directory where registration approvals are held. Should be somewhere that is not browsable from the web.
{RegistrationApprovals}
If set, this will cause TWiki to treat warnings as errors that will cause TWiki to die. Provided for use by Plugin and Skin developers, who should develop with it switched on.
{WarningsAreErrors}
Plugins
The plugins listed below were discovered by searching the @INC path for modules that match the TWiki standard e.g. TWiki/Plugins/MyPlugin.pm. see Installed Plugins for diagnostics
CommentPlugin
{Plugins}{CommentPlugin}{Enabled}
EmptyPlugin
{Plugins}{EmptyPlugin}{Enabled}
NatSkinPlugin
{Plugins}{NatSkinPlugin}{Enabled}
RedDotPlugin
{Plugins}{RedDotPlugin}{Enabled}
SessionPlugin
{Plugins}{SessionPlugin}{Enabled}
Plugins evaluation order. If set to a comma-separated list of plugin names, will change the execution order of plugins so the listed subset of plugins are executed first. The default execution order is alphabetical on plugin name.
{PluginsOrder}
Total: 4 warnings