Документ взят из кэша поисковой машины. Адрес
оригинального документа
: http://wiki.cs.msu.ru/System/Macros?cover=print;sortcol=1;table=9;up=0
Дата изменения: Unknown Дата индексирования: Mon Apr 11 18:22:05 2016 Кодировка: |
Macros are text strings in one of two forms:
%MACRONAME% %MACRONAME{ parameter="value" }%These usually expand into content when a topic is rendered for viewing. There are two types of macros:
%CALC{}%
macro)
%T%
to get (a preference settings)
%TOPIC%
to get Macros
(a predefined macro)
%CALC{ "$UPPER(Text)" }%
to get TEXT
(CALC is a macro defined by SpreadSheetPlugin)
!%TOPIC%
to get %TOPIC%
<nop>
anywhere in the macro, Eg. %<nop>TOPIC%
%ALLVARIABLES%
to get a full listing of all macros defined for a particular topic
default
parameter, in which case the value of the default
parameter will replace the macro call in the output. For example, %UNDEFINED{default="blank"}%
will expand to blank
.
Not those that use commonTagsHandler()
Notable exceptions include: CALC, STARTSECTION/ENDSECTION, STARTINCLUDE/STOPINCLUDE
%MACRO1{ something="%MACRO2{ somethingelse="%MACRO3%, %MACRO4%" }%" }%The macros are expanded in this order: MACRO3, MACRO4, MACRO2, MACRO1.
%INCLUDE{ "%QUERY{ "'%THETOPIC%'/%THEFIELD%" }%" section="Summary" }% * Set THETOPIC = %SYSTEMWEB%.FAQWhatIsWikiWiki * Set THEFIELD = TopicClassification
%INCLUDE{ "%QUERY{ "'%SYSTEMWEB%.FAQWhatIsWikiWiki'/%THEFIELD%" }%" section="Summary" }% * Set THETOPIC = %SYSTEMWEB%.FAQWhatIsWikiWiki * Set THEFIELD = TopicClassification
%INCLUDE{ "%QUERY{ "'%SYSTEMWEB%.FAQWhatIsWikiWiki'/TopicClassification" }%" section="Summary" }% * Set THETOPIC = %SYSTEMWEB%.FAQWhatIsWikiWiki * Set THEFIELD = TopicClassification
%INCLUDE{ "%QUERY{ "'System.FAQWhatIsWikiWiki'/TopicClassification" }%" section="Summary" }% * Set THETOPIC = %SYSTEMWEB%.FAQWhatIsWikiWiki * Set THEFIELD = TopicClassification
%INCLUDE{ "FrequentlyAskedQuestion" section="Summary" }% * Set THETOPIC = %SYSTEMWEB%.FAQWhatIsWikiWiki * Set THEFIELD = TopicClassification
These topics are for frequently asked questions including answers. * Set THETOPIC = %SYSTEMWEB%.FAQWhatIsWikiWiki * Set THEFIELD = TopicClassification
These topics are for frequently asked questions including answers. * Set THETOPIC = System.FAQWhatIsWikiWiki * Set THEFIELD = TopicClassification
%
, and escaping any "
character it uses (becomes \"
)
When working with a given macro, consult its documentation to determine which parameters support theExample:$percent/$percnt
format tokens. Generally only output parameters likeheader
,format
andfooter
support format tokens.
%MACRO1{ format="$percentMACRO2{ format=\"%MACRO3%, %MACRO4%\" }$percent" }%The macros are expanded in this order: MACRO3, MACRO4, MACRO1, MACRO2.
%SEARCH{ "info.date >= d2n('2009-01-01') AND info.date <= d2n('2009-12-31')" type="query" limit="2" nonoise="on" format=" * $percentICON{ \"$percentIF{ \"'$topic'/parent.name='%PARENT%'\" then=\"info\" else=\"gear\" }$percent\" }$percent [[$topic]]" }% ---- * Set PARENT = UserDocumentationCategory
%SEARCH{ "info.date >= d2n('2009-01-01') AND info.date <= d2n('2009-12-31')" type="query" limit="2" nonoise="on" format=" * $percentICON{ \"$percentIF{ \"'$topic'/parent.name='UserDocumentationCategory'\" then=\"info\" else=\"gear\" }$percent\" }$percent [[$topic]]" }% ---- * Set PARENT = UserDocumentationCategory
* %ICON{ "%IF{ "'AccessKeys'/parent.name='UserDocumentationCategory'" then="info" else="gear" }%" }% [[AccessKeys]] * %ICON{ "%IF{ "'AdminSkillsAssumptions'/parent.name='UserDocumentationCategory'" then="info" else="gear" }%" }% [[AdminSkillsAssumptions]] ---- * Set PARENT = UserDocumentationCategory
* %ICON{ "info" }% [[AccessKeys]] * %ICON{ "gear" }% [[AdminSkillsAssumptions]] ---- * Set PARENT = UserDocumentationCategory
* <img src="http://wiki.cs.msu.ru/pub/System/DocumentGraphics/info.png"/> [[AccessKeys]] * <img src="http://wiki.cs.msu.ru/pub/System/DocumentGraphics/gear.png"/> [[AdminSkillsAssumptions]] ---- * Set PARENT = UserDocumentationCategory
%MYVAR%
, %MyVar%
, %My2ndVar%
, and %My_Var%
are all separate, valid macro names (macros are case sensitive - %MyVAR%
and %MYVAR%
are not the same).
By convention all settings, predefined macros and macros registered by plugins are always UPPER-CASE.
%META:TOPICPARENT{name="AdminToolsCategory"}% #SettingPrefs
[multiple of 3 spaces] * [space] Set [space] MACRONAME [space] = [space] value
Example:
* Set WEBBGCOLOR = #FFFFC0Macros defined using preference settings are expanded by enclosing their name in percent signs. So when you write
%WEBBGCOLOR%
, it gets expanded to #FFD8AA
A preference macro is always taken from the most current topic revision, even when accessing previous revisions of a topic.
Preferences can be defined in a number of places: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.
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%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 MYLOGO = %PUBURL%/%WEB%/LogoTopic/mylogo.gifPreference settings are case sensitive. (Foswiki by convention always writes settings in upper case.)
* Set lower = This is LOWER * Set LOWER = This is UPPER * Set 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
<!-- * 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.
Preview
will show the wrong thing, and you must Save
the topic to see it correctly.
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* Set CONDITIONS = According to [[%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"}%
DEFAULT
gets the value of any unnamed parameter in the macro call.
default
parameter so that they expand to something even when a value isn't passed for them in the call.
* Set WEATHER = It's %DEFAULT{default="raining"}%.
%WEATHER%
expands to It's raining.
%WEATHER{"sunny"}%
expands to It's sunny.
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 = 20Then, 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.
%SEARCH%
, are powerful and general tools.
Predefined macros can be overridden by preference settings (except TOPIC and WEB) Plugins may extend the set of predefined macros (see individual Plugins topics for details) Take the time to thoroughly read through ALL preference macros. If you actively configure your site, review macros periodically. They cover a wide range of functions, and it can be easy to miss the one perfect macro for something you have in mind. For example, see%BASETOPIC%
,%INCLUDE%
, and the mighty%SEARCH%
.
Your installation of Foswiki v1.1.9 has the following registered macros:
%ACTIVATEDPLUGINS%
%ADDTOZONE{"head" ...}%
%ADDTOZONE{ "zone" ... }%Parameters:
"zone"
optional, comma-separated list of the names of zones that the content should be added to. The only zones guaranteed to exist are head
and script
. Defaults to head
.
id
optional, identifier
for the text being added with the ADDTOZONE
call, to be used in the requires
parameter of other ADDTOZONE
calls. ADDTOZONE
calls with the same id
parameter will simply overwrite the earlier ADDTOZONE
call.
requires="..."
optional, comma separated string of ids
of text within this zone
that this content should follow when the zone is rendered. The content will be rendered even if a specified id
is missing.
text="..."
optional, text to be added to the named zone, mutually exclusive with topic
.
topic="..."
optional, full qualified web.topic
name that contains the text to be added, mutually exclusive with text
. Defaults to %BASETOPIC%
section="..."
optional, section of the topic
to be added, defaults to the default section between STARTINCLUDE and STOPINCLUDE.
head
and script
. The head
zone is rendered
as part of the HTML head section. It is the catch-all container for any content supposed
to be placed into the HTML head section, except Javascript, which is collected in the
script
zone.
All Javascript must always be added to the script
zone exclusively, in order to
grant ordering constraints among scripts are resolved properly. Never add Javascript to
the head
zone -- never add non-Javascript content to the script
zone.
Both zones are added to the HTML head section automatically just before the
closing </head> tag as if they were specified explicitly in the skin templates using:
<head> ... %RENDERZONE{"head"}% %RENDERZONE{"script"}% </head>You may create as many zones in addition to the standard
head
and script
zones as you like. For any non-standard zone specified in
ADDTOZONE you will also need to provide an appropriate
RENDERZONE.
Interesting use cases in wiki applications: sidebar
zone to add widgets,
toolbar
zone to add buttons icons
menu
zone to add menu entries
id
parameter.
An id
identifier is unique within the zone that they are added to.
When the same id
is used in multiple calls to ADDTOZONE the
last call will win, that is previous content of the same id
will be overwritten.
ids
in
the requires
parameter. The requires
parameter constraints the linear order
of content added to a zone. When a zone is rendered, all ordering constraints
expressed via requires
are satisfied. Those ids
not found in a zone don't
have any influence on the final ordering. Missing ids
aren't considered an error
rather than an over-specified ordering problem.
{MergeHeadAndScriptZones}
disabled (default) head
and script
zones are treated separately.
Even when head
and script
zones are treated separately, the head
zone will
always be rendered before the script
zone, unless otherwise specified using RENDERZONE explicitly.
So any content in the script
zone that depends on content placed into
the head
zone is satisfied intrinsicly as they are both rendered as specified above.
{MergeHeadAndScriptZones}
enabled head
and script
zones are separate when adding to them,
but may be treated as merged when you call RENDERZONE if
there are any dependencies specified that only exist in the opposite zone. This
allows an ADDTOZONE{"head"...}
to to successfully require an id
that has
been added to script
.
{MergeHeadAndScriptZones}
is provided to maintain compatibility with legacy extensions that use ADDTOHEAD to add<script>
markup and require content that is now in thescript
zone.{MergeHeadAndScriptZones}
will be removed from a future version of Foswiki.
head
content (and no inline Javascript) depends on
script
content. Any such dependency will be ignored.
In real world application this isn't a problem as Javascript is never added
to the head
zone or Javascript zone part of the script
zone never really
depends on non-Javascript content part of the head
zone.
HTML comment decoration which normally appears after each id's content in the rendered HTML will contain a small informative text to aid debugging.
Example%ADDTOZONE{ "script" text=" <script type='text/javascript'> alert('test'); </script>" requires="some-id-that-exists-in-script" id="MY::TEST" }%Result
<script type='text/javascript'> alert('test'); </script> <!-- MY::TEST: requires= missing ids: some-id-that-exists-in-script -->
%ADDTOZONE{"script"...requires="library-id"}%
with the appropriate library-id to guarantee a correct load order. For example, jQuery code should be added as follows:
%JQREQUIRE{"shake"}% %ADDTOZONE{ "script" id="MyApp::ShakePart" text=" <script type='text/javascript'> jQuery('#something').shake(3, 10, 180); </script>" requires="JQUERYPLUGIN::SHAKE" }%where "MyApp::ShakePart" is a unique
id
to identify the text added to
script
; and JQUERYPLUGIN::SHAKE
signifies that the content added with that
identifier should appear beforehand.
%ADDTOZONE{"head" id="MyCSS" text=" <style type='text/css' media='all'> @import url('%PUBURLPATH%/%SYSTEMWEB%/MyCSS/foo.css'); </style>" }%See also RENDERZONE, Using ADDTOZONE, Updating applications to use
script
zone
%ALLVARIABLES%
AQUA
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%AQUA% aqua text %ENDCOLOR%Expands to: aqua text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%ATTACHURL%
http://wiki.cs.msu.ru/pub/System/VarATTACHURL
%ATTACHURL%/image.gif
%ATTACHURLPATH%
/pub/System/VarATTACHURLPATH
{AuthRealm}
expert option in configure. This is used in certain password encodings, and in login templates as part of the login prompt.
%AUTHREALM%
%TOPIC%
if there is no INCLUDE
%BASETOPIC%
%WEB%
in case there is no include.
%BASEWEB%
BLACK
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%BLACK% black text %ENDCOLOR%Expands to: black text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
BLUE
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%BLUE% blue text %ENDCOLOR%Expands to: blue text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
BROWN
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%BROWN% brown text %ENDCOLOR%Expands to: brown text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
Parameter: | Description: | Default: |
---|---|---|
"text", value="text" | text to be put on this button | |
accesskey | access key used for this button | |
class | extra class: use foswikiRight or foswikiLeft to specify aligment; use cyan , red , green for different background colors; use simple for a non-3D button | |
href | url of the click target | # |
icon | icon to be put on the left; note, this can be any icon attached to the {IconSearchPath} ; see also VarJQICON | |
id | html id for this button | |
onclick | javascript event triggered when clicking the button | |
onmouseout | javascript event triggered when the pointer leaves the button | |
onmouseover | javascript event triggered when the pointer hovers over the button | |
target | topic to open when clicking on the button | |
title | popup title displayed when hovering over the button | |
type | type of action to be performed; available actions are
| button |
%BUTTON{ "%MAKETEXT{"Submit"}%" onclick="confirm('Are your sure?')" }% %BUTTON{ "%MAKETEXT{"Cancel"}%" icon="cross" target="%WEB%.%TOPIC%" }% %CLEAR%
%CLEAR%
after the %BUTTON{...}%
so that further content does not overlap with the button.
%CALC{"formula"}%
macro is handled by the SpreadSheetPlugin. There are around 90 formulae, such as $ABS()
, $EXACT()
, $EXISTS()
, $GET()/$SET()
, $IF()
, $LOG()
, $LOWER()
, $PERCENTILE()
, $TIME()
, $VALUE()
.
%CALC{"formula"}%
%CALC{"$SUM($ABOVE())"}%
returns the sum of all cells above the current cell
%CALC{"$EXISTS(Web.SomeTopic)"}%
returns 1
if the topic exists
%CALC{"$UPPER(Collaboration)"}%
returns COLLABORATION
%COMMENT%
without parameters shows a simple text box.
Name | Description | Default |
---|---|---|
type | This is the name of the template to use for this comment. Comment templates are defined in a Foswiki template - see Customisation, below. If this attribute is not defined, the type is whatever is defined by COMMENTPLUGIN_DEFAULT_TYPE, either in this topic or in your WebPreferences. | below |
default | Default text to put into the textarea of the prompt. | |
target | Name of the topic to add the comment to | the current topic |
location | Regular expression specifying the comment location in the target topic. Read carefully the CommentPlugin documentation! | |
mode | For compatibility with older versions only, synonymous with type | |
nonotify | Set to "on" to disable change notification for target topics | off |
noform | Set to "on" to disable the automatic form that encloses your comment block - remember to insert <form> tags yourself! See CommentPluginExamples:noform for an example. | off |
nopost | Set to "on" to disable insertion of the posted text into the topic. | off |
remove | Set to "on" to remove the comment prompt after the first time it is clicked. | off |
button | Button label text | Add comment |
%COVER%
extends the skin search path. For instance, if SKIN is set to catskin, bearskin
, and COVER
is set to ruskin
, the skin search path becomes ruskin, catskin, bearskin
.
COVER
setting can be overridden using the URL parameter cover
, such as ?cover=ruskin
%COVER%
%COVER%
%DATE%
11 Apr 2016
When used in a template topic, this variable will be expanded when the template is used to create a new topic. See TemplateTopics#TemplateTopicsVars for details.
%GMTIME%
%DISPLAYTIME%
OR %DISPLAYTIME{"format"}%
%DISPLAYTIME%
The time is shown as hh:mm (24 hour clock) 11 Apr 2016 - 15:22
%DISPLAYTIME{"$hou:$min"}%expands to
15:22
EDITACTION
preference setting lets you define the use of an editaction template instead of the standard edit. If EDITACTION
is defined as text
, then hide the form. If EDITACTION
is defined as form
hide the normal text area and only edit the form.
* Set EDITACTION = text|form
%EDITACTION%
WhenEDITACTION
is defined as text or form the Edit and Edit Raw buttons simply add;action=text
or;action=form
to the URL for the edit script. If you have defined anEDITACTION
preference setting you can still edit the topic content or the form by removing the;action=form
or;action=text
from the edit URL in the browser and reload.
%EDITTABLE{}%
macro is handled by the EditTablePlugin
%EDITTABLE{ attributes }%
Attribute | Comment | Default |
---|---|---|
header | Specify the header format of a new table like "|*Food*|*Drink*|" . Useful to start a table with only a button | (no header) |
format | The format of one column when editing the table. A cell can be a text input field, or any of these edit field types: • Text input field (1 line): | text, <size>, <initial value> | • Textarea input field: | textarea, <rows>x<columns>, <initial value> | • Drop down box: | select, <size>, <option 1>, <option 2>, etc* | * only one item can be selected • Radio buttons: | radio, <size*>, <option 1>, <option 2>, etc | * size indicates the number of buttons per line in edit mode • Checkboxes: | checkbox, <size*>, <option 1>, <option 2>, etc | * size indicates the number of checkboxes per line in edit mode • Fixed label: | label, 0, <label text> | • Row number: | row, <offset> | • Date: | date, <size>, <initial value>, <DHTML date format> | (see Date Field Type) | "text, 16" for all cells |
changerows | Rows can be added and removed if "on" Rows can be added but not removed if "add" Rows cannot be added or removed if "off" | CHANGEROWS plugin setting |
quietsave | Quiet Save button is shown if "on" , hidden if "off" | QUIETSAVE plugin setting |
include | Other topic defining the EDITTABLE parameters. The first %EDITTABLE% in the topic is used. This is useful if you have many topics with the same table format and you want to update the format in one place. Use topic or web.topic notation. | (none) |
helptopic | Topic name containing help text shown below the table when editing a table. The %STARTINCLUDE% and %STOPINCLUDE% macros can be used in the topic to specify what is shown. | (no help text) |
headerislabel | Table header cells are read-only (labels) if "on" ; header cells can be edited if "off" or "0" | "on" |
editbutton | Set edit button text, e.g. "Edit this table" ; set button image with alt text, e.g. "Edit table, %PUBURL%/%SYSTEMWEB%/DocumentGraphics/edittopic.gif" ; hide edit button at the end of the table with "hide" (Note: Button is automatically hidden if an edit button is present in a cell) | EDITBUTTON plugin setting |
buttonrow | Set to top to put the edit buttons above the table. | bottom |
javascriptinterface | Use javascript to directly move and delete row without page refresh. Enable with "on" , disable with "off" . | JAVASCRIPTINTERFACE plugin setting |
%EDITTABLE{ format="| text, 20 | select, 1, one, two, three |" changerows="on" }% | *Name* | *Type* | | Foo | two |Produces:
"string"
, by mapping characters (or sequences of characters) to an alternative character (or sequence of characters). This macro can be used to encode strings for use in URLs, to encode to HTML entities, to protect quotes, and for as many other uses as you can imagine.
%ENCODE{"string"}%
Parameter | Description | Default |
---|---|---|
"string" | String to encode | "" (empty string) |
type="encodingname" | Use a predefined encoding (see below). | Default is 'url'. Parameter type not be used if old or new are given. |
old="tokenlist" | Comma-separated list of tokens to replace. Tokens are normally single characters, but can also be sequences of characters. The standard format tokens may be used in this list. Each token must be unique - you cannot list the same token twice. | May not be used with type ; required if new is used |
new="tokenlist" | comma-separated list of replacement tokens. The elements in this list match 1:1 with the elements in the old list. Again, the standard format tokens may be used. An empty element in the new list will result in the corresponding token in the old list being deleted from the string. If the new list is shorter than the old list it will be extended to the same length using the empty element. Tokens do not have to be unique. When using | May not be used with type ; required if old is used |
ENCODE
is called with no optional parameters (e.g. %ENCODE{"string"}%
) then the default type="url"
encoding will be used.
type
parameter encodes the following "special characters" "\n"
) and carriage return ("\r"
)
"<"
, ">"
, "&"
, single quote ('
) and double quote ("
)
"%"
, "["
, "]"
, "@"
, "_"
, "*"
, "="
and "|"
type="entity"
or type="entities"
Encode special characters into HTML entities, like a double quote into "
. Does not encode \n
(newline).
type="html"
As type="entity"
except it also encodes \n
(newline)
type="safe"
Encode just the characters '"<>%
into HTML entities.
type="quote"
or type="quotes"
Escapes double quotes with backslashes (\"
), does not change any other characters
type="url"
Encode special characters for use in URL parameters, like a double quote into %22
%ENCODE{"spaced name"}%= expands to spaced%20name %ENCODE{"| Blah | | More blah |" old="|,$n" new="|,<br />"}% expands to | Blah | | More blah | - this encoding is useful to protect special TML characters in tables. %ENCODE{"10xx1x01x" old="1,x,0" new="A,,B"}% expands to ABABA %ENCODE{"1,2" old="$comma" new=";"}% expands to 1;2
<input type="text" name="address" value="%ENCODE{ "any text" type="entity" }%" />
ENCODE
can be used to filter user input from URL parameters and similar to help protect against cross-site scripting. The safest approach is to use type="entity"
. This can however prevent an application from fully working. You can alternatively use type="safe"
which encodes only the characters '"<>%
into HTML entities. When ENCODE
is passing a string inside another macro always use double quotes ("") type="quote". For maximum protection against cross-site scripting you are advised to install the Foswiki:Extensions.SafeWikiPlugin.
%SEARCH{ "%ENCODE{ "string with "quotes"" type="quotes" }%" noheader="on" }%
When usingold
andnew
, be aware that the results of applying earlier tokens are not processed again using later tokens. For example:%ENCODE{"A" old="A,B" new="B,C"}% will result in 'B' (not 'C'), %ENCODE{"asd" old="as,d" new="d,f"}% will yield 'df', and %ENCODE{"A" old="A,AA" new="AA,B"}% will give 'AA' and. %ENCODE{"asdf" old="a,asdf" new="a,2"}% will give 'asdf'
ENDCOLOR
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of shortcuts.%GREEN% green text %ENDCOLOR%Expands to: green text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%ENDSECTION{"name"}%
%ENDSECTION{type="include"}%
Parameter: | Description: |
---|---|
"name" | Name of the section. |
type="..." | Type of the section being terminated; supported types "section" , "include" , "expandvariables" , "templateonly" . |
STARTSECTION
is named, the corresponding ENDSECTION
must also be named with the same name. If the STARTSECTION
specifies a type, then the corresponding ENDSECTION
must also specify the same type. If the section is unnamed, ENDSECTION
will match with the nearest unnamed %STARTSECTION%
of the same type above it.
%ENDTWISTY%
%ENDTWISTYTOGGLE%
%ENDTWISTYTOGGLE%
{AccessibleENV}
in the Security Settings/Miscellaneous section of configure
can be displayed. Any other variable will just be shown as an empty string, irrespective of its real value.
%ENV{MOD_PERL}%
displays as: not set
not set
.
%EXAMPLETAG{}%
variable is handled by the ExamplePlugin
%EXAMPLETAG{"text" format="..."}%
text="..."
- example text.
format="..."
- format of report.
%EXAMPLETAG{"hello" format="| $topic: $summary |"}%
expression
as if they were used in the topic topictoexpandin
. The viewer must have VIEW access to topictoexpandin
for this to work. All the standard formatting macros can be used in expression
, such as $percent
and $quot
.
EXPAND
can be useful when you want to pick up the value of macros defined in another topic. For example, you might want to define a set of preferences in one topic, but pick up their value in another topic (this is very useful when building reusable applications). In this case you can write:
* Set MYPREFERENCE = valuein "SettingsTopic" and then, in "MyTopic", write:
%EXPAND{"$percentMYPREFERENCE$percent" scope="SettingsTopic"}%Of course we can also write:
%EXPAND{"$percentMYPREFERENCE$percent" scope="%OTHERTOPIC%"}%which lets us select which other topic to get the preference value from.
Additional parameters can be passed to the macro being expanded using the standard macro syntax in the name of the macro; for example,
%EXPAND{"$percentMYPREFERENCE{$quotdefault$quot param=$quotvalue$quot}" scope="SettingsTopic"}%Notes:
EXPAND
is not very efficient, and should be used sparingly.
scope="Theotherweb.%WEBPREFSTOPIC%"
%FAILEDPLUGINS%
%FORMAT{"list"}%
Parameter: | Description: | Default: |
---|---|---|
"one, two, three" | The list to be expanded into the format. Required. Currently only two types of list data are supported; topic names (type="topic" ) and plain strings (type="string" ). | "" |
format="..." | Format string; see Supported formatting tokens for possible values. | "" |
header="..." | Text to come before the formatted output | "" |
footer="..." | Text to come after the formatted output | "" |
separator="n" | Separator between formatted elements | "$n" |
type="" | Treat input list as either topic or string | "topic" |
%FORMAT{"one,two,three" type="string" format=" * $item"}% %FORMAT{"%SKIN%" header="the Skin setting is evaluated in this order:" format=" 1 =$topic=" footer=" 1 =default=" }%
type="topic"
(the default) the format string can contain any of the
topic-specific format tokens
specified in FormattedSearch ($web
, $topic
, $parent
, $text
, $locked
,
$date
, $isodate
, $index
, $item
, $rev
, $username
, $wikiname
, $wikiusername
,
$createdate
, $createusername
, $createwikiname
, $createwikiusername
,
$summary
, $changes
, $formname
, $formfield
, $pattern
, $count
,
$ntopics
, $nhits
, $pager
).
In addition, the macro supports all the standard format tokens.
If type="string"
then the comma separated list is treated as a list of
strings. In this case, the format tokens $index
and $item
will return
the position of the item in the list (1-based), and the item itself,
respectively. Note that a comma can be embedded in the data using the standard
formatting token $comma
.
The FORMAT macro is currently only of use in formatting lists of topics, or of simple strings. It will be extended in future releases to add the capability to render other object types.
For more sophisticated handling of string lists, consider installing Foswiki:Extensions.FilterPlugin.
%FORMFIELD{"fieldname"}%
Parameter: | Description: | Default: |
---|---|---|
"fieldname" | The name of a Data form field | required |
topic="..." | Topic where form data is located. May be of the form Web.TopicName | Current topic |
format="..." | Format string. $value expands to the field value, and $name expands to the field name, $title to the field title, $form to the name of the form the field is in. The standard format tokens are also expanded. | "$value" |
default="..." | Text shown if the field is defined in the topic, but the field value is empty. For example, a text field for which all the content has been deleted. | "" |
alttext="..." | Text shown if the field is not defined in the topic (even if it is specified in the form definition). For example, this is used when a field exists in the form definition, but the referring topic hasn't been edited since it was added. | "" |
rev="n" | Specifiy a revision of the topic. If not specified, defaults to the most recent rev (or the viewed rev if viewing an old rev of the same topic) |
%FORMFIELD{"ProjectName" topic="Projects.SushiProject" default="(no project name given)" alttext="ProjectName field not found in form" }%
%GENPDF%
http://wiki.cs.msu.ru/bin/genpdf/System/VarGENPDF?cover=print;sortcol=1;table=9;up=0
%GMTIME%
OR %GMTIME{"format"}%
%GMTIME%
uses the default date format defined by the {DefaultDateFormat} setting in configure Token: | Unit: | Example |
---|---|---|
$mo | 2 digit month | 12 |
$ye | 2 digit year | 99 |
$year | 4 digit year | 1999 |
$day | day of month | 31 |
$dow | day of the week (Sun = 0) | 2 |
$wday | day of the Week (Sun, Mon, Tue, Wed, Thu, Fri, Sat) | Thu |
$http | E-mail & http format timestamp | Mon, 11 Apr 2016 15:22:12 GMT |
$tz | either "GMT" (if set to gmtime), or "Local" (if set to servertime) | GMT |
$hours | hours | 23 |
$iso | ISO format timestamp | 2016-04-11T15:22:12Z |
$minutes | minutes | 59 |
$epoch | Number of seconds since 00:00 on 1st January, 1970 | 1460388132 |
$week | number of week in year (ISO 8601) | 34 |
$rcs | RCS format timestamp | 2016/04/11 15:22:12 |
$seconds | seconds | 59 |
$month | short name of month | Dec |
%GMTIME{"$day $month, $year - $hour:$min:$sec"}%expands to
11 Apr, 2016 - 15:22:12
When used in a template topic, this macro will be expanded when the template is used to create a new topic. See TemplateTopics#TemplateTopicsVars for details.
GRAY
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%GRAY% gray text %ENDCOLOR%Expands to: gray text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
GREEN
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%GREEN% green text %ENDCOLOR%Expands to: green text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%GROUPINFO%
%GROUPINFO{"groupname"}%
format | Format of a single user or group in the list.
| $name for groups list, $wikiusername for users list |
separator | separator between items in the list | , |
header | Header for the list | '' |
footer | Footer for the list | '' |
zeroresults | If set, and there are no Groups or Members that can be shown, the header and footer are suppressed, and this text is output | undefined |
show | filter the output list of Groups - can be set to all , allowschange , denychange , allowschange(UserWikiName) , denychange(UserWikiName) | all |
expand | Set false if users should not be expanded from nested groups. Default behavior is to expand all nested groups into a flat list of users. | 1 |
limit | If set, limits the number of results to this | infinity |
limited | If limit is set, and the list is truncated, this text will be added at the end of the list | '' |
Note: GROUPINFO will not list members that are hidden from the current authenticated user. If the current user does not have VIEW authority for a user's topic, then the user will not be shown as a group member.
%GROUPS%
%HISTORY{}%
macro is handled by the HistoryPlugin
%HISTORY{ attributes }%
Argument | Description | Default value |
---|---|---|
none | Default layout: a simple list of topic revisions using the default format (see below) | |
"format" or format="string" |
Format of one line, may include any variable which is supported by macro REVINFO | "r$rev - $date - $wikiusername" |
topic="topic" |
Topic name, can be in web.topic format |
current topic |
web="web" |
Web name | current web |
versions="number or range" |
Number or range (format: from..to ). Examples: To get version 2, write: versions="2" To get version 2 to 3, write: versions="2..3" To get version 2 to the latest, write: versions="2.." To get all versions up to version 5, write: versions="..5" To get all versions up to but not including the latest, write: versions="..-1" To get the versions from 1 to 5 in reverse order, write: versions="5..1" |
all versions in the order latest to first |
header="text" |
Text to print before the list. May contain the tokens $next and $previous which will be evaluated if there are newer or older revisions available for the topic that are not listed according to versions (or rev1 , rev2 , nrev ). These tokens take the syntax $next{'some text' url='url'} (the same for $previous ). 'some text' is the text which should be printed, 'url' is the url for the corresponding link. The tokens $rev1 , $rev2 , $nrev in 'text' or 'url' will be replaced by appropriate values for the next or previous block of revisions. See the attached oopshistory.tmpl for an example of how to use this. |
"$next" |
footer="text" |
Text to print after the list. May contain the tokens $next and $previous (see header ) |
"$previous" |
Argument | Description | Default value |
---|---|---|
nrev="number" |
Number of revisions to show. Ignored if versions is specified, or if both rev1 and rev2 are specified. |
10 |
rev2="number" |
Newest revision to show | rev1+nrev if rev1 is specified, latest revision otherwise |
rev1="number" |
Oldest revision to show | rev2-nrev |
reverse="boolean" |
Show newest revisions first, if on |
"on" |
%HISTORY%
on the page. If more than one %HISTORY%
is used on the same page, the values from the last one will be used.
%HISTORY_REV1%
: Oldest revision from the printed history
%HISTORY_REV2%
: Latest revision from the printed history
%HISTORY_NREV%
: Number of the printed revisions
%HISTORY_MAXREV%
: Latest available revision of the topic
%HOMETOPIC%
WebHome
, renders as WebHome
%HTTP%
%HTTP{"Header-name"}%
%HTTP% | |
%HTTP{"Accept-language"}% | |
%HTTP{"User-Agent"}% | GTS_Crawler/0.7.3 |
You can see the HTTP headers your browser sends to the server on a number of sites e.g. http://www.ericgiguere.com/tools/http-header-viewer.html
%HTTP_HOST%
wiki.cs.msu.ru
%HTTP%
but operates on the HTTPS environment variables present when the SSL protocol is in effect. Can be used to determine whether SSL is turned on.
%HTTPS%
%HTTPS{"Header-name"}%
default
parameter will be used (and if that fails, the 'else' icon will be used)
%ICON{"flag-gray"}%
displays as
%ICON{"pdf"}%
displays as
%ICON{"docx" default="doc"}%
displays as
%ICON{"smile.pdf"}%
displays as
%ICON{"/dont/you/dare/smile.pdf"}%
returns
%ICON{"data.unknown" alt="Unknown file type"}%
displays as
%ICON{"data.unknown"}%
displays as
%ICON{"http://trunk.foswiki.org/pub/System/DocumentGraphics/xsl.gif"}%
displays
arrowbright
, bubble
, choice-yes
, hand
bmp
, doc
, gif
, hlp
, html
, mp3
, pdf
, ppt
, txt
, xls
, xml
, zip
%ICON{"name"}%
generates the full HTML img tag. Specify image name or full filename (see ICON for details on filenames.)
%ICONURL{"name"}%
%ICONURL{"arrowbright"}%
returns http://wiki.cs.msu.ru/pub/System/DocumentGraphics/arrowbright.png
%ICONURL{"novel.pdf"}%
returns http://wiki.cs.msu.ru/pub/System/DocumentGraphics/pdf.png
%ICONURL{"/queen/boheme.mp3"}%
returns http://wiki.cs.msu.ru/pub/System/DocumentGraphics/mp3.png
%ICONURLPATH{"name"}%
%ICONURLPATH{"locktopic"}%
returns /pub/System/DocumentGraphics/locktopic.png
%ICONURLPATH{"eggysmell.xml"}%
returns /pub/System/DocumentGraphics/xml.png
%ICONURLPATH{"/doc/xhtml.xsl"}%
returns /pub/System/DocumentGraphics/xsl.png
%IF{"CONDITION" then="THEN" else="ELSE"}%shows
"THEN"
if "CONDITION"
evaluates to TRUE
, otherwise "ELSE"
will be shown
%IF{"defined FUNFACTOR" then="FUNFACTOR is defined" else="FUNFACTOR is not defined" }%renders as
FUNFACTOR is not defined
%INCLUDE{"topic" ...}%
(See also the URL form of %INCLUDE%
)
Parameter: | Description: | Default: |
---|---|---|
"SomeTopic" | The name of a topic located in the current web, i.e. %INCLUDE{"WebNotify"}% | |
"Web.Topic" | A topic in another web, i.e. %INCLUDE{"System.SiteMap"}% | |
pattern="..." | Include a subset of a topic or a web page. Specify a RegularExpression that contains the text you want to keep in parenthesis, e.g. pattern="(from here.*?to here)" . IncludeTopicsAndWebPages has more. | none |
rev="2" | Include a previous topic revision; N/A for URLs | top revision |
warn="off" | Warn if topic include fails: Fail silently (if off ); output default warning (if set to on ); else, output specific text (use $topic for topic name) | %INCLUDEWARNING% preferences setting |
section="name" | Includes only the specified named section, as defined in the included topic by the STARTSECTION{"name" type="section"} and ENDSECTION{"name" type="section"} macros. Nothing is shown if the named section does not exists. section="" is equivalent to not specifying a section | |
PARONE="val 1" | Any other parameter will be defined as a macro within the scope of the included topic. The example parameters on the left will result in %PARONE% and %PARTWO% being defined within the included topic. |
%INCLUDE{"http://..." ...}%
(See also the topic form of %INCLUDE%
)
Parameter: | Description: | Default: |
---|---|---|
"http://..." | A full qualified URL, i.e. %INCLUDE{"http://foswiki.org:80/index.html"}% . Supported content types are text/html and text/plain . If the URL resolves to an attachment file on the server this will automatically translate to a server-side include. | |
pattern="..." | Include a subset of a topic or a web page. Specify a RegularExpression that contains the text you want to keep in parenthesis, e.g. pattern="(from here.*?to here)" . IncludeTopicsAndWebPages has more. | none |
raw="on" | When a page is included, normally Foswiki will process it, doing the following: 1) Alter relative links to point back to originating host, 2) Remove some basic HTML tags (html, head, body, script) and finally 3) Remove newlines from HTML tags spanning multiple lines. If you prefer to include exactly what is in the source of the originating page set this to on . raw="on" is short for disableremoveheaders="on" , disableremovescript="on" , disableremovebody="on" , disablecompresstags="on" and disablerewriteurls="on" . | disabled |
literal="on" | While using the raw option will indeed include the raw content, the included content will still be processed and rendered like regular topic content. To disable parsing of the included content, set the literal option to "on" . | disabled |
disableremoveheaders="on" | Bypass stripping headers from included HTML (everything until first </head> tag) | disabled |
disableremovescript="on" | Bypass stripping all <script> tags from included HTML | disabled |
disableremovebody="on" | Bypass stripping the </body> tag and everything around over and below it | disabled |
disablecompresstags="on" | Bypass replacing newlines in HTML tags with spaces. This compression step rewrites unmatched <'s into < entities unless bypassed | disabled |
disablerewriteurls="on" | Bypass rewriting relative URLs into absolute ones | disabled |
warn="off" | Warn if URL include fails: Fail silently (if off ); output default warning (if set to on ); else, output specific text (use $topic for topic name) appended with the http error information. | %INCLUDEWARNING% preferences setting |
JavaScript in included webpages is filtered out as a security precaution per default (disable filter with disableremovescript
parameter)
Foswiki by default is configured to deny URL format includes.
%INCLUDE{"doc:Foswiki::Func" ...}%
Parameter: | Description: | Default: |
---|---|---|
"doc:..." | A full qualified Foswiki module, i.e. %INCLUDE{"doc:Foswiki::Func"}% . The module must be found on the Foswiki lib path | |
level="1" | Override the root heading level to the specified number | |
pattern="..." | Include a subset of the module. Specify a RegularExpression that contains the text you want to keep in parenthesis, e.g. pattern="(from here.*?to here)" . IncludeTopicsAndWebPages has more. | none |
%TOPIC%
in case there is no include
INCLUDEs
, INCLUDINGTOPIC
is set to the topic directly INCLUDing this one, NOT the topic that has been requested by the user (which is set in BASETOPIC
) While this Macro may appear to work, unless you require the subtle difference betweenINCLUDINGTOPIC
andBASETOPIC
, you probably should useBASETOPIC
%INCLUDINGTOPIC%
%WEB%
if there is no INCLUDE
.
INCLUDEs
, INCLUDINGWEB
is set to the topic directly INCLUDing this one, NOT the web that has been requested by the user (which is set in BASEWEB
) While this Macro may appear to work, unless you require the subtle difference betweenINCLUDINGWEB
andBASEWEB
, you probably should useBASEWEB
%INCLUDINGWEB%
{JQueryPlugin}{IconSearchPath}
and defaults to FamFamFamSilkIcons, FamFamFamSilkCompanion1Icons, FamFamFamFlagIcons, FamFamFamMiniIcons, FamFamFamMintIcons'. The named icon will be picked found first on this path of topics where icons are attached to. The JQICON leverages the general icon loading mechanism as implemented by the JQueryPlugin and used by BUTTON as well.
Parameter: | Description: | Default: |
---|---|---|
"name" | name of the icon to display | |
class | additional css class for the img tag | |
alt | alt attribute | |
title | title attribute | |
format | format string used to render the icon; known variables to be used in the format string are:
| <img src='$iconPath' class='$iconClass' $iconAlt$iconTitle/> |
%JQICON{"tick" alt="alternative content" title="this is a tick icon"}% %JQICON{"cross"}% %JQICON{"disk"}% %JQICON{"star"}% %JQICON{"lightbulb"}% %JQICON{"camera"}% %JQICON{"date"}%Produces:
%JQICON{"name" format="$iconPath"}%
/pub/System/FamFamFamSilkIcons/tick.png
Parameter: | Description: | Default: |
---|---|---|
"plugins" | this is a regular expression that the plugin identifier must match to be displayed | |
format | format string to render information for each matching plugin; known variables to be used in the format string are:
| 1 <a href="$homepage">$name</a> $active $version $author |
header | header string prepended to the output; empty when no plugin matches | |
footer | footer string appended to the output; empty when no plugin matches | |
separator | separator put between each plugin rendered in a row | $n |
tagformat | format string to render a link to any tag documentation a plugin implements | [[%SYSTEMWEB%.Var$tag][$tag]] |
%JQPLUGINS{ "treeview|slimbox" header=" * JQuery Plugins:$n" format=" * [[$documentation][$name]] v$version was developed by [[$homepage][$author]]" }%Produces:
Parameter: | Description: | Default: |
---|---|---|
"plugin[, plugin, plugin]" | list of plugins to be loaded | |
warn | (on/off) allows you to switch off warnings when a plugin was not found | on |
$Foswiki::cfg{JQueryPlugin}{JQueryTheme}
and defaults to base
. Use configure to change this site wide. Use JQTHEME if you decide to use a different theme on the current page.
Parameter: | Description: | Default: |
---|---|---|
"name" | name of theme: JQueryPlugin knows the following themes base , lightness , redmod , smoothness ; additional themes maybe created using the themeroller and installed to /pub/System/JQueryPlugin/$name | base |
lang
(and xml:lang
) attribute in generated HTML pages. If {UseLocale}
is enabled, it is calculated from the configure setting of {Site}{Locale}
. Otherwise it defaults to en
(English). lang
attribute is defined like this: <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="%LANG%" lang="%LANG%">
LANG
with LANGUAGE
%LANG%
ru-RU
LANGUAGE
preference is explicitly set, this will be used as the user language instead of any language detected from the browser.
LANGUAGE
in a non- per-user way, otherwise users will not be able to choose their preferred language.
LANGUAGE
with LANG
%LANGUAGE%
PO
files). These are the languages in which the user interface is available.
%LANGUAGES{...}%
Parameter: | Description: | Default: |
---|---|---|
format | format for each item. See below for format tokens available in the format string. | " * $langname" |
separator | separator between items. | "\n" (newline) |
marker="selected" | Text for $marker if the item matches selection | "selected" |
selection="%LANGUAGE%" | Current language to be selected in list | (none) |
format
tokens: Token | Meaning |
---|---|
$langname | language's name, as informed by the translators |
$langtag | language's tag. Ex: en , pt-br , etc. |
<select>%LANGUAGES{format="<option $marker value='$langtag'>$langname</option>" selection="%LANGUAGE%"}%</select>
creates an option list of the available languages with the current language selected
LIME
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%LIME% lime text %ENDCOLOR%Expands to: lime text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%LOCALSITEPREFS%
Main.SitePreferences
, renders as SitePreferences
%LOGIN%
You are already logged out, so %LOGOUT
expands to an empty string
%LOGOUT%
Deprecated. Please use %USERSWEB%
instead.
MAKETEXT
macro are automatically mapped to the
current user's selected language via locale/*.po
translation files. %MAKETEXT{"string" args="..."}%
Parameter | Description | Default |
---|---|---|
"text" or string="text" | The text to be displayed (the translatable string). | none |
args="param1, param2" | a comma-separated list of arguments to be interpolated in the string, replacing [_N] placeholders in it. | none |
%MAKETEXT{string="Notes:"}% expands to: Notes: %MAKETEXT{ "If you have any questions, please contact [_1]." args="%WIKIWEBMASTER%" }% expands to: If you have any questions, please contact rkondakov@yandex.ru. %MAKETEXT{ "Did you want to [[[_1]][reset [_2]'s password]]?" args="%SYSTEMWEB%.ResetPassword,%WIKIUSERNAME%" }% expands to: Did you want to [[System.ResetPassword][reset Main.WikiGuest's password]]?
[_n]
brackets are validated to a positive integer from 1 to 100.
&
) followed by one ascii alphabetic character (a...z, A...Z) in the translatable string will be expanded to an access key string. For example, &X
will expand to <span class='foswikiAccessKey'>X</span>
. If you want to write an actual ampersand, either follow it with a non-alphabetic character or write two consecutive ampersands (&&
).
_
) are reserved. You cannot use translatable phrases starting with an underscore.
%MACROS%
inside the translatable strings as they will be expanded before the %MAKETEXT{...}%
itself is handled. You can, however, use macros in the args
, as shown in the examples above.
.po
translation file for the current user's selected language.
%MAKETEXT
macro also supports a limited subset of the quant
style bracket notation: %MAKETEXT{string="Edit [*,_1,file]" args="4"}% expands to: Edit 4 files
quant
, numf
or #
are not supported.
MAROON
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%MAROON% maroon text %ENDCOLOR%Expands to: maroon text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%META{ "item" ...}%
Parameters: "form"
- generates the table showing the form fields. See Form Definition.
"attachments"
- generate a table of attachments all="on"
to show hidden attachments.
title="..."
to show a title - only if attachments are displayed.
template="..."
to use a custom template for the rendering of attachments; default attachtables
is used.
"moved"
- if a topic was moved or renamed, generates a message with details and a revert link prefix="..."
: Prefix that goes before the moved message, but only if the message is generated, default ""
.
suffix="..."
: Prefix that goes after the moved message, but only if the message is generated, default ""
.
"parent"
- display details of ancestor topics dontrecurse="on"
: By default recurses up tree, this has some cost. Equivalent to depth=1
depth="..."
: Return only the specified ancestor.
nowebhome="on"
: Suppress WebHome.
format="..."
: Format string used to display each parent topic where $web
expands to the web name, and $topic
expands to the topic name; default: "[[$web.$topic][$topic]]"
separator="..."
: Separator between parents; default " > "
prefix="..."
: Prefix that goes before parents, but only if there are parents, default ""
.
suffix="..."
: Suffix, only appears if there are parents; default ""
.
"formfield"
- display the value of a single form field name="..."
: name of the field.
newline="..."
: by default, each newline character will be rewritten to <br />
to allow metadata that contains newlines to be used in tables, etc. $n
indicates a newline character.
bar="..."
: by default, each vertical bar is rewritten to an HTML entity so as to not be mistaken for a table separator.
display="on"
- only used with "formfield"
, retrieves the displayed value of a *+values
formfield type, as against the default, stored, value.
topic="Main.WebPreferences"
- optional parameter to select which topic to get the meta-data from.
Use ofRelated: QUERY"formfield"
is deprecated in favour of the much more powerfulQUERY
macro.
METASEARCH
is deprecated in favour of the new and much more powerful query type search. See SEARCH and QuerySearch.
%METASEARCH{...}%
Parameter: | Description: | Default: |
---|---|---|
type="topicmoved" | What sort of search is required? "topicmoved" if search for a topic that may have been moved "parent" if searching for topics that have a specific parent i.e. its children "field" if searching for topics that have a particular form field value (use the name and value parameters to specify which field to search). | Required |
web="%WEB%" | Wiki web to search: A web, a list of webs separated by whitespace, or all webs. | Current web |
topic="%TOPIC%" | The topic the search relates to, for topicmoved and parent searches | All topics in a web |
name | form field to search, for field type searches. May be a regular expression (see SEARCH). | |
value | form field value, for field type searches. May be a regular expression (see SEARCH). | |
title="Title" | Text that is prefixed to any search results | empty |
format="..." | Custom format results. Supports same format strings as SEARCH. See FormattedSearch for usage & examples | Results in table |
default="none" | Default text shown if no search hit | Empty |
%METASEARCH{ type="topicmoved" web="%WEB%" topic="%TOPIC%" title="This topic used to exist and was moved to: " }%You may want to use this in WebTopicViewTemplate and WebTopicNonWikiTemplate:
%METASEARCH{ type="parent" web="%WEB%" topic="%TOPIC%" title="Children: " }% %METASEARCH{ type="field" name="Country" value="China" }%
NAVY
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%NAVY% navy text %ENDCOLOR%Expands to: navy text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%NOP%
%NOP{...}%
deprecated This is deprecated. Do not use it. Use%STARTSECTION{type="templateonly"}%
..%ENDSECTION{type="templateonly"}%
instead (see TemplateTopics for more details).
%NOTIFYTOPIC%
WebNotify
, renders as WebNotify
OLIVE
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%OLIVE% olive text %ENDCOLOR%Expands to: olive text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
ORANGE
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%ORANGE% orange text %ENDCOLOR%Expands to: orange text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
PINK
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%PINK% pink text %ENDCOLOR%Expands to: pink text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%PLUGINDESCRIPTIONS%
%PLUGINVERSION{"name"}%
to get the version of a specific plugin
%PLUGINVERSION{"InterwikiPlugin"}%
expands to v1.1.7
%PLUGINVERSION%
to get the version of the API
2.2
Parameter: | Description: | Default: |
---|---|---|
"topic" , topic="topic" , topic="web.topic" | Topic to open | |
url | URL to open (if topic is not used) | |
label | Link label | the topic or the url |
template | View template to call when viewing a topic; not used for URLs | "viewplain" |
width | Width of window | "600" |
height | Height of window | "480" |
toolbar | Show toolbars? | "0" |
scrollbars | Show scrollbars? | "1" |
status | Show status? | "1" |
location | Show location bar? | "0" |
resizable | Is the window resizable? | "1" |
left | Left position | "0" |
top | Top position | "0" |
center | Center the window? | "0" |
menubar | Show menubar? | "0" |
createnew | Create a new window for each popup? | "1" |
%POPUPWINDOW{"Macros" label="Open this topic in a new window"}%Generates: Open this topic in a new window
%POPUPWINDOW{url="http://foswiki.org"}%Generates: http://foswiki.org
POPUPWINDOW
by writing %JQREQUIRE{"popupwindow"}%
on the page
%PUBURL%
http://wiki.cs.msu.ru/pub
%PUBURL%/%WEB%/OtherTopic/image.gif
%PUBURLPATH%
/pub
PURPLE
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%PURPLE% purple text %ENDCOLOR%Expands to: purple text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
IF
and SEARCH
statements,
FORMFIELD
macro for most applications.
%QUERY{ "query" }%
style="stylename"
- set the output format (see below)
rev="version"
- operate on the given version of the current topic. Note that this will only affect simple queries that refer to the current topic, such as form.name
. More complex queries that use searches or indirection to refer to other topics always use the latest version of those topics.
Get the name of the form in the current topic: %QUERY{"form.name"}% Get the value of the 'Firstname' form field in the current topic: %QUERY{"fields[name='Firstname'].value"}% Get the value of the 'Firstname' form field in the current topic (shorthand version): %QUERY{"Firstname"}% Get a list of all the names of attachments on the topic 'System.DocumentGraphics': %QUERY{"'System.DocumentGraphics'/attachments.name"}% Get configuration setting {NameFilter}: %QUERY{"{NameFilter}"}%
style
parameter: style="perl"
- generates values as Perl code strings
style="json"
- generates values as JSON strings, suitable for reading by browsers.
{ScriptSuffix}
, {LoginManager}
, {AuthScripts}
, {LoginNameFilterIn}
, {AdminUserLogin}
, {AdminUserWikiName}
, {SuperAdminGroup}
, {UsersTopicName}
, {AuthRealm}
, {MinPasswordLength}
, {Register}{AllowLoginName}
, {Register}{EnableNewUserRegistration}
, {Register}{NeedVerification}
, {Register}{RegistrationAgentWikiName}
, {AllowInlineScript}
, {DenyDotDotInclude}
, {UploadFilter}
, {NameFilter}
, {AccessibleCFG}
, {AntiSpam}{EmailPadding}
, {AntiSpam}{EntityEncode}
, {AntiSpam}{HideUserDetails}
, {AntiSpam}{RobotsAreWelcome}
, {Stats}{TopViews}
, {Stats}{TopContrib}
, {Stats}{TopicName}
, {UserInterfaceInternationalisation}
, {UseLocale}
, {Site}{Locale}
, {Site}{CharSet}
, {DisplayTimeValues}
, {DefaultDateFormat}
, {Site}{LocaleRegexes}
, {UpperNational}
, {LowerNational}
, {PluralToSingular}
, {EnableHierarchicalWebs}
, {WebMasterEmail}
, {WebMasterName}
, {NotifyTopicName}
, {SystemWebName}
, {TrashWebName}
, {SitePrefsTopicName}
, {LocalSitePreferences}
, {HomeTopicName}
, {WebPrefsTopicName}
, {UsersWebName}
, {TemplatePath}
, {LinkProtocolPattern}
, {NumberOfRevisions}
, {MaxRevisionsInADiff}
, {ReplaceIfEditedAgainWithin}
, {LeaseLength}
, {LeaseLengthLessForceful}
, {Plugins}{WebSearchPath}
, {PluginsOrder}
, {Cache}{Enabled}
, {Validation}{Method}
, {Register}{DisablePasswordConfirmation}
%QUERYPARAMS{...}%
Parameter: | Description: | Default: |
---|---|---|
format="..." | Format string for each entry | $name=$value |
separator="..." | Separator string | separator="$n" (newline) |
encoding="entity" encoding="safe" encoding="html" encoding="quotes" encoding="url" | Control how special characters are encoded. If this parameter is not given, "safe" encoding is performed which HTML entity encodes the characters '"<>% . entity : Encode special characters into HTML entities, like a double quote into " . Does not encode \n or \r . safe : Encode characters '"<>% into HTML entities. (this is the default) html : As type="entity" except it also encodes \n and \r quotes : Escape double quotes with backslashes (\" ), does not change other characters url : Encode special characters for URL parameter use, like a double quote into %22 | type="safe" |
Sequence: | Expands To: |
---|---|
$name |
Name of the parameter |
$value |
String value of the parameter. Multi-valued parameters will have a "row" for each value. |
$n or $n() |
New line. Use $n() if followed by alphanumeric character, e.g. write Foo$n()Bar instead of Foo$nBar Most macros accept parameter strings which are split over multiple lines. This is usually more readable than using Note that newline is not a line break. The browser will wrap the lines together. If you require a line break, displaying the results on two lines, use |
$nop or $nop() |
Is a "no operation". This token gets removed; useful for nested search |
$quot |
Double quote (" ) (\" also works) |
$percent |
Percent sign (% ) ($percnt also works) |
$dollar |
Dollar sign ($ ) |
$lt |
Less than sign (< ) |
$gt |
Greater than sign (> ) |
$amp |
Ampersand (& ) |
$comma |
Comma (, ) |
%QUERYPARAMS{ format="<input type='hidden' name='$name' value='$value' encoding="entity" />" }%
Security warning!
Using QUERYPARAMS can easily be misused for cross-site scripting unless specific characters are entity encoded. By default QUERYPARAMS encodes the characters '"<>%
into HTML entities (same as encoding="safe") which is relatively safe. The safest is to use encoding="entity". When passing QUERYPARAMS inside another macro always use double quotes ("") combined with using QUERYPARAMS with encoding="quote". For maximum security against cross-site scripting you are adviced to install the Foswiki:Extensions.SafeWikiPlugin.
URLs built this way are typically restricted in length, typically to 2048 characters. If you need more space than this, you will need to use an HTML form and =%QUERYPARAMS%=
%QUERYSTRING%
cover=print;sortcol=1;table=9;up=0
RED
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%RED% red text %ENDCOLOR%Expands to: red text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%REMOTE_ADDR%
93.180.27.85
%REMOTE_PORT%
%REMOTE_USER%
%RENDERLIST%
variable is handled by the RenderFormPlugin
%RENDERFORM{ "ADataFormDefinition"}%
%RENDERLIST{ "System.HelpDeskForm" }%
%RENDERLIST%
macro is handled by the RenderListPlugin
%RENDERLIST%
%RENDERLIST{"org" focus="Sales.WestCoastTeam"}% * [[Eng.WebHome][Engineering]] * [[Eng.TechPubs][Tech Pubs]] * [[Sales.WestCoastTeam][Sales]] * [[Sales.EastCoastTeam][East Coast]] * [[Sales.WestCoastTeam][West Coast]]
%RENDERZONE{"zone" ...}%See ADDTOZONE for an explanation of zones. Parameters:
"zone"
required, name of the zone.
format="..."
optional, format string for each item added to the zone, default: $item <!--<literal> $id $missing</literal>-->Tokens:
$id
- id
of the ADDTOZONE call within the zone
currently being rendered.
$item
- text of the ADDTOZONE call within the zone
currently being rendered.
$zone
- the "zone"
currently being rendered.
$missing
- if the ADDTOZONE call being rendered required any id
which was not found, then $missing
is the missingtoken
parameter; empty string otherwise.
$missingids
- comma separated list of ids that were required by the ADDTOZONE call currently being rendered but weren't found within this zone
.
missingtoken="..."
optional, this will be the string assigned to the $missing
format token for use in the format
parameter. Default: $id: requires= missing ids: $missingids
chomp="on"
remove leading and trailing whitespace from formatted items, can be useful for pretty-printing and compression.
header="..."
optional, prepended to the output
footer="..."
optional, appended to the output
separator="..."
optional, put between each item of a zone
header
and footer
are not output if there is no content in the zone (nothing has been ADDTOZONEd
). However they are output if the output is the empty string (at least one ADDTOZONE
has been processed).
head
and script
are automatic zones. They don't require a corresponding RENDERZONE
anywhere in the templates - they are automatically inserted before the </head>
tag in the output HTML page.
ADDTOZONE
statements are resolved within each zone. However, if {MergeHeadAndScriptZones}
is enabled in configure, then head
content which requires an id
that only exists in script
will be re-ordered to satisfy this dependency. {MergeHeadAndScriptZones}
will be removed from a future version of Foswiki.
&rev=n
URL revision parameter of current topic %REVARG%
%REVARG%
If a topic revision is requested in the URL, it returns the revision of the current topic suitable for concatenation to the view query parameters. Otherwise returns an empty string.
&rev=3
(actual)
%REVINFO%
%REVINFO%
is equivalent to %REVINFO{format="r1.$rev - $date - $wikiusername"}%
r1 - 26 Jun 2011 - 21:39:52 - ProjectContributor
%REVINFO{"format"}%
%REVINFO%
is equivalent to %REVINFO{format="r$rev - $date - $wikiusername"}%
r1 - 26 Jun 2011 - 21:39:52 - ProjectContributor
Parameter: | Description: | Default: |
---|---|---|
"format" | Format of revision information, see supported formatting tokens below | "r1.$rev - $date - $wikiusername" |
web="..." | Name of web | Current web |
topic="..." | Topic name | Current topic |
rev="1.5" | Specific revision number | Latest revision |
Token: | Unit: | Example |
---|---|---|
$web | Name of web | Current web |
$topic | Topic name | Current topic |
$rev | Revision number. Prefix r1. to get the usual r1.5 format | 5 |
$username | Login username of revision | jsmith |
$wikiname | WikiName of revision | JohnSmith |
$wikiusername | WikiName with Main web prefix | Main.JohnSmith |
$date | Revision date. Actual date format defined as {DefaultDateFormat} in configure | 21 Sep 2006 |
$time | Revision time | 23:24:25 |
$iso | Revision date in ISO date format | 2006-09-22T06:24:25Z |
$min , $sec , etc. | Same date format qualifiers as GMTIME{"format"} |
%REVINFO{"$date - $wikiusername" rev="1.1"}%
%REVINFO{"$rev" rev="-1"}%
(r1)
The requested revision as displayed in topic breadcrumbs %REVTITLE%
%REVTITLE%
If a topic revision is requested in the URL, it returns the printable revision of the current topic revision. Otherwise returns an empty string.
(r3)
(actual)
viewauth.cgi
)
%SCRIPTNAME%
view
.pl
or .cgi
%SCRIPTSUFFIX%
%SCRIPTURL%
OR %SCRIPTURL{"script"}%
%SCRIPTURL%
returns the base URL of scripts - expands to http://wiki.cs.msu.ru/bin
http://wiki.cs.msu.ru/bin/script
%SCRIPTURL{"viewauth"}%/%WEB%/%TOPIC%
which expands to http://wiki.cs.msu.ru/bin/viewauth/System/Macros
In most cases you should use%SCRIPTURLPATH{"script"}%
instead, as it works with URL rewriting much better Theedit
script should always be used in conjunction with?t=%GMTIME{"$epoch"}%
to ensure pages about to be edited are not cached in the browser
%SCRIPTURL{"script"}%
, but doesn't include the protocol and host part of the URL
%SCRIPTURL%
OR %SCRIPTURLPATH{"script"}%
/bin/script
Theedit
script should always be used in conjunction with?t=%GMTIME{"$epoch"}%
to ensure pages about to be edited are not cached in the browser
%SEARCH{"text" ...}%
Parameter: | Description: | Default: |
---|---|---|
"text" | Search term. Is a keyword search, literal search, regular expression search, or query, depending on the type parameter. SearchHelp has more | required |
search="text" | (Alternative to above) | N/A |
web="Name" web="Main, Know" web="all" | Comma-separated list of webs to search. You can specifically exclude webs from an all search using a minus sign - for example, web="all,-Secretweb" . The special word all means all webs that do not have the NOSEARCHALL preference set to on in their WebPreferences. Note that AccessControls are respected when searching webs; it is much better to use them than NOSEARCHALL . Wildcards are not currently supported for web names. | Current web |
topic="WebPreferences" topic="*Bug" | Limit search to topics: A topic, a topic with asterisk wildcards, or a list of topics separated by comma. Note this is a list of topic names and must not include web names. | All topics in a web |
excludetopic="Web*" excludetopic="WebHome, WebChanges" | Exclude topics from search: A topic, a topic with asterisk wildcards, or a list of topics separated by comma. Note this is a list of topic names and must not include web names. | None |
scope="topic" scope="text" scope="all" | Search topic name (title); the text (body) of topic; or all (title and body) | "text" |
type="keyword" type="word" type="literal" type="regex" type="query" | Control how the search is performed when scope="text" or scope="all" keyword : use Google-like controls as in soap "web service" -shampoo ; searches word parts: using the example, topics with "soapsuds" will be found as well, but topics with "shampoos" will be excluded word : identical to keyword but searches whole words: topics with "soapsuds" will not be found, and topics with "shampoos" will not be excluded literal : search for the exact string, like web service regex : use a RegularExpression search like soap;web service;!shampoo ; to search on whole words use \bsoap\b query : query search of form fields and other meta-data, like (Firstname='Emma' OR Firstname='John') AND Lastname='Peel' | %SEARCHVAR- DEFAULTTYPE% preferences setting (literal) |
order="topic" order="created" order="modified" order="editby" order= | Sort the results of search by the topic names, topic creation time, last modified time, last editor's WikiName, or named field of DataForms. The sorting is done web by web; if you want to sort across webs, create a formatted table and sort it with TablePlugin's initsort. Note that dates are sorted most recent date last (i.e at the bottom of the table). | Sort by topic name |
limit="all" limit="16" | Limit the number of topics from which results will be returned. This is done after sorting if order is specified. Note that this does not limit the number of hits from the same topic when you have multiple="on". | All results |
date="..." | limits the results to those pages with latest edit time in the given time interval. | All results |
reverse="on" | Reverse the direction of the search | Ascending search |
casesensitive="on" | Case sensitive search | Ignore case |
bookview="on" | BookView search, e.g. show complete topic text. Very resource demanding. Use only with small result sets | Show entire topic content. |
nonoise="on" | Shorthand for nosummary="on" nosearch="on" nototal="on" zeroresults="off" noheader="on" noempty="on" | Off |
nosummary="on" | Show topic title only | Show topic summary |
nosearch="on" | Suppress search string | Show search string |
noheader="on" | Suppress default search header Topics: Changed: By: , unless a header is explicitly specified | Show default search header, unless search is inline and a format is specified (Cairo compatibility) |
nototal="on" | Do not show number of topics found | Show number |
zeroresults="off" or zeroresults="..." | Suppress/replace all output if there are no hits (the boolean nature of the setting uses true , false , on , off , 0 so those cannot be used as a format string on their own (insert a to escape them))- can also be set to a FormattedSearch string to customise the output | zeroresults="on" - displays the summary, and number of topics found. "Number of topics: 0" |
noempty="on" | Suppress results for webs that have no hits. | Show webs with no hits |
header="..." format="..." footer="..." | Custom format results: see FormattedSearch for usage & examples | Results in table |
expandvariables="on" | Expand embedded macros before applying a FormattedSearch on a search hit. Useful to show the expanded text, e.g. to show the result of a SpreadSheetPlugin %CALC{}% instead of the formula | Raw text |
multiple="on" | Multiple hits per topic. Each hit can be formatted. The last token is used in case of a regular expression ";" and search | Only one hit per topic |
nofinalnewline="on" | If on , the search variable does not end in a line by itself. Any text continuing immediately after the SEARCH macro on the same line will be rendered as part of the table generated by the search, if appropriate. This feature is only active when format is defined. | on |
recurse="on" | Recurse into subwebs, if subwebs are enabled. Note: recurse will currently search subwebs of explicitly excluded webs. (web="all, -Sandbox" recurse="on") will still search subwebs of Sandbox . This behavior is likely to change in a future release. | off |
separator=", " | Line separator between search hits (only used when format= is set) uses FormatTokens. If separator is not defined, the default is "$n" (newline). Not defining the separator will additionally cause a newline to be added after a header and before a footer. | "$n" (Newline) |
newline="%BR%" | Line separator within a search hit. Useful if you want to put multi-line content into a table cell, for example if the format="" parameter contains a $pattern() that captures more than one line. | "$n" (Newline) |
pagesize="25" | number of items to show per page | "25" |
showpage="1" | Page of items to show (starts at 1) (over-ridden by the value specified by the URL parameter hash from $previousurl and $nexturl ) | "1" |
pager="on" | appends the pager to the footer format (the quickest way to add paging to your SEARCHes is to just add pager="on" ) Note: the default pager (when pagerformat is not defined) requires the parameters to the SEARCH to not change while paging, as it uses $previousurl and $nexturl which use a hash of the Macro's parameters to override the value of showpage . If you use time variable parameters, you will need to define your own pagerformat . | "off" |
pagerformat="text" | Custom format results: see FormattedSearch for usage & examples | filled from skin template |
groupby="none" | Warning: this option is liable to change dramatically (and potentially incompatibly) in the next major release of foswiki. Setting to "none" applies only to multi-web SEARCHs, and means the header and footer are only output once - at the beginning and end of the list of results, and the order parameter is applied over the entire set of results (this setting removes the legacy that results are always partitioned by web) see SiteChanges for an example. | "web" |
%SEARCH{"wiki" web="%USERSWEB%" scope="topic"}%
%SEARCH{ "FAQ" nonoise="on" header="| *Topic: * | *Summary: * |" format="| $topic | $summary |" }%(displays results in a table with header - details)
The appearance of the table emitted by the SEARCH may be controlled with TablePlugin's%TABLE{}%
macro placed just before the%SEARCH{}%
. Example:%TABLE{ tablewidth="90%" }%
%GMTIME%
%SERVERTIME%
OR %SERVERTIME{"format"}%
%SERVERTIME%
uses the Date format defined as {DefaultDateFormat} in configure
%SERVERTIME{"$hou:$min"}%
expands to 18:22
Note: When used in a template topic, this macro will be expanded when the template is used to create a new topic. See TemplateTopics#TemplateTopicsVars for details.
%SESSIONID%
530926da12e1459be77074f05a049fc6
%SESSIONVAR%
%SESSION_VARIABLE{"name"}%
%SESSION_VARIABLE{"name" set="value"}%
%SESSION_VARIABLE{"name" clear=""}%
The users ID is in the AUTHUSER
session variable, and is read-only
%SHOWPREFERENCE%
%SHOWPREFERENCE{"PREFERENCENAME"}%
%SHOWPREFERENCE{"ATTACHFILESIZELIMIT"}%
* Set ATTACHFILESIZELIMIT = "10000" * ATTACHFILESIZELIMIT was *finalised* in System.DefaultPreferences
%SHOWPREFERENCE{"PREFERENCENAME,PREFERENCENAME,..."}%
%SHOWPREFERENCE{"DENYWEBCHANGE,ALLOWWEBCHANGE"}%
* Set DENYWEBCHANGE = "" * Set ALLOWWEBCHANGE = "%USERSWEB%.AdminGroup" * ALLOWWEBCHANGE was defined in System.WebPreferences
SILVER
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%SILVER% silver text %ENDCOLOR%Expands to: silver text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%SKIN%
expands the skin search path. For instance, SKIN
can be set to catskin, bearskin
.
SKIN
setting can be overridden using the URL parameter skin
, such as ?skin=catskin,bearskin
%SKIN%
pattern
%SLIDESHOWEND%
macro is handled by the SlideShowPlugin
%SLIDESHOWEND%
%SLIDESHOWSTART%
macro is handled by the SlideShowPlugin
%SLIDESHOWSTART%
%SLIDESHOWSTART{ template="MyOwnSlideTemplate" }%
%SLIDESHOWSTART% ---++ Sample Slide 1 * Bullet 1 * Bullet 2 ---++ Sample Slide 2 * Bullet 1 * Bullet 2 %SLIDESHOWEND%
%SPACEDTOPIC%
Var%20*SPACEDTOPIC
This is a deprecated macro. It can be duplicated with %ENCODE{%SPACEOUT{"%TOPIC%" separator=" *"}%}%
%SPACEOUT{ "%TOPIC%" }%
Macros
Parameter: | Description: | Default: |
---|---|---|
separator | The separator to put between words e.g. %SPACEOUT{"DogsCatsBudgies" separator=", "}% -> Dogs, Cats, Budgies | ' ' |
Spaced out WikiWords are not automatically linked. ToSPACEOUT
a WikiWord but preserve the link use "double bracket" format. For example,[[WebHome][%SPACEOUT{"WebHome"}%]]
expands to Web Home
%STOPINCLUDE%
macro. A normal view of the topic shows everything exept the %STARTINCLUDE%
macro itself.
%STARTINCLUDE%
If you want more than one part of the topic included, use %STARTSECTION{type="include"}%
instead
%STARTSECTION{}%
and %ENDSECTION{}%
.
type="section"
- the default, used for a generic section, such as a named section used by INCLUDE.
type="include"
- like %STARTINCLUDE%
... %STOPINCLUDE%
except that you can have as many include blocks as you want which are all merged into one when included (%STARTINCLUDE%
is restricted to only one). Sections of type include may not be given a name.
type="expandvariables"
- all macros inside an "expandvariables" type section gets expanded when a new topic based on the template topic is created. See TemplateTopics for more information.
type="templateonly"
- start position of text to be removed when a template topic is used. This is used to embed text that you do not want expanded when a new topic based on the template topic is created. See TemplateTopics for more information.
%STARTSECTION{"name"}% ................... %ENDSECTION{"name"}%
%STARTSECTION{"name" type="section"}% .... %ENDSECTION{"name" type="section"}%
(type="section" is the default)
%STARTSECTION{type="include"}% ........... %ENDSECTION{type="include"}%
%STARTSECTION{type="expandvariables"}% ... %ENDSECTION{type="expandvariables"}%
%STARTSECTION{type="templateonly"}% ...... %ENDSECTION{type="templateonly"}%
Parameter: | Description: | Default |
---|---|---|
"name" | Name of the section. Must be unique inside a topic. | Generated name |
type="..." | Type of the section; type "section" , "expandvariables" , "include" or "templateonly" | "section" |
If a section is not given a name, it will be assigned one. Unnamed sections are assigned names starting with_SECTION0
for the first unnamed section in the topic,_SECTION1
for the second, etc.. You can define nested sections. It is not recommended to overlap sections, although it is valid in Foswiki. Use named sections to make sure that the correct START and ENDs are matched. Section markers are not displayed when a topic is viewed.
%STATISTICSTOPIC%
WebStatistics
, renders as WebStatistics
%STOPINCLUDE%
macro itself.
%STOPINCLUDE%
%SYSTEMWEB%
System
Parameter: | Description: | Default: |
---|---|---|
"text" | label of the tab | Tab |
before | when switching tabs, this is the javascript fragment to be executed just before the tab is displayed | |
after | this javascript handler is to be executed after the tab has been made visible | |
afterload | this javascript handler will be called when content loaded asynchronously (using the url parameter, below) has finished loading; depending on the network latency, this can be significantly later than execution of the after handler above | |
id | id of this tab; this id can be used in the TABPANEs select parameter to display this tab; this id is also added to the class attribute of the html element representing the tab button | |
url | link from where to load the content of the tab asynchronously when selecting this tab; the result of the addressed handler will replace the content area; if no url is set the content of the TAB ... ENDTAB area will be shown when the tab is selected | |
width | width of the tab area | auto |
height | height of the tab area | auto |
container | element where ajax content will be loaded; this is only used together with url |
%TABLE{}%
macro is handled by the TablePlugin
%TABLE{ attributes }%
Argument | Comment | Default value | Example |
---|---|---|---|
tableborder |
Table border width (pixels). | "1" |
tableborder="2" |
tablebordercolor |
Table border color . Is only visible when cellspacing is larger than 1, or cellborder is 0 , or tablerules is none , otherwise the cell borders overlap the table border. |
unspecified | tablebordercolor="#333" |
tableframe |
Table frame, set to "void" (no sides), "above" (the top side only), "below" (the bottom side only), "hsides" (the top and bottom sides only), "lhs" (the left-hand side only), "rhs" (the right-hand side only), "vsides" (the right and left sides only), "box" (all four sides), "border" (all four sides). |
unspecified | tableframe="hsides" |
tablerules |
Table rules, set to "none" (no rules), "groups" (rules will appear between row groups and column groups only), "rows" (rules will appear between rows only), "cols" (rules will appear between columns only), "all" (rules will appear between all rows and columns). See also: headerrules and datarules . |
unspecified | tablerules="rows" |
tablewidth |
Table width: percentage of window width, or absolute pixel value. | unspecified | tablewidth="100%" |
headerrows |
Number of header rows to exclude from sort. (will be rendered in a HTML thead section) |
"1" |
headerrows="1" |
footerrows |
Number of footer rows to exclude from sort. (will be rendered in a HTML tfoot section) |
"0" |
footerrows="1" |
id |
Unique table identifier string, used for targeting a table with CSS. | tableN (where N is the table order number on the page) |
id="userTable" |
summary |
Table summary used by screen readers: A summary of what the table presents. It should provide an orientation for someone who listens to the table. | unspecified | summary="List of subscribed users" |
caption |
Table caption: A title that will be displayed just above the table. | unspecified | caption="Users" |
inlinemarkup |
Set to "on" to generate inline markup HTML (in addition to the CSS markup); useful if you need to copy the table, for instance to paste the table into an email). | unspecified | inlinemarkup="on" |
Argument | Comment | Default value | Example |
---|---|---|---|
sort |
Set the table sorting user interface (clickable column headers) "on" or "off" . |
unspecified | sort="on" |
initsort |
Column to sort initially (use "1" for the first column). If specified, sorting is enabled; by setting sort="off" the sorting interface can be hidden. |
unspecified | initsort="2" |
initdirection |
Initial sorting direction for initsort , set to "up" (descending, or decreasing in value) or "down" (ascending, or increasing in value). |
down |
initdirection="up" |
disableallsort |
Disable all sorting, both initsort and header sort. This is mainly used by plugins such as the EditTablePlugin to disable sorting in a table while editing the table. | unspecified | disableallsort="on" |
Argument | Comment | Default value | Example |
---|---|---|---|
cellpadding |
Cell padding (pixels). | unspecified | cellpadding="0" |
cellspacing |
Cell spacing (pixels). | unspecified | cellspacing="3" |
cellborder |
Cell border width (pixels). | unspecified | cellborder="0" |
valign |
Vertical alignment of cells and headers, set to "top" , "middle" , "bottom" or "baseline" . |
unspecified | valign="top" |
columnwidths |
Column widths: Comma delimited list of column widths, percentage or absolute pixel value. | unspecified | columnwidths="80%,20%" |
Argument | Comment | Default value | Example |
---|---|---|---|
datarules |
Set to "none" (no rules), "rows" (rules will appear between rows only), "cols" (rules will appear between columns only), "all" (rules will appear between all rows and columns). Overrides tablerules for data cells. |
unspecified | datarules="none" |
datavalign |
Vertical alignment of data cells; overrides valign . |
unspecified | datavalign="top" |
dataalign |
Data cell alignment, one value for all columns, or a comma separated list for different alignment of individual columns. Set to "left" , "center" , "right" or "justify" . Overrides individual cell settings. |
unspecified | dataalign="center" |
databg |
Data cell background colour, a comma separated list. Specify "none" for no colour, that is to use the colour/background of the page the table is on. |
"#edf4f9,#fff" |
databg="#f2f2f2,#fff" |
databgsorted |
Data cell background colour of a sorted column; see databg . |
the values of databg |
databgsorted="#d4e8e4, #e5f5ea" |
datacolor |
Data cell text colour, a comma separated list. | unspecified | datacolor="#00c, #000" |
Argument | Comment | Default value | Example |
---|---|---|---|
headerrules |
Set to "none" (no rules), "rows" (rules will appear between rows only), "cols" (rules will appear between columns only), "all" (rules will appear between all rows and columns). Overrides tablerules for header cells. |
unspecified | headerrules="none" |
headerbg |
Header cell background colour. Specify "none" for no colour, that is to use the colour/background of the page the table is on. |
"#6b7f93" |
headerbg="#999" |
headerbgsorted |
Header cell background colour of a sorted column. Specify "none" for no colour, that is to use the colour/background of the page the table is on. |
the value of headerbg |
headerbgsorted="#32596c" |
headercolor |
Header cell text colour. | "#fff" |
headercolor="#00c" |
headervalign |
Vertical alignment of header cells; overrides valign . |
unspecified | headervalign="top" |
headeralign |
Header cell alignment, one value for all columns, or a comma separated list for different alignment of individual columns. Set to "left" , "center" , "right" or "justify" . Overrides individual cell settings. |
unspecified | headeralign="left,right" |
headerrows |
See: Attributes for tables |
Argument | Comment | Default value | Example |
---|---|---|---|
include |
Other topic defining the TABLE parameters. The first %TABLE% in the topic is used. This is useful if you have many topics with the same table format and you want to update the format in one place. Use topic or web.topic notation. |
unspecified | include="Main.WebHome" |
%TABLE{ tableborder="0" cellpadding="4" cellspacing="3" cellborder="0" }% | *A1* | *B1* | | A2 | B2 |
A1 | B1 |
---|---|
A2 | B2 |
%TABPANE% %TAB{"tab 1"}% ... %ENDTAB% %TAB{"tab 2"}% ... %ENDTAB% %ENDTABPANE%Multiple tabpanes can be nested using the following scheme:
%TABPANE% %TAB{"tab 1"}% %TABPANE% %TAB{"tab 1.1"}% ... %ENDTAB% %TAB{"tab1.2"}% ... %ENDTAB% %ENDTABPANE% %ENDTAB% %TAB{"tab 2"}% ... %ENDTAB% %ENDTABPANE%
Parameter: | Description: | Default: |
---|---|---|
select | number or id of tab to select | 1 |
automaxexpand | resizes the tabpane to the maximum height to fit into the window | off |
minheight | when automaxexpand is enabled, this is the minimum size a tab is allowed to be resized | 230 |
class | extra class: use simple for a non-3D tabpane | |
animate | (on/off) enables/disables animation of switching tabs | off |
TEAL
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%TEAL% teal text %ENDCOLOR%Expands to: teal text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
"---++ text"
) and HTML ("<h2>text</h2>"
) are taken into account. Any heading text after "!!"
is excluded from the TOC; for example, write "---+!! text"
if you do not want to list a header in the TOC
%TOC%
OR %TOC{"SomeTopic" ...}%
Parameter: | Description: | Default: |
---|---|---|
"TopicName" | topic name | Current topic |
web="Name" | Name of web | Current web |
depth="2" | Limit depth of headings shown in TOC | 6 |
title="Some text" | Title to appear at top of TOC | none |
%TOC{depth="2"}% %TOC{"CompleteDocumentation" web="%SYSTEMWEB%" title="Contents:"}%See also: Foswiki:Support/HowToCreateATableOfContents
TOC will add an HTML anchor calledfoswikiTOC
just before the table of contents. This enables adding a link from within a topic back to the table of contents to ease navigation. Example[[#foswikiTOC][Back to TOC]]
creates Back to TOC. If multiple headers have the exact same text, the anchors for the 2nd, 3rd etc will be suffixed by _AN1, _AN2 etc so the anchors become unique.
%TOPIC%
expands to the name of the topic. If you are looking at the text of an included topic, it is the name of the included topic.
%TOPIC%
Macros
, renders as Macros
$topic
token gets expanded to the topic name, $marker
to marker
parameter where topic matches selection
, and $web
to the name of the web, or any of the standard FormatTokens.
%TOPICLIST{"format" ...}%
Parameter: | Description: | Default: |
---|---|---|
"format" | Format of one line, may include $web (name of web), $topic (name of the topic), $marker (which expands to marker for the item matching selection only) | "$topic" |
format="format" | (Alternative to above) | "$topic" |
separator=", " | line separator | "$n" (new line) |
marker="selected" | Text for $marker if the item matches selection | "selected" |
selection="TopicA, TopicB" | Current value to be selected in list | (none) |
web="Name" | Name of web | Current web |
Create a bullet list of all topics: %TOPICLIST{" * $web.$topic"}% Create a comma separated list of all topics: %TOPICLIST{separator=", "}% Create an option list (for drop down menus): %TOPICLIST{" <option>$topic</option>"}% Create an option list of web topics with the current topic selected: <select>%TOPICLIST{ " <option $marker value='$topic'>$topic</option>" separator=" " selection="%TOPIC%" }%</select>
TOPICURL
= http://wiki.cs.msu.ru/bin/view/System/Macros
Deprecated. Use %SYSTEMWEB%
instead
ENDTWISTY
tag.
Usage: %TWISTY{ ... }% Toggable contents %ENDTWISTY%
Parameter | Value | Description | Remark |
---|---|---|---|
id |
Unique identifier | Used to link TWISTYBUTTON and TWISTYTOGGLE | optional |
link |
Link label | Link label for both show and hide links | optional |
hidelink |
Link label | Hide link label | optional |
showlink |
Link label | Show link label | optional |
mode |
"div" or "span" |
Specify if the Twisty Toggle section will use a <div> or a <span> tag. Note that if the contents contains block elements such as div , mode should be div as well to create valid HTML markup. |
optional, defaults to <div> |
showimgleft |
Image url | Specify the url of an image that will be displayed with the show link at the left side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. |
optional, defaults to no image |
hideimgleft |
Image url | Specify the url of an image that will be displayed with the hide link at the left side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. |
optional, defaults to no image |
showimgright |
Image url | Specify the url of an image that will be displayed with the show link at the right side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. |
optional, defaults to no image |
hideimgright |
Image url | Specify the url of an image that will be displayed with the hide link at the right side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. |
optional, defaults to no image |
remember |
"on" , "off" |
If "on" , the Twisty state is remembered the next time the page is shown. If "off" , the stored setting will be cleared.
Note: when used, think carefully about a unique name (id) for the Twisty, otherwise the cookie that is set might affect other Twisties with the same name. Also note that only interaction is stored, not the state of the Twisty when left unclicked. |
optional, no default |
start |
"hide" or "show" |
Initial state of the Twisty; this will override any setting stored in a cookie (see remember ). |
optional, default no initial state |
firststart |
"hide" or "show" |
Initial state of the Twisty the first time the visitor gets to see the Twisty; this will NOT override cookie settings (see remember ). |
optional, default no initial state |
noscript |
"hide" |
Make content hidden in case use does not have JavaScript on | optional, default content is shown in case JavaScript if off |
class |
CSS class name | Class for Twisty div or span | optional, default none |
linkclass |
CSS class name | Class for link | optional, default none |
prefix |
Text | Text to display before the show/hide links | optional, default none |
suffix |
Text | Text to display after the show/hide links | optional, default none |
img |
Image url | Deprecated, use showimgleft, hideimgleft, showimgright or hideimgright. | optional, defaults to no image |
imgleft |
Image url | Deprecated, use showimgleft, hideimgleft, showimgright or hideimgright. | optional, defaults to no image |
imgright |
Image url | Deprecated, use showimgleft, hideimgleft, showimgright or hideimgright. | optional, defaults to no image |
hideimg |
Image url | Deprecated, use showimgleft, hideimgleft, showimgright or hideimgright. | optional, defaults to no image |
showimg |
Image url | Deprecated, use showimgleft, hideimgleft, showimgright or hideimgright. | optional, defaults to no image |
noscript
and class
(only used for 'toggle' content)
mode
: button mode defaults to div
%TWISTYBUTTON{id="myid" ... }%
Parameter | Value | Description | Remark |
---|---|---|---|
mode | "div" or "span" | Specify if the Twisty button will use a <div> or a <span> tag. Note that if the contents contains block elements such as div , mode should be div as well to create valid HTML markup. | optional, defaults to <div> |
%TWISTYBUTTON{ id="myid" link="more" }%%TWISTYTOGGLE{ id="myid" }%content%ENDTWISTYTOGGLE%
%TWISTYHIDE{id="myid" ... }%
Parameter | Value | Description | Remark |
---|---|---|---|
id | Unique identifier | Used to link TWISTYSHOW, TWISTYHIDE and TWISTYTOGGLE | required |
link | Link label | Hide link label | optional |
mode | "div" or "span" | Specify if the Twisty Hide link will use a <div> or a <span> tag. Note that if the contents contains block elements such as div , mode should be div as well to create valid HTML markup. | optional, defaults to <div> |
img | Image url | Specify the url of an image that will be displayed at the right side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. | optional, defaults to no image |
remember | "on" , "off" | If "on" , the Twisty state is remembered the next time the page is shown. If "off" , the stored setting will be cleared.Note: when used, think carefully about a unique name (id) for the Twisty, otherwise the cookie that is set might affect other Twisties with the same name. Also note that only interaction is stored, not the state of the Twisty when left unclicked. | optional, no default |
start | "hide" or "show" | Initial state of the Twisty; this will override any setting stored in a cookie (see remember ). | optional, default no initial state |
firststart | "hide" or "show" | Initial state of the Twisty the first time the visitor gets to see the Twisty; this will NOT override cookie settings (see remember ). | optional, default no initial state |
%TWISTYHIDE{id="demo" link=" Click to Fold " imgleft="%ICONURLPATH{toggleclose}%"}%
%TWISTYSHOW{id="myid" ... }%
Parameter | Value | Description | Remark |
---|---|---|---|
id | Unique identifier | Used to link TWISTYSHOW, TWISTYHIDE and TWISTYTOGGLE | required |
link | Link label | Show link label | optional |
mode | "div" or "span" | Specify if the Twisty Show link will use a <div> or a <span> tag. Note that if the contents contains block elements such as div , mode should be div as well to create valid HTML markup. | optional, defaults to <div> |
img | Image url | Specify the url of an image that will be displayed at the right side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. | optional, defaults to no image |
imgleft | Image url | Specify the url of an image that will be displayed at the left side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. | optional, defaults to no image |
imgright | Image url | Specify the url of an image that will be displayed at the right side of the link. You may use ICONURLPATH to display one of the DocumentGraphics icons. Alternatively use an image attached to the topic. | optional, defaults to no image |
remember | "on" , "off" | If "on" , the Twisty state is remembered the next time the page is shown. If "off" , the stored setting will be cleared.Note: when used, think carefully about a unique name (id) for the Twisty, otherwise the cookie that is set might affect other Twisties with the same name. Also note that only interaction is stored, not the state of the Twisty when left unclicked. | optional, no default |
start | "hide" or "show" | Initial state of the Twisty; this will override any setting stored in a cookie (see remember ). | optional, default no initial state |
firststart | "hide" or "show" | Initial state of the Twisty the first time the visitor gets to see the Twisty; this will NOT override cookie settings (see remember ). | optional, default no initial state |
%TWISTYSHOW{id="demo" link=" Click to Unfold " imgleft="%ICONURLPATH{toggleopen}%"}%
%TWISTYTOGGLE{id="myid"}%
Parameter | Value | Description | Remark |
---|---|---|---|
id | Unique identifier | Used to link TWISTYSHOW, TWISTYHIDE and TWISTYTOGGLE. | required |
mode | "div" or "span" | Specify if the Twisty Toggle section will use a <div> or a <span> tag. Note that if the contents contains block elements such as div , mode should be div as well to create valid HTML markup. | optional, defaults to <div> |
class | CSS class name | Class for content div or span | optional, default none |
linkclass | CSS class name | Class for link | optional, default none |
remember | "on" , "off" | If "on" , the Twisty state is remembered the next time the page is shown. If "off" , the stored setting will be cleared.Note: when used, think carefully about a unique name (id) for the Twisty, otherwise the cookie that is set might affect other Twisties with the same name. Also note that only interaction is stored, not the state of the Twisty when left unclicked. | optional, no default |
start | "hide" or "show" | Initial state of the Twisty; this will override any setting stored in a cookie (see remember ). | optional, default no initial state |
firststart | "hide" or "show" | Initial state of the Twisty the first time the visitor gets to see the Twisty; this will NOT override cookie settings (see remember ). | optional, default no initial state |
noscript | "hide" | Make content hidden in case use does not have JavaScript on | optional, default content is shown with no JavaScript |
%TWISTYTOGGLE{id="demo" mode="div" remember="on"}%My content%ENDTWISTYTOGGLE%
%URLPARAM{"name"}%
Parameter: | Description: | Default: |
---|---|---|
"name" | The name of a URL parameter | required |
default="..." | Default value, used if the parameter is not present | empty string |
newline="<br />" | Convert newlines in textarea to other delimiters | no conversion |
encode="off" encode="entity" encode="safe" encode="url" encode="quote" | Control how special characters are encoded off : No encoding. Avoid using this when possible. See the security warning below. entity : Encode special characters into HTML entities. See ENCODE for more details. safe : Encode characters '"<>% into HTML entities. url : Encode special characters for URL parameter use, like a double quote into %22 quote : Escape double quotes with backslashes (\" ), does not change other characters; required when feeding URL parameters into other macros. | "safe" |
multiple="on" multiple="[[$item]]" | If set, gets all selected elements of a <select multiple="multiple"> tag. A format can be specified, with $item indicating the element, e.g. multiple="Option: $item" (also supports the standard format tokens) | first element |
separator=", " | Separator between multiple selections. Only relevant if multiple is specified | "\n" (new line) |
%URLPARAM{"skin"}%
returns print
for a .../view/System/Macros?skin=print
URL
%SEARCH{ "%URLPARAM{ "search" encode="quote" }%" noheader="on" }%
rev
, skin
, template
, topic
, web
; they have a special meaning in Foswiki. Common parameters and view script specific parameters are documented at CommandAndCGIScripts.
%URLPARAM{
in the value of a URL parameter, it will be modified to %<nop>URLPARAM{
. This is to prevent an infinite loop during expansion.
'"<>%
into HTML entities (same as encode="safe") which is relatively safe. The safest is to use encode="entity". When passing URLPARAM inside another macro always use double quotes ("") combined with using URLPARAM with encode="quote". For maximum security against cross-site scripting you are adviced to install the Foswiki:Extensions.SafeWikiPlugin.
%USERINFO%
guest, WikiGuest,
(comma-separated list of the username, wikiusername, and emails)
$emails
, $username
, $wikiname
, $wikiusername
, $groups
and $admin
($admin returns 'true' or 'false'): %USERINFO{ format="$username is really $wikiname" }%
guest is really WikiGuest
%USERINFO{ "WikiGuest" format="$username is really $wikiname" }%
guest is really WikiGuest
You need to be a member of AdminGroup for the USERINFO
macro to provide details about other users
The parameter should be the wikiname of a user. You can also pass a login name. You can only get information about another user if the {AntiSpam}{HideUserDetails}
configuration option is not enabled, or if you are an admin. (User details are hidden in this site)
jsmith
, WIKINAME like JohnSmith
and WIKIUSERNAME like Main.JohnSmith
. Un-authenticated users are all WikiGuest.
%USERNAME%
guest
When used in a template topic, this macro will be expanded when the template is used to create a new topic. See TemplateTopics#TemplateTopicsVars for details
%USERSWEB%
Main
%VAR{"NAME" web="Web"}%
%WEBBGCOLOR%
of the Main web write %VAR{"WEBBGCOLOR" web="Main"}%
, which expands to #FFEFA6
%VARCACHE{ "24" }%
Attribute | Comment | Default |
---|---|---|
"..." orrefresh="..." | Cache refresh period in hours (maximum age of cache). Accepts decimals, such as 0.25 | 24 |
cachemsg="..." | Message shown when looking at a cached topic. Use $age to indicate the age of cache, $link to indicate the refresh URL | This topic was cached $age ago ([[$link][refresh]]) |
updatemsg="..." | Message shown after a cache refresh. Use $link to indicate the refresh URL | This topic is now cached ([[$link][refresh]]) |
%VARCACHE{"168"}%
caches the current page for 7 days
cachmsg
and updatemsg
.
%VARCACHE{}%
variable is handled by the VarCachePlugin.
%WEB%
expands to the name of the web where the topic is located. If you are looking at the text of an included topic, it is the web where the included topic is located.
%WEB%
System
NOSEARCHALL = on
preference setting. The "format"
defines the format of one web item. The $name
gets expanded to the name of the web, $qname
gets expanded to double quoted name, $marker
to marker
where web matches selection
. Subwebs are listed recursively.
%WEBLIST{"format" ...}%
Parameter: | Description: | Default: |
---|---|---|
"format" | Format of one line, may include $name (the name of the web), $qname (the name of the web in double quotes), $indentedname (the name of the web with parent web names replaced by indents, for use in indented lists), and $marker (which expands to marker for the item matching selection only) | $name |
format="format" | (Alternative to above) | $name |
separator=", " | Line separator | $n (new line) |
web="" | if you specify $web in format, it will be replaced with this value. | none |
webs="public" | Comma separated list of webs to consider. This list can include two pseudo-webs, public which expands to all non-hidden and webtemplate which expands to the names of all template webs.NOTE: Administrators will see all webs, not just the public ones | public |
subwebs="Sandbox" | Specifies a single web. If specified, then public and webtemplate (described above) will expand relative to show subwebs *below this web only. | "" |
selection="%WEB%" | Entry to be selected in list. If one of the webs matches this selection, then $marker in the format will be expanded | selection=%WEB% |
marker="selected" | Text for $marker if the item matches selection | selected="selected" |
%WEBLIST{" * [[$name.%HOMETOPIC%]]"}%
<form><select name="web">%WEBLIST{ "<option $marker value='$qname'>$name</option>" webs="Trash, public" selection="%WEB%" separator=" " }% </select></form>
WEBLIST
will not show a web called 'TWiki' even if it exists in the file system unless theTWikiCompatibilityPlugin
is installed and activated in configure. This is done to ensure that the TWiki compatibility components such as the TWiki web are only visible and active when needed
%WEBPREFSTOPIC%
WebPreferences
, renders as WebPreferences
WHITE
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%WHITE% white text %ENDCOLOR%Expands to: white text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%WIKIHOMEURL%
/bin/view/
%SCRIPTURLPATH{"view"}%
For the top bar logo URL use %WIKILOGOURL%
defined in WebPreferences instead.
%USERNAME%
if not defined in the WikiUsers topic
%WIKINAME%
WikiGuest
When used in a template topic, this macro will be expanded when the template is used to create new topic. See TemplateTopics#TemplateTopicsVars for details
%WIKIPREFSTOPIC%
DefaultPreferences
, renders as DefaultPreferences
%WIKITOOLNAME%
Foswiki
%WIKIUSERNAME%
Main.WikiGuest
, renders as WikiGuest When used in a template topic, this macro will be expanded when the template is used to create a new topic. See TemplateTopics#TemplateTopicsVars for details
%WIKIUSERSTOPIC%
WikiUsers
, with Main prefix renders as WikiUsers
%WIKIVERSION%
v1.1.9
%WIKIWEBMASTER%
rkondakov@yandex.ru
%WIKIWEBMASTERNAME%
Wiki Administrator
YELLOW
is one of the shortcut macros predefined in DefaultPreferences. See the section shortcut macros in that topic for a complete list of colors.%YELLOW% yellow text %ENDCOLOR%Expands to: yellow text
%<color>%
text must end with%ENDCOLOR%
. If you want to switch from one color to another one you first need to end the active color with%ENDCOLOR%
, e.g. write%RED% some text %ENDCOLOR% %GREEN% more text %ENDCOLOR%
%BR%
- line break
%BULLET%
- bullet sign
%BB%
- line break and bullet combined
%BB2%
- indented line break and bullet
%RED% text %ENDCOLOR%
- colored text (also %YELLOW%
, %ORANGE%
, %PINK%
, %PURPLE%
, %TEAL%
, %NAVY%
, %BLUE%
, %AQUA%
, %LIME%
, %GREEN%
, %OLIVE%
, %MAROON%
, %BROWN%
, %BLACK%
, %GRAY%
, %SILVER%
, %WHITE%
)
%H%
- Help icon
%I%
- Idea icon
%M%
- Moved to icon
%N%
- New icon
%P%
- Refactor icon
%Q%
- Question icon
%S%
- Red star icon
%T%
- Tip icon
%U%
- Updated icon
%X%
- Alert icon
%Y%
- Done icon