Zend Framework

Two more Standard Validator needed

Details

  • Type: Improvement Improvement
  • Status: Resolved Resolved
  • Priority: Minor Minor
  • Resolution: Not an Issue
  • Affects Version/s: None
  • Fix Version/s: 1.8.1
  • Component/s: Zend_Validate
  • Labels:
    None

Description

When validating register form, two validations are always needed:

1) Check user name availability
2) Check password and re enter password(or emails) matching

Christer has done 2) in his blog:
http://cogo.wordpress.com/2008/04/16/custom-validators-for-zend_form_element/

I have done 1) in my project as a custom validator.

But I think it is nice that these two validators could be ship with ZF as standard validator.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Christer Edvartsen added a comment -

To implement 1) you would need to have some sort of interface that the end users of ZF would have to implement though. It's impossible to make a generic validator for that since pretty much everyone has their own setup regarding user accounts.

I have implemented something like that but the class I have written will only work for my setup. If you could make a generic validator along with a small interface with a single method:

public function isTaken($userName);

or something like that, I guess it could be more simple to use. But 2) would be great to have in ZF I think.

Show
Christer Edvartsen added a comment - To implement 1) you would need to have some sort of interface that the end users of ZF would have to implement though. It's impossible to make a generic validator for that since pretty much everyone has their own setup regarding user accounts. I have implemented something like that but the class I have written will only work for my setup. If you could make a generic validator along with a small interface with a single method: public function isTaken($userName); or something like that, I guess it could be more simple to use. But 2) would be great to have in ZF I think.
Hide
Permalink
Jason Qi added a comment -

For 1), What I did is writing a custom validator, similar with other validators.

The end user can use it without any difference to other validators. i.g. AddValidator('CheckAvailability' , false, array('user', 'username')). Where the 'user' is the table name and 'username' is the field name in the table.

In isValid($value) function, just check if there is a record in table 'user' and the value of field 'username' match $value.

And you are right, this is just for "DB Table Adapter", but I believe there should be a solution to combine other adapters together.

Show
Jason Qi added a comment - For 1), What I did is writing a custom validator, similar with other validators. The end user can use it without any difference to other validators. i.g. AddValidator('CheckAvailability' , false, array('user', 'username')). Where the 'user' is the table name and 'username' is the field name in the table. In isValid($value) function, just check if there is a record in table 'user' and the value of field 'username' match $value. And you are right, this is just for "DB Table Adapter", but I believe there should be a solution to combine other adapters together.
Hide
Permalink
Wil Sinclair added a comment -

Please evaluate and fix/categorize as necessary.

Show
Wil Sinclair added a comment - Please evaluate and fix/categorize as necessary.
Hide
Permalink
Thomas Weidner added a comment -

For DB there is a validator within the incubator almost finished and probably ready for 1.8.
For the second "password" matching you should eighter use the Identical (incubator) or InArray validator.
Both can compare form element values with a given string.

Show
Thomas Weidner added a comment - For DB there is a validator within the incubator almost finished and probably ready for 1.8. For the second "password" matching you should eighter use the Identical (incubator) or InArray validator. Both can compare form element values with a given string.
Hide
Permalink
Thomas Weidner added a comment -

Closing as non-issue as for both already solution are ready or almost finished and independently proposed.

Show
Thomas Weidner added a comment - Closing as non-issue as for both already solution are ready or almost finished and independently proposed.

People

Vote (1)
Watch (2)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Zend Framework. Try JIRA - bug tracking software for your team.