SCRIPTURLPATH -- URL path of script(s)

Parameters

Examples

• %SCRIPTURLPATH{"view" topic="Cartoons.EvilMonkey"}% expands to /bin/view/Cartoons/EvilMonkey?topic=Cartoons.EvilMonkey
• %SCRIPTURLPATH{"view" web="Cartoons"}% expands to /bin/view/Cartoons?web=Cartoons
• %SCRIPTURLPATH{"view" topic="Cartoons.EvilMonkey" rev="1"}% will expand to /bin/view/Cartoons/EvilMonkey?rev=1;topic=Cartoons.EvilMonkey
• %SCRIPTURLPATH{"edit" web="Cartoons" topic="EvilMonkey" t="%GMTIME{"$epoch"}%"}% expands to /bin/edit/Cartoons/EvilMonkey?topic=EvilMonkey;t=1725538889;web=Cartoons
• %SCRIPTURLPATH% expands to /bin
• %SCRIPTURLPATH{script}% expands to /bin/script

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

See SCRIPTURL if you expect to need the protocol and host e.g. if you are saving the HTML of the page and using it on a different host.

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

Related