unurl
Changes text from URL-compatible characters to plain text.
[unurl]Any URL Text[/unurl]To automatically convert text containing URL characters such as %20, %3A, etc, put it inside a [UnURL] context. Certain letters, such as spaces, colons, and the equals sign (=) are not allowed inside URLs unless they are first converted to hexadecimal form -- the UnURL context converts them back. This is the opposite of [url].
Example (normally you would put the following text into a .tpl file on your server and use a web browser to link to it):
Example WebDNA code:
In the example above, the displayed text will be
Example result:
This context is rarely needed, because most of the time WebDNA has already converted the text (in URL parameters, for instance) back to plain text. If you plan to store text with embedded unusual characters such as tabs or carriage returns into a field of a database, you might use [url] to store them and [unurl] to retrieve them.
Example (normally you would put the following text into a .tpl file on your server and use a web browser to link to it):
Example WebDNA code:
[unurl]Filename%20with%20spaces.gif[/unurl]In the example above, the displayed text will be
Example result:
Filename with spaces.gifBy default, the [unurl] context will not convert hex codes that contain lowercase letters. So, %3A will be converted to a colon while %3a will not. You can use the 'ignorecase' parameter to force the [unurl] context to convert hex codes containing lowercase letters. So [unurl ignorecase =T]%3a[/unurl] will convert %3a to a colon.
This context is rarely needed, because most of the time WebDNA has already converted the text (in URL parameters, for instance) back to plain text. If you plan to store text with embedded unusual characters such as tabs or carriage returns into a field of a database, you might use [url] to store them and [unurl] to retrieve them.