Wiki Follow @yiiframework

Assume we want to use a single HTML form to collect input for both model A and model B, and we want to display input errors (if any) in the same error summary box. We can define the following action code:

warning: While this security guide tries to be quite complete, is not exhaustive. If security matters for you, you ought to check several other references.

There is a lot of confusion surrounding what is happening behind the scenes when you render a view.

By default, the expression Yii::app()->user returns a CWebUser application component which represents the information that are closely related with the current user. Some information can be persistent throughout the current user session. For example, CWebUser already comes with a name property that stores the username of the current user.

In this article, we describe the directory structure used by yiiframework.com - the official Yii framework website. While this structure may look overly complicated for small projects or may not be optimal in some sense, we believe it is appropriate for medium or large projects in a team development environment. In fact, we have successfully used the similar structure in some other big projects.

Many newcomers to Yii ask about the assets/ directory found under the webroot, and this article means to explain why it's there and how to work with it.

Some times the core validation rules provided by Yii won't satisfy all your needs, so you'll need to create your very own validation rule.

Hello ppl. Even though i have a small experience with yii I though of writing this to help people which want to do something similar.

Lets say we have two models and relation between them:

If you have to display a overview of related data in a table, you can use the CListView, create your view with table/tr/td tags and implement db-queries in the view to display detaildata of the current (master-)record.