e544ed6d9a
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.
89 lines
4.1 KiB
Markdown
89 lines
4.1 KiB
Markdown
# {config_load}
|
|
|
|
`{config_load}` is used for loading config
|
|
[`#variables#`](#language.config.variables) from a [configuration file](#config.files) into the template.
|
|
|
|
## Attributes
|
|
|
|
| Attribute Name | Required | Description |
|
|
|----------------|----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
|
|
| file | Yes | The name of the config file to include |
|
|
| section | No | The name of the section to load |
|
|
| scope | no | How the scope of the loaded variables are treated, which must be one of local, parent or global. local means variables are loaded into the local template context. parent means variables are loaded into both the local context and the parent template that called it. global means variables are available to all templates. |
|
|
|
|
|
|
## Examples
|
|
|
|
The `example.conf` file.
|
|
|
|
```ini
|
|
#this is config file comment
|
|
|
|
# global variables
|
|
pageTitle = "Main Menu"
|
|
bodyBgColor = #000000
|
|
tableBgColor = #000000
|
|
rowBgColor = #00ff00
|
|
|
|
#customer variables section
|
|
[Customer]
|
|
pageTitle = "Customer Info"
|
|
```
|
|
|
|
and the template
|
|
|
|
```smarty
|
|
{config_load file="example.conf"}
|
|
{config_load "example.conf"} {* short-hand *}
|
|
|
|
<html>
|
|
<title>{#pageTitle#|default:"No title"}</title>
|
|
<body bgcolor="{#bodyBgColor#}">
|
|
<table border="{#tableBorderSize#}" bgcolor="{#tableBgColor#}">
|
|
<tr bgcolor="{#rowBgColor#}">
|
|
<td>First</td>
|
|
<td>Last</td>
|
|
<td>Address</td>
|
|
</tr>
|
|
</table>
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
[Config Files](#config.files) may also contain sections. You can load
|
|
variables from within a section with the added attribute `section`. Note
|
|
that global config variables are always loaded along with section
|
|
variables, and same-named section variables overwrite the globals.
|
|
|
|
> **Note**
|
|
>
|
|
> Config file *sections* and the built-in template function called
|
|
> [`{section}`](../language-builtin-functions/language-function-section.md) have nothing to do with each
|
|
> other, they just happen to share a common naming convention.
|
|
|
|
```smarty
|
|
{config_load file='example.conf' section='Customer'}
|
|
{config_load 'example.conf' 'Customer'} {* short-hand *}
|
|
|
|
<html>
|
|
<title>{#pageTitle#}</title>
|
|
<body bgcolor="{#bodyBgColor#}">
|
|
<table border="{#tableBorderSize#}" bgcolor="{#tableBgColor#}">
|
|
<tr bgcolor="{#rowBgColor#}">
|
|
<td>First</td>
|
|
<td>Last</td>
|
|
<td>Address</td>
|
|
</tr>
|
|
</table>
|
|
</body>
|
|
</html>
|
|
```
|
|
|
|
See [`$config_overwrite`](../../programmers/api-variables/variable-config-overwrite.md) to create arrays
|
|
of config file variables.
|
|
|
|
See also the [config files](../config-files.md) page, [config variables](../language-variables/language-config-variables.md) page,
|
|
[`$config_dir`](../../programmers/api-variables/variable-config-dir.md),
|
|
[`getConfigVars()`](../../programmers/api-functions/api-get-config-vars.md) and
|
|
[`configLoad()`](../../programmers/api-functions/api-config-load.md).
|