<ruby id="bdb3f"></ruby>

    <p id="bdb3f"><cite id="bdb3f"></cite></p>

      <p id="bdb3f"><cite id="bdb3f"><th id="bdb3f"></th></cite></p><p id="bdb3f"></p>
        <p id="bdb3f"><cite id="bdb3f"></cite></p>

          <pre id="bdb3f"></pre>
          <pre id="bdb3f"><del id="bdb3f"><thead id="bdb3f"></thead></del></pre>

          <ruby id="bdb3f"><mark id="bdb3f"></mark></ruby><ruby id="bdb3f"></ruby>
          <pre id="bdb3f"><pre id="bdb3f"><mark id="bdb3f"></mark></pre></pre><output id="bdb3f"></output><p id="bdb3f"></p><p id="bdb3f"></p>

          <pre id="bdb3f"><del id="bdb3f"><progress id="bdb3f"></progress></del></pre>

                <ruby id="bdb3f"></ruby>

                ThinkChat2.0新版上線,更智能更精彩,支持會話、畫圖、視頻、閱讀、搜索等,送10W Token,即刻開啟你的AI之旅 廣告
                # Tutorial 6: V?kuró V?kuró is another sample application you can use to learn more about Phalcon. V?kuró is a small website that shows how to implement a security features and management of users and permissions. You can clone its code from[Github](https://github.com/phalcon/vokuro). ## Project Structure Once you clone the project in your document root you’ll see the following structure: ~~~ vokuro/ app/ config/ controllers/ forms/ library/ models/ views/ cache/ public/ css/ img/ schemas/ ~~~ This project follows a quite similar structure to INVO. Once you open the application in your browser[http://localhost/vokuro](http://localhost/vokuro)you’ll see something like this: ![../_images/vokuro-1.png](http://docs.iphalcon.cn/_images/vokuro-1.png) The application is divided into two parts, a frontend, where visitors can sign up the service and a backend where administrative users can manage registered users. Both frontend and backend are combined in a single module. ## Load Classes and Dependencies This project uses[Phalcon\\Loader](http://docs.iphalcon.cn/api/Phalcon_Loader.html)to load controllers, models, forms, etc. within the project and[composer](https://getcomposer.org/)to load the project’s dependencies. So, the first thing you have to do before execute V?kuró is install its dependencies via[composer](https://getcomposer.org/). Assuming you have it correctly installed, type the following command in the console: ~~~ cd vokuro composer install ~~~ V?kuró sends emails to confirm the sign up of registered users using Swift, the composer.json looks like: ~~~ { "require" : { "php" : ">=5.5.0", "ext-phalcon" : ">=3.0.0", "swiftmailer/swiftmailer" : "^5.4", "amazonwebservices/aws-sdk-for-php" : "~1.0" } } ~~~ Now, there is a file called app/config/loader.php where all the auto-loading stuff is set up. At the end of this file you can see that the composer autoloader is included enabling the application to autoload any of the classes in the downloaded dependencies: ~~~ <?php // ... // Use composer autoloader to load vendor classes require_once BASE_PATH . "/vendor/autoload.php"; ~~~ Moreover, V?kuró, unlike the INVO, utilizes namespaces for controllers and models which is the recommended practice to structure a project. This way the autoloader looks slightly different than the one we saw before (app/config/loader.php): ~~~ <?php use Phalcon\Loader; $loader = new Loader(); $loader->registerNamespaces( [ "Vokuro\\Models" => $config->application->modelsDir, "Vokuro\\Controllers" => $config->application->controllersDir, "Vokuro\\Forms" => $config->application->formsDir, "Vokuro" => $config->application->libraryDir, ] ); $loader->register(); // ... ~~~ Instead of using`registerDirectories()`, we use`registerNamespaces()`. Every namespace points to a directory defined in the configuration file (app/config/config.php). For instance the namespace Vokuro\\Controllers points to app/controllers so all the classes required by the application within this namespace requires it in its definition: ~~~ <?php namespace Vokuro\Controllers; class AboutController extends ControllerBase { // ... } ~~~ ## Sign Up First, let’s check how users are registered in V?kuró. When a user clicks the “Create an Account” button, the controller SessionController is invoked and the action “signup” is executed: ~~~ <?php namespace Vokuro\Controllers; use Vokuro\Forms\SignUpForm; class RegisterController extends ControllerBase { public function signupAction() { $form = new SignUpForm(); // ... $this->view->form = $form; } } ~~~ This action simply pass a form instance of SignUpForm to the view, which itself is rendered to allow the user enter the login details: ~~~ {{ form("class": "form-search") }} <h2> Sign Up </h2> <p>{{ form.label("name") }}</p> <p> {{ form.render("name") }} {{ form.messages("name") }} </p> <p>{{ form.label("email") }}</p> <p> {{ form.render("email") }} {{ form.messages("email") }} </p> <p>{{ form.label("password") }}</p> <p> {{ form.render("password") }} {{ form.messages("password") }} </p> <p>{{ form.label("confirmPassword") }}</p> <p> {{ form.render("confirmPassword") }} {{ form.messages("confirmPassword") }} </p> <p> {{ form.render("terms") }} {{ form.label("terms") }} {{ form.messages("terms") }} </p> <p>{{ form.render("Sign Up") }}</p> {{ form.render("csrf", ["value": security.getToken()]) }} {{ form.messages("csrf") }} <hr> {{ endForm() }} ~~~
                  <ruby id="bdb3f"></ruby>

                  <p id="bdb3f"><cite id="bdb3f"></cite></p>

                    <p id="bdb3f"><cite id="bdb3f"><th id="bdb3f"></th></cite></p><p id="bdb3f"></p>
                      <p id="bdb3f"><cite id="bdb3f"></cite></p>

                        <pre id="bdb3f"></pre>
                        <pre id="bdb3f"><del id="bdb3f"><thead id="bdb3f"></thead></del></pre>

                        <ruby id="bdb3f"><mark id="bdb3f"></mark></ruby><ruby id="bdb3f"></ruby>
                        <pre id="bdb3f"><pre id="bdb3f"><mark id="bdb3f"></mark></pre></pre><output id="bdb3f"></output><p id="bdb3f"></p><p id="bdb3f"></p>

                        <pre id="bdb3f"><del id="bdb3f"><progress id="bdb3f"></progress></del></pre>

                              <ruby id="bdb3f"></ruby>

                              哎呀哎呀视频在线观看