Special Topics

Special Topics Yii 2

Content of the «Special Topics» section:

Articles section «Special Topics»:

Details: Parent Category: The Definitive Guide to Yii 2.0; Category: Special Topics

User Rating: 5 / 5

Using Yii as a Micro-framework

Yii can be easily used without the features included in basic and advanced templates. In other words, Yii is already a micro-framework. It is not required to have the directory structure provided by templates to work with Yii.

Details: Parent Category: The Definitive Guide to Yii 2.0; Category: Special Topics

User Rating: 5 / 5

Working with Third-Party Code

From time to time, you may need to use some third-party code in your Yii applications. Or you may want to use Yii as a library in some third-party systems. In this section, we will show how to achieve these goals.

Details: Parent Category: The Definitive Guide to Yii 2.0; Category: Special Topics

User Rating: 5 / 5

Using template engines

By default, Yii uses PHP as its template language, but you can configure Yii to support other rendering engines, such as Twig or Smarty available as extensions.

The view component is responsible for rendering views. You can add a custom template engine by reconfiguring this component's behavior:

Shared Hosting Environment

Shared hosting environments are often quite limited about configuration and directory structure. Still in most cases you can run Yii 2.0 on a shared hosting environment with a few adjustments.

Performance Tuning

There are many factors affecting the performance of your Web application. Some are environmental, some are related with your code, while some others are related with Yii itself. In this section, we will enumerate most of these factors and explain how you can improve your application performance by adjusting these factors.

Mailing

Note: This section is under development.

Yii supports composition and sending of the email messages. However, the framework core provides only the content composition functionality and basic interface. Actual mail sending mechanism should be provided by the extension, because different projects may require its different implementation and it usually depends on the external services and libraries.