This indicates which filters are automatically loaded into Smarty.
Smarty Configuration Section
The name of the directory for cache files.
Smarty Configuration Section
The function used for cache file handling. If not set, built-in caching is used.
Smarty Configuration Section
This is the number of seconds cached content will persist.
Smarty Configuration Section
- 0 = always regenerate cache
- -1 = never expires
Only used when $caching is enabled. If true, then If-Modified-Since headers are respected with cached content, and appropriate HTTP headers are sent.
Smarty Configuration Section This way repeated hits to a cached page do not send the entire page to the client every time.
This enables template caching.
Smarty Configuration Section
- 0 = no caching
- 1 = use class cache_lifetime value
- 2 = use cache_lifetime in cache file
The class used for compiling templates.
The file that contains the compiler class. This can a full pathname, or relative to the php_include path.
This tells Smarty whether to check for recompiling or not. Recompiling does not need to happen unless a template or config file is changed.
Smarty Configuration Section Typically you enable this during development, and disable for production.
The directory where compiled templates are located.
Smarty Configuration Section
Set this if you want different sets of compiled files for the same templates. This is useful for things like different languages.
Smarty Configuration Section Instead of creating separate sets of templates per language, you set different compile_ids like 'en' and 'de'.
This tells whether or not to automatically booleanize config file variables.
If enabled, then the strings "on", "true", and "yes" are treated as boolean true, and "off", "false" and "no" are treated as boolean false.
The class used to load config vars.
The directory where config files are located.
Smarty Configuration Section
This tells whether or not automatically fix newlines in config files.
It basically converts \r (mac) or \r\n (dos) to \n
This tells if config file vars of the same name overwrite each other or not.
if disabled, same name variables are accumulated in an array.
This tells whether hidden sections [.foobar] are readable from the tempalates or not. Normally you would never allow this since that is the point behind hidden sections: the application can access them, but the templates cannot.
If debugging is enabled, a debug console window will display when the page loads (make sure your browser allows unrequested popup windows)
Smarty Configuration Section
This determines if debugging is enable-able from the browser.
Smarty Configuration Section
- NONE => no debugging control allowed
- URL => enable debugging when SMARTY_DEBUG is found in the URL.
Information Tags:
This is the path to the debug console template. If not set, the default one will be used.
Smarty Configuration Section
This is a list of the modifiers to apply to all template variables.
Smarty Configuration Section Put each modifier in a separate array element in the order you want them applied. example:
- array('escape:"htmlall"');
This is the resource type to be used when not specified
Smarty Configuration Section at the beginning of the resource path. examples: $smarty->display('file:index.tpl'); $smarty->display('db:index.tpl'); $smarty->display('index.tpl'); // will use default resource type {include file="file:index.tpl"} {include file="db:index.tpl"} {include file="index.tpl"} {* will use default resource type *}
If a template cannot be found, this PHP function will be executed.
Useful for creating templates on-the-fly or other special action.
When set, smarty does uses this value as error_reporting-level.
Smarty Configuration Section
This forces templates to compile every time. Useful for development or debugging.
Smarty Configuration Section
The left delimiter used for the template tags.
Smarty Configuration Section
This determines how Smarty handles "<?php ... ?>" tags in templates.
Smarty Configuration Section possible values:
- SMARTY_PHP_PASSTHRU -> print tags as plain text
- SMARTY_PHP_QUOTE -> escape tags as entities
- SMARTY_PHP_REMOVE -> remove php tags
- SMARTY_PHP_ALLOW -> execute php tags
An array of directories searched for plugins.
Smarty Configuration Section
Indicates wether $HTTP_*_VARS[] (request_use_auto_globals=false)
Smarty Configuration Section are uses as request-vars or $_*[]-vars. note: if request_use_auto_globals is true, then $request_vars_order has no effect, but the php-ini-value "gpc_order"
The order in which request variables are registered, similar to variables_order in php.ini E = Environment, G = GET, P = POST, C = Cookies, S = Server
Smarty Configuration Section
The right delimiter used for the template tags.
Smarty Configuration Section
This is the list of template directories that are considered secure. This is used only if $security is enabled. One directory per array element. $template_dir is in this list implicitly.
Smarty Configuration Section
This enables template security. When enabled, many things are restricted
Smarty Configuration Section in the templates that normally would go unchecked. This is useful when untrusted parties are editing templates and you want a reasonable level of security. (no direct execution of PHP in templates for example)
These are the security settings for Smarty. They are used only when $security is enabled.
Smarty Configuration Section
The name of the directory where templates are located.
Smarty Configuration Section
This is an array of directories where trusted php scripts reside.
Smarty Configuration Section $security is disabled during their inclusion/execution.
This tells Smarty whether or not to use sub dirs in the cache/ and templates_c/ directories. sub directories better organized, but may not work well with PHP safe mode enabled.
Smarty Configuration Section
