Yii Models

Models are part of MVC structure. They represent the rules and logic for an application. Means they hold data and define the validating rules for the data.

Model classes are extended by yiibaseModel or its child classes.

Mainly following features are implemented using models.

attribute declaration
attribute labels
massive attribute assignment
scenario-based validation
can not embed HTML
can not be directly accessed

Attributes

Attributes mainly represent the business data. Each attribute is a publicly accessible property of a model. They can be accessed like array elements or normal object properties. it is like publicly accessible properties of a model.

The method,

specifies what attributes a model class has.

Model class is also the base class for ActiveRecord class (which is an advanced model with additional functionality).

Attribute as a normal object property:

  $model = new appmodelsContactForm;    // “name” is an attribute of ContactForm  $model->name = ‘example’;  echo $model->name;    Attribute as array elements:    $model = new appmodelsContactForm;    // accessing attributes like array elements  $model[‘name’] = ‘example’;  echo $model[‘name’];    // Model is traversable using foreach.  foreach ($model as $name => $value) {      echo “$name: $valuen”;  }  

In earlier versions of Yii, scenarios and validation were handled with the same function. But in Yii2, they are split into different functions i.e; rules() and scenarios().

Here, rules() specify the validation of a data while scenarios() specify which attributes are safe to be assigned to the model.

Attribute Labels

Attribute labels are values which are displayed with attributes to get the input from the users.

For example, in the below code, ID, Name, Designation, Contact and Email denotes the attribute labels. All this is defined under a function attributeLabels().

  public function attributeLabels()       {           return [               ‘id’ => ‘ID’,               ‘name’ => ‘Name’,               ‘designation’ => ‘Designation’,               ‘contact’ => ‘Contact’,               ’email’ => ‘Email’,           ];       }  

Look at the above snapshot, the heading data denotes the attribute labels.

Scenarios

A model may be used for different scenarios. For example, a model may be used to collect login user inputs while it may also be used to collect inputs of new users for registration. So in different scenarios a model may use different rules and logic.

Example

This is the ContactForm.php code,

  <?php      namespace frontendmodels;      use Yii;      use yiibaseModel;      /**      * ContactForm is the model behind the contact form.      */      class ContactForm extends Model {         public $name;         public $email;         public $subject;         public $body;         public $verifyCode;          const SCENARIO_EMAIL_FROM_GUEST = ‘EMAIL_FROM_GUEST’;         const SCENARIO_EMAIL_FROM_USER = ‘EMAIL_FROM_USER’;                public function scenarios() {            return [               self::SCENARIO_EMAIL_FROM_GUEST => [‘name’, ’email’, ‘subject’,                  ‘body’, ‘verifyCode’],               self::SCENARIO_EMAIL_FROM_USER => [‘name’, ’email’ ,’subject’, ‘body’,                  ‘verifyCode’],            ];         }         /**         * @return array the validation rules.         */         public function rules() {            return [               // name, email, subject and body are required               [[‘name’, ’email’, ‘subject’, ‘body’], ‘required’],               // email has to be a valid email address               [’email’, ’email’],               // verifyCode needs to be entered correctly               [‘verifyCode’, ‘captcha’],            ];         }         /**         * @return array customized attribute labels         */         public function attributeLabels() {            return [              ‘name’ => ‘Name’,               ’email’ => ‘Email’,               ‘subject’ => ‘Subject’,               ‘body’ => ‘Body’,               ‘verifyCode’ => ‘Verification Code’,            ];         }         /**         * Sends an email to the specified email address using the information            collected by this model.         * @param  string  $email the target email address         * @return boolean whether the model passes validation         */         public function contact($email) {            if ($this -> validate()) {               Yii::$app->mailer->compose()                  ->setTo($email)                  ->setFrom([$this->email => $this->name])                  ->setSubject($this->subject)                  ->setTextBody($this->body)                  ->send();               return true;            }            return false;         }      }   ?>  

Create an action actionContact in SiteController.php file

    public function actionContact() {      $model = new ContactForm();      $model->scenario = ContactForm::SCENARIO_EMAIL_FROM_GUEST;      if ($model->load(Yii::$app->request->post()) && $model->         contact(Yii::$app->params [‘adminEmail’])) {            Yii::$app->session->setFlash(‘contactFormSubmitted’);             return $this->refresh();      }      return $this->render(‘contact’, [         ‘model’ => $model,      ]);   }  

Now, we’ll run the program in the browser,

Now change the scenarion in actionContact in SiteController.php as

Now on running the program in the browser, Subject and Body field will be no longer required field.

Validation Rules

These are the rules which are set for the fields to be fulfilled by the users. For example, required rule will make sure that the respective field is not empty. And email attribute will make sure that the email entered is a valid email. If values do not satisfy the rules, an error message will appear on the screen.

To declare validation rules for all the fields in all the scenarios, following code is used.

  public function rules()  {      return [          // the name, email, subject and body attributes are required          [[‘name’, ’email’, ‘subject’, ‘body’], ‘required’],            // the email attribute should be a valid email address          [’email’, ’email’],      ];  }    To declare different validation rules for different scenarios, use the following code.    public function rules()  {      return [          // username, email and password are all required in “register” scenario          [[‘username’, ’email’, ‘password’, ‘d_o_b’], ‘required’, ‘on’ => self::SCENARIO_REGISTER],            // username and password are required in “login” scenario          [[‘username’, ‘password’], ‘required’, ‘on’ => self::SCENARIO_LOGIN],      ];  }  

The on property implements that, rule will be applied to a particular scenario. If you’ll not use on property than by default rule will be applied for all the fields.

Massive Assignment

In massive assignment, a model is populated with user inputs using a single line of code. Massive assignment only applies to the safe attributes.

Look at the following two types of code, both assigning the submitted form data by the end users to attributes of the ContactForm model.

First one is,

  $model = new appmodelsContactForm;  $model->attributes = Yii::$app->request->post(‘ContactForm’);  Second one is,      $model = new appmodelsContactForm;  $data = Yii::$app->request->post(‘ContactForm’, []);  $model->name = isset($data[‘name’]) ? $data[‘name’] : null;  $model->email = isset($data[’email’]) ? $data[’email’] : null;  $model->subject = isset($data[‘subject’]) ? $data[‘subject’] : null;  $model->body = isset($data[‘body’]) ? $data[‘body’] : null;  

The first one using massive assignment is much easier, neat and less error prone.

Next TopicYII Views

YII Models

Yii Models

Attributes

Attribute Labels

Scenarios

Validation Rules

Massive Assignment

XSLT Element

YII2 Installation

You may also like