
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.
32 lines
1.3 KiB
Markdown
32 lines
1.3 KiB
Markdown
\$use\_sub\_dirs {#variable.use.sub.dirs}
|
|
================
|
|
|
|
Smarty will create subdirectories under the [compiled
|
|
templates](#variable.compile.dir) and [cache](#variable.cache.dir)
|
|
directories if `$use_sub_dirs` is set to TRUE, default is FALSE. In an
|
|
environment where there are potentially tens of thousands of files
|
|
created, this may help the filesystem speed. On the other hand, some
|
|
environments do not allow PHP processes to create directories, so this
|
|
must be disabled which is the default.
|
|
|
|
Sub directories are more efficient, so use them if you can.
|
|
Theoretically you get much better performance on a filesystem with 10
|
|
directories each having 100 files, than with 1 directory having 1000
|
|
files. This was certainly the case with Solaris 7 (UFS)\... with newer
|
|
filesystems such as ext3 and especially reiserfs, the difference is
|
|
almost nothing.
|
|
|
|
> **Note**
|
|
>
|
|
> - `$use_sub_dirs=true` doesn\'t work with
|
|
> [safe\_mode=On](https://www.php.net/features.safe-mode), that\'s why
|
|
> it\'s switchable and why it\'s off by default.
|
|
>
|
|
> - `$use_sub_dirs=true` on Windows can cause problems.
|
|
>
|
|
> - Safe\_mode is being deprecated in PHP6.
|
|
>
|
|
See also [`$compile_id`](#variable.compile.id),
|
|
[`$cache_dir`](#variable.cache.dir), and
|
|
[`$compile_dir`](#variable.compile.dir).
|