Restrict tag execution in a region. If a restricted tag is encountered, it is simply output.
[restrict tag1 tag2] [restrict policy=deny enable="page area value"]
|policy||Whether to allow or deny by default.||deny|
|enable||Tags to enable when default policy is deny.||none|
|disable||Tags to disable. Overrides enable.||none|
[read-cookie name=MV_SESSION_ID] --- 6CZ2whqo
ASP-like Perl call:
N/A. Cannot be called effectively.
Restrict tag execution in a region. If a restricted tag is encountered, it is simply output. It can be used to allow certain tags in a user-editable region, while denying dangerous tags. Or it can be used to restrict all tag execution in a region.
Default is deny, which makes most sense. You then specifically enable certain ITL tags. If you set allow by default, you must be very careful that you really are disabling all of what you consider to be dangerous tags.
A space-separated or comma-separated list of tags to disable when the default policy is deny. Has no effect when the default policy is allow, and any tags passed in the disable parameter override the enable.
A space-separated or comma-separated list of tags to disable when the default policy is allow. If you have a list of tags that are enabled, perhaps stored in a scratch variable, you can disable some of those tags since this takes precedence over the enable.