aboutsummaryrefslogtreecommitdiffstats
path: root/vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-debug.md
diff options
context:
space:
mode:
Diffstat (limited to 'vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-debug.md')
-rw-r--r--vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-debug.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-debug.md b/vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-debug.md
new file mode 100644
index 000000000..fbaae1944
--- /dev/null
+++ b/vendor/smarty/smarty/docs/designers/language-builtin-functions/language-function-debug.md
@@ -0,0 +1,18 @@
+{debug} {#language.function.debug}
+=======
+
+`{debug}` dumps the debug console to the page. This works regardless of
+the [debug](#chapter.debugging.console) settings in the php script.
+Since this gets executed at runtime, this is only able to show the
+[assigned](#api.assign) variables; not the templates that are in use.
+However, you can see all the currently available variables within the
+scope of a template.
+
+If caching is enabled and a page is loaded from cache `{debug}` does
+show only the variables which assigned for the cached page.
+
+In order to see also the variables which have been locally assigned
+within the template it does make sense to place the `{debug}` tag at the
+end of the template.
+
+See also the [debugging console page](#chapter.debugging.console).