⚠ In case you've missed it we are migrating to our new website, with a brand new forum. For more details about the migration you can read our blog post for website migration. This forum is read-only and soon will be archived. ⚠

matches - rarely problem

1.3.3 1.4.1 password matches set_rules

  • Please log in to reply
2 replies to this topic

#1 kenshicu


    Advanced Member

  • Members
  • PipPipPip
  • 85 posts

Posted 12 February 2014 - 02:38 PM

hello to all

I have in GC1.3.3 a field  "password" and other "confirm_password" ,this last one does not exist in the database.
And I have this rule:

$crud->set_rules('confirm_password', 'Confirm password', 'required|matches[password]');

When migrating it to GC1.4.1, when I give to click in the button "save and go back", he does not do anything, does not work.

that he could be?

//sorry my bad english...


#2 Amit Shah

Amit Shah

    grocery CRUD Master

  • Advanced Member
  • PipPipPip
  • 1,192 posts

Posted 13 February 2014 - 10:55 AM

Hi there,


There should be some other issue that might be causing u do the bypass - such update dose not matter - 1.33 and 1.4.1 is both based on CI 2+ and is using the rules of CI internally

#3 kenshicu


    Advanced Member

  • Members
  • PipPipPip
  • 85 posts

Posted 13 February 2014 - 03:28 PM

I,  do not believe that it is the rule, but, use this one with a false field "confirm_password". Because I did not make changes in the controller, single I updated the GC, in any case I will continue studying the problem thanks

Also tagged with one or more of these keywords: 1.3.3, 1.4.1, password, matches, set_rules

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users