Yes, you just remove the error index in the view.
And I disagree, Tarique, error message should be _generated_ by the
model, as it is related to the value of the data. The _formatting_ of
the error message should most definately be handled in the view.
On Jun 29, 5:03 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
> Do you have any examples of how this is accomplished? Do i just remove
> the error index from the array in the view.. And tarique, i think to
> me it seems a matter of opinion whether you have errors in the view or
> the model.. Personally i'd rather have them in the model but i'm sure
> many people would prefer it in the view so they can see what the error
> messages would be without looking at back-end code. In my opinion i'd
> rather not be bothered messing with it in the view as its easier to
> just set it in the model and then display whatever errors there are in
> the view..
>
> On Jun 28, 4:00 pm,GeoffFord<[EMAIL PROTECTED]> wrote:
>
> > In 1.2 $form->input() automatically picks up the error message and you
> > don't need to set error in the view.
>
> > In 1.1 I think you need to use $html->errorTag() or something like
> > that.
>
> > Either way you shouldn't set the error message in the view, it should
> > be pulled from the models validationErrors
>
> > On Jun 28, 4:40 pm, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote:
>
> > > If i use $this->invalidate("password", "Passwords do not match");
> > > how do i associate that in my view.. Currently my view has
> > > <?php echo $form->input('password',
> > > array('error' => 'Password must be at least 4
> > > characters.',
> > > 'type'=>'password',
> > > 'value' =>''));
> > > ?>
>
> > > for the password.. If i do as you say, i still get the error about
> > > being at least 4 characters.. Personally i'd rather not even have the
> > > error messages in the view but in the models.. How do i set the error
> > > from invalidate to display in the views?
>
> > > On Jun 27, 4:27 pm, Grant Cox <[EMAIL PROTECTED]> wrote:
>
> > > > I would use $this->invalidate('password', "Passwords do not match") -
> > > > this way it is just the same as any other validation routine. You
> > > > also don't need to call beforeValidate() in your beforeSave, it is
> > > > done automatically by Cake when you save.
>
> > > > Your beforeSave is still MD5-ing every password that gets put in
> > > > there. So, if you do:
>
> > > > $existing_user = $this->User->read(null, $user_id);
> > > > $existing_user['User']['name'] = 'I am changing your name';
> > > > $this->User->save( $existing_user );
>
> > > > then your password is now double MD5'd. What I was saying previously
> > > > is that the field submitted from the form that has the plain text
> > > > password should not be the actual password field used in your
> > > > database. So if you use "password" in the database to indicate a
> > > > hashed password, then on your form make the field "plain_password" or
> > > > "new_password" or something - this way in your beforeSave you know if
> > > > it needs to be MD5'd, otherwise don't change. The "plain_password"
> > > > should not be saved into the db at all. And you're right, the hashed
> > > > password field should not appear in a form either.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake
PHP" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~----------~----~----~----~------~----~------~--~---
