CStringValidator allowEmpty=>false

andy_s · February 13, 2010, 9:05am

I’ve just noticed that if I use CStringValidator with allowEmpty => false and an attribute’s value is an empty string, then the validator doesn’t show any error. In a combination with CRequiredValidator it works well and shows “Attribute can’t be blank” message:




array('name', 'required'),

array('name', 'length', 'max'=>100, 'allowEmpty'=>false),

I just wonder if it is an expected behavior or I’m missing something

tri · February 13, 2010, 9:23am

Randomly Throw Cache Error

I’ve just noticed that if I use CStringValidator with allowEmpty => false and an attribute’s value is an empty string, then the validator doesn’t show any error. In a combination with CRequiredValidator it works well and shows “Attribute can’t be blank” message:
array('name', 'required'),

array('name', 'length', 'max'=>100, 'allowEmpty'=>false),
I just wonder if it is an expected behavior or I’m missing something

Should not make a difference whether what’s not required is empty or not

/Tommy

andy_s · February 13, 2010, 10:07am

You are right, but it doesn’t look intuitive to me when I disallow a field to be empty, but it can be empty anyway Had to spend some time to figure this out…