Home/ Questions/Q 3790122
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T12:15:55+00:00

I saw this code. I removed some of the irrelevant code to make it

  • 0

I saw this code. I removed some of the irrelevant code to make it simpler (like the identical validator that checks that the passwords match). 

$password = new Zend_Form_Element_Password('password');
$password->addFilter(new My_Filters_Sha());

$password2 = new Zend_Form_Element_Password('password2');
$password2->addFilter(new My_Filters_Sha());

My question is about the filter. My guess is that whoever wrote it is saving the password in the database as a hashed and that’s why they hash the password with the filter. But what’s the point of having a filter handle the hashing? Shouldn’t this be done once in the controller when he account is being created? When the input is received, process it to a hash and save it then. Is there a point to having this done as a filter?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The responsibility of your controller is to handle the request and delegate to the appropriate Model. Hashing a password is business logic. Business logic has no place in a controller but belongs to the Model. Your Form class is a Model class and thus it’s appropriate to put the filter there.

    • 0