Parameter | Description | Default |
---|---|---|
"attachment" |
Name of attachment to link | |
web |
Web | |
topic |
Topic, or Web.Topic | |
topic_version |
Select topic version, if supported | most recent |
attachment_version |
Select attachment version, if supported | most recent |
%PUBURL%
expands to http://gsics.atmos.umd.edu/bin/../pub
%PUBURL{"icon_plus.png"}%
expands to =%PUBURL{"icon_plus.png"}%
%PUBURL{web="System"}%
expands to http://gsics.atmos.umd.edu/bin/../pub/System
%PUBURL{topic="System.MainFeatures"}%
expands to http://gsics.atmos.umd.edu/bin/../pub/System/MainFeatures
%PUBURL{web="System" topic="MainFeatures"}%
expands to http://gsics.atmos.umd.edu/bin/../pub/System/MainFeatures
%PUBURL{topic="System.MainFeatures"}%
expands to http://gsics.atmos.umd.edu/bin/../pub/System/MainFeatures
%PUBURL{topic="System.MainFeatures" "icon_plus.png"}%
expands to http://gsics.atmos.umd.edu/bin/../pub/System/MainFeatures/icon_plus.png
topic_version
and attachment_version
parameters. These can be used with advanced store implementations to select specific attachment versions. However simple file-based stores do not normally support them. PUBURL
involved concatenating the web and topic names to the PUBURL
e.g. %PUBURL%/Main/SystemFeatures
. This practice is strongly discouraged, as it does not correctly handle encoding of the parts of the URL. At the first opportunity you should replace all such URLs with the equivalent %PUBURL%{topic="System.MainFeatures"}%
, which will handle URL encoding for you.