![]() |
Flat-Frog - the faster compiling PHP template engine |
This is a string that tells Flat-Frog what directory to look for the templates in. You can refer to subdirectories of this folder, too, but this is the base folder for templates.
The default is the templates
subdirectory of the Flat-Frog folder.
This is a string that tells Flat-Frog what directory to look for config files in.
The default is the templates
subdirectory of the Flat-Frog folder.
This is a string that tells Flat-Frog what directory compiled files will be saved to. Whatever directory this is must have write permissions available for the webserver or else compiled files cannot be saved.
The default is the compiled
subdirectory of the Flat-Frog folder.
This is a string that tells Flat-Frog what directory cached files will be saved to. Whatever directory this is must have write permissions available for the webserver or else cached files cannot be saved.
The default is the cached
subdirectory of the Flat-Frog folder.
This is a string that tells Flat-Frog what directory plugins will be loaded from. There can only be one plugin directory and it will have all of the plugins in it. However, you can also dynamically register plugin functions if you must.
The default is the plugins
subdirectory of the Flat-Frog folder.
This is the left tag used by the template engine. The default is "<%".
This is the right tag used by the template engine. The default is "%>".
Tells Flat-Frog whether or not to cache the output of the templates. By default this is set to false
or disabled. If your templates generate content that rarely changes, or you are looking to increase the speed at which your templates are generated, it is advisable to turn on caching, as your templates will load significantly faster. You can have multiple caches for the same page, but this is described in the caching appendix. It is important to reset the $cache_lifetime
variable when beginning to work with a page that is being cached or else the page will not be cached. Before any cached file is loaded, it will be checked to see if the original template has changed, or if the cache is out of date. Also, if $force_compile
is enabled, then the cache will be regenerated each time the page is loaded.
This is the length of time in seconds that a template cache is valid. Once this time has expired, the cache will be regenerated. $cache
must be set to true
for $cache_lifetime
to have any valid meaning. A value of 0, the default, will always regenerate the cache, which is good for testing purposes only. To disable caching, you should always set $cache
to false
. If $force_compile
is set to true, then the cache files will be regenerated every time the page is loaded, also effectively disabling caching. You can clear all cached files by calling clear_cached()
.
If this is set to true
then each page will be recompiled upon every viewing. This is horribly inefficient and highly discouraged, but is useful for testing your templates.
When loading config files either from your PHP script or from your templates themselves, this variable can change the behavior of the loading process. When set to true
, config variables with the same name will overwrite each other. If set to false
, config variables of the same name will be pushed into a numerically indexed array. The default is to not overwrite. This is for storing arrays in config files, simply by listing the same config file multiple times.
When this is set to true
, a config value of true
or yes
or on
or 1
will be translated to mean "true". At the same time, a config value of false
or no
or off
or 0
will be translated to "false". This is true
by default.
If set to true, Mac and DOS newlines, \r and \r\n, respectively, in config files are converted to \n when they are parsed. This is true
by default.
If set to true, hidden sections, those are sections that begin with a period, such as [.secret], can be and are read from config files into templates. Hidden sections are usually meant to store things such as database passwords and thus, this is typically false. The default is set to true.