SCRIPTURL -- URL of script(s)

Parameters

Examples

• %SCRIPTURL{"view" topic="Cartoons.EvilMonkey"}% will expand to https://damask2.mpie.de/bin/view/Cartoons/EvilMonkey?topic=Cartoons.EvilMonkey
• %SCRIPTURL{"view" web="Cartoons"}% will expand to https://damask2.mpie.de/bin/view/Cartoons?web=Cartoons
• %SCRIPTURL{"view" topic="Cartoons.EvilMonkey" rev="1"}% will expand to https://damask2.mpie.de/bin/view/Cartoons/EvilMonkey?topic=Cartoons.EvilMonkey;rev=1
• %SCRIPTURL{"edit" web="Cartoons" topic="EvilMonkey" t="%GMTIME{"$epoch"}%"}% expands to https://damask2.mpie.de/bin/edit/Cartoons/EvilMonkey?web=Cartoons;topic=EvilMonkey;t=1725532231
• %SCRIPTURL% expands to https://damask2.mpie.de/bin
• %SCRIPTURL{script}% expands to https://damask2.mpie.de/bin/script

In most cases you should use SCRIPTURLPATH instead, as it works much better with URL rewriting

The edit script should always be used in conjunction a t="%GMTIME{"$epoch"}%" parameter to ensure pages about to be edited are not cached in the browser

The 'old' way of building URLs using SCRIPTURL involved concatenating the web and topic names to the SCRIPTURL e.g. %SCRIPTURL{"script"}%/Cartoons/EvilMonkey. 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 %SCRIPTURL%{"script" topic="Cartoons.EvilMonkey"}%, which will handle URL encoding for you.

Related