FotoWeb 6.0 User Guide - Customization - FotoWare

Customizing FotoWeb 3.0
2.6 Script rules
Now that you have been introduces to basic elements of FotoWeb scripting, its time to get to know the rules. The
rules are few and simple and, more or less, already explained during the introduction of the elements.
Failure to follow these rules can cause incorrect information display, compromise security and processing stops.
FotoWeb has implemented several mechanisms to prevent these occurrences, but the best mechanism lies in the
hands of the template programmer – adoption of FotoWeb script rules.
2.6.1 Close/End the tags
Whether it is an empty or non-empty tag, it must be closed with a forward slash ‘/’. For example:
Example 31: Closing empty tags.
Empty tags are closed by themselves by adding the closing mark ‘/’ right before the closing identifier ‘%>’, with no
space in between them.
. . .
Example 32: Closing non-empty tags.
The non-empty tags that create a context, must be closed with a separate closing tag. The closing tag is the same as
starting tag, but with a closing mark ‘/’ right before the tag name, with no space in between them.
Failure to close a tag will invalidate the hierarchal structure of the template and case a parsing error during template
validation.
2.6.2 Close/End contexts
This rule is based on the same principal as the previous, but extends a little further. As explained in the previous
rule, tags creating a context (non-empty tags) must be closed with a closing tag. Similarly, the evaluation tags (‘if’
and ‘ifnot’) must also close their contexts with ‘endif’.
. . .
. . .
. . .
. . .
Example 33: Closing 'if' and 'ifnot' tags.
Starting tag.
Closing tag with closing mark ’/’.
’/’ closes the tag.
Starting evaluation tag.
Closing evaluation tag.
Starting evaluation tag.
Closing evaluation tag.
Optional else.
Optional else.
Failure to close a tags’ context will invalidate the hierarchal structure of the template and cause a parsing error
during the template validation..
16 / 47 FotoWare