Linux server.kiran-academy.com 3.10.0-1160.108.1.el7.x86_64 #1 SMP Thu Jan 25 16:17:31 UTC 2024 x86_64
Apache/2.4.57 (Unix) OpenSSL/1.0.2k-fips
: 194.233.91.196 | : 216.73.216.216
Cant Read [ /etc/named.conf ]
7.4.32
finalho
www.github.com/MadExploits
Terminal
AUTO ROOT
Adminer
Backdoor Destroyer
Linux Exploit
Lock Shell
Lock File
Create User
CREATE RDP
PHP Mailer
BACKCONNECT
UNLOCK SHELL
HASH IDENTIFIER
CPANEL RESET
CREATE WP USER
README
+ Create Folder
+ Create File
/
usr /
local /
cwpsrv /
var /
services /
twig /
doc /
functions /
[ HOME SHELL ]
Name
Size
Permission
Action
attribute.rst
604
B
-rw-r--r--
block.rst
789
B
-rw-r--r--
constant.rst
487
B
-rw-r--r--
cycle.rst
548
B
-rw-r--r--
date.rst
1.04
KB
-rw-r--r--
dump.rst
1.54
KB
-rw-r--r--
include.rst
2.24
KB
-rw-r--r--
index.rst
213
B
-rw-r--r--
max.rst
332
B
-rw-r--r--
min.rst
331
B
-rw-r--r--
parent.rst
563
B
-rw-r--r--
random.rst
703
B
-rw-r--r--
range.rst
1.19
KB
-rw-r--r--
source.rst
694
B
-rw-r--r--
template_from_string.rst
867
B
-rw-r--r--
Delete
Unzip
Zip
${this.title}
Close
Code Editor : include.rst
``include`` =========== The ``include`` function returns the rendered content of a template: .. code-block:: jinja {{ include('template.html') }} {{ include(some_var) }} Included templates have access to the variables of the active context. If you are using the filesystem loader, the templates are looked for in the paths defined by it. The context is passed by default to the template but you can also pass additional variables: .. code-block:: jinja {# template.html will have access to the variables from the current context and the additional ones provided #} {{ include('template.html', {foo: 'bar'}) }} You can disable access to the context by setting ``with_context`` to ``false``: .. code-block:: jinja {# only the foo variable will be accessible #} {{ include('template.html', {foo: 'bar'}, with_context = false) }} .. code-block:: jinja {# no variables will be accessible #} {{ include('template.html', with_context = false) }} And if the expression evaluates to a ``Twig_Template`` or a ``Twig_TemplateWrapper`` instance, Twig will use it directly:: // {{ include(template) }} $template = $twig->load('some_template.twig'); $twig->display('template.twig', array('template' => $template)); When you set the ``ignore_missing`` flag, Twig will return an empty string if the template does not exist: .. code-block:: jinja {{ include('sidebar.html', ignore_missing = true) }} You can also provide a list of templates that are checked for existence before inclusion. The first template that exists will be rendered: .. code-block:: jinja {{ include(['page_detailed.html', 'page.html']) }} If ``ignore_missing`` is set, it will fall back to rendering nothing if none of the templates exist, otherwise it will throw an exception. When including a template created by an end user, you should consider sandboxing it: .. code-block:: jinja {{ include('page.html', sandboxed = true) }} Arguments --------- * ``template``: The template to render * ``variables``: The variables to pass to the template * ``with_context``: Whether to pass the current context variables or not * ``ignore_missing``: Whether to ignore missing templates or not * ``sandboxed``: Whether to sandbox the template or not
Close