The best way to use this guide is to follow along and try to have fun. You can get the complete code here<\/a>. If you get stuck or have questions, please visit us on Discord<\/a> or in our Forum<\/a>.<\/p>\n\n\n\n One of the key features of Phalcon is that it is loosely coupled. Because of that, you can use any directory structure that is convenient to you. In this tutorial we will use a standard<\/em> directory structure, commonly used in MVC applications. NOTE<\/p>\n\n\n\n Since all the code that Phalcon exposes is encapsulated in the extension (that you have loaded on your web server), you will not see In the case of our tutorial, this file must be located in the You can also use nginX, apache, cherokee or other web servers. You can check the\u00a0webserver setup\u00a0page for instructions.<\/p>\n\n\n\n The first file you need to create is the bootstrap file. This file acts as the entry-point and configuration for your application. In this file, you can implement initialization of components as well define application behavior.<\/p>\n\n\n\n This file handles 3 things: – Registration of component autoloaders – Configuring Services and registering them with the Dependency Injection context – Resolving the application’s HTTP requests<\/p>\n\n\n\n We are going to use\u00a0Phalcon\\Loader\u00a0a\u00a0PSR-4\u00a0compliant file loader. Common things that should be added to the autoloader are your controllers and models. You can also register directories which will be scanned for files required by the application.<\/p>\n\n\n\n To start, lets register our app’s\u00a0 Since Phalcon is loosely coupled, services are registered with the frameworks Dependency Manager so they can be injected automatically to components and services wrapped in the IoC<\/a> container. Frequently you will encounter the term DI which stands for Dependency Injection. Dependency Injection and Inversion of Control(IoC) may sound complex but Phalcon ensures that their use is simple, practical and efficient. Phalcon’s IoC container consists of the following concepts: – Service Container: a “bag” where we globally store the services that our application needs to function. – Service or Component: Data processing object which will be injected into components<\/p>\n\n\n\n Each time the framework requires a component or service, it will ask the container using an agreed upon name for the service. This way we have an easy way to retrieve objects necessary for our application, such as the logger, database connection etc.<\/p>\n\n\n\n NOTE<\/p>\n\n\n\n If you are still interested in the details please see this article by Martin Fowler<\/a>. Also we have a great tutorial<\/a> covering many use cases.<\/p>\n\n\n\n The\u00a0Phalcon\\Di\\FactoryDefault\u00a0is a variant of\u00a0Phalcon\\Di. To make things easier, it will automatically register most of the components that are required by an application and come with Phalcon as standard. Although it is recommended to set up services manually, you can use the\u00a0Phalcon\\Di\\FactoryDefault\u00a0container initially and later on customize it to fit your needs.<\/p>\n\n\n\n Services can be registered in several ways, but for our tutorial, we will use an\u00a0anonymous function:<\/p>\n\n\n\n Now we need to register the view<\/em> service, setting the directory where the framework will find the view files. As the views do not correspond to classes, they cannot be automatically loaded by our autoloader.<\/p>\n\n\n\n Now we need to register a base URI, that will offer the functionality to create all URIs by Phalcon. The component will ensure that whether you run your application through the top directory or a subdirectory, all your URIs will be correct. For this tutorial our base path is In order to handle any requests, the\u00a0Phalcon\\Mvc\\Application\u00a0object is used to do all the heavy lifting for us. The component will accept the request by the user, detect the routes and dispatch the controller and render the view returning back the results.<\/p>\n\n\n\n The As you can see, the bootstrap file is very short and we do not need to include any additional files. You are well on your way to creating a flexible MVC application in less than 30 lines of code.<\/p>\n\n\n\n By default Phalcon will look for a controller named The controller classes must have the suffix NOTE<\/p>\n\n\n\n Congratulations, you are Phlying with Phalcon!<\/strong><\/p>\n\n\n\n Sending output to the screen from the controller is at times necessary but not desirable as most purists in the MVC community will attest. Everything must be passed to the view that is responsible for outputting data on screen. Phalcon will look for a view with the same name as the last executed action inside a directory named as the last executed controller.<\/p>\n\n\n\n Therefore in our case if the URL is: will invoke the If found it will parse it and send the output on screen. Our view then will have the following contents:<\/p>\n\n\n\n and since we moved the The browser output will remain the same. The Now we will change the The generated HTML code displays an anchor ( To generate the link for the NOTE<\/p>\n\n\n\n The\u00a0Phalcon\\Tag\u00a0component also uses the previously registered\u00a0Phalcon\\Uri\u00a0component to correctly generate URIs. A more detailed article regarding HTML generation\u00a0can be found here.<\/p>\n\n\n\n And the Signup controller is ( The empty index action gives the clean pass to a view with the form definition ( Viewing the form in your browser will display the following:<\/p>\n\n\n\n As mentioned above, the Phalcon\\Tag<\/a> utility class, exposes useful methods allowing you to build form HTML elements with ease. The By clicking the Register<\/em> button, you will notice an exception thrown from the framework, indicating that we are missing the Implementing that method will remove the exception:<\/p>\n\n\n\n If you click the Register<\/em> button again, you will see a blank page. We will be adding a view a little later that provides useful feedback. But first, we should work on the code to store the user’s inputs in a database.<\/p>\n\n\n\n According to MVC guidelines, database interactions must be done through models to ensure clean, object-oriented code.<\/p>\n\n\n\n Phalcon brings the first ORM for PHP entirely written in C-language. Instead of increasing the complexity of development, it simplifies it.<\/p>\n\n\n\n Before creating our first model, we need to create a database table using a database access tool or the database command line utility. For this tutorial we are using MySQL as our database, A simple table to store registered users can be created as follows:<\/p>\n\n\n\n A model should be located in the NOTE<\/p>\n\n\n\n Note that the public properties of the model correspond to the names of the fields in our table.<\/p>\n\n\n\n In order to use a database connection and subsequently access data through our models, we need to specify it in our bootstrap process. A database connection is just another service that our application has, that can be used throughout our application:<\/p>\n\n\n\n Adjust the code snippet above as appropriate for your database.<\/p>\n\n\n\n With the correct database parameters, our model is ready to interact with the rest of the application so we can save the user’s input. First, let’s take a moment and create a view for At the beginning of the The ORM will automatically escape the input preventing SQL injections so we only need to pass the request to the Additional validation happens automatically on fields that are defined as not null (required). If we do not enter any of the required fields in the sign-up form our screen will look like this:<\/p>\n\n\n\n Now we will need to get and display all the registered users in our database<\/p>\n\n\n\n The first thing that we are going to do in our NOTE<\/p>\n\n\n\n We assign the results of the In our view file The view will look like this:<\/p>\n\n\n\n As you can see our variable We can now add small design touches to our application. We can add the Bootstrap CSS<\/a> in our code so that it is used throughout our views. We will add an File Structure<\/h2>\n\n\n\n
<\/a>. <\/a>\u2514\u2500\u2500 tutorial <\/a> \u251c\u2500\u2500 app <\/a> \u2502 \u251c\u2500\u2500 controllers <\/a> \u2502 \u2502 \u251c\u2500\u2500 IndexController.php <\/a> \u2502 \u2502 \u2514\u2500\u2500 SignupController.php <\/a> \u2502 \u251c\u2500\u2500 models <\/a> \u2502 \u2502 \u2514\u2500\u2500 Users.php <\/a> \u2502 \u2514\u2500\u2500 views <\/a> \u2514\u2500\u2500 public <\/a> \u251c\u2500\u2500 css <\/a> \u251c\u2500\u2500 img <\/a> \u251c\u2500\u2500 index.php <\/a> \u2514\u2500\u2500 js<\/code><\/p>\n\n\n\nvendor<\/code> directory containing Phalcon code. Everything you need is in memory. If you have not installed the application yet, head over to the installation<\/a> page and complete the installation prior to continuing with this tutorial.<\/p>\n\n\n\nIf this is all brand new it is recommended that you install the Phalcon Devtools<\/a> also. The DevTools leverage PHP's built-in web server, allowing you to run your application almost immediately. If you choose this option, you will need a .htrouter.php<\/code> file at the root of your project with the following contents:<\/a><?php <\/a> <\/a>$uri = urldecode( <\/a> parse_url($_SERVER['REQUEST_URI'], PHP_URL_PATH) <\/a>); <\/a> <\/a>if ($uri !== '\/' && file_exists(__DIR__ . '\/public' . $uri)) { <\/a> return false; <\/a>} <\/a> <\/a>$_GET['_url'] = $_SERVER['REQUEST_URI']; <\/a> <\/a>require_once __DIR__ . '\/public\/index.php';<\/code><\/code><\/pre>\n\n\n\ntutorial<\/code> directory.<\/p>\n\n\n\nBootstrap<\/h2>\n\n\n\n
Autoloader<\/h3>\n\n\n\n
controllers<\/code>\u00a0and\u00a0models<\/code>\u00a0directories using\u00a0Phalcon\\Loader:<\/p>\n\n\n\npublic\/index.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Loader; <\/a> <\/a>define('BASE_PATH', dirname(__DIR__)); <\/a>define('APP_PATH', BASE_PATH . '\/app'); <\/a>\/\/ ... <\/a> <\/a>$loader = new Loader(); <\/a> <\/a>$loader->registerDirs( <\/a> [ <\/a> APP_PATH . '\/controllers\/', <\/a> APP_PATH . '\/models\/', <\/a> ] <\/a>); <\/a> <\/a>$loader->register();<\/code><\/code><\/pre>\n\n\n\nDependency Management\u00b6<\/a><\/h3>\n\n\n\n
Factory Default\u00b6<\/a><\/h3>\n\n\n\n
public\/index.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Di\\FactoryDefault; <\/a> <\/a>\/\/ Create a DI <\/a>$container = new FactoryDefault();<\/code><\/code><\/pre>\n\n\n\npublic\/index.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\View; <\/a> <\/a>\/\/ ... <\/a> <\/a>$container->set( <\/a> 'view', <\/a> function () { <\/a> $view = new View(); <\/a> $view->setViewsDir(APP_PATH . '\/views\/'); <\/a> <\/a> return $view; <\/a> } <\/a>);<\/code><\/code><\/pre>\n\n\n\n\/<\/code>. This will become important later on in this tutorial when we use the class Phalcon\\Tag<\/code> to generate hyperlinks.<\/p>\n\n\n\npublic\/index.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Url; <\/a> <\/a>\/\/ ... <\/a> <\/a>$container->set( <\/a> 'url', <\/a> function () { <\/a> $url = new Url(); <\/a> $url->setBaseUri('\/'); <\/a> <\/a> return $url; <\/a> } <\/a>);<\/code><\/p>\n\n\n\nHandling the Application Request\u00b6<\/a><\/h3>\n\n\n\n
public\/index.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\Application; <\/a> <\/a>\/\/ ... <\/a> <\/a>$application = new Application($container); <\/a> <\/a>$response = $application->handle( <\/a> $_SERVER[\"REQUEST_URI\"] <\/a>); <\/a> <\/a>$response->send();<\/code><\/code><\/pre>\n\n\n\nPutting Everything Together\u00b6<\/a><\/h3>\n\n\n\n
tutorial\/public\/index.php<\/code> file should look like:<\/p>\n\n\n\npublic\/index.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Di\\FactoryDefault; <\/a>use Phalcon\\Loader; <\/a>use Phalcon\\Mvc\\View; <\/a>use Phalcon\\Mvc\\Application; <\/a>use Phalcon\\Url; <\/a> <\/a>\/\/ Define some absolute path constants to aid in locating resources <\/a>define('BASE_PATH', dirname(__DIR__)); <\/a>define('APP_PATH', BASE_PATH . '\/app'); <\/a> <\/a>\/\/ Register an autoloader <\/a>$loader = new Loader(); <\/a> <\/a>$loader->registerDirs( <\/a> [ <\/a> APP_PATH . '\/controllers\/', <\/a> APP_PATH . '\/models\/', <\/a> ] <\/a>); <\/a> <\/a>$loader->register(); <\/a> <\/a>$container = new FactoryDefault(); <\/a> <\/a>$container->set( <\/a> 'view', <\/a> function () { <\/a> $view = new View(); <\/a> $view->setViewsDir(APP_PATH . '\/views\/'); <\/a> return $view; <\/a> } <\/a>); <\/a> <\/a>$container->set( <\/a> 'url', <\/a> function () { <\/a> $url = new Url(); <\/a> $url->setBaseUri('\/'); <\/a> return $url; <\/a> } <\/a>); <\/a> <\/a>$application = new Application($container); <\/a> <\/a>try { <\/a> \/\/ Handle the request <\/a> $response = $application->handle( <\/a> $_SERVER[\"REQUEST_URI\"] <\/a> ); <\/a> <\/a> $response->send(); <\/a>} catch (\\Exception $e) { <\/a> echo 'Exception: ', $e->getMessage(); <\/a>}<\/code><\/code><\/pre>\n\n\n\nCreating a Controller\u00b6<\/a><\/h2>\n\n\n\n
IndexController<\/code>. It is the starting point when no controller or action has been added in the request (eg. https:\/\/localhost\/<\/code>). An IndexController<\/code> and its IndexAction<\/code> should resemble the following example:<\/p>\n\n\n\napp\/controllers\/IndexController.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\Controller; <\/a> <\/a>class IndexController extends Controller <\/a>{ <\/a> public function indexAction() <\/a> { <\/a> return '<h1>Hello!<\/h1>'; <\/a> } <\/a>}<\/code><\/p>\n\n\n\nController<\/code> and controller actions must have the suffix Action<\/code>. For more information you can read our document about controllers<\/a>. If you access the application from your browser, you should see something like this:<\/p>\n\n\n\n![\"\"\/](\"https:\/\/docs.phalcon.io\/4.2\/assets\/images\/content\/tutorial-basic-1.png\")
<\/figure>\n\n\n\nSending Output to a View\u00b6<\/a><\/h2>\n\n\n\n
<\/a>http:\/\/localhost\/<\/code><\/p>\n\n\n\nIndexController<\/code> and indexAction<\/code>, and it will search the view:<\/a>\/views\/index\/index.phtml<\/code><\/p>\n\n\n\napp\/views\/index\/index.phtml<\/code><\/a><?php echo \"<h1>Hello!<\/h1>\";<\/code><\/p>\n\n\n\necho<\/code> from our controller action to the view, it will be empty now:<\/p>\n\n\n\napp\/controllers\/IndexController.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\Controller; <\/a> <\/a>class IndexController extends Controller <\/a>{ <\/a> public function indexAction() <\/a> { <\/a> <\/a> } <\/a>}<\/code><\/p>\n\n\n\nPhalcon\\Mvc\\View<\/code> component is automatically created when the action execution has ended. You can read more about views in Phalcon here<\/a>.<\/p>\n\n\n\nDesigning a Sign-up Form\u00b6<\/a><\/h2>\n\n\n\n
index.phtml<\/code> view file, to add a link to a new controller named signup<\/em>. The goal is to allow users to sign up to our application.<\/p>\n\n\n\napp\/views\/index\/index.phtml<\/code><\/a><?php <\/a> <\/a>echo \"<h1>Hello!<\/h1>\"; <\/a> <\/a>echo PHP_EOL; <\/a> <\/a>echo PHP_EOL; <\/a> <\/a>echo $this->tag->linkTo( <\/a> 'signup', <\/a> 'Sign Up Here!' <\/a>);<\/code><\/code><\/pre>\n\n\n\n<a><\/code>) HTML tag linking to a new controller:<\/p>\n\n\n\napp\/views\/index\/index.phtml<\/code> (rendered)<\/a><h1>Hello!<\/h1> <\/a> <\/a><a href=\"\/signup\">Sign Up Here!<\/a><\/code><\/code><\/pre>\n\n\n\n<a><\/code> tag, we use the Phalcon\\Tag<\/a> component. This is a utility class that offers an easy way to build HTML tags with framework conventions in mind. This class is also a service registered in the Dependency Injector so we can use $this->tag<\/code> to access its functionality.<\/p>\n\n\n\nPhalcon\\Tag<\/code> is already registered in the DI container since we have used the Phalcon\\Di\\FactoryDefault<\/code> container. If you registered all the services on your own, you will need to register this component in your container to make it available in your application.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/docs.phalcon.io\/4.2\/assets\/images\/content\/tutorial-basic-2.png\")
<\/figure>\n\n\n\napp\/controllers\/SignupController.php<\/code>):<\/p>\n\n\n\napp\/controllers\/SignupController.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\Controller; <\/a> <\/a>class SignupController extends Controller <\/a>{ <\/a> public function indexAction() <\/a> { <\/a> <\/a> } <\/a>}<\/code><\/code><\/pre>\n\n\n\napp\/views\/signup\/index.phtml<\/code>):<\/p>\n\n\n\napp\/views\/signup\/index.phtml<\/code><\/a><h2>Sign up using this form<\/h2> <\/a> <\/a><?php echo $this->tag->form(\"signup\/register\"); ?> <\/a> <\/a> <p> <\/a> <label for=\"name\">Name<\/label> <\/a> <?php echo $this->tag->textField(\"name\"); ?> <\/a> <\/p> <\/a> <\/a> <p> <\/a> <label for=\"email\">E-Mail<\/label> <\/a> <?php echo $this->tag->textField(\"email\"); ?> <\/a> <\/p> <\/a> <\/a> <p> <\/a> <?php echo $this->tag->submitButton(\"Register\"); ?> <\/a> <\/p> <\/a> <\/a><\/form><\/code><\/code><\/pre>\n\n\n\n![\"\"\/](\"https:\/\/docs.phalcon.io\/4.2\/assets\/images\/content\/tutorial-basic-3.png\")
<\/figure>\n\n\n\nPhalcon\\Tag::form()<\/code> method receives only one parameter for instance, a relative URI to a controller\/action in the application. The Phalcon\\Tag::textField()<\/code> creates a text HTML element with the name as the passed parameter, while the Phalcon\\Tag::submitButton()<\/code> creates a submit HTML button.<\/p>\n\n\n\nregister<\/code> action in the controller signup<\/code>. Our public\/index.php<\/code> file throws this exception:<\/a>Exception: Action \"register\" was not found on handler \"signup\"<\/code><\/p>\n\n\n\napp\/controllers\/SignupController.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\Controller; <\/a> <\/a>class SignupController extends Controller <\/a>{ <\/a> public function indexAction() <\/a> { <\/a> <\/a> } <\/a> <\/a> public function registerAction() <\/a> { <\/a> <\/a> } <\/a>}<\/code><\/code><\/pre>\n\n\n\nCreating a Model<\/h2>\n\n\n\n
create_users_table.sql<\/code><\/a>CREATE TABLE `users` ( <\/a> `id` int(10) unsigned NOT NULL AUTO_INCREMENT, <\/a> `name` varchar(70) NOT NULL, <\/a> `email` varchar(70) NOT NULL, <\/a> <\/a> PRIMARY KEY (`id`) <\/a>);<\/code><\/code><\/pre>\n\n\n\napp\/models<\/code> directory (app\/models\/Users.php<\/code>). The model maps to the users<\/em> table:<\/p>\n\n\n\napp\/models\/Users.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\Model; <\/a> <\/a>class Users extends Model <\/a>{ <\/a> public $id; <\/a> public $name; <\/a> public $email; <\/a>}<\/code><\/code><\/pre>\n\n\n\nSetting a Database Connection\u00b6<\/a><\/h2>\n\n\n\n
public\/index.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Db\\Adapter\\Pdo\\Mysql; <\/a> <\/a>$container->set( <\/a> 'db', <\/a> function () { <\/a> return new Mysql( <\/a> [ <\/a> 'host' => '127.0.0.1', <\/a> 'username' => 'root', <\/a> 'password' => 'secret', <\/a> 'dbname' => 'tutorial', <\/a> ] <\/a> ); <\/a> } <\/a>);<\/code><\/code><\/pre>\n\n\n\nSignupController::registerAction()<\/code> that will display a message letting the user know the outcome of the save<\/em> operation.<\/p>\n\n\n\napp\/views\/signup\/register.phtml<\/code><\/a><div class=\"alert alert-<?php echo $success === true ? 'success' : 'danger'; ?>\"> <\/a> <?php echo $message; ?> <\/a><\/div> <\/a> <\/a><?php echo $this->tag->linkTo(['\/', 'Go back', 'class' => 'btn btn-primary']); ?> <\/code>Note that we have added some css styling in the code above. We will cover including the stylesheet in the Styling<\/a> section below.<\/code><\/pre>\n\n\n\nStoring Data using Models<\/h2>\n\n\n\n
app\/controllers\/SignupController.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\Controller; <\/a> <\/a>class SignupController extends Controller <\/a>{ <\/a> public function indexAction() <\/a> { <\/a> <\/a> } <\/a> <\/a> public function registerAction() <\/a> { <\/a> $user = new Users(); <\/a> <\/a> \/\/assign value from the form to $user <\/a> $user->assign( <\/a> $this->request->getPost(), <\/a> [ <\/a> 'name', <\/a> 'email' <\/a> ] <\/a> ); <\/a> <\/a> \/\/ Store and check for errors <\/a> $success = $user->save(); <\/a> <\/a> \/\/ passing the result to the view <\/a> $this->view->success = $success; <\/a> <\/a> if ($success) { <\/a> $message = \"Thanks for registering!\"; <\/a> } else { <\/a> $message = \"Sorry, the following problems were generated:<br>\" <\/a> . implode('<br>', $user->getMessages()); <\/a> } <\/a> <\/a> \/\/ passing a message to the view <\/a> $this->view->message = $message; <\/a> } <\/a>}<\/code><\/code><\/pre>\n\n\n\nregisterAction<\/code> we create an empty user object using the Users<\/code> class we created earlier. We will use this class to manage the record of a user. As mentioned above, the class’s public properties map to the fields of the users<\/code> table in our database. Setting the relevant values in the new record and calling save()<\/code> will store the data in the database for that record. The save()<\/code> method returns a boolean<\/code> value which indicates whether the save was successful or not.<\/p>\n\n\n\nsave()<\/code> method.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/docs.phalcon.io\/4.2\/assets\/images\/content\/tutorial-basic-4.png\")
<\/figure>\n\n\n\nList the Registered Users\u00b6<\/a><\/h2>\n\n\n\n
indexAction<\/code> of theIndexController<\/code> is to show the result of the search of all the users, which is done simply by calling the static method find()<\/code> on our model (Users::find()<\/code>).<\/p>\n\n\n\nindexAction<\/code> would change as follows:<\/p>\n\n\n\napp\/controllers\/IndexController.php<\/code><\/a><?php <\/a> <\/a>use Phalcon\\Mvc\\Controller; <\/a> <\/a>class IndexController extends Controller <\/a>{ <\/a> \/** <\/a> * Welcome and user list <\/a> *\/ <\/a> public function indexAction() <\/a> { <\/a> $this->view->users = Users::find(); <\/a> } <\/a>}<\/code><\/code><\/pre>\n\n\n\nfind<\/code> to a magic property on the view<\/code> object. This sets this variable with the assigned data and makes it available in our view<\/p>\n\n\n\nviews\/index\/index.phtml<\/code> we can use the $users<\/code> variable as follows:<\/p>\n\n\n\nviews\/index\/index.phtml<\/code><\/a><?php <\/a> <\/a>echo \"<h1>Hello!<\/h1>\"; <\/a> <\/a>echo $this->tag->linkTo([\"signup\", \"Sign Up Here!\", 'class' => 'btn btn-primary']); <\/a> <\/a>if ($users->count() > 0) { <\/a> ?> <\/a> <table class=\"table table-bordered table-hover\"> <\/a> <thead class=\"thead-light\"> <\/a> <tr> <\/a> <th>#<\/th> <\/a> <th>Name<\/th> <\/a> <th>Email<\/th> <\/a> <\/tr> <\/a> <\/thead> <\/a> <tfoot> <\/a> <tr> <\/a> <td colspan=\"3\">Users quantity: <?php echo $users->count(); ?><\/td> <\/a> <\/tr> <\/a> <\/tfoot> <\/a> <tbody> <\/a> <?php foreach ($users as $user) { ?> <\/a> <tr> <\/a> <td><?php echo $user->id; ?><\/td> <\/a> <td><?php echo $user->name; ?><\/td> <\/a> <td><?php echo $user->email; ?><\/td> <\/a> <\/tr> <\/a> <?php } ?> <\/a> <\/tbody> <\/a> <\/table> <\/a> <?php <\/a>}<\/code><\/code><\/pre>\n\n\n\n$users<\/code> can be iterated and counted. You can get more information on how models operate in our document about models<\/a>.<\/p>\n\n\n\n![\"\"\/](\"https:\/\/docs.phalcon.io\/4.2\/assets\/images\/content\/tutorial-basic-5.png\")
<\/figure>\n\n\n\nStyling<\/h2>\n\n\n\n
index.phtml<\/code> file in theviews<\/code> folder, with the following content:<\/p>\n\n\n\napp\/views\/index.phtml<\/code>