# Volt 模版引擎（Volt: Template Engine）[](# "永久链接至标题")
Volt 是一个用C为PHP编写的超快的并且对设计师友好的模板语言。Volt 提供一组辅助工具有助于你以一种更简单的的方式编写视图（Views）。同时，Volt与Phalcon的其他组件高度集成在一起，就像你在应用中单独使用Volt一样。
Volt is an ultra-fast and designer friendly templating language written in C for PHP. It provides you a set ofhelpers to write views in an easy way. Volt is highly integrated with other components of Phalcon,just as you can use it as a stand-alone component in your applications.
Volt is inspired by [Jinja](http://jinja.pocoo.org/), originally created by [Armin Ronacher](https://github.com/mitsuhiko). Therefore many developers will be in familiarterritory using the same syntax they have been using with similar template engines. Volt’s syntax and featureshave been enhanced with more elements and of course with the performance that developers have beenaccustomed to while working with Phalcon.
### 简介（Introduction）[](# "永久链接至标题")
Volt views are compiled to pure PHP code, so basically they save the effort of writing PHP code manually:
Volt 视图被编译成纯PHP代码，所以基本上他们节省手工编写PHP代码的工作：
~~~
{# app/views/products/show.volt #}
{% block last_products %}
{% for product in products %}
* Name: {{ product.name|e }}
{% if product.status == "Active" %}
Price: {{ product.price + product.taxes/100 }}
{% endif %}
{% endfor %}
{% endblock %}
~~~
### 启用 Vlot（Activating Volt）[](# "永久链接至标题")
As other template engines, you may register Volt in the view component, using a new extension orreusing the standard .phtml:
~~~
<?php
use Phalcon\Mvc\View;
// Registering Volt as template engine
$di->set('view', function () {
$view = new View();
$view->setViewsDir('../app/views/');
$view->registerEngines(array(
".volt" => 'Phalcon\Mvc\View\Engine\Volt'
));
return $view;
});
~~~
Use the standard ”.phtml” extension:
~~~
<?php
$view->registerEngines(array(
".phtml" => 'Phalcon\Mvc\View\Engine\Volt'
));
~~~
### 基本用法（Basic Usage）[](# "永久链接至标题")
A view consists of Volt code, PHP and HTML. A set of special delimiters is available to enter intoVolt mode. {% ... %} is used to execute statements such as for-loops or assign values and {{ ... }},prints the result of an expression to the template.
Below is a minimal template that illustrates a few basics:
~~~
{# app/views/posts/show.phtml #}
<!DOCTYPE html>
<html>
<head>
<title>{{ title }} - An example blog</title>
</head>
<body>
{% if show_navigation %}
<ul id="navigation">
{% for item in menu %}
<li><a href="{{ item.href }}">{{ item.caption }}</a></li>
{% endfor %}
</ul>
{% endif %}
<h1>{{ post.title }}</h1>
<div class="content">
{{ post.content }}
</div>
</body>
</html>
~~~
Using Phalcon\Mvc\View you can pass variables from the controller to the views.In the above example, three variables were passed to the view: title, menu and post:
~~~
<?php
use Phalcon\Mvc\Controller;
class PostsController extends Controller
{
public function showAction()
{
$post = Post::findFirst();
$this->view->title = $post->title;
$this->view->post = $post;
$this->view->menu = Menu::find();
$this->view->show_navigation = true;
}
}
~~~
### 变量（Variables）[](# "永久链接至标题")
Object variables may have attributes which can be accessed using the syntax: foo.bar.If you are passing arrays, you have to use the square bracket syntax: foo[‘bar']
~~~
{{ post.title }} {# for $post->title #}
{{ post['title'] }} {# for $post['title'] #}
~~~
### 过滤器（Filters）[](# "永久链接至标题")
Variables can be formatted or modified using filters. The pipe operator | is used to apply filters tovariables:
~~~
{{ post.title|e }}
{{ post.content|striptags }}
{{ name|capitalize|trim }}
~~~
The following is the list of available built-in filters in Volt:
| Filter | Description |
|-----|-----|
| e | Applies Phalcon\Escaper->escapeHtml to the value |
| escape | Applies Phalcon\Escaper->escapeHtml to the value |
| escape_css | Applies Phalcon\Escaper->escapeCss to the value |
| escape_js | Applies Phalcon\Escaper->escapeJs to the value |
| escape_attr | Applies Phalcon\Escaper->escapeHtmlAttr to the value |
| trim | Applies the [trim](http://php.net/manual/en/function.trim.php) PHP function to the value. Removing extra spaces |
| left_trim | Applies the [ltrim](http://php.net/manual/en/function.ltrim.php) PHP function to the value. Removing extra spaces |
| right_trim | Applies the [rtrim](http://php.net/manual/en/function.rtrim.php) PHP function to the value. Removing extra spaces |
| striptags | Applies the [striptags](http://php.net/manual/en/function.striptags.php) PHP function to the value. Removing HTML tags |
| slashes | Applies the [slashes](http://php.net/manual/en/function.slashes.php) PHP function to the value. Escaping values |
| stripslashes | Applies the [stripslashes](http://php.net/manual/en/function.stripslashes.php) PHP function to the value. Removing escaped quotes |
| capitalize | Capitalizes a string by applying the [ucwords](http://php.net/manual/en/function.ucwords.php) PHP function to the value |
| lower | Change the case of a string to lowercase |
| upper | Change the case of a string to uppercase |
| length | Counts the string length or how many items are in an array or object |
| nl2br | Changes newlines \n by line breaks (<br />). Uses the PHP function [nl2br](http://php.net/manual/en/function.nl2br.php) |
| sort | Sorts an array using the PHP function [asort](http://php.net/manual/en/function.asort.php) |
| keys | Returns the array keys using [array_keys](http://php.net/manual/en/function.array-keys.php) |
| join | Joins the array parts using a separator [join](http://php.net/manual/en/function.join.php) |
| format | Formats a string using [sprintf](http://php.net/manual/en/function.sprintf.php). |
| json_encode | Converts a value into its [JSON](http://php.net/manual/en/function.json-encode.php) representation |
| json_decode | Converts a value from its [JSON](http://php.net/manual/en/function.json-encode.php) representation to a PHP representation |
| abs | Applies the [abs](http://php.net/manual/en/function.abs.php) PHP function to a value. |
| url_encode | Applies the [urlencode](http://php.net/manual/en/function.urlencode.php) PHP function to the value |
| default | Sets a default value in case that the evaluated expression is empty(is not set or evaluates to a falsy value) |
| convert_encoding | Converts a string from one charset to another |
Examples:
~~~
{# e or escape filter #}
{{ "<h1>Hello<h1>"|e }}
{{ "<h1>Hello<h1>"|escape }}
{# trim filter #}
{{ " hello "|trim }}
{# striptags filter #}
{{ "<h1>Hello<h1>"|striptags }}
{# slashes filter #}
{{ "'this is a string'"|slashes }}
{# stripslashes filter #}
{{ "\'this is a string\'"|stripslashes }}
{# capitalize filter #}
{{ "hello"|capitalize }}
{# lower filter #}
{{ "HELLO"|lower }}
{# upper filter #}
{{ "hello"|upper }}
{# length filter #}
{{ "robots"|length }}
{{ [1, 2, 3]|length }}
{# nl2br filter #}
{{ "some\ntext"|nl2br }}
{# sort filter #}
{% set sorted=[3, 1, 2]|sort %}
{# keys filter #}
{% set keys=['first': 1, 'second': 2, 'third': 3]|keys %}
{# join filter #}
{% "a".."z"|join(",") %}
{# format filter #}
{% "My real name is %s"|format(name) %}
{# json_encode filter #}
{% robots|json_encode %}
{# json_decode filter #}
{% set decoded='{"one":1,"two":2,"three":3}'|json_decode %}
{# url_encode filter #}
{{ post.permanent_link|url_encode }}
{# convert_encoding filter #}
{{ "désolé"|convert_encoding('utf8', 'latin1') }}
~~~
### 注释（Comments）[](# "永久链接至标题")
Comments may also be added to a template using the {# ... #} delimiters. All text inside them is just ignored in the final output:
~~~
{# note: this is a comment
{% set price = 100; %}
#}
~~~
### 流程控制列表（List of Control Structures）[](# "永久链接至标题")
Volt provides a set of basic but powerful control structures for use in templates:
### 循环语句 For[](# "永久链接至标题")
Loop over each item in a sequence. The following example shows how to traverse a set of “robots” and print his/her name:
~~~
<h1>Robots</h1>
<ul>
{% for robot in robots %}
<li>{{ robot.name|e }}</li>
{% endfor %}
</ul>
~~~
for-loops can also be nested:
~~~
<h1>Robots</h1>
{% for robot in robots %}
{% for part in robot.parts %}
Robot: {{ robot.name|e }} Part: {{ part.name|e }} <br/>
{% endfor %}
{% endfor %}
~~~
You can get the element “keys” as in the PHP counterpart using the following syntax:
~~~
{% set numbers = ['one': 1, 'two': 2, 'three': 3] %}
{% for name, value in numbers %}
Name: {{ name }} Value: {{ value }}
{% endfor %}
~~~
An “if” evaluation can be optionally set:
~~~
{% set numbers = ['one': 1, 'two': 2, 'three': 3] %}
{% for value in numbers if value < 2 %}
Value: {{ value }}
{% endfor %}
{% for name, value in numbers if name != 'two' %}
Name: {{ name }} Value: {{ value }}
{% endfor %}
~~~
If an ‘else' is defined inside the ‘for', it will be executed if the expression in the iterator result in zero iterations:
~~~
<h1>Robots</h1>
{% for robot in robots %}
Robot: {{ robot.name|e }} Part: {{ part.name|e }} <br/>
{% else %}
There are no robots to show
{% endfor %}
~~~
Alternative syntax:
~~~
<h1>Robots</h1>
{% for robot in robots %}
Robot: {{ robot.name|e }} Part: {{ part.name|e }} <br/>
{% elsefor %}
There are no robots to show
{% endfor %}
~~~
### 循环控制（Loop Controls）[](# "永久链接至标题")
The ‘break' and ‘continue' statements can be used to exit from a loop or force an iteration in the current block:
~~~
{# skip the even robots #}
{% for index, robot in robots %}
{% if index is even %}
{% continue %}
{% endif %}
...
{% endfor %}
~~~
~~~
{# exit the foreach on the first even robot #}
{% for index, robot in robots %}
{% if index is even %}
{% break %}
{% endif %}
...
{% endfor %}
~~~
### 条件判断语句 If[](# "永久链接至标题")
As PHP, an “if” statement checks if an expression is evaluated as true or false:
~~~
<h1>Cyborg Robots</h1>
<ul>
{% for robot in robots %}
{% if robot.type == "cyborg" %}
<li>{{ robot.name|e }}</li>
{% endif %}
{% endfor %}
</ul>
~~~
The else clause is also supported:
~~~
<h1>Robots</h1>
<ul>
{% for robot in robots %}
{% if robot.type == "cyborg" %}
<li>{{ robot.name|e }}</li>
{% else %}
<li>{{ robot.name|e }} (not a cyborg)</li>
{% endif %}
{% endfor %}
</ul>
~~~
The ‘elseif' control flow structure can be used together with if to emulate a ‘switch' block:
~~~
{% if robot.type == "cyborg" %}
Robot is a cyborg
{% elseif robot.type == "virtual" %}
Robot is virtual
{% elseif robot.type == "mechanical" %}
Robot is mechanical
{% endif %}
~~~
### 循环上下文（Loop Context）[](# "永久链接至标题")
A special variable is available inside ‘for' loops providing you information about
| Variable | Description |
|-----|-----|
| loop.index | The current iteration of the loop. (1 indexed) |
| loop.index0 | The current iteration of the loop. (0 indexed) |
| loop.revindex | The number of iterations from the end of the loop (1 indexed) |
| loop.revindex0 | The number of iterations from the end of the loop (0 indexed) |
| loop.first | True if in the first iteration. |
| loop.last | True if in the last iteration. |
| loop.length | The number of items to iterate |
~~~
{% for robot in robots %}
{% if loop.first %}
<table>
<tr>
<th>#</th>
<th>Id</th>
<th>Name</th>
</tr>
{% endif %}
<tr>
<td>{{ loop.index }}</td>
<td>{{ robot.id }}</td>
<td>{{ robot.name }}</td>
</tr>
{% if loop.last %}
</table>
{% endif %}
{% endfor %}
~~~
### 赋值（Assignments）[](# "永久链接至标题")
Variables may be changed in a template using the instruction “set”:
~~~
{% set fruits = ['Apple', 'Banana', 'Orange'] %}
{% set name = robot.name %}
~~~
Multiple assignments are allowed in the same instruction:
~~~
{% set fruits = ['Apple', 'Banana', 'Orange'], name = robot.name, active = true %}
~~~
Additionally, you can use compound assignment operators:
~~~
{% set price += 100.00 %}
{% set age *= 5 %}
~~~
The following operators are available:
| Operator | Description |
|-----|-----|
| = | Standard Assignment |
| += | Addition assignment |
| -= | Subtraction assignment |
| *= | Multiplication assignment |
| /= | Division assignment |
### 表达式（Expressions）[](# "永久链接至标题")
Volt provides a basic set of expression support, including literals and common operators.
A expression can be evaluated and printed using the ‘{{‘ and ‘}}' delimiters:
~~~
{{ (1 + 1) * 2 }}
~~~
If an expression needs to be evaluated without be printed the ‘do' statement can be used:
~~~
{% do (1 + 1) * 2 %}
~~~
### 字面值（Literals）[](# "永久链接至标题")
The following literals are supported:
| Filter | Description |
|-----|-----|
| “this is a string” | Text between double quotes or single quotes are handled as strings |
| 100.25 | Numbers with a decimal part are handled as doubles/floats |
| 100 | Numbers without a decimal part are handled as integers |
| false | Constant “false” is the boolean false value |
| true | Constant “true” is the boolean true value |
| null | Constant “null” is the Null value |
### 数组（Arrays）[](# "永久链接至标题")
Whether you're using PHP 5.3, 5.4 or 5.5, you can create arrays by enclosing a list of values in square brackets:
~~~
{# Simple array #}
{{ ['Apple', 'Banana', 'Orange'] }}
{# Other simple array #}
{{ ['Apple', 1, 2.5, false, null] }}
{# Multi-Dimensional array #}
{{ [[1, 2], [3, 4], [5, 6]] }}
{# Hash-style array #}
{{ ['first': 1, 'second': 4/2, 'third': '3'] }}
~~~
Curly braces also can be used to define arrays or hashes:
~~~
{% set myArray = {'Apple', 'Banana', 'Orange'} %}
{% set myHash = {'first': 1, 'second': 4/2, 'third': '3'} %}
~~~
### 算术运算（Math）[](# "永久链接至标题")
You may make calculations in templates using the following operators:
| Operator | Description |
|-----|-----|
| + | Perform an adding operation. {{ 2 + 3 }} returns 5 |
| - | Perform a substraction operation {{ 2 - 3 }} returns -1 |
| * | Perform a multiplication operation {{ 2 * 3 }} returns 6 |
| / | Perform a division operation {{ 10 / 2 }} returns 5 |
| % | Calculate the remainder of an integer division {{ 10 % 3 }} returns 1 |
### 比较运算（Comparisons）[](# "永久链接至标题")
The following comparison operators are available:
| Operator | Description |
|-----|-----|
| == | Check whether both operands are equal |
| != | Check whether both operands aren't equal |
| <> | Check whether both operands aren't equal |
| > | Check whether left operand is greater than right operand |
| < | Check whether left operand is less than right operand |
| <= | Check whether left operand is less or equal than right operand |
| >= | Check whether left operand is greater or equal than right operand |
| === | Check whether both operands are identical |
| !== | Check whether both operands aren't identical |
### 逻辑运算（Logic）[](# "永久链接至标题")
Logic operators are useful in the “if” expression evaluation to combine multiple tests:
| Operator | Description |
|-----|-----|
| or | Return true if the left or right operand is evaluated as true |
| and | Return true if both left and right operands are evaluated as true |
| not | Negates an expression |
| ( expr ) | Parenthesis groups expressions |
### 其他操作（Other Operators）[](# "永久链接至标题")
Additional operators seen the following operators are available:
| Operator | Description |
|-----|-----|
| ~ | Concatenates both operands {{ “hello ” ~ “world” }} |
| | | Applies a filter in the right operand to the left {{ “hello”|uppercase }} |
| .. | Creates a range {{ ‘a'..'z' }} {{ 1..10 }} |
| is | Same as == (equals), also performs tests |
| in | To check if an expression is contained into other expressions if “a” in “abc” |
| is not | Same as != (not equals) |
| ‘a' ? ‘b' : ‘c' | Ternary operator. The same as the PHP ternary operator |
| ++ | Increments a value |
| – | Decrements a value |
The following example shows how to use operators:
~~~
{% set robots = ['Voltron', 'Astro Boy', 'Terminator', 'C3PO'] %}
{% for index in 0..robots|length %}
{% if robots[index] is defined %}
{{ "Name: " ~ robots[index] }}
{% endif %}
{% endfor %}
~~~
### 测试运算（Tests）[](# "永久链接至标题")
Tests can be used to test if a variable has a valid expected value. The operator “is” is used to perform the tests:
~~~
{% set robots = ['1': 'Voltron', '2': 'Astro Boy', '3': 'Terminator', '4': 'C3PO'] %}
{% for position, name in robots %}
{% if position is odd %}
{{ name }}
{% endif %}
{% endfor %}
~~~
The following built-in tests are available in Volt:
| Test | Description |
|-----|-----|
| defined | Checks if a variable is defined (isset) |
| empty | Checks if a variable is empty |
| even | Checks if a numeric value is even |
| odd | Checks if a numeric value is odd |
| numeric | Checks if value is numeric |
| scalar | Checks if value is scalar (not an array or object) |
| iterable | Checks if a value is iterable. Can be traversed by a “for” statement |
| divisibleby | Checks if a value is divisible by other value |
| sameas | Checks if a value is identical to other value |
| type | Checks if a value is of the specified type |
More examples:
~~~
{% if robot is defined %}
The robot variable is defined
{% endif %}
{% if robot is empty %}
The robot is null or isn't defined
{% endif %}
{% for key, name in [1: 'Voltron', 2: 'Astroy Boy', 3: 'Bender'] %}
{% if key is even %}
{{ name }}
{% endif %}
{% endfor %}
{% for key, name in [1: 'Voltron', 2: 'Astroy Boy', 3: 'Bender'] %}
{% if key is odd %}
{{ name }}
{% endif %}
{% endfor %}
{% for key, name in [1: 'Voltron', 2: 'Astroy Boy', 'third': 'Bender'] %}
{% if key is numeric %}
{{ name }}
{% endif %}
{% endfor %}
{% set robots = [1: 'Voltron', 2: 'Astroy Boy'] %}
{% if robots is iterable %}
{% for robot in robots %}
...
{% endfor %}
{% endif %}
{% set world = "hello" %}
{% if world is sameas("hello") %}
{{ "it's hello" }}
{% endif %}
{% set external = false %}
{% if external is type('boolean') %}
{{ "external is false or true" }}
{% endif %}
~~~
### 宏定义（Macros）[](# "永久链接至标题")
Macros can be used to reuse logic in a template, they act as PHP functions, can receive parameters and return values:
~~~
{%- macro related_bar(related_links) %}
<ul>
{%- for rellink in related_links %}
<li><a href="{{ url(link.url) }}" title="{{ link.title|striptags }}">{{ link.text }}</a></li>
{%- endfor %}
</ul>
{%- endmacro %}
{# Print related links #}
{{ related_bar(links) }}
<div>This is the content</div>
{# Print related links again #}
{{ related_bar(links) }}
~~~
When calling macros, parameters can be passed by name:
~~~
{%- macro error_messages(message, field, type) %}
<div>
<span class="error-type">{{ type }}</span>
<span class="error-field">{{ field }}</span>
<span class="error-message">{{ message }}</span>
</div>
{%- endmacro %}
{# Call the macro #}
{{ error_messages('type': 'Invalid', 'message': 'The name is invalid', 'field': 'name') }}
~~~
Macros can return values:
~~~
{%- macro my_input(name, class) %}
{% return text_field(name, 'class': class) %}
{%- endmacro %}
{# Call the macro #}
{{ '<p>' ~ my_input('name', 'input-text') ~ '</p>' }}
~~~
And receive optional parameters:
~~~
{%- macro my_input(name, class="input-text") %}
{% return text_field(name, 'class': class) %}
{%- endmacro %}
{# Call the macro #}
{{ '<p>' ~ my_input('name') ~ '</p>' }}
{{ '<p>' ~ my_input('name', 'input-text') ~ '</p>' }}
~~~
### 使用标签助手（Using Tag Helpers）[](# "永久链接至标题")
Volt is highly integrated with [*Phalcon\Tag*](#), so it's easy to use the helpers provided by that component in a Volt template:
~~~
{{ javascript_include("js/jquery.js") }}
{{ form('products/save', 'method': 'post') }}
<label for="name">Name</label>
{{ text_field("name", "size": 32) }}
<label for="type">Type</label>
{{ select("type", productTypes, 'using': ['id', 'name']) }}
{{ submit_button('Send') }}
{{ end_form() }}
~~~
The following PHP is generated:
~~~
<?php echo Phalcon\Tag::javascriptInclude("js/jquery.js") ?>
<?php echo Phalcon\Tag::form(array('products/save', 'method' => 'post')); ?>
<label for="name">Name</label>
<?php echo Phalcon\Tag::textField(array('name', 'size' => 32)); ?>
<label for="type">Type</label>
<?php echo Phalcon\Tag::select(array('type', $productTypes, 'using' => array('id', 'name'))); ?>
<?php echo Phalcon\Tag::submitButton('Send'); ?>
{{ end_form() }}
~~~
To call a Phalcon\Tag helper, you only need to call an uncamelized version of the method:
| Method | Volt function |
|-----|-----|
| Phalcon\Tag::linkTo | link_to |
| Phalcon\Tag::textField | text_field |
| Phalcon\Tag::passwordField | password_field |
| Phalcon\Tag::hiddenField | hidden_field |
| Phalcon\Tag::fileField | file_field |
| Phalcon\Tag::checkField | check_field |
| Phalcon\Tag::radioField | radio_field |
| Phalcon\Tag::dateField | date_field |
| Phalcon\Tag::emailField | email_field |
| Phalcon\Tag::numberField | number_field |
| Phalcon\Tag::submitButton | submit_button |
| Phalcon\Tag::selectStatic | select_static |
| Phalcon\Tag::select | select |
| Phalcon\Tag::textArea | text_area |
| Phalcon\Tag::form | form |
| Phalcon\Tag::endForm | end_form |
| Phalcon\Tag::getTitle | get_title |
| Phalcon\Tag::stylesheetLink | stylesheet_link |
| Phalcon\Tag::javascriptInclude | javascript_include |
| Phalcon\Tag::image | image |
| Phalcon\Tag::friendlyTitle | friendly_title |
### 函数（Functions）[](# "永久链接至标题")
The following built-in functions are available in Volt:
| Name | Description |
|-----|-----|
| content | Includes the content produced in a previous rendering stage |
| get_content | Same as ‘content' |
| partial | Dynamically loads a partial view in the current template |
| super | Render the contents of the parent block |
| time | Calls the PHP function with the same name |
| date | Calls the PHP function with the same name |
| dump | Calls the PHP function ‘var_dump' |
| version | Returns the current version of the framework |
| constant | Reads a PHP constant |
| url | Generate a URL using the ‘url' service |
### 视图集成（View Integration）[](# "永久链接至标题")
Also, Volt is integrated with [*Phalcon\Mvc\View*](#), you can play with the view hierarchy and include partials as well:
~~~
{{ content() }}
<!-- Simple include of a partial -->
<div id="footer">{{ partial("partials/footer") }}</div>
<!-- Passing extra variables -->
<div id="footer">{{ partial("partials/footer", ['links': links]) }}</div>
~~~
A partial is included in runtime, Volt also provides “include”, this compiles the content of a view and returns its contentsas part of the view which was included:
~~~
{# Simple include of a partial #}
<div id="footer">{% include "partials/footer" %}</div>
{# Passing extra variables #}
<div id="footer">{% include "partials/footer" with ['links': links] %}</div>
~~~
### 包含（Include）[](# "永久链接至标题")
‘include' has a special behavior that will help us improve performance a bit when using Volt, if you specify the extensionwhen including the file and it exists when the template is compiled, Volt can inline the contents of the template in the parenttemplate where it's included. Templates aren't inlined if the ‘include' have variables passed with ‘with':
~~~
{# The contents of 'partials/footer.volt' is compiled and inlined #}
<div id="footer">{% include "partials/footer.volt" %}</div>
~~~
### 模版的继承（Template Inheritance）[](# "永久链接至标题")
With template inheritance you can create base templates that can be extended by others templates allowing to reuse code. A base templatedefine *blocks* than can be overridden by a child template. Let's pretend that we have the following base template:
~~~
{# templates/base.volt #}
<!DOCTYPE html>
<html>
<head>
{% block head %}
<link rel="stylesheet" href="style.css" />
{% endblock %}
<title>{% block title %}{% endblock %} - My Webpage</title>
</head>
<body>
<div id="content">{% block content %}{% endblock %}</div>
<div id="footer">
{% block footer %}© Copyright 2015, All rights reserved.{% endblock %}
</div>
</body>
</html>
~~~
From other template we could extend the base template replacing the blocks:
~~~
{% extends "templates/base.volt" %}
{% block title %}Index{% endblock %}
{% block head %}<style type="text/css">.important { color: #336699; }</style>{% endblock %}
{% block content %}
<h1>Index</h1>
<p class="important">Welcome on my awesome homepage.</p>
{% endblock %}
~~~
Not all blocks must be replaced at a child template, only those that are needed. The final output produced will be the following:
~~~
<!DOCTYPE html>
<html>
<head>
<style type="text/css">.important { color: #336699; }</style>
<title>Index - My Webpage</title>
</head>
<body>
<div id="content">
<h1>Index</h1>
<p class="important">Welcome on my awesome homepage.</p>
</div>
<div id="footer">
© Copyright 2015, All rights reserved.
</div>
</body>
</html>
~~~
### 多重继承（Multiple Inheritance）[](# "永久链接至标题")
Extended templates can extend other templates. The following example illustrates this:
~~~
{# main.volt #}
<!DOCTYPE html>
<html>
<head>
<title>Title</title>
</head>
<body>
{% block content %}{% endblock %}
</body>
</html>
~~~
Template “layout.volt” extends “main.volt”
~~~
{# layout.volt #}
{% extends "main.volt" %}
{% block content %}
<h1>Table of contents</h1>
{% endblock %}
~~~
Finally a view that extends “layout.volt”:
~~~
{# index.volt #}
{% extends "layout.volt" %}
{% block content %}
{{ super() }}
<ul>
<li>Some option</li>
<li>Some other option</li>
</ul>
{% endblock %}
~~~
Rendering “index.volt” produces:
~~~
<!DOCTYPE html>
<html>
<head>
<title>Title</title>
</head>
<body>
<h1>Table of contents</h1>
<ul>
<li>Some option</li>
<li>Some other option</li>
</ul>
</body>
</html>
~~~
Note the call to the function “super()”. With that function it's possible to render the contents of the parent block.
As partials, the path set to “extends” is a relative path under the current views directory (i.e. app/views/).
> By default, and for performance reasons, Volt only checks for changes in the children templatesto know when to re-compile to plain PHP again, so it is recommended initialize Volt with the option‘compileAlways' => true. Thus, the templates are compiled always taking into account changes inthe parent templates.
### 自动编码模式（Autoescape mode）[](# "永久链接至标题")
You can enable auto-escaping of all variables printed in a block using the autoescape mode:
~~~
Manually escaped: {{ robot.name|e }}
{% autoescape true %}
Autoescaped: {{ robot.name }}
{% autoescape false %}
No Autoescaped: {{ robot.name }}
{% endautoescape %}
{% endautoescape %}
~~~
### 配置 Volt 引擎（Setting up the Volt Engine)[](# "永久链接至标题")
Volt can be configured to alter its default behavior, the following example explain how to do that:
~~~
<?php
use Phalcon\Mvc\View;
use Phalcon\Mvc\View\Engine\Volt;
// Register Volt as a service
$di->set('voltService', function ($view, $di) {
$volt = new Volt($view, $di);
$volt->setOptions(array(
"compiledPath" => "../app/compiled-templates/",
"compiledExtension" => ".compiled"
));
return $volt;
});
// Register Volt as template engine
$di->set('view', function () {
$view = new View();
$view->setViewsDir('../app/views/');
$view->registerEngines(array(
".volt" => 'voltService'
));
return $view;
});
~~~
If you do not want to reuse Volt as a service you can pass an anonymous function to register the engine instead of a service name:
~~~
<?php
use Phalcon\Mvc\View;
use Phalcon\Mvc\View\Engine\Volt;
// Register Volt as template engine with an anonymous function
$di->set('view', function () {
$view = new View();
$view->setViewsDir('../app/views/');
$view->registerEngines(array(
".volt" => function ($view, $di) {
$volt = new Volt($view, $di);
// Set some options here
return $volt;
}
));
return $view;
});
~~~
The following options are available in Volt:
| Option | Description | Default |
|-----|-----|-----|
| compiledPath | A writable path where the compiled PHP templates will be placed | ./ |
| compiledExtension | An additional extension appended to the compiled PHP file | .php |
| compiledSeparator | Volt replaces the directory separators / and \ by this separator in order to create a single file in the compiled directory | %% |
| stat | Whether Phalcon must check if exists differences between the template file and its compiled path | true |
| compileAlways | Tell Volt if the templates must be compiled in each request or only when they change | false |
| prefix | Allows to prepend a prefix to the templates in the compilation path | null |
The compilation path is generated according to the above options, if the developer wants total freedom defining the compilation path,an anonymous function can be used to generate it, this function receives the relative path to the template in theviews directory. The following examples show how to change the compilation path dynamically:
~~~
<?php
// Just append the .php extension to the template path
// leaving the compiled templates in the same directory
$volt->setOptions(array(
'compiledPath' => function ($templatePath) {
return $templatePath . '.php';
}
));
// Recursively create the same structure in another directory
$volt->setOptions(array(
'compiledPath' => function ($templatePath) {
$dirName = dirname($templatePath);
if (!is_dir('cache/' . $dirName)) {
mkdir('cache/' . $dirName);
}
return 'cache/' . $dirName . '/'. $templatePath . '.php';
}
));
~~~
### 扩展 Volt（Extending Volt）[](# "永久链接至标题")
Unlike other template engines, Volt itself is not required to run the compiled templates.Once the templates are compiled there is no dependence on Volt. With performance independence in mind,Volt only acts as a compiler for PHP templates.
The Volt compiler allow you to extend it adding more functions, tests or filters to the existing ones.
### 函数（Functions）[](# "永久链接至标题")
Functions act as normal PHP functions, a valid string name is required as function name.Functions can be added using two strategies, returning a simple string or using an anonymousfunction. Always is required that the chosen strategy returns a valid PHP string expression:
~~~
<?php
use Phalcon\Mvc\View\Engine\Volt;
$volt = new Volt($view, $di);
$compiler = $volt->getCompiler();
// This binds the function name 'shuffle' in Volt to the PHP function 'str_shuffle'
$compiler->addFunction('shuffle', 'str_shuffle');
~~~
Register the function with an anonymous function. This case we use $resolvedArgs to pass the arguments exactlyas were passed in the arguments:
~~~
<?php
$compiler->addFunction('widget', function ($resolvedArgs, $exprArgs) {
return 'MyLibrary\Widgets::get(' . $resolvedArgs . ')';
});
~~~
Treat the arguments independently and unresolved:
~~~
<?php
$compiler->addFunction('repeat', function ($resolvedArgs, $exprArgs) use ($compiler) {
// Resolve the first argument
$firstArgument = $compiler->expression($exprArgs[0]['expr']);
// Checks if the second argument was passed
if (isset($exprArgs[1])) {
$secondArgument = $compiler->expression($exprArgs[1]['expr']);
} else {
// Use '10' as default
$secondArgument = '10';
}
return 'str_repeat(' . $firstArgument . ', ' . $secondArgument . ')';
});
~~~
Generate the code based on some function availability:
~~~
<?php
$compiler->addFunction('contains_text', function ($resolvedArgs, $exprArgs) {
if (function_exists('mb_stripos')) {
return 'mb_stripos(' . $resolvedArgs . ')';
} else {
return 'stripos(' . $resolvedArgs . ')';
}
});
~~~
Built-in functions can be overridden adding a function with its name:
~~~
<?php
// Replace built-in function dump
$compiler->addFunction('dump', 'print_r');
~~~
### 过滤器（Filters）[](# "永久链接至标题")
A filter has the following form in a template: leftExpr|name(optional-args). Adding new filtersis similar as seen with the functions:
~~~
<?php
// This creates a filter 'hash' that uses the PHP function 'md5'
$compiler->addFilter('hash', 'md5');
~~~
~~~
<?php
$compiler->addFilter('int', function ($resolvedArgs, $exprArgs) {
return 'intval(' . $resolvedArgs . ')';
});
~~~
Built-in filters can be overridden adding a function with its name:
~~~
<?php
// Replace built-in filter 'capitalize'
$compiler->addFilter('capitalize', 'lcfirst');
~~~
### 扩展（Extensions）[](# "永久链接至标题")
With extensions the developer has more flexibility to extend the template engine, and override the compilationof a specific instruction, change the behavior of an expression or operator, add functions/filters, and more.
An extension is a class that implements the events triggered by Volt as a method of itself.
For example, the class below allows to use any PHP function in Volt:
~~~
<?php
class PhpFunctionExtension
{
/**
* This method is called on any attempt to compile a function call
*/
public function compileFunction($name, $arguments)
{
if (function_exists($name)) {
return $name . '('. $arguments . ')';
}
}
}
~~~
The above class implements the method ‘compileFunction' which is invoked before any attempt to compile a function call in anytemplate. The purpose of the extension is to verify if a function to be compiled is a PHP function allowing to call itfrom the template. Events in extensions must return valid PHP code, this will be used as result of the compilationinstead of the one generated by Volt. If an event doesn't return an string the compilation is done using the defaultbehavior provided by the engine.
The following compilation events are available to be implemented in extensions:
| Event/Method | Description |
|-----|-----|
| compileFunction | Triggered before trying to compile any function call in a template |
| compileFilter | Triggered before trying to compile any filter call in a template |
| resolveExpression | Triggered before trying to compile any expression. This allows the developer to override operators |
| compileStatement | Triggered before trying to compile any expression. This allows the developer to override any statement |
Volt extensions must be in registered in the compiler making them available in compile time:
~~~
<?php
// Register the extension in the compiler
$compiler->addExtension(new PhpFunctionExtension());
~~~
### 缓存视图片段（Caching view fragments）[](# "永久链接至标题")
With Volt it's easy cache view fragments. This caching improves performance preventingthat the contents of a block from being executed by PHP each time the view is displayed:
~~~
{% cache "sidebar" %}
<!-- generate this content is slow so we are going to cache it -->
{% endcache %}
~~~
Setting a specific number of seconds:
~~~
{# cache the sidebar by 1 hour #}
{% cache "sidebar" 3600 %}
<!-- generate this content is slow so we are going to cache it -->
{% endcache %}
~~~
Any valid expression can be used as cache key:
~~~
{% cache ("article-" ~ post.id) 3600 %}
<h1>{{ post.title }}</h1>
<p>{{ post.content }}</p>
{% endcache %}
~~~
The caching is done by the [*Phalcon\Cache*](#) component via the view component.Learn more about how this integration works in the section [*“Caching View Fragments”*](#).
### 注入服务到模版（Inject Services into a Template）[](# "永久链接至标题")
If a service container (DI) is available for Volt, you can use the services by only accessing the name of the service in the template:
~~~
{# Inject the 'flash' service #}
<div id="messages">{{ flash.output() }}</div>
{# Inject the 'security' service #}
<input type="hidden" name="token" value="{{ security.getToken() }}">
~~~
### 独立的组件（Stand-alone component）[](# "永久链接至标题")
Using Volt in a stand-alone mode can be demonstrated below:
~~~
<?php
Phalcon\Mvc\View\Engine\Volt\Compiler as VoltCompiler;
// Create a compiler
$compiler = new VoltCompiler();
// Optionally add some options
$compiler->setOptions(array(
// ...
));
// Compile a template string returning PHP code
echo $compiler->compileString('{{ "hello" }}');
// Compile a template in a file specifying the destination file
$compiler->compileFile('layouts/main.volt', 'cache/layouts/main.volt.php');
// Compile a template in a file based on the options passed to the compiler
$compiler->compile('layouts/main.volt');
// Require the compiled templated (optional)
require $compiler->getCompiledTemplatePath();
~~~
### 外部资源（External Resources）[](# "永久链接至标题")
- A bundle for Sublime/Textmate is available [here](https://github.com/phalcon/volt-sublime-textmate)
- [Album-O-Rama](http://album-o-rama.phalconphp.com) is a sample application using Volt as template engine, [[Github](https://github.com/phalcon/album-o-rama)]
- [Our website](http://phalconphp.com) is running using Volt as template engine, [[Github](https://github.com/phalcon/website)]
- [Phosphorum](http://forum.phalconphp.com), the Phalcon's forum, also uses Volt, [[Github](https://github.com/phalcon/forum)]
- [Vkuró](http://vokuro.phalconphp.com), is another sample application that use Volt, [[Github](https://github.com/phalcon/vokuro)]
|
- [索引](# "总目录")
- [下一页](# "MVC 应用（MVC Applications）") |
- [上一页](# "资源文件管理（Assets Management）") |
- Phalcon 2.0.6文档
- API参考
- API列表
- Abstract class Phalcon\Acl
- Abstract class Phalcon\Acl\Adapter
- Class Phalcon\Acl\Adapter\Memory
- Interface Phalcon\Acl\AdapterInterface
- Class Phalcon\Acl\Exception
- Class Phalcon\Acl\Resource
- Interface Phalcon\Acl\ResourceInterface
- Class Phalcon\Acl\Role
- Interface Phalcon\Acl\RoleInterface
- Class Phalcon\Annotations\Annotation
- Abstract class Phalcon\Annotations\Adapter
- Class Phalcon\Annotations\Adapter\Apc
- Class Phalcon\Annotations\Adapter\Files
- Class Phalcon\Annotations\Adapter\Memory
- Class Phalcon\Annotations\Adapter\Xcache
- Interface Phalcon\Annotations\AdapterInterface
- Class Phalcon\Annotations\Collection
- Class Phalcon\Annotations\Exception
- Class Phalcon\Annotations\Reader
- Interface Phalcon\Annotations\ReaderInterface
- Class Phalcon\Annotations\Reflection
- Class Phalcon\Assets\Collection
- Class Phalcon\Assets\Exception
- Interface Phalcon\Assets\FilterInterface
- Class Phalcon\Assets\Filters\Cssmin
- Class Phalcon\Assets\Filters\Jsmin
- Class Phalcon\Assets\Filters\None
- Class Phalcon\Assets\Inline
- Class Phalcon\Assets\Inline\Css
- Class Phalcon\Assets\Inline\Js
- Class Phalcon\Assets\Manager
- Class Phalcon\Assets\Resource
- Class Phalcon\Assets\Resource\Css
- Class Phalcon\Assets\Resource\Js
- Abstract class Phalcon\Cache\Backend
- Class Phalcon\Cache\Backend\Apc
- Class Phalcon\Cache\Backend\File
- Class Phalcon\Cache\Backend\Libmemcached
- Class Phalcon\Cache\Backend\Memcache
- Class Phalcon\Cache\Backend\Memory
- Class Phalcon\Cache\Backend\Mongo
- Class Phalcon\Cache\Backend\Redis
- Class Phalcon\Cache\Backend\Xcache
- Interface Phalcon\Cache\BackendInterface
- Class Phalcon\Cache\Exception
- Class Phalcon\Cache\Frontend\Base64
- Class Phalcon\Cache\Frontend\Data
- Class Phalcon\Cache\Frontend\Igbinary
- Class Phalcon\Cache\Frontend\Json
- Class Phalcon\Cache\Frontend\None
- Class Phalcon\Cache\Frontend\Output
- Interface Phalcon\Cache\FrontendInterface
- Class Phalcon\Cache\Multiple
- Class Phalcon\Cli\Router\Route
- Class Phalcon\Config
- Class Phalcon\Config\Adapter\Ini
- Class Phalcon\Config\Adapter\Json
- Class Phalcon\Config\Adapter\Php
- Class Phalcon\Config\Adapter\Yaml
- Class Phalcon\Config\Exception
- Class Phalcon\Crypt
- Class Phalcon\Crypt\Exception
- Interface Phalcon\CryptInterface
- Abstract class Phalcon\Db
- Abstract class Phalcon\Db\Adapter
- Abstract class Phalcon\Db\Adapter\Pdo
- Class Phalcon\Db\Adapter\Pdo\Mysql
- Class Phalcon\Db\Adapter\Pdo\Oracle
- Class Phalcon\Db\Adapter\Pdo\Postgresql
- Class Phalcon\Db\Adapter\Pdo\Sqlite
- Interface Phalcon\Db\AdapterInterface
- Class Phalcon\Db\Column
- Interface Phalcon\Db\ColumnInterface
- Abstract class Phalcon\Db\Dialect
- Class Phalcon\Db\Dialect\Oracle
- Class Phalcon\Db\Dialect\Postgresql
- Class Phalcon\Db\Dialect\Sqlite
- Interface Phalcon\Db\DialectInterface
- Class Phalcon\Db\Exception
- Class Phalcon\Db\Index
- Interface Phalcon\Db\IndexInterface
- Class Phalcon\Db\Profiler
- Class Phalcon\Db\Profiler\Item
- Class Phalcon\Db\RawValue
- Class Phalcon\Db\Reference
- Interface Phalcon\Db\ReferenceInterface
- Class Phalcon\Db\Result\Pdo
- Interface Phalcon\Db\ResultInterface
- Class Phalcon\Debug
- Class Phalcon\Debug\Dump
- Class Phalcon\Debug\Exception
- Interface Phalcon\DiInterface
- Abstract class Phalcon\Dispatcher
- Interface Phalcon\DispatcherInterface
- Class Phalcon\Escaper
- Class Phalcon\Escaper\Exception
- Interface Phalcon\EscaperInterface
- Class Phalcon\Events\Event
- Interface Phalcon\Events\EventsAwareInterface
- Class Phalcon\Events\Exception
- Class Phalcon\Events\Manager
- Interface Phalcon\Events\ManagerInterface
- Class Phalcon\Exception
- Class Phalcon\Filter
- Class Phalcon\Filter\Exception
- Interface Phalcon\Filter\UserFilterInterface
- Interface Phalcon\FilterInterface
- Abstract class Phalcon\Flash
- Class Phalcon\Flash\Direct
- Class Phalcon\Flash\Exception
- Class Phalcon\Flash\Session
- Interface Phalcon\FlashInterface
- Class Phalcon\Forms\Form
- Abstract class Phalcon\Forms\Element
- Class Phalcon\Forms\Element\Check
- Class Phalcon\Forms\Element\Email
- Class Phalcon\Forms\Element\File
- Class Phalcon\Forms\Element\Date
- Class Phalcon\Forms\Element\Hidden
- Class Phalcon\Forms\Element\Numeric
- Class Phalcon\Forms\Element\Password
- Class Phalcon\Forms\Element\Radio
- Class Phalcon\Forms\Element\Select
- Class Phalcon\Forms\Element\Submit
- Class Phalcon\Forms\Element\Text
- Class Phalcon\Forms\Element\TextArea
- Interface Phalcon\Forms\ElementInterface
- Class Phalcon\Forms\Exception
- Class Phalcon\Forms\Manager
- Class Phalcon\Http\Cookie
- Class Phalcon\Http\Cookie\Exception
- Class Phalcon\Http\Request
- Class Phalcon\Http\Request\Exception
- Class Phalcon\Http\Request\File
- Interface Phalcon\Http\Request\FileInterface
- Interface Phalcon\Http\RequestInterface
- Class Phalcon\Http\Response
- Class Phalcon\Http\Response\Cookies
- Interface Phalcon\Http\Response\CookiesInterface
- Class Phalcon\Http\Response\Exception
- Class Phalcon\Http\Response\Headers
- Interface Phalcon\Http\Response\HeadersInterface
- Interface Phalcon\Http\ResponseInterface
- Class Phalcon\Image
- Abstract class Phalcon\Image\Adapter
- Class Phalcon\Image\Adapter\Imagick
- Interface Phalcon\Image\AdapterInterface
- Class Phalcon\Image\Exception
- Class Phalcon\Kernel
- Class Phalcon\Loader
- Class Phalcon\Loader\Exception
- Abstract class Phalcon\Logger
- Abstract class Phalcon\Logger\Adapter
- Class Phalcon\Logger\Adapter\File
- Class Phalcon\Logger\Adapter\Firephp
- Class Phalcon\Logger\Adapter\Stream
- Class Phalcon\Logger\Adapter\Syslog
- Interface Phalcon\Logger\AdapterInterface
- Class Phalcon\Logger\Exception
- Abstract class Phalcon\Logger\Formatter
- Class Phalcon\Logger\Formatter\Firephp
- Class Phalcon\Logger\Formatter\Json
- Class Phalcon\Logger\Formatter\Line
- Class Phalcon\Logger\Formatter\Syslog
- Interface Phalcon\Logger\FormatterInterface
- Class Phalcon\Logger\Item
- Class Phalcon\Logger\Multiple
- Class Phalcon\Mvc\Application
- Class Phalcon\Mvc\Application\Exception
- Abstract class Phalcon\Mvc\Collection
- Abstract class Phalcon\Mvc\Collection\Behavior
- Class Phalcon\Mvc\Collection\Behavior\SoftDelete
- Class Phalcon\Mvc\Collection\Behavior\Timestampable
- Interface Phalcon\Mvc\Collection\BehaviorInterface
- Class Phalcon\Mvc\Collection\Document
- Class Phalcon\Mvc\Collection\Exception
- Class Phalcon\Mvc\Collection\Manager
- Interface Phalcon\Mvc\Collection\ManagerInterface
- Interface Phalcon\Mvc\CollectionInterface
- Abstract class Phalcon\Mvc\Controller
- Interface Phalcon\Mvc\ControllerInterface
- Class Phalcon\Mvc\Dispatcher
- Class Phalcon\Mvc\Dispatcher\Exception
- Interface Phalcon\Mvc\DispatcherInterface
- Interface Phalcon\Mvc\EntityInterface
- Class Phalcon\Mvc\Micro
- Class Phalcon\Mvc\Micro\Collection
- Interface Phalcon\Mvc\Micro\CollectionInterface
- Class Phalcon\Mvc\Micro\Exception
- Class Phalcon\Mvc\Micro\LazyLoader
- Interface Phalcon\Mvc\Micro\MiddlewareInterface
- Abstract class Phalcon\Mvc\Model
- Abstract class Phalcon\Mvc\Model\Behavior
- Class Phalcon\Mvc\Model\Behavior\SoftDelete
- Class Phalcon\Mvc\Model\Behavior\Timestampable
- Interface Phalcon\Mvc\Model\BehaviorInterface
- Class Phalcon\Mvc\Model\Criteria
- Interface Phalcon\Mvc\Model\CriteriaInterface
- Class Phalcon\Mvc\Model\Exception
- Class Phalcon\Mvc\Model\Manager
- Interface Phalcon\Mvc\Model\ManagerInterface
- Class Phalcon\Mvc\Model\Message
- Interface Phalcon\Mvc\Model\MessageInterface
- Abstract class Phalcon\Mvc\Model\MetaData
- Class Phalcon\Mvc\Model\MetaData\Apc
- Class Phalcon\Mvc\Model\MetaData\Files
- Class Phalcon\Mvc\Model\MetaData\Libmemcached
- Class Phalcon\Mvc\Model\MetaData\Memcache
- Class Phalcon\Mvc\Model\MetaData\Memory
- Class Phalcon\Mvc\Model\MetaData\Session
- Class Phalcon\Mvc\Model\MetaData\Strategy\Annotations
- Class Phalcon\Mvc\Model\MetaData\Strategy\Introspection
- Interface Phalcon\Mvc\Model\MetaData\StrategyInterface
- Class Phalcon\Mvc\Model\MetaData\Xcache
- Interface Phalcon\Mvc\Model\MetaDataInterface
- Class Phalcon\Mvc\Model\Query
- Class Phalcon\Mvc\Model\Query\Builder
- Interface Phalcon\Mvc\Model\Query\BuilderInterface
- Abstract class Phalcon\Mvc\Model\Query\Lang
- Class Phalcon\Mvc\Model\Query\Status
- Interface Phalcon\Mvc\Model\Query\StatusInterface
- Interface Phalcon\Mvc\Model\QueryInterface
- Class Phalcon\Mvc\Model\Relation
- Interface Phalcon\Mvc\Model\RelationInterface
- Interface Phalcon\Mvc\Model\ResultInterface
- Abstract class Phalcon\Mvc\Model\Resultset
- Class Phalcon\Mvc\Model\Resultset\Complex
- Class Phalcon\Mvc\Model\Resultset\Simple
- Abstract class Phalcon\Mvc\Model\Validator
- Class Phalcon\Mvc\Model\Validator\Email
- Class Phalcon\Mvc\Model\Validator\Exclusionin
- Class Phalcon\Mvc\Model\Validator\Inclusionin
- Class Phalcon\Mvc\Model\Validator\Ip
- Class Phalcon\Mvc\Model\Validator\Numericality
- Class Phalcon\Mvc\Model\Validator\PresenceOf
- Class Phalcon\Mvc\Model\Validator\Regex
- Class Phalcon\Mvc\Model\Validator\StringLength
- Class Phalcon\Mvc\Model\Validator\Uniqueness
- Class Phalcon\Mvc\Model\Validator\Url
- Interface Phalcon\Mvc\Model\ValidatorInterface
- Interface Phalcon\Mvc\Model\ResultsetInterface
- Class Phalcon\Mvc\Model\Row
- Class Phalcon\Mvc\Model\Transaction
- Class Phalcon\Mvc\Model\Transaction\Exception
- Class Phalcon\Mvc\Model\Transaction\Failed
- Class Phalcon\Mvc\Model\Transaction\Manager
- Interface Phalcon\Mvc\Model\Transaction\ManagerInterface
- Interface Phalcon\Mvc\Model\TransactionInterface
- Class Phalcon\Mvc\Model\ValidationFailed
- Interface Phalcon\Mvc\ModelInterface
- Interface Phalcon\Mvc\ModuleDefinitionInterface
- Class Phalcon\Mvc\Router
- Class Phalcon\Mvc\Router\Annotations
- Class Phalcon\Mvc\Router\Exception
- Class Phalcon\Mvc\Router\Group
- Interface Phalcon\Mvc\Router\GroupInterface
- Class Phalcon\Mvc\Router\Route
- Interface Phalcon\Mvc\Router\RouteInterface
- Interface Phalcon\Mvc\RouterInterface
- Class Phalcon\Mvc\Url
- Class Phalcon\Mvc\Url\Exception
- Interface Phalcon\Mvc\UrlInterface
- Class Phalcon\Mvc\User\Component
- Class Phalcon\Mvc\User\Module
- Class Phalcon\Mvc\User\Plugin
- Class Phalcon\Mvc\View
- Abstract class Phalcon\Mvc\View\Engine
- Class Phalcon\Mvc\View\Engine\Php
- Class Phalcon\Mvc\View\Engine\Volt
- Class Phalcon\Mvc\View\Engine\Volt\Compiler
- Interface Phalcon\Mvc\View\EngineInterface
- Class Phalcon\Mvc\View\Exception
- Class Phalcon\Mvc\View\Simple
- Interface Phalcon\Mvc\ViewBaseInterface
- Interface Phalcon\Mvc\ViewInterface
- Abstract class Phalcon\Paginator\Adapter
- Class Phalcon\Paginator\Adapter\Model
- Class Phalcon\Paginator\Adapter\NativeArray
- Class Phalcon\Paginator\Adapter\QueryBuilder
- Interface Phalcon\Paginator\AdapterInterface
- Class Phalcon\Paginator\Exception
- Class Phalcon\Queue\Beanstalk
- Class Phalcon\Queue\Beanstalk\Job
- Final class Phalcon\Registry
- Class Phalcon\Security
- Class Phalcon\Security\Exception
- Abstract class Phalcon\Session
- Abstract class Phalcon\Session\Adapter
- Class Phalcon\Session\Adapter\Files
- Class Phalcon\Session\Adapter\Libmemcached
- Class Phalcon\Session\Adapter\Memcache
- Interface Phalcon\Session\AdapterInterface
- Class Phalcon\Session\Bag
- Interface Phalcon\Session\BagInterface
- Class Phalcon\Session\Exception
- Class Phalcon\Tag
- Class Phalcon\Tag\Exception
- Abstract class Phalcon\Tag\Select
- Abstract class Phalcon\Text
- Abstract class Phalcon\Translate
- Abstract class Phalcon\Translate\Adapter
- Class Phalcon\Translate\Adapter\Csv
- Class Phalcon\Translate\Adapter\Gettext
- Class Phalcon\Translate\Adapter\NativeArray
- Interface Phalcon\Translate\AdapterInterface
- Class Phalcon\Translate\Exception
- Class Phalcon\Validation
- Class Phalcon\Validation\Exception
- Class Phalcon\Validation\Message
- Class Phalcon\Validation\Message\Group
- Interface Phalcon\Validation\MessageInterface
- Abstract class Phalcon\Validation\Validator
- Class Phalcon\Validation\Validator\Alnum
- Class Phalcon\Validation\Validator\Alpha
- Class Phalcon\Validation\Validator\Between
- Class Phalcon\Validation\Validator\Confirmation
- Class Phalcon\Validation\Validator\Digit
- Class Phalcon\Validation\Validator\Email
- Class Phalcon\Validation\Validator\ExclusionIn
- Class Phalcon\Validation\Validator\File
- Class Phalcon\Validation\Validator\Identical
- Class Phalcon\Validation\Validator\InclusionIn
- Class Phalcon\Validation\Validator\Numericality
- Class Phalcon\Validation\Validator\PresenceOf
- Class Phalcon\Validation\Validator\Regex
- Class Phalcon\Validation\Validator\StringLength
- Class Phalcon\Validation\Validator\Uniqueness
- Class Phalcon\Validation\Validator\Url
- Interface Phalcon\Validation\ValidatorInterface
- Class Phalcon\Version
- 参考手册
- 安装（Installation）
- 教程 1：让我们通过例子来学习（Tutorial 1: Let’s learn by example）
- 教程 2：Introducing INVO（Tutorial 2: Introducing INVO）
- 教程 3: Securing INVO
- 教程 4: Using CRUDs
- 教程 5: Customizing INVO
- 教程 6: Vkuró
- 教程 7：创建简单的 REST API（Tutorial 7: Creating a Simple REST API）
- 示例列表（List of examples）
- 依赖注入与服务定位器（Dependency Injection/Service Location）
- MVC 架构（The MVC Architecture）
- 使用控制器（Using Controllers）
- 使用模型（Working with Models）
- 模型元数据（Models Meta-Data）
- 事务管理（Model Transactions）
- Phalcon 查询语言（Phalcon Query Language (PHQL)）
- 缓存对象关系映射（Caching in the ORM）
- 对象文档映射 ODM (Object-Document Mapper)
- 使用视图（Using Views）
- 视图助手（View Helpers）
- 资源文件管理（Assets Management）
- Volt 模版引擎（Volt: Template Engine）
- MVC 应用（MVC Applications）
- 路由（Routing）
- 调度控制器（Dispatching Controllers）
- 微应用（Micro Applications）
- 使用命名空间（Working with Namespaces）
- 事件管理器（Events Manager）
- Request Environment
- 返回响应（Returning Responses）
- Cookie 管理（Cookies Management）
- 生成 URL 和 路径（Generating URLs and Paths）
- 闪存消息（Flashing Messages）
- 使用 Session 存储数据（Storing data in Session）
- 过滤与清理（Filtering and Sanitizing）
- 上下文编码（Contextual Escaping）
- 验证（Validation）
- 表单（Forms）
- 读取配置（Reading Configurations）
- 分页（Pagination）
- 使用缓存提高性能（Improving Performance with Cache）
- 安全（Security）
- Encryption/Decryption
- 访问控制列表 ACL（Access Control Lists ACL）
- 多语言支持（Multi-lingual Support）
- Universal Class Loader
- 日志记录（Logging）
- 注释解析器（Annotations Parser）
- 命令行应用（Command Line Applications）
- 队列（Queueing）
- 数据库抽象层（Database Abstraction Layer）
- 国际化（Internationalization）
- 数据库迁移（Database Migrations）
- 调试应用程序（Debugging Applications）
- Phalcon 开发工具（Phalcon Developer Tools）
- 提高性能：下一步该做什么？（Increasing Performance: What’s next?）
- 单元测试（Unit testing）
- 授权（License）