List this web in the SiteMap. If you want the web listed, then set SITEMAPLIST to on, do not set NOSEARCHALL, and add the "what" and "use to..." description for the site map. Use links that include the name of the web, i.e. Sites.Topic links.Note: Unlike other variables, the setting of SITEMAPLIST is not inherited from parent webs. It has to be set in every web that is to be listed in the SiteMap

Set SITEMAPLIST = on

Set SITEMAPWHAT =

Set SITEMAPUSETO =

Note: Above settings are automatically configured when you create a web

Exclude web from a web="all" search: (Set to on for hidden webs).

Set NOSEARCHALL =

Note: This setting is automatically configured when you create a web

Prevent automatic linking of WikiWords and acronyms (if set to on); link WikiWords (if empty); can be overwritten by web preferences:

#Set NOAUTOLINK =

Note: You can still use the [[...][...]] syntax to link topics if you disabled WikiWord linking. The <noautolink> ... </noautolink> syntax can be used to prevents links within a block of text.

Default template for new topics for this web:

WebTopicEditTemplate: Default template for new topics in this web. (Site-level is used if topic does not exist)

Comma separated list of forms that can be attached to topics in this web. See TWikiForms for more information.

Set WEBFORMS =

Users or groups who are not / are allowed to view / change / rename topics in the Sites web: (See TWikiAccessControl). Remove the # to enable any of these settings. Remember that an empty setting is a valid setting; setting DENYWEBVIEW to nothing means that anyone can view the web.

#Set DENYWEBVIEW =

#Set ALLOWWEBVIEW =

#Set DENYWEBCHANGE =

#Set ALLOWWEBCHANGE =

#Set DENYWEBRENAME =

#Set ALLOWWEBRENAME =

Users or groups allowed to change or rename this WebPreferences topic: (e.g., AdminGroup)

In this list, Set statements which occur at numerically higher locations override macros of the same name defined at lower numbered levels, unless the macro was listed in a finalpreferences setting (finalised) at a lower-numbered level. in this case, the macro is locked to the value at that level; set statements at higher-numbered levels are ignored.

Writing preference settings

Preference settings are written as a simple bullet. In TML, they are written
as 3-spaces,asterisk,equals,value

* Set MYSETTING = My setting value

When using the Wysiwyg editor, click the "Bullet" button and write the setting
as a simple bullet. Don't include the asterisk.

Spaces between the = sign and the value will be ignored. You can split a value over several lines by indenting following lines with spaces - as long as you don't try to use * as the first character on the following line.

Example:

* Set MACRONAME = value starts here
and continues here

Whatever you include in your macro will be expanded on display, exactly as if it had been entered directly (though see Parameters, below).

Example: Create a custom logo macro

To place a logo anywhere in a web by typing %MYLOGO%, define the preference settings in the web's WebPreferences topic, and upload a logo file, ex: mylogo.gif. You can upload by attaching the file to WebPreferences, or, to avoid clutter, to any other topic in the same web, e.g. LogoTopic. Sample preference setting in WebPreferences:

* Set lower = This is LOWER
* Set LOWER = This is UPPER
* Set System.LoWeR = This is MIXED
Expand %lower%, %LOWER% and %LoWeR%

Expand %lower%, %LOWER% and %LoWeR%.

preference settings can easily be disabled with a # sign. Example:

* #Set DENYWEBCHANGE = %USERSWEB%.UnknownUser

Hiding preference settings

You can hide preference settings in the output by enclosing them in HTML comments; for example,

<!--
* Set HIDDEN = This will be invisible in the output
-->

You can also set preference settings in a topic by clicking the link Edit topic preference settings under More topic actions. Preferences set in this manner are known as 'meta' preferences and are not visible in the topic text, but take effect nevertheless.

Caution If your topic will be used in an INCLUDE, it is recommended to not use HTML comments. instead, set preferences
into the topic metadata by using the "Edit Settings for this topic" button on the "More topic actions" page. Settings in an included topic are always ignored,
but nested comments will break the HTML.

Order of perference settings

If you are setting a preference and using it in the same topic, note that Foswiki reads all the preference settings from the saved version of the topic before it displays anything. This means you can use a setting anywhere in the topic, even if you set it at the very end. But beware: it also means that if you change the setting of a macro you are using in the same topic, Preview will show the wrong thing, and you must Save the topic to see it correctly.

Preference settings and topic revision history

Foswiki always reads the settings from the most current topic revision, so viewing older revisions of a topic can show unexpected results.

And especially important, preference settings are never overridden or set in "%INCLUDE{" topics. in the below example about weather conditions, note the difference in the CONDITIONS expansion

Parameters

Note that %CONDITIONS% expands differently when this example is viewed in Macros. This is because Set statement are not active in included topics. The including topic's set statements are used.

Macros defined using preference settings can take parameters. These are symbols passed in the call to the macro to define local macros that will be expanded in the output. For example,

* Set CONDITIONS = According to [[System.%BASETOPIC%][%BASETOPIC%]] the %WHAT% is %STATE% today (Set in ...).

You can call this macro passing in values for WHAT and STATE. For example:

%CONDITIONS{WHAT="sea" STATE="choppy"}%

expands to %CONDITIONS{WHAT="sea" STATE="choppy"}%.

Parameter defaults

The special parameter name DEFAULT gets the value of any unnamed parameter in the macro call.

Parameter macros can accept a default parameter so that they expand to something even when a value isn't passed for them in the call.

Example:

* Set WEATHER = It's %DEFAULT{default="raining"}%.

%WEATHER% expands to %WEATHER%

%WEATHER{"sunny"}% expands to %WEATHER{"sunny"}%

The standard formatting tokens can be used in parameters. They will be expanded immediately when the macro is instantiated.

Note that parameters override all other macros, including system defined macros, in the expansion of the macro where they are used.

Access Control Settings

These are special types of preference settings to control access to content. AccessControl explains these security settings in detail. Parameters are not available in access control settings.

Local values for preferences

Certain topics (user, plugin, web, site and default preferences topics) have a problem; macros defined in those topics can have two meanings. For example, consider a user topic. A user may want to use a double-height edit box when they are editing their home topic - but only when editing their home topic. The rest of the time, they want to have a normal edit box. This separation is achieved using Local in place of Set in the macro definition. For example, if the user sets the following in their home topic:

* Set EDITBOXHEIGHT = 10
* Local EDITBOXHEIGHT = 20

Then, when they are editing any other topic, they will get a 10 high edit box. However, when they are editing their home topic they will get a 20 high edit box.
Local can be used wherever a preference needs to take a different value depending on where the current operation is being performed.

Use this powerful feature with great care! %ALLVARIABLES% can be used to get a listing of the values of all macros in their evaluation order, so you can see macro scope if you get confused.

Deprecation warning. The setting used in
this example, EDITBOXHEIGHT, is being deprecated and will be remove from
Foswiki 1.2. Note that if the edit box size is changed using the javascript
controls in the lower right corner of the edit box window, those settings will
be used, and the EDITBOX* settings will be ignored.