General path settings
Operating system
Security setup 1 warning
Sessions You can use persistent CGI session tracking even if you are not using login.
This allows you to have persistent session variables - for example, skins.
Client sessions are not required for logins to work, but TWiki will not
be able to remember logged-in users consistently.
See TWiki.TWikiUserAuthentication for a full discussion of the pros and
cons of using persistent sessions. Session files are stored in the
{TempfileDir}.
{UseClientSessions}
EXPERT Set the session timeout, in seconds. The session will be cleared after this
amount of time without the session being accessed. The default is 6 hours
(21600 seconds).
Note By default, session expiry is done "on the fly" by the same
processes used to
serve TWiki requests. As such it imposes a load on the server. When
there are very large numbers of session files, this load can become
significant. For best performance, you can set {Sessions}{ExpireAfter}
to a negative number, which will mean that TWiki won't try to clean
up expired sessions using CGI processes. Instead you should use a cron
job to clean up expired sessions. The standard maintenance cron script
tools/tick_twiki.pl includes this function.
Warning: TWiki will *not* clean up sessions automatically. Make sure you
have a cron job running.
{Sessions}{ExpireAfter}δ
EXPERT If you have persistent sessions enabled, then TWiki will use a cookie in
the browser to store the session ID. If the client has cookies disabled,
then TWiki will not be able to record the session. As a fallback, TWiki
can rewrite local URLs to pass the session ID as a parameter to the URL.
This is a potential security risk, because it increases the chance of a
session ID being stolen (accidentally or intentionally) by another user.
If this is turned off, users with cookies disabled will have to
re-authenticate for every secure page access (unless you are using
{Sessions}{MapIP2SID}).
{Sessions}{IDsInURLs}
EXPERT It's important to check that the user trying to use a session is the
same user who originally created the session. TWiki does this by making
sure, before initializing a previously stored session, that the IP
address stored in the session matches the IP address of the user asking
for that session. Turn this off if a client IP address may change during
the lifetime of a session (unlikely)
{Sessions}{UseIPMatching}
EXPERT For compatibility with older versions, TWiki supports the mapping of the
clients IP address to a session ID. You can only use this if all
client IP addresses are known to be unique.
If this option is enabled, TWiki will not store cookies in the
browser.
The mapping is held in the file $TWiki::cfg{TempfileDir}/ip2sid. If you turn
this option on, you can safely turn {Sessions}{IDsInURLs} off .
{Sessions}{MapIP2SID}
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:
none - Don't support logging in, all users have access to everything.
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.
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}δ
TWiki::Client::TemplateLogin none TWiki::Client::ApacheLogin
The perl regular expression used to constrain user login names. Some
environments may require funny characters in login names, such as \.
This is a filter in expression i.e. a login name must match this
expression or an error will be thrown and the login denied.
{LoginNameFilterIn}
EXPERT Guest user's login name. You are recommended not to change this.
{DefaultUserLogin}
EXPERT Guest user's wiki name. You are recommended not to change this.
{DefaultUserWikiName}
EXPERT An admin user login is is required by the install script for some addons and
plugins, usually to gain write access to the TWiki web.
If you change this you risk making topics uneditable.
{AdminUserWikiName}
EXPERT 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. This user will also run all the
standard cron jobs, such as statistics and mail notification.
Make sure you edit this topic if you enable authentication
{SuperAdminGroup}
EXPERT 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}
EXPERT 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}
EXPERT Comma-separated list of scripts that require the user to authenticate.
With TemplateLogin, any time 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.
If you want finer access control (e.g. authorised users only in one web
but open access in another) then you should *clear* this list, and use
TWiki Permissions to control access. Users wishing to make changes will
have to log in by clicking a "log in" link instead of being automatically
redirected when they try to edit.
{AuthScripts}
EXPERT Authentication realm. This is
normally only used in md5 password encoding. You may need to change it
if you are sharing a password file with another application.
{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:
TWiki::Users::HtPasswdUser - handles 'htpasswd' format files, with
passwords encoded as per the HtpasswdEncoding
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}
TWiki::Users::HtPasswdUser none TWiki::Users::ApacheHtpasswdUser
Minimum length for a password, for new registrations and password changes.
If you want to allow null passwords, set this to 0.
{MinPasswordLength}δ
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}
crypt sha1 md5 plain
User Mapping This allows advanced users to write and over-ride the TWiki User and group mappings
rather than the loginname->TWikiUser and Groups definitions comming from TWiki
user and group topics. Currently only TWikiUserMapping is implemented.
TWiki::Users::TWikiUserMapping - uses TWiki user and group topics to determine user
information and group memberships
{UserMappingManager}
TWiki::Users::TWikiUserMapping
Registration If you want users to be able to use a login ID other than their
wikiname, you need to turn this on. It controls whether the 'LoginName'
box appears during the user registration process. If you are using
intranet authentication instead of TWiki authentication, you probably
need to turn this on.
{Register}{AllowLoginName}δ
EXPERT Hide password in registration email to the *user*
Note that TWiki sends admins a separate confirmation.
{Register}{HidePasswd}
EXPERT Whether registrations must be verified by the user following
a link sent in an email to the user's registered email address
{Register}{NeedVerification}
Paths EXPERT 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.
Unix or Linux
path separator is :
ensure diff and shell (Bourne or bash type) is found on
the path.
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.
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 '/cygdrive/c/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
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}
Miscellaneous EXPERT Remove .. from %INCLUDE{filename}%, to stop includes
of relative paths.
{DenyDotDotInclude}
EXPERT
Allow %INCLUDE of URLs. This is disabled by default, because it is possible
to mount a denial-of-service (DoS) attack on a TWiki site using INCLUDE and
URLs. Only enable it if you are in an environment where a DoS attack is not
a high risk.
{INCLUDE}{AllowURLs}
EXPERT Allow the use of SCRIPT and LITERAL tags in content. If this is set false,
all SCRIPT and LITERAL sections will be removed from the body of topics.
SCRIPT can still be used in the HEAD section, though. Note that this may
prevent some plugins from functioning correctly.
{AllowInlineScript}
EXPERT Filter-in regex for uploaded (attached) file names. This is a filter
in , so any files that match this filter will be renamed on upload
to prevent upload of files with the same file extensions as executables.
NOTE: Be sure to update
this list with any configuration or script filetypes that are
automatically run by your web server.
{UploadFilter}
EXPERT Filter-out regex for webnames, topic names, usernames, include paths
and skin names. This is a filter out , so if any of the
characters matched by this expression are seen in names, they will be
removed.
{NameFilter}δ
EXPERT If this is set, the the search module will use more relaxed
rules governing regular expressions searches.
{ForceUnsafeRegexes}
EXPERT 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}
EXPERT Draining STDIN may be necessary if the script is called due to a
redirect and the original query was a POST. In this case the web
server is waiting to write the POST data to this script's STDIN,
but CGI.pm won't drain STDIN as it is seeing a GET because of the
redirect, not a POST. Enable this only in case a TWiki script
hangs.
{DrainStdin}
EXPERT 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}
EXPERT Allow the use of URLs in the redirectto parameter to the
save script, and in topic parameter to the
view script. WARNING: Enabling this feature makes it
very easy to build phishing pages using the wiki, so in general,
public sites should not enable it. Note: It is possible to
redirect to a topic regardless of this setting, such as
redirectto=OtherTopic or redirectto=Web.OtherTopic .
{AllowRedirectUrl}
Anti-spam measures
Log files
Localisation
Configuration items in this section control two things: recognition of
national (non-ascii) characters and the system locale used by TWiki, which
influences how programs TWiki and external programa called by it behave
regarding internationalization.
Note: for user interface internationalization, the only settings that
matter are {UserInterfaceInternationalisation}, which enables user interface
internationalisation, and {Site}{CharSet}, which controls which charset TWiki
will use for storing topics and displaying content for the users. As soon as
{UserInterfaceInternationalisation} is set and the required
(Locale::Maketext::Lexicon
and Encode
/MapUTF8 Perl
modules) are installed (see the CGI Setup section above), the
multi-language user interface will just work.
Enable user interface internationalisation, i.e. presenting the user
interface in the users own language.
Under {UserInterfaceInternationalisation}, check every language that you want
your site to support. This setting is only used when
{UserInterfaceInternationalisation} is enabled. If you disable all languages,
internationalisation will also be disabled, even if
{UserInterfaceInternationalisation} is enabled: internationalisation support
for no languages doesn't make any sense.
Allowing all languages is the best for really international sites.
But for best performance you should enable only the languages you really
need. English is the default language, and is always enabled.
{LocalesDir} is used to find the languages supported in your instalation,
so if the list below is empty, it's probably because {LocalesDir} is pointing
to the wrong place.
{UserInterfaceInternationalisation}
Languages
{Languages}{ru}{Enabled}
{Languages}{sv}{Enabled}
{Languages}{'zh-tw'}{Enabled}
{Languages}{cs}{Enabled}
{Languages}{'zh-cn'}{Enabled}
{Languages}{es}{Enabled}
{Languages}{nl}{Enabled}
{Languages}{pl}{Enabled}
{Languages}{fr}{Enabled}
{Languages}{da}{Enabled}
{Languages}{de}{Enabled}
{Languages}{pt}{Enabled}
{Languages}{it}{Enabled}
Set the timezone (this only effects the display of times,
all internal storage is still in GMT). May be gmtime or servertime
{DisplayTimeValues}
gmtime servertime
Locale - set to enable operating system level locales and
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 in which content must be presented for the user's
web browser.
The language part also prevents English plural handling for non-English
languages. If the language is not English, TWiki won't try to calculate
plurals for WikiNames automatically.
Note that {Site}{Locale} is 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 regarding character
encodings and external programs.
{Site}{Locale}
EXPERT 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}
EXPERT 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}
EXPERT
{LowerNational}
EXPERT 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}δ
EXPERT Site language - change this from the default if it is incorrect. Only
used if {UseLocale} is set.
{Site}{Lang}δ
EXPERT Site language - change this from the default if it is incorrect. Only
used if {UseLocale} is set.
{Site}{FullLang}δ
EXPERT Change non-existant plural topic name to singular,
e.g. TestPolicies to TestPolicy. Only works in English.
{PluralToSingular}
Store settings
EXPERT 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.
You can manually add options to LocalSite.cfg to select a
different store for each web. If $TWiki::cfg{Store}{Fred} is defined, it will
be taken as the name of a perl class (which must implement the methods of
TWiki::Store::RcsFile).
The TWiki::Store::Subversive class is an example implementation using the
Subversion version control system as a data store.
Note: The 'diff' program found on the path is used by RcsWrap to compare
revisions
(diff is version 2.8.1).
{StoreImpl}
RcsWrap RcsLite
Specifies the extension to use on RCS files. Set to -x,v on windows, leave
blank on other platforms.
{RCS}{ExtOption}
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}
EXPERT Some file-based Store implementations (RcsWrap and RcsLite for
example) store attachment meta-data separately from the actual attachments.
This means that it is possible to have a file in an attachment directory
that is not seen as an attachment by TWiki. Sometimes it is desirable to
be able to simply copy files into a directory and have them appear as
attachments, and that's what this feature allows you to do.
Considered experimental.
{AutoAttachPubFiles}
EXPERT Perl regular expression matching suffixes valid on plain text files
Defines which attachments will be treated as ASCII in RCS. This is a
filter in , so any filenames that match this expression will
be treated as ASCII.
{RCS}{asciiFileSuffixes}
EXPERT Set this if you want to use RCS subdirectories instead of storing
,v files alongside the topics. Not recommended.
{RCS}{useSubDir}
EXPERT 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}
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 break a file lock.
{RCS}{breaklockCmd}
RcsWrap delete a specific revision.
(/usr/bin/rcs is version 5.7)
{RCS}{delRevCmd}
TWiki RCS has three built-in search algorithms
The default 'Forking' algorithm, which forks a subprocess that
runs a 'grep' command,
the 'Native' implementation, which uses a search implemented in a
special library (see http://twiki.org/cgi-bin/view/Codev/NativeSearch),
the 'PurePerl' implementation, which is written in Perl and
usually only used as a last resort.
Normally you will be just fine with the 'Forking' implementation. However
if you find searches run very slowly, you may want to try a different
algorithm, which may work better on your configuration.
{RCS}{SearchAlgorithm}
TWiki::Store::SearchAlgorithms::Forking TWiki::Store::SearchAlgorithms::PurePerl TWiki::Store::SearchAlgorithms::Native
EXPERT Full path to GNU-compatible egrep program. This is used for searching when
{SearchAlgorithm} is 'TWiki::Store::SearchAlgorithms::Forking'.
%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).
(/bin/egrep is version 2.5.1).
{RCS}{EgrepCmd}
EXPERT Full path to GNU-compatible fgrep program. This is used for searching when
{SearchAlgorithm} is 'TWiki::Store::SearchAlgorithms::Forking'.
(/bin/fgrep is version 2.5.1).
{RCS}{FgrepCmd}
Path to the directory where the RCS store implementation will create
plugin work areas. Plugin work areas are directories that are managed
by plugins, for example for temporary files. The directory has to be
readable and writable by the webserver user.
{RCS}{WorkAreaDir}δ
Set to enable hierarchical webs. Without this setting, TWiki will only
allow a single level of 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}
EXPERT Name of the web where documentation and default 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}
EXPERT 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}
EXPERT 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}
Mail and Proxies
Statistics
Miscellaneous settings
EXPERT Template path. A comma-separated list of generic file names, containing
variables standing for part of the file name. When a template $name in $web
with $skin is requested, this path is instantiated into a sequence of file
names. The first file on this list that is found considered to be the
requested template file. The file names can either be absolute file names
ending in ".tmpl" or a topic file in a TWiki web.
{TemplatePath}δ
EXPERT List of protocols (URI schemes) that TWiki will
automatically recognize and activate if found in absolute links.
Additions you might find useful in your environment could be 'imap' or 'pop'
(if you are using shared mailboxes accessible through your browser), or 'tel'
if you have a softphone setup that supports links using this URI scheme. A list of popular URI schemes can be
found at http://en.wikipedia.org/wiki/URI_scheme .
{LinkProtocolPattern}
EXPERT 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, untested feature!
{SiteWebTopicName}
EXPERT Name of site-level preferences topic in the {SystemWebName} web.
If you change this setting you will have to
use TWiki and *manually* rename the existing topic.
(i.e. don't change it unless you are certain that you know what
you are doing!)
{SitePrefsTopicName}
EXPERT 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}
EXPERT 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
(i.e. don't change it unless you are certain that you know what
you are doing!)
{HomeTopicName}
EXPERT 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
(i.e. don't change it unless you are certain that you know what
you are doing!)
{WebPrefsTopicName}
EXPERT How many links to other revisions to show in the bottom bar. 0 for all
{NumberOfRevisions}
EXPERT 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). Set this to 0 if you want all topic changes to create
a new revision (as required by most formal development processes).
{ReplaceIfEditedAgainWithin}
EXPERT 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. Leases are released
automatically when the topic is saved; otherwise they remain active
for {LeaseLength} seconds from when the edit started (or was checkpointed).
Note: Leases are not locks; they are purely advisory. Leases
can always be broken, but they are valuable if you want to avoid merge
conflicts (e.g. you use highly structured data in your topic text and
want to avoid ever having to deal with conflicts)
{LeaseLength}
EXPERT Even if the other users' lease has expired, then you can specify that
they should still get a (less forceful) warning about the old lease for
some additional time after the lease expired. You can set this to 0 to
suppress these extra warnings completely, or to -1 so they are always
issued, or to a number of seconds since the old lease expired.
{LeaseLengthLessForceful}
EXPERT 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}δ
EXPERT Directory where registration approvals are held. Should be somewhere
that is not browsable from the web.
{RegistrationApprovals}δ
EXPERT 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