I just chased my tail around for a bit today. I got lost with setting the status of all inputs, and banging my head on why the "validate" function just wasn't working.
I just chased my tail around for a bit today. I got lost with setting the status of all inputs, and banging my head on why the "validate" function just wasn't working.
Ok, it is a little bit difficult to full understanding the unsafe validator.
Suppose we want to set a category to product (or an item in general term), Also suppose categories has sub-categories (multi-level)
There are cases that you want to validate the file format, size, extension etc but how to do that without submit the form ?
Suppose you have an Application in Yii that manages hotels each one has many customers.
CGridview displays existent rows of the table (using DataProvider)
This is a reference about model validators and user roles. In many cases we want model validators to applied only for some privileged users or not
There are cases you want to update a record on CGridview directly
Everyone have seen a multilayer menu in several CMS
Relational databases do not support inheritance so if we need to represent it, we have to somehow store meta info while keeping performance by minimizing JOINs. One way to solve this problem is using single table inheritance. All fields for the whole class tree are stored in a single table. Class name is stored in the type field...
This is a reference to be used for Model rule validation and is compiled from the Yii documentation and code. The purpose is to have all the information gathered in one place instead of scattered. This reference is not an intro. See The Definitive Guide to Yii, Declaring Validation Rules for a tutorial.