ParseVariables

Specify whether global and local variables should be parsed in a website's local configuration file.

Synopsis

This is a Yes or No directive.  The default is No.

Scope

This directive is only available for use in the local (catalog.cfg) configuration file.  It will not affect any other website in any way.  This directive will not work in the global (interchange.cfg) configuration file. 

Description

Determines whether global and local variables should be parsed in a website's local configuration file.  This only applies to variables with names in ALL_CAPS.  The Standard demo's catalog.cfg file switches ParseVariables on, and expects it to be on throughout, but you can switch it on and off at will, if you prefer.

Note Although parsing of variables can be switched on and off throughout the configuration file, you'll probably find it better to just switch variable parsing on at the top of the configuration file and forget about it.

Example

Include a configuration file named after some sort of website ID

The "configs" directory, in this example, could be a symbolic link to a centrally-maintained directory containing one configuration file for each of the websites configured into the Interchange instance.

Apache-style container syntax

This is one of the few (if only) directives where the Apache-style configuration syntax may be useful.  Using the following variation of the previous example, only variables referenced within the container will be parsed: