|
|
|
输入验证
|
|
|
|
================
|
|
|
|
|
|
|
|
一般说来,程序猿永远不应该信任从最终用户直接接收到的数据,
|
|
|
|
并且使用它们之前应始终先验证其可靠性。
|
|
|
|
|
|
|
|
要给 [model](structure-models.md) 填充其所需的用户输入数据,你可以调用 [[yii\base\Model::validate()]]
|
|
|
|
方法验证它们。该方法会返回一个布尔值,指明是否通过验证。若没有通过,你能通过 [[yii\base\Model::errors]]
|
|
|
|
属性获取相应的报错信息。比如,
|
|
|
|
|
|
|
|
```php
|
|
|
|
$model = new \app\models\ContactForm();
|
|
|
|
|
|
|
|
// populate model attributes with user inputs
|
|
|
|
$model->load(\Yii::$app->request->post());
|
|
|
|
// which is equivalent to the following:
|
|
|
|
// $model->attributes = \Yii::$app->request->post('ContactForm');
|
|
|
|
|
|
|
|
if ($model->validate()) {
|
|
|
|
// all inputs are valid
|
|
|
|
} else {
|
|
|
|
// validation failed: $errors is an array containing error messages
|
|
|
|
$errors = $model->errors;
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
## 声明规则(Rules) <span id="declaring-rules"></span>
|
|
|
|
|
|
|
|
要让 `validate()` 方法起作用,你需要声明与需验证模型特性相关的验证规则。
|
|
|
|
为此,需要重写 [[yii\base\Model::rules()]] 方法。下面的例子展示了如何
|
|
|
|
声明用于验证 `ContactForm` 模型的相关验证规则:
|
|
|
|
|
|
|
|
```php
|
|
|
|
public function rules()
|
|
|
|
{
|
|
|
|
return [
|
|
|
|
// name,email,subject 和 body 特性是 `require`(必填)的
|
|
|
|
[['name', 'email', 'subject', 'body'], 'required'],
|
|
|
|
|
|
|
|
// email 特性必须是一个有效的 email 地址
|
|
|
|
['email', 'email'],
|
|
|
|
];
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
[[yii\base\Model::rules()|rules()]] 方法应返回一个由规则所组成的数组,
|
|
|
|
每一个规则都呈现为以下这类格式的小数组:
|
|
|
|
|
|
|
|
```php
|
|
|
|
[
|
|
|
|
// required, specifies which attributes should be validated by this rule.
|
|
|
|
// For a single attribute, you can use the attribute name directly
|
|
|
|
// without having it in an array
|
|
|
|
['attribute1', 'attribute2', ...],
|
|
|
|
|
|
|
|
// required, specifies the type of this rule.
|
|
|
|
// It can be a class name, validator alias, or a validation method name
|
|
|
|
'validator',
|
|
|
|
|
|
|
|
// optional, specifies in which scenario(s) this rule should be applied
|
|
|
|
// if not given, it means the rule applies to all scenarios
|
|
|
|
// You may also configure the "except" option if you want to apply the rule
|
|
|
|
// to all scenarios except the listed ones
|
|
|
|
'on' => ['scenario1', 'scenario2', ...],
|
|
|
|
|
|
|
|
// optional, specifies additional configurations for the validator object
|
|
|
|
'property1' => 'value1', 'property2' => 'value2', ...
|
|
|
|
]
|
|
|
|
```
|
|
|
|
|
|
|
|
对于每个规则,你至少需要指定该规则适用于哪些特性,以及本规则的类型是什么。
|
|
|
|
你可以指定以下的规则类型之一:
|
|
|
|
|
|
|
|
* 核心验证器的昵称,比如 `required`、`in`、`date`,等等。请参考
|
|
|
|
[核心验证器](tutorial-core-validators.md)章节查看完整的核心验证器列表。
|
|
|
|
* 模型类中的某个验证方法的名称,或者一个匿名方法。
|
|
|
|
请参考[行内验证器](#inline-validators)小节了解更多。
|
|
|
|
* 验证器类的名称。
|
|
|
|
请参考[独立验证器](#standalone-validators)小节了解更多。
|
|
|
|
|
|
|
|
一个规则可用于验证一个或多个模型特性,且一个特性可以被一个或多个规则所验证。
|
|
|
|
一个规则可以施用于特定[场景(scenario)](structure-models.md#scenarios),只
|
|
|
|
要指定 `on` 选项。如果你不指定 `on` 选项,那么该规则会适配于所有场景。
|
|
|
|
|
|
|
|
当调用 `validate()` 方法时,它将运行以下几个具体的验证步骤:
|
|
|
|
|
|
|
|
1. 检查从声明自 [[yii\base\Model::scenarios()]] 方法的场景中所挑选出的当前[[yii\base\Model::scenario|场景]]的信息,
|
|
|
|
从而确定出那些特性需要被验证。这些特性被称为激活特性。
|
|
|
|
2. 检查从声明自 [[yii\base\Model::rules()]] 方法的众多规则中所挑选出的适用于当前[[yii\base\Model::scenario|场景]]的规则,
|
|
|
|
从而确定出需要验证哪些规则。这些规则被称为激活规则。
|
|
|
|
3. 用每个激活规则去验证每个
|
|
|
|
与之关联的激活特性。
|
|
|
|
|
|
|
|
基于以上验证步骤,有且仅有声明在 `scenarios()`
|
|
|
|
方法里的激活特性,且它还必须与一或多个声明自
|
|
|
|
`rules()` 里的激活规则相关联才会被验证。
|
|
|
|
|
|
|
|
> Note: It is handy to give names to rules i.e.
|
|
|
|
> ```php
|
|
|
|
> public function rules()
|
|
|
|
> {
|
|
|
|
> return [
|
|
|
|
> // ...
|
|
|
|
> 'password' => [['password'], 'string', 'max' => 60],
|
|
|
|
> ];
|
|
|
|
> }
|
|
|
|
> ```
|
|
|
|
>
|
|
|
|
> You can use it in a child model:
|
|
|
|
>
|
|
|
|
> ```php
|
|
|
|
> public function rules()
|
|
|
|
> {
|
|
|
|
> $rules = parent::rules();
|
|
|
|
> unset($rules['password']);
|
|
|
|
> return $rules;
|
|
|
|
> }
|
|
|
|
|
|
|
|
|
|
|
|
### 自定义错误信息 <span id="customizing-error-messages"></span>
|
|
|
|
|
|
|
|
大多数的验证器都有默认的错误信息,当模型的某个特性验证失败的时候,该错误信息会被返回给模型。
|
|
|
|
比如,用 [[yii\validators\RequiredValidator|required]] 验证器的规则检验 `username`
|
|
|
|
特性失败的话,会返还给模型 "Username cannot be blank." 信息。
|
|
|
|
|
|
|
|
你可以通过在声明规则的时候同时指定 `message` 属性,
|
|
|
|
来定制某个规则的错误信息,比如这样:
|
|
|
|
|
|
|
|
```php
|
|
|
|
public function rules()
|
|
|
|
{
|
|
|
|
return [
|
|
|
|
['username', 'required', 'message' => 'Please choose a username.'],
|
|
|
|
];
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
一些验证器还支持用于针对不同原因的验证失败返回更加准确的额外错误信息。比如,[[yii\validators\NumberValidator|number]]
|
|
|
|
验证器就支持 [[yii\validators\NumberValidator::tooBig|tooBig]] 和 [[yii\validators\NumberValidator::tooSmall|tooSmall]]
|
|
|
|
两种错误消息用于分别返回输入值是太大还是太小。你也可以像配置验证器的
|
|
|
|
其他属性一样配置它们俩各自的错误信息。
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### 验证事件 <span id="validation-events"></span>
|
|
|
|
|
|
|
|
当调用 [[yii\base\Model::validate()]] 方法的过程里,它同时会调用两个特殊的方法,
|
|
|
|
把它们重写掉可以实现自定义验证过程的目的:
|
|
|
|
|
|
|
|
* [[yii\base\Model::beforeValidate()]]:在默认的实现中会触发 [[yii\base\Model::EVENT_BEFORE_VALIDATE]] 事件。
|
|
|
|
你可以重写该方法或者响应此事件,来在验证开始之前,先进行一些预处理的工作。
|
|
|
|
(比如,标准化数据输入)该方法应该返回一个布尔值,用于标明验证是否通过。
|
|
|
|
* [[yii\base\Model::afterValidate()]]:在默认的实现中会触发 [[yii\base\Model::EVENT_AFTER_VALIDATE]] 事件。
|
|
|
|
你可以重写该方法或者响应此事件,来在验证结束之后,
|
|
|
|
再进行一些收尾的工作。
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### 条件式验证 <span id="conditional-validation"></span>
|
|
|
|
|
|
|
|
若要只在某些条件满足时,才验证相关特性,比如:是否验证某特性取决于另一特性的值,
|
|
|
|
你可以通过[[yii\validators\Validator::when|when]]
|
|
|
|
属性来定义相关条件。举例而言,
|
|
|
|
|
|
|
|
```php
|
|
|
|
['state', 'required', 'when' => function($model) {
|
|
|
|
return $model->country == 'USA';
|
|
|
|
}]
|
|
|
|
```
|
|
|
|
|
|
|
|
[[yii\validators\Validator::when|when]] 属性会读入一个如下所示结构的 PHP callable 函数对象:
|
|
|
|
|
|
|
|
```php
|
|
|
|
/**
|
|
|
|
* @param Model $model 要验证的模型对象
|
|
|
|
* @param string $attribute 待测特性名
|
|
|
|
* @return bool 返回是否启用该规则
|
|
|
|
*/
|
|
|
|
function ($model, $attribute)
|
|
|
|
```
|
|
|
|
|
|
|
|
若你需要支持客户端的条件验证,你应该配置[[yii\validators\Validator::whenClient|whenClient]] 属性,
|
|
|
|
它会读入一条包含有 JavaScript 函数的字符串。
|
|
|
|
这个函数将被用于确定该客户端验证规则是否被启用。比如,
|
|
|
|
|
|
|
|
```php
|
|
|
|
['state', 'required', 'when' => function ($model) {
|
|
|
|
return $model->country == 'USA';
|
|
|
|
}, 'whenClient' => "function (attribute, value) {
|
|
|
|
return $('#country').value == 'USA';
|
|
|
|
}"]
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
### 数据预处理 <span id="data-filtering"></span>
|
|
|
|
|
|
|
|
用户输入经常需要进行数据过滤,或者叫预处理。比如你可能会需要先去掉 `username` 输入的收尾空格。
|
|
|
|
你可以通过使用验证规则来实现此目的。
|
|
|
|
|
|
|
|
下面的例子展示了如何去掉输入信息的首尾空格,并将空输入返回为 null。具体方法为通过调用
|
|
|
|
[trim](tutorial-core-validators.md#trim) 和 [default](tutorial-core-validators.md#default) 核心验证器:
|
|
|
|
|
|
|
|
```php
|
|
|
|
return [
|
|
|
|
[['username', 'email'], 'trim'],
|
|
|
|
[['username', 'email'], 'default'],
|
|
|
|
];
|
|
|
|
```
|
|
|
|
|
|
|
|
也还可以用更加通用的 [filter(滤镜)](tutorial-core-validators.md#filter)
|
|
|
|
核心验证器来执行更加复杂的数据过滤。
|
|
|
|
|
|
|
|
如你所见,这些验证规则并不真的对输入数据进行任何验证。而是,对输入数据进行一些处理,
|
|
|
|
然后把它们存回当前被验证的模型特性。
|
|
|
|
|
|
|
|
|
|
|
|
### 处理空输入 <span id="handling-empty-inputs"></span>
|
|
|
|
|
|
|
|
当输入数据是通过 HTML 表单,你经常会需要给空的输入项赋默认值。你可以通过调整
|
|
|
|
[default](tutorial-core-validators.md#default) 验证器来实现这一点。举例来说,
|
|
|
|
|
|
|
|
```php
|
|
|
|
return [
|
|
|
|
// 若 "username" 和 "email" 为空,则设为 null
|
|
|
|
[['username', 'email'], 'default'],
|
|
|
|
|
|
|
|
// 若 "level" 为空,则设其为 1
|
|
|
|
['level', 'default', 'value' => 1],
|
|
|
|
];
|
|
|
|
```
|
|
|
|
|
|
|
|
默认情况下,当输入项为空字符串,空数组,或 null 时,会被视为“空值”。
|
|
|
|
你也可以通过配置[[yii\validators\Validator::isEmpty]]
|
|
|
|
属性来自定义空值的判定规则。比如,
|
|
|
|
|
|
|
|
```php
|
|
|
|
['agree', 'required', 'isEmpty' => function ($value) {
|
|
|
|
return empty($value);
|
|
|
|
}]
|
|
|
|
```
|
|
|
|
|
|
|
|
> Note: 对于绝大多数验证器而言,若其 [[yii\base\Validator::skipOnEmpty]] 属性为默认值
|
|
|
|
true,则它们不会对空值进行任何处理。也就是当他们的关联特性接收到空值时,相关验证会被直接略过。在
|
|
|
|
[核心验证器](tutorial-core-validators.md) 之中,只有 `captcha`(验证码),`default`(默认值),
|
|
|
|
`filter`(滤镜),`required`(必填),以及 `trim`(去首尾空格),这几个验证器会处理空输入。
|
|
|
|
|
|
|
|
|
|
|
|
## 临时验证 <span id="ad-hoc-validation"></span>
|
|
|
|
|
|
|
|
有时,你需要对某些没有绑定任何模型类的值进行 **临时验证**。
|
|
|
|
|
|
|
|
若你只需要进行一种类型的验证 (e.g. 验证邮箱地址),你可以调用所需验证器的
|
|
|
|
[[yii\validators\Validator::validate()|validate()]] 方法。像这样:
|
|
|
|
|
|
|
|
```php
|
|
|
|
$email = 'test@example.com';
|
|
|
|
$validator = new yii\validators\EmailValidator();
|
|
|
|
|
|
|
|
if ($validator->validate($email, $error)) {
|
|
|
|
echo '有效的 Email 地址。';
|
|
|
|
} else {
|
|
|
|
echo $error;
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
> Note: 不是所有的验证器都支持这种形式的验证。比如 [unique(唯一性)](tutorial-core-validators.md#unique)核心验证器就就是一个例子,
|
|
|
|
它的设计初衷就是只作用于模型类内部的。
|
|
|
|
|
|
|
|
若你需要针对一系列值执行多项验证,你可以使用 [[yii\base\DynamicModel]]
|
|
|
|
。它支持即时添加特性和验证规则的定义。它的使用规则是这样的:
|
|
|
|
|
|
|
|
```php
|
|
|
|
public function actionSearch($name, $email)
|
|
|
|
{
|
|
|
|
$model = DynamicModel::validateData(compact('name', 'email'), [
|
|
|
|
[['name', 'email'], 'string', 'max' => 128],
|
|
|
|
['email', 'email'],
|
|
|
|
]);
|
|
|
|
|
|
|
|
if ($model->hasErrors()) {
|
|
|
|
// 验证失败
|
|
|
|
} else {
|
|
|
|
// 验证成功
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
[[yii\base\DynamicModel::validateData()]] 方法会创建一个 `DynamicModel` 的实例对象,
|
|
|
|
并通过给定数据定义模型特性(以 `name` 和 `email` 为例),
|
|
|
|
之后用给定规则调用[[yii\base\Model::validate()]] 方法。
|
|
|
|
|
|
|
|
除此之外呢,你也可以用如下的更加“传统”的语法来执行临时数据验证:
|
|
|
|
|
|
|
|
```php
|
|
|
|
public function actionSearch($name, $email)
|
|
|
|
{
|
|
|
|
$model = new DynamicModel(compact('name', 'email'));
|
|
|
|
$model->addRule(['name', 'email'], 'string', ['max' => 128])
|
|
|
|
->addRule('email', 'email')
|
|
|
|
->validate();
|
|
|
|
|
|
|
|
if ($model->hasErrors()) {
|
|
|
|
// 验证失败
|
|
|
|
} else {
|
|
|
|
// 验证成功
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
验证之后你可以通过调用 [[yii\base\DynamicModel::hasErrors()|hasErrors()]]
|
|
|
|
方法来检查验证通过与否,并通过 [[yii\base\DynamicModel::errors|errors]]
|
|
|
|
属性获得验证的错误信息,过程与普通模型类一致。
|
|
|
|
你也可以访问模型对象内定义的动态特性,就像:
|
|
|
|
`$model->name` 和 `$model->email`。
|
|
|
|
|
|
|
|
|
|
|
|
## 创建验证器(Validators) <span id="creating-validators"></span>
|
|
|
|
|
|
|
|
除了使用 Yii 的发布版里所包含的[核心验证器](tutorial-core-validators.md)之外,你也可以创建你自己的验证器。
|
|
|
|
自定义的验证器可以是**行内验证器**,也可以是**独立验证器**。
|
|
|
|
|
|
|
|
|
|
|
|
### 行内验证器(Inline Validators) <span id="inline-validators"></span>
|
|
|
|
|
|
|
|
行内验证器是一种以模型方法或匿名函数的形式定义的验证器。
|
|
|
|
这些方法/函数的结构如下:
|
|
|
|
|
|
|
|
```php
|
|
|
|
/**
|
|
|
|
* @param string $attribute 当前被验证的特性
|
|
|
|
* @param array $params 以名-值对形式提供的额外参数
|
|
|
|
*/
|
|
|
|
function ($attribute, $params)
|
|
|
|
```
|
|
|
|
|
|
|
|
若某特性的验证失败了,该方法/函数应该调用 [[yii\base\Model::addError()]] 保存错误信息到模型内。
|
|
|
|
这样这些错误就能在之后的操作中,被读取并展现给终端用户。
|
|
|
|
|
|
|
|
下面是一些例子:
|
|
|
|
|
|
|
|
```php
|
|
|
|
use yii\base\Model;
|
|
|
|
|
|
|
|
class MyForm extends Model
|
|
|
|
{
|
|
|
|
public $country;
|
|
|
|
public $token;
|
|
|
|
|
|
|
|
public function rules()
|
|
|
|
{
|
|
|
|
return [
|
|
|
|
// an inline validator defined as the model method validateCountry()
|
|
|
|
['country', 'validateCountry'],
|
|
|
|
|
|
|
|
// an inline validator defined as an anonymous function
|
|
|
|
['token', function ($attribute, $params) {
|
|
|
|
if (!ctype_alnum($this->$attribute)) {
|
|
|
|
$this->addError($attribute, 'The token must contain letters or digits.');
|
|
|
|
}
|
|
|
|
}],
|
|
|
|
];
|
|
|
|
}
|
|
|
|
|
|
|
|
public function validateCountry($attribute, $params)
|
|
|
|
{
|
|
|
|
if (!in_array($this->$attribute, ['USA', 'Web'])) {
|
|
|
|
$this->addError($attribute, 'The country must be either "USA" or "Web".');
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
> Note: 缺省状态下,行内验证器不会在关联特性的输入值为空或该特性已经在其他验证中失败的情况下起效。
|
|
|
|
若你想要确保该验证器始终启用的话,你可以在定义规则时,酌情将
|
|
|
|
[[yii\validators\Validator::skipOnEmpty|skipOnEmpty]] 以及
|
|
|
|
[[yii\validators\Validator::skipOnError|skipOnError]]属性设为 false,比如,
|
|
|
|
>
|
|
|
|
> ```php
|
|
|
|
> [
|
|
|
|
> ['country', 'validateCountry', 'skipOnEmpty' => false, 'skipOnError' => false],
|
|
|
|
> ]
|
|
|
|
> ```
|
|
|
|
|
|
|
|
|
|
|
|
### 独立验证器(Standalone Validators) <span id="standalone-validators"></span>
|
|
|
|
|
|
|
|
独立验证器是继承自 [[yii\validators\Validator]] 或其子类的类。你可以通过重写
|
|
|
|
[[yii\validators\Validator::validateAttribute()]] 来实现它的验证规则。若特性验证失败,可以调用
|
|
|
|
[[yii\base\Model::addError()]] 以保存错误信息到模型内,
|
|
|
|
操作与 [inline validators](#inline-validators) 所需操作完全一样。比如,
|
|
|
|
|
|
|
|
|
|
|
|
For example the inline validator above could be moved into new [[components/validators/CountryValidator]] class.
|
|
|
|
|
|
|
|
```php
|
|
|
|
namespace app\components;
|
|
|
|
|
|
|
|
use yii\validators\Validator;
|
|
|
|
|
|
|
|
class CountryValidator extends Validator
|
|
|
|
{
|
|
|
|
public function validateAttribute($model, $attribute)
|
|
|
|
{
|
|
|
|
if (!in_array($model->$attribute, ['USA', 'Web'])) {
|
|
|
|
$this->addError($model, $attribute, 'The country must be either "USA" or "Web".');
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
若你想要验证器支持不使用 model 的数据验证,你还应该重写[[yii\validators\Validator::validate()]] 方法。
|
|
|
|
你也可以通过重写[[yii\validators\Validator::validateValue()]] 方法替代
|
|
|
|
`validateAttribute()` 和 `validate()`,因为默认状态下,
|
|
|
|
后两者的实现使用过调用`validateValue()`实现的。
|
|
|
|
|
|
|
|
Below is an example of how you could use the above validator class within your model.
|
|
|
|
|
|
|
|
```php
|
|
|
|
namespace app\models;
|
|
|
|
|
|
|
|
use Yii;
|
|
|
|
use yii\base\Model;
|
|
|
|
use app\components\validators\CountryValidator;
|
|
|
|
|
|
|
|
class EntryForm extends Model
|
|
|
|
{
|
|
|
|
public $name;
|
|
|
|
public $email;
|
|
|
|
public $country;
|
|
|
|
|
|
|
|
public function rules()
|
|
|
|
{
|
|
|
|
return [
|
|
|
|
[['name', 'email'], 'required'],
|
|
|
|
['country', CountryValidator::className()],
|
|
|
|
['email', 'email'],
|
|
|
|
];
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
## 客户端验证器(Client-Side Validation) <span id="client-side-validation"></span>
|
|
|
|
|
|
|
|
当终端用户通过 HTML 表单提供相关输入信息时,我们可能会需要用到基于 JavaScript 的客户端验证。
|
|
|
|
因为,它可以让用户更快速的得到错误信息,也因此可以提供更好的用户体验。
|
|
|
|
你可以使用或自己实现除服务器端验证之外,**还能额外**客户端验证功能的验证器。
|
|
|
|
|
|
|
|
> Info: 尽管客户端验证为加分项,但它不是必须项。它存在的主要意义在于给用户提供更好的客户体验。
|
|
|
|
正如“永远不要相信来自终端用户的输入信息”,也同样永远不要相信客户端验证。基于这个理由,
|
|
|
|
你应该始终如前文所描述的那样,通过调用 [[yii\base\Model::validate()]]
|
|
|
|
方法执行服务器端验证。
|
|
|
|
|
|
|
|
|
|
|
|
### 使用客户端验证 <span id="using-client-side-validation"></span>
|
|
|
|
|
|
|
|
许多[核心验证器](tutorial-core-validators.md)都支持开箱即用的客户端验证。你只需要用 [[yii\widgets\ActiveForm]]
|
|
|
|
的方式构建 HTML 表单即可。比如,下面的 `LoginForm`(登录表单)声明了两个规则:其一为 [required](tutorial-core-validators.md#required)
|
|
|
|
核心验证器,它同时支持客户端与服务器端的验证;另一个则采用
|
|
|
|
`validatePassword` 行内验证器,它只支持服务器端。
|
|
|
|
|
|
|
|
|
|
|
|
```php
|
|
|
|
namespace app\models;
|
|
|
|
|
|
|
|
use yii\base\Model;
|
|
|
|
use app\models\User;
|
|
|
|
|
|
|
|
class LoginForm extends Model
|
|
|
|
{
|
|
|
|
public $username;
|
|
|
|
public $password;
|
|
|
|
|
|
|
|
public function rules()
|
|
|
|
{
|
|
|
|
return [
|
|
|
|
// username 和 password 都是必填项
|
|
|
|
[['username', 'password'], 'required'],
|
|
|
|
|
|
|
|
// 用 validatePassword() 验证 password
|
|
|
|
['password', 'validatePassword'],
|
|
|
|
];
|
|
|
|
}
|
|
|
|
|
|
|
|
public function validatePassword()
|
|
|
|
{
|
|
|
|
$user = User::findByUsername($this->username);
|
|
|
|
|
|
|
|
if (!$user || !$user->validatePassword($this->password)) {
|
|
|
|
$this->addError('password', 'Incorrect username or password.');
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
使用如下代码构建的 HTML 表单包含两个输入框 `username` 以及 `password`。
|
|
|
|
如果你在没有输入任何东西之前提交表单,就会在没有任何与服务器端的通讯的情况下,
|
|
|
|
立刻收到一个要求你填写空白项的错误信息。
|
|
|
|
|
|
|
|
```php
|
|
|
|
<?php $form = yii\widgets\ActiveForm::begin(); ?>
|
|
|
|
<?= $form->field($model, 'username') ?>
|
|
|
|
<?= $form->field($model, 'password')->passwordInput() ?>
|
|
|
|
<?= Html::submitButton('Login') ?>
|
|
|
|
<?php yii\widgets\ActiveForm::end(); ?>
|
|
|
|
```
|
|
|
|
|
|
|
|
幕后的运作过程是这样的:[[yii\widgets\ActiveForm]] 会读取声明在模型类中的验证规则,
|
|
|
|
并生成那些支持支持客户端验证的验证器所需的 JavaScript 代码。当用户修改输入框的值,
|
|
|
|
或者提交表单时,就会触发相应的客户端验证 JS 代码。
|
|
|
|
|
|
|
|
若你需要完全关闭客户端验证,你只需配置
|
|
|
|
[[yii\widgets\ActiveForm::enableClientValidation]]
|
|
|
|
属性为 false。你同样可以关闭各个输入框各自的客户端验证,
|
|
|
|
只要把它们的 [[yii\widgets\ActiveField::enableClientValidation]]
|
|
|
|
属性设为 false。
|
|
|
|
|
|
|
|
|
|
|
|
### 自己实现客户端验证 <span id="implementing-client-side-validation"></span>
|
|
|
|
|
|
|
|
要创建一个支持客户端验证的验证器,你需要实现
|
|
|
|
[[yii\validators\Validator::clientValidateAttribute()]] 方法,
|
|
|
|
用于返回一段用于运行客户端验证的 JavaScript 代码。
|
|
|
|
在这段 JavaScript 代码中,你可以使用以下预定义的变量:
|
|
|
|
|
|
|
|
- `attribute`:正在被验证的模型特性的名称。
|
|
|
|
- `value`:进行验证的值。
|
|
|
|
- `messages`:一个用于暂存模型特性的报错信息的数组。
|
|
|
|
- `deferred`: an array which deferred objects can be pushed into (explained in the next subsection).
|
|
|
|
|
|
|
|
在下面的例子里,我们会创建一个 `StatusValidator`,它会通过比对现有的状态数据,
|
|
|
|
验证输入值是否为一个有效的状态。该验证器同时支持客户端以及服务器端验证。
|
|
|
|
|
|
|
|
```php
|
|
|
|
namespace app\components;
|
|
|
|
|
|
|
|
use yii\validators\Validator;
|
|
|
|
use app\models\Status;
|
|
|
|
|
|
|
|
class StatusValidator extends Validator
|
|
|
|
{
|
|
|
|
public function init()
|
|
|
|
{
|
|
|
|
parent::init();
|
|
|
|
$this->message = '无效的状态输入。';
|
|
|
|
}
|
|
|
|
|
|
|
|
public function validateAttribute($model, $attribute)
|
|
|
|
{
|
|
|
|
$value = $model->$attribute;
|
|
|
|
if (!Status::find()->where(['id' => $value])->exists()) {
|
|
|
|
$model->addError($attribute, $this->message);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
public function clientValidateAttribute($model, $attribute, $view)
|
|
|
|
{
|
|
|
|
$statuses = json_encode(Status::find()->select('id')->asArray()->column());
|
|
|
|
$message = json_encode($this->message);
|
|
|
|
return <<<JS
|
|
|
|
if ($.inArray(value, $statuses) === -1) {
|
|
|
|
messages.push($message);
|
|
|
|
}
|
|
|
|
JS;
|
|
|
|
}
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
> Tip: 上述代码主要是演示了如何支持客户端验证。在具体实践中,
|
|
|
|
> 你可以使用 [in](tutorial-core-validators.md#in) 核心验证器来达到同样的目的。
|
|
|
|
> 比如这样的验证规则:
|
|
|
|
>
|
|
|
|
> ```php
|
|
|
|
> [
|
|
|
|
> ['status', 'in', 'range' => Status::find()->select('id')->asArray()->column()],
|
|
|
|
> ]
|
|
|
|
> ```
|
|
|
|
|
|
|
|
> Tip: If you need to work with client validation manually i.e. dynamically add fields or do some custom UI logic, refer
|
|
|
|
> to [Working with ActiveForm via JavaScript](https://github.com/samdark/yii2-cookbook/blob/master/book/forms-activeform-js.md)
|
|
|
|
> in Yii 2.0 Cookbook.
|
|
|
|
|
|
|
|
### Deferred Validation <span id="deferred-validation"></span>
|
|
|
|
|
|
|
|
If you need to perform asynchronous client-side validation, you can create [Deferred objects](http://api.jquery.com/category/deferred-object/).
|
|
|
|
For example, to perform a custom AJAX validation, you can use the following code:
|
|
|
|
|
|
|
|
```php
|
|
|
|
public function clientValidateAttribute($model, $attribute, $view)
|
|
|
|
{
|
|
|
|
return <<<JS
|
|
|
|
deferred.push($.get("/check", {value: value}).done(function(data) {
|
|
|
|
if ('' !== data) {
|
|
|
|
messages.push(data);
|
|
|
|
}
|
|
|
|
}));
|
|
|
|
JS;
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
In the above, the `deferred` variable is provided by Yii, which is an array of Deferred objects. The `$.get()`
|
|
|
|
jQuery method creates a Deferred object which is pushed to the `deferred` array.
|
|
|
|
|
|
|
|
You can also explicitly create a Deferred object and call its `resolve()` method when the asynchronous callback
|
|
|
|
is hit. The following example shows how to validate the dimensions of an uploaded image file on the client side.
|
|
|
|
|
|
|
|
```php
|
|
|
|
public function clientValidateAttribute($model, $attribute, $view)
|
|
|
|
{
|
|
|
|
return <<<JS
|
|
|
|
var def = $.Deferred();
|
|
|
|
var img = new Image();
|
|
|
|
img.onload = function() {
|
|
|
|
if (this.width > 150) {
|
|
|
|
messages.push('Image too wide!!');
|
|
|
|
}
|
|
|
|
def.resolve();
|
|
|
|
}
|
|
|
|
var reader = new FileReader();
|
|
|
|
reader.onloadend = function() {
|
|
|
|
img.src = reader.result;
|
|
|
|
}
|
|
|
|
reader.readAsDataURL(file);
|
|
|
|
|
|
|
|
deferred.push(def);
|
|
|
|
JS;
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
> Note: The `resolve()` method must be called after the attribute has been validated. Otherwise the main form
|
|
|
|
validation will not complete.
|
|
|
|
|
|
|
|
For simplicity, the `deferred` array is equipped with a shortcut method `add()` which automatically creates a Deferred
|
|
|
|
object and adds it to the `deferred` array. Using this method, you can simplify the above example as follows,
|
|
|
|
|
|
|
|
```php
|
|
|
|
public function clientValidateAttribute($model, $attribute, $view)
|
|
|
|
{
|
|
|
|
return <<<JS
|
|
|
|
deferred.add(function(def) {
|
|
|
|
var img = new Image();
|
|
|
|
img.onload = function() {
|
|
|
|
if (this.width > 150) {
|
|
|
|
messages.push('Image too wide!!');
|
|
|
|
}
|
|
|
|
def.resolve();
|
|
|
|
}
|
|
|
|
var reader = new FileReader();
|
|
|
|
reader.onloadend = function() {
|
|
|
|
img.src = reader.result;
|
|
|
|
}
|
|
|
|
reader.readAsDataURL(file);
|
|
|
|
});
|
|
|
|
JS;
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
|
|
|
|
### AJAX Validation <span id="ajax-validation"></span>
|
|
|
|
|
|
|
|
Some validations can only be done on the server side, because only the server has the necessary information.
|
|
|
|
For example, to validate if a username is unique or not, it is necessary to check the user table on the server side.
|
|
|
|
You can use AJAX-based validation in this case. It will trigger an AJAX request in the background to validate the
|
|
|
|
input while keeping the same user experience as the regular client-side validation.
|
|
|
|
|
|
|
|
To enable AJAX validation for a single input field, configure the [[yii\widgets\ActiveField::enableAjaxValidation|enableAjaxValidation]]
|
|
|
|
property of that field to be true and specify a unique form `id`:
|
|
|
|
|
|
|
|
```php
|
|
|
|
use yii\widgets\ActiveForm;
|
|
|
|
|
|
|
|
$form = ActiveForm::begin([
|
|
|
|
'id' => 'registration-form',
|
|
|
|
]);
|
|
|
|
|
|
|
|
echo $form->field($model, 'username', ['enableAjaxValidation' => true]);
|
|
|
|
|
|
|
|
// ...
|
|
|
|
|
|
|
|
ActiveForm::end();
|
|
|
|
```
|
|
|
|
|
|
|
|
To enable AJAX validation for the whole form, configure [[yii\widgets\ActiveForm::enableAjaxValidation|enableAjaxValidation]]
|
|
|
|
to be true at the form level:
|
|
|
|
|
|
|
|
```php
|
|
|
|
$form = ActiveForm::begin([
|
|
|
|
'id' => 'contact-form',
|
|
|
|
'enableAjaxValidation' => true,
|
|
|
|
]);
|
|
|
|
```
|
|
|
|
|
|
|
|
> Note: When the `enableAjaxValidation` property is configured at both the input field level and the form level,
|
|
|
|
the former will take precedence.
|
|
|
|
|
|
|
|
You also need to prepare the server so that it can handle the AJAX validation requests.
|
|
|
|
This can be achieved by a code snippet like the following in the controller actions:
|
|
|
|
|
|
|
|
```php
|
|
|
|
if (Yii::$app->request->isAjax && $model->load(Yii::$app->request->post())) {
|
|
|
|
Yii::$app->response->format = Response::FORMAT_JSON;
|
|
|
|
return ActiveForm::validate($model);
|
|
|
|
}
|
|
|
|
```
|
|
|
|
|
|
|
|
The above code will check whether the current request is an AJAX. If yes, it will respond to
|
|
|
|
this request by running the validation and returning the errors in JSON format.
|
|
|
|
|
|
|
|
> Info: You can also use [Deferred Validation](#deferred-validation) to perform AJAX validation.
|
|
|
|
However, the AJAX validation feature described here is more systematic and requires less coding effort.
|
|
|
|
|
|
|
|
When both `enableClientValidation` and `enableAjaxValidation` are set to true, AJAX validation request will be triggered
|
|
|
|
only after the successful client validation.
|