
Comparing changes: https://github.com/smarty-php/smarty/compare/v4.3.1...v4.4.1 It is noticeable that Smarty 4.3.1 does not officially support PHP 8.3. Is only supported with 4.4.0. Remark: During tests with Smarty 4.5.1, it was noticed that the following warning occurs: Deprecated: Using the unregistered function "function_exists" in a template is deprecated and will be removed in a future version. Use Smarty::registerPlugin to explicitly register a custom modifier. As of Smarty 5.X.X, templates must be revised again. The Smarty release 5.0.2 is already officially available. However, integration into FlatPress is not entirely trivial.
29 lines
1.1 KiB
Markdown
29 lines
1.1 KiB
Markdown
\$plugins\_dir {#variable.plugins.dir}
|
|
==============
|
|
|
|
This is the directory or directories where Smarty will look for the
|
|
plugins that it needs. Default is `plugins/` under the
|
|
[`SMARTY_DIR`](#constant.smarty.dir). If you supply a relative path,
|
|
Smarty will first look under the [`SMARTY_DIR`](#constant.smarty.dir),
|
|
then relative to the current working directory, then relative to the PHP
|
|
include\_path. If `$plugins_dir` is an array of directories, Smarty will
|
|
search for your plugin in each plugin directory **in the order they are
|
|
given**.
|
|
|
|
> **Note**
|
|
>
|
|
> For best performance, do not setup your `$plugins_dir` to have to use
|
|
> the PHP include path. Use an absolute pathname, or a path relative to
|
|
> `SMARTY_DIR` or the current working directory.
|
|
|
|
> **Note**
|
|
>
|
|
> As of Smarty 3.1 the attribute \$plugins\_dir is no longer accessible
|
|
> directly. Use [`getPluginsDir()`](#api.get.plugins.dir),
|
|
> [`setPluginsDir()`](#api.set.plugins.dir) and
|
|
> [`addPluginsDir()`](#api.add.plugins.dir) instead.
|
|
|
|
See also [`getPluginsDir()`](#api.get.plugins.dir),
|
|
[`setPluginsDir()`](#api.set.plugins.dir) and
|
|
[`addPluginsDir()`](#api.add.plugins.dir).
|