Clear render_PHP tutorial in php Zend Framework
I became interested in php mvc when using asp.net mvc. I looked at Zend Framework (hereinafter referred to as ZF) and I can compare and understand mvc. I was confused about a relatively core function render for a while. Record the clarification process
Usually when we use ZF to implement PHP's mvc, the most critical place is of course the various action methods of the Controller class. In the action method, we determine and output the content. In the dispatch method in the abstract class Zend_Controller_Action, you can Found this line $this->$action();
Then how to determine and output the content is to render, but there are several renders. These situations are listed below
1
2class IndexController extends Zend_Controller_Action
3{
4 public function contactAction()
5 {
6 //$this->render("index");
7 //$this->render();
8 //$this->renderScript("sidebar.phtml");
9
10
11 //$this->_helper->viewRenderer("sidebar");
12
13 //$this->view->render("sidebar.phtml");
14 //$this->view("sidebar");
15
16}
17}
18?>
To sum up, it seems that these are the three renders (welcome additions)
1. Self render
Look at the first type first
//$this->render("index");
//$this->render();
//$this->renderScript("sidebar.phtml");
This is directly using the render method of the Zend_Controller_Action class
The first sentence is to render the view corresponding to another action (see clearly that it is to render the view corresponding to that action, not to execute that action!)
The second sentence renders the view corresponding to this action. What is the meaning of this (because in many cases you cannot see this writing), we will discuss this below.
The third sentence is a render-specific view file. Here you may think that the first two methods actually call this renderScript, but this is not the case.
Let’s explain it below. By the way, explain the reason for the second sentence.
There are actually two branches in the render method of the Zend_Controller_Action class. The render function code is as follows
1 public function render($action = null, $name = null, $noController = false)
2 {
3 if (!$this->getInvokeArg('noViewRenderer') && $this->_helper->hasHelper('viewRenderer')) {
4 return $this->_helper->viewRenderer->render($action, $name, $noController);
5}
6
7 $view = $this->initView();
8 $script = $this->getViewScript($action, $noController);
9
10 $this->getResponse()->appendBody(
11 $view->render($script),
12 $name
13);
14}
You can see that one situation is to use (proxy) the render method of the view assistant class (viewRenderer)
The other situation is when the assistant is disabled, you have to do it yourself. This is why render() appears. After you disable the view assistant, you can use render() to output the view content corresponding to this action.
2. Through the view assistant viewRenderer
We talked about the view assistant above, let’s look at the second fragment in the action, which is done with the help of the view assistant
//$this->_helper->viewRenderer("sidebar");
In fact, this sentence here is not the render content, but specifies which view to render. Refer to this function of the Zend_Controller_Action_Helper_ViewRenderer class
1 public function direct($action = null, $name = null, $noController = null)
2 {
3 $this->setRender($action, $name, $noController);
4}
So what about the output? How is it output?
You can call $this->render(); directly after $this->_helper->viewRenderer("sidebar");.
But actually you don’t need to call it at all, just write that sentence.
When you don’t write render, the view assistant will do it for you. There is such a sentence in the dispatch method in the Zend_Controller_Action class
$this->_helper->notifyPostDispatch();
What is _helper? It is a Zend_Controller_Action_HelperBroker class, which has this method
1 public function notifyPostDispatch()
2 {
3 foreach (self::getStack() as $helper) {
4 $helper->postDispatch();
5}
6}
You can see that postDispatch() of each assistant is called;
The viewRenderer is one of its assistants, and its postDispatch method is as follows
1 public function postDispatch()
2 {
3 if ($this->_shouldRender()) {
4 $this->render();
5}
6}
It is here that the view assistant helps you render. If you render it yourself, the smart view assistant will know it. You can check the $this->getRequest()->isDispatched() in _shouldRender() ), and this sentence of the dispatch method in the Zend_Controller_Front class: $this->_request->setDispatched(true);
- Total 2 pages:
- Previous page
- 1
- 2
- Next page

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

PHP 8.4 brings several new features, security improvements, and performance improvements with healthy amounts of feature deprecations and removals. This guide explains how to install PHP 8.4 or upgrade to PHP 8.4 on Ubuntu, Debian, or their derivati

If you are an experienced PHP developer, you might have the feeling that you’ve been there and done that already.You have developed a significant number of applications, debugged millions of lines of code, and tweaked a bunch of scripts to achieve op

Visual Studio Code, also known as VS Code, is a free source code editor — or integrated development environment (IDE) — available for all major operating systems. With a large collection of extensions for many programming languages, VS Code can be c

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

A string is a sequence of characters, including letters, numbers, and symbols. This tutorial will learn how to calculate the number of vowels in a given string in PHP using different methods. The vowels in English are a, e, i, o, u, and they can be uppercase or lowercase. What is a vowel? Vowels are alphabetic characters that represent a specific pronunciation. There are five vowels in English, including uppercase and lowercase: a, e, i, o, u Example 1 Input: String = "Tutorialspoint" Output: 6 explain The vowels in the string "Tutorialspoint" are u, o, i, a, o, i. There are 6 yuan in total

This tutorial demonstrates how to efficiently process XML documents using PHP. XML (eXtensible Markup Language) is a versatile text-based markup language designed for both human readability and machine parsing. It's commonly used for data storage an

Static binding (static::) implements late static binding (LSB) in PHP, allowing calling classes to be referenced in static contexts rather than defining classes. 1) The parsing process is performed at runtime, 2) Look up the call class in the inheritance relationship, 3) It may bring performance overhead.

What are the magic methods of PHP? PHP's magic methods include: 1.\_\_construct, used to initialize objects; 2.\_\_destruct, used to clean up resources; 3.\_\_call, handle non-existent method calls; 4.\_\_get, implement dynamic attribute access; 5.\_\_set, implement dynamic attribute settings. These methods are automatically called in certain situations, improving code flexibility and efficiency.
