CE1.9.1 Please make sure your password match issue during User registration












22















I am encountering this issue in CE1.9.1.



When a User registers (doesn't matter if it's during checkout or from the Create an Account link) the user keeps getting the password mismatch error even though the password is re-entered correctly.



The form validation does not indicate a miss-match, but once a user clicks on Register it returns the mismatch error.



There is no errors in the chrome console...



I found this: "Please make sure your passwords match" - Password error in Checkout with New Registration form



But I don't believe it is the same error.



I need to fix it soon, any help is greatly appreciated!










share|improve this question

























  • This fixes the error in checkout cart but to get the "My Account" section to work I had to disable the compiler in ( admin|system|tools|compilation). ( re-compiling would probably work as well)

    – wiredoug
    Jan 5 '15 at 7:20
















22















I am encountering this issue in CE1.9.1.



When a User registers (doesn't matter if it's during checkout or from the Create an Account link) the user keeps getting the password mismatch error even though the password is re-entered correctly.



The form validation does not indicate a miss-match, but once a user clicks on Register it returns the mismatch error.



There is no errors in the chrome console...



I found this: "Please make sure your passwords match" - Password error in Checkout with New Registration form



But I don't believe it is the same error.



I need to fix it soon, any help is greatly appreciated!










share|improve this question

























  • This fixes the error in checkout cart but to get the "My Account" section to work I had to disable the compiler in ( admin|system|tools|compilation). ( re-compiling would probably work as well)

    – wiredoug
    Jan 5 '15 at 7:20














22












22








22


2






I am encountering this issue in CE1.9.1.



When a User registers (doesn't matter if it's during checkout or from the Create an Account link) the user keeps getting the password mismatch error even though the password is re-entered correctly.



The form validation does not indicate a miss-match, but once a user clicks on Register it returns the mismatch error.



There is no errors in the chrome console...



I found this: "Please make sure your passwords match" - Password error in Checkout with New Registration form



But I don't believe it is the same error.



I need to fix it soon, any help is greatly appreciated!










share|improve this question
















I am encountering this issue in CE1.9.1.



When a User registers (doesn't matter if it's during checkout or from the Create an Account link) the user keeps getting the password mismatch error even though the password is re-entered correctly.



The form validation does not indicate a miss-match, but once a user clicks on Register it returns the mismatch error.



There is no errors in the chrome console...



I found this: "Please make sure your passwords match" - Password error in Checkout with New Registration form



But I don't believe it is the same error.



I need to fix it soon, any help is greatly appreciated!







magento-1.9 error validation form-validation password






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 27 '17 at 10:39









Prince Patel

13.8k55279




13.8k55279










asked Dec 5 '14 at 7:23









BillBill

121116




121116













  • This fixes the error in checkout cart but to get the "My Account" section to work I had to disable the compiler in ( admin|system|tools|compilation). ( re-compiling would probably work as well)

    – wiredoug
    Jan 5 '15 at 7:20



















  • This fixes the error in checkout cart but to get the "My Account" section to work I had to disable the compiler in ( admin|system|tools|compilation). ( re-compiling would probably work as well)

    – wiredoug
    Jan 5 '15 at 7:20

















This fixes the error in checkout cart but to get the "My Account" section to work I had to disable the compiler in ( admin|system|tools|compilation). ( re-compiling would probably work as well)

– wiredoug
Jan 5 '15 at 7:20





This fixes the error in checkout cart but to get the "My Account" section to work I had to disable the compiler in ( admin|system|tools|compilation). ( re-compiling would probably work as well)

– wiredoug
Jan 5 '15 at 7:20










9 Answers
9






active

oldest

votes


















21














Children of class Mage_Customer_Model_Customer should use getPasswordConfirmation() instead of getConfirmation()



Upd: In class Mage_Customer_Model_Customer, method validate() was changed



Before v1.9.1:



$confirmation = $this->getConfirmation();


After:



$confirmation = $this->getPasswordConfirmation();






  • https://github.com/speedupmate/Magento-CE-Mirror/blame/master/app/code/core/Mage/Customer/Model/Customer.php#L841

  • https://github.com/speedupmate/Magento-CE-Mirror/commits/magento-ce-1.9.1.0/app/code/core/Mage/Customer/Model/Customer.php






share|improve this answer


























  • Note also that you should check any controller overrides as well, not just models that extend this class!

    – benz001
    May 25 '15 at 5:51






  • 2





    The mind boggles how something so critical as to stop an ecommerce store allowing purchases can make it through QA and into an official release.

    – mikemike
    Jul 10 '15 at 10:11






  • 1





    Also in some extensions need to change setConfirmation() to setPasswordConfirmation(). That was FireCheckout in my case. Class: TM_FireCheckout_Model_Type_Standard, method: _validateCustomerData().

    – gSorry
    Dec 4 '15 at 15:15



















5














Finally, I was able to solve the issue.



I have to mention it is really not good that magento core files have this kind of issues when they secure the passwords, guess the core developers forgot some simple things.



Ok, so to fix this issue you have to override the core customer model in local like app/code/local/Mage/Customer/Model/Customer.php. In that go to around line no. 843 (if you haven't already overriden) or go to line if (strlen($password) && !Zend_Validate::is($password, 'StringLength', array(6))) {
$errors = Mage::helper('customer')->__('The minimum password length is %s', 6);
}
and add the following code below that block:



//To match passwords in both Create account and Checkout register pages start
if ( Mage::app()->getRequest()->getServer('HTTP_REFERER') == Mage::getUrl('customer/account/create') )
$confirmation = $this->getPasswordConfirmation();
else
$confirmation = $this->getConfirmation();
//To match passwords in both Create account and Checkout register pages end


After this the password and confirm password will match on both "Checkout" and "Create Account" pages.



Hope this could help someone.






share|improve this answer

































    3














    If anybody still can't figure out, why this is happening:
    The Conlabz Useroptin extension (http://www.magentocommerce.com/magento-connect/newsletter-double-opt-in-for-customers.html) can cause this behavior aswell.



    Update 1.1.0 of said extension adds 1.9 compatibility






    share|improve this answer

































      3














      I have an extension that was overriding the AccountController.php and was having the same issue for Magento Platforms below 1.9.1



      My solution was;



      if (version_compare(Mage::getVersion(), '1.9.1', '<=')) {        
      $customer->setPasswordConfirmation($request->getPost('confirmation'));
      }

      if (version_compare(Mage::getVersion(), '1.9.0', '>=')) {
      $customer->setConfirmation($request->getPost('confirmation'));
      }





      share|improve this answer































        2














        For me neither $this->getPasswordConfirmation() nor $this->getConfirmation() worked. Both returned an empty string. So I ended up in accessing the POST parameter directly, in /app/code/core/Mage/Customer/Model/Customer.php (yes, better use a copy in /app/code/local):



        if (isset($_REQUEST['confirmation']))
        $confirmation = $_REQUEST['confirmation'];
        else
        $confirmation = $this->getPasswordConfirmation();





        share|improve this answer



















        • 1





          ha ha good crack :)

          – Keyur Shah
          Nov 14 '16 at 19:37



















        0














        it's because of this change in 1.9.1 update. You have to update your extensions code
        -Customer passwords are no longer stored in clear text during registration.






        share|improve this answer
























        • I see, I'll check the extension codes. Thanks!

          – Bill
          Dec 8 '14 at 6:52





















        0














        I have a same issue as I am using third party extension for checkout so this issue has to come



        I have solved that error by doing following steps




        1) in my module I search for confirmation



        2) check that it is setting data for customer model



        3) then change key to password_confirmation from confirmation




        I follow above steps to debug the issue and solved it.






        share|improve this answer































          0














          My solution was



          $confirmation = $this->getPasswordConfirmation(); // test works for Create, fails for Checkout
          if ($password != $confirmation) {
          $confirmation = $this->getConfirmation(); // test works for Checkout fails for Create
          if ($password != $confirmation) {
          $errors = Mage::helper('customer')->__('Please make sure your passwords match.');
          }
          }





          share|improve this answer































            -2














            Hi Friends This Problem Can be resolved by doing below steps:



            Step 1: Open This file /app/code/core/Mage/Customer/Model/Customer.php

            Step 2: Find This line in Customer.php $confirmation = $this->getPasswordConfirmation();
            Step 3: Replace That that line with $confirmation = $this->getConfirmation();



            Your Problem is now Resolved.






            share|improve this answer





















            • 3





              Unless this truly is a core bug, I wouldn't recommend changing core files.

              – Andrew Kett
              Jan 1 '15 at 3:16










            protected by Community Feb 8 '15 at 6:20



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?














            9 Answers
            9






            active

            oldest

            votes








            9 Answers
            9






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            21














            Children of class Mage_Customer_Model_Customer should use getPasswordConfirmation() instead of getConfirmation()



            Upd: In class Mage_Customer_Model_Customer, method validate() was changed



            Before v1.9.1:



            $confirmation = $this->getConfirmation();


            After:



            $confirmation = $this->getPasswordConfirmation();






            • https://github.com/speedupmate/Magento-CE-Mirror/blame/master/app/code/core/Mage/Customer/Model/Customer.php#L841

            • https://github.com/speedupmate/Magento-CE-Mirror/commits/magento-ce-1.9.1.0/app/code/core/Mage/Customer/Model/Customer.php






            share|improve this answer


























            • Note also that you should check any controller overrides as well, not just models that extend this class!

              – benz001
              May 25 '15 at 5:51






            • 2





              The mind boggles how something so critical as to stop an ecommerce store allowing purchases can make it through QA and into an official release.

              – mikemike
              Jul 10 '15 at 10:11






            • 1





              Also in some extensions need to change setConfirmation() to setPasswordConfirmation(). That was FireCheckout in my case. Class: TM_FireCheckout_Model_Type_Standard, method: _validateCustomerData().

              – gSorry
              Dec 4 '15 at 15:15
















            21














            Children of class Mage_Customer_Model_Customer should use getPasswordConfirmation() instead of getConfirmation()



            Upd: In class Mage_Customer_Model_Customer, method validate() was changed



            Before v1.9.1:



            $confirmation = $this->getConfirmation();


            After:



            $confirmation = $this->getPasswordConfirmation();






            • https://github.com/speedupmate/Magento-CE-Mirror/blame/master/app/code/core/Mage/Customer/Model/Customer.php#L841

            • https://github.com/speedupmate/Magento-CE-Mirror/commits/magento-ce-1.9.1.0/app/code/core/Mage/Customer/Model/Customer.php






            share|improve this answer


























            • Note also that you should check any controller overrides as well, not just models that extend this class!

              – benz001
              May 25 '15 at 5:51






            • 2





              The mind boggles how something so critical as to stop an ecommerce store allowing purchases can make it through QA and into an official release.

              – mikemike
              Jul 10 '15 at 10:11






            • 1





              Also in some extensions need to change setConfirmation() to setPasswordConfirmation(). That was FireCheckout in my case. Class: TM_FireCheckout_Model_Type_Standard, method: _validateCustomerData().

              – gSorry
              Dec 4 '15 at 15:15














            21












            21








            21







            Children of class Mage_Customer_Model_Customer should use getPasswordConfirmation() instead of getConfirmation()



            Upd: In class Mage_Customer_Model_Customer, method validate() was changed



            Before v1.9.1:



            $confirmation = $this->getConfirmation();


            After:



            $confirmation = $this->getPasswordConfirmation();






            • https://github.com/speedupmate/Magento-CE-Mirror/blame/master/app/code/core/Mage/Customer/Model/Customer.php#L841

            • https://github.com/speedupmate/Magento-CE-Mirror/commits/magento-ce-1.9.1.0/app/code/core/Mage/Customer/Model/Customer.php






            share|improve this answer















            Children of class Mage_Customer_Model_Customer should use getPasswordConfirmation() instead of getConfirmation()



            Upd: In class Mage_Customer_Model_Customer, method validate() was changed



            Before v1.9.1:



            $confirmation = $this->getConfirmation();


            After:



            $confirmation = $this->getPasswordConfirmation();






            • https://github.com/speedupmate/Magento-CE-Mirror/blame/master/app/code/core/Mage/Customer/Model/Customer.php#L841

            • https://github.com/speedupmate/Magento-CE-Mirror/commits/magento-ce-1.9.1.0/app/code/core/Mage/Customer/Model/Customer.php







            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited May 18 '16 at 17:50









            7ochem

            5,77293768




            5,77293768










            answered Dec 8 '14 at 21:05









            BogdanBogdan

            22113




            22113













            • Note also that you should check any controller overrides as well, not just models that extend this class!

              – benz001
              May 25 '15 at 5:51






            • 2





              The mind boggles how something so critical as to stop an ecommerce store allowing purchases can make it through QA and into an official release.

              – mikemike
              Jul 10 '15 at 10:11






            • 1





              Also in some extensions need to change setConfirmation() to setPasswordConfirmation(). That was FireCheckout in my case. Class: TM_FireCheckout_Model_Type_Standard, method: _validateCustomerData().

              – gSorry
              Dec 4 '15 at 15:15



















            • Note also that you should check any controller overrides as well, not just models that extend this class!

              – benz001
              May 25 '15 at 5:51






            • 2





              The mind boggles how something so critical as to stop an ecommerce store allowing purchases can make it through QA and into an official release.

              – mikemike
              Jul 10 '15 at 10:11






            • 1





              Also in some extensions need to change setConfirmation() to setPasswordConfirmation(). That was FireCheckout in my case. Class: TM_FireCheckout_Model_Type_Standard, method: _validateCustomerData().

              – gSorry
              Dec 4 '15 at 15:15

















            Note also that you should check any controller overrides as well, not just models that extend this class!

            – benz001
            May 25 '15 at 5:51





            Note also that you should check any controller overrides as well, not just models that extend this class!

            – benz001
            May 25 '15 at 5:51




            2




            2





            The mind boggles how something so critical as to stop an ecommerce store allowing purchases can make it through QA and into an official release.

            – mikemike
            Jul 10 '15 at 10:11





            The mind boggles how something so critical as to stop an ecommerce store allowing purchases can make it through QA and into an official release.

            – mikemike
            Jul 10 '15 at 10:11




            1




            1





            Also in some extensions need to change setConfirmation() to setPasswordConfirmation(). That was FireCheckout in my case. Class: TM_FireCheckout_Model_Type_Standard, method: _validateCustomerData().

            – gSorry
            Dec 4 '15 at 15:15





            Also in some extensions need to change setConfirmation() to setPasswordConfirmation(). That was FireCheckout in my case. Class: TM_FireCheckout_Model_Type_Standard, method: _validateCustomerData().

            – gSorry
            Dec 4 '15 at 15:15













            5














            Finally, I was able to solve the issue.



            I have to mention it is really not good that magento core files have this kind of issues when they secure the passwords, guess the core developers forgot some simple things.



            Ok, so to fix this issue you have to override the core customer model in local like app/code/local/Mage/Customer/Model/Customer.php. In that go to around line no. 843 (if you haven't already overriden) or go to line if (strlen($password) && !Zend_Validate::is($password, 'StringLength', array(6))) {
            $errors = Mage::helper('customer')->__('The minimum password length is %s', 6);
            }
            and add the following code below that block:



            //To match passwords in both Create account and Checkout register pages start
            if ( Mage::app()->getRequest()->getServer('HTTP_REFERER') == Mage::getUrl('customer/account/create') )
            $confirmation = $this->getPasswordConfirmation();
            else
            $confirmation = $this->getConfirmation();
            //To match passwords in both Create account and Checkout register pages end


            After this the password and confirm password will match on both "Checkout" and "Create Account" pages.



            Hope this could help someone.






            share|improve this answer






























              5














              Finally, I was able to solve the issue.



              I have to mention it is really not good that magento core files have this kind of issues when they secure the passwords, guess the core developers forgot some simple things.



              Ok, so to fix this issue you have to override the core customer model in local like app/code/local/Mage/Customer/Model/Customer.php. In that go to around line no. 843 (if you haven't already overriden) or go to line if (strlen($password) && !Zend_Validate::is($password, 'StringLength', array(6))) {
              $errors = Mage::helper('customer')->__('The minimum password length is %s', 6);
              }
              and add the following code below that block:



              //To match passwords in both Create account and Checkout register pages start
              if ( Mage::app()->getRequest()->getServer('HTTP_REFERER') == Mage::getUrl('customer/account/create') )
              $confirmation = $this->getPasswordConfirmation();
              else
              $confirmation = $this->getConfirmation();
              //To match passwords in both Create account and Checkout register pages end


              After this the password and confirm password will match on both "Checkout" and "Create Account" pages.



              Hope this could help someone.






              share|improve this answer




























                5












                5








                5







                Finally, I was able to solve the issue.



                I have to mention it is really not good that magento core files have this kind of issues when they secure the passwords, guess the core developers forgot some simple things.



                Ok, so to fix this issue you have to override the core customer model in local like app/code/local/Mage/Customer/Model/Customer.php. In that go to around line no. 843 (if you haven't already overriden) or go to line if (strlen($password) && !Zend_Validate::is($password, 'StringLength', array(6))) {
                $errors = Mage::helper('customer')->__('The minimum password length is %s', 6);
                }
                and add the following code below that block:



                //To match passwords in both Create account and Checkout register pages start
                if ( Mage::app()->getRequest()->getServer('HTTP_REFERER') == Mage::getUrl('customer/account/create') )
                $confirmation = $this->getPasswordConfirmation();
                else
                $confirmation = $this->getConfirmation();
                //To match passwords in both Create account and Checkout register pages end


                After this the password and confirm password will match on both "Checkout" and "Create Account" pages.



                Hope this could help someone.






                share|improve this answer















                Finally, I was able to solve the issue.



                I have to mention it is really not good that magento core files have this kind of issues when they secure the passwords, guess the core developers forgot some simple things.



                Ok, so to fix this issue you have to override the core customer model in local like app/code/local/Mage/Customer/Model/Customer.php. In that go to around line no. 843 (if you haven't already overriden) or go to line if (strlen($password) && !Zend_Validate::is($password, 'StringLength', array(6))) {
                $errors = Mage::helper('customer')->__('The minimum password length is %s', 6);
                }
                and add the following code below that block:



                //To match passwords in both Create account and Checkout register pages start
                if ( Mage::app()->getRequest()->getServer('HTTP_REFERER') == Mage::getUrl('customer/account/create') )
                $confirmation = $this->getPasswordConfirmation();
                else
                $confirmation = $this->getConfirmation();
                //To match passwords in both Create account and Checkout register pages end


                After this the password and confirm password will match on both "Checkout" and "Create Account" pages.



                Hope this could help someone.







                share|improve this answer














                share|improve this answer



                share|improve this answer








                edited Jul 30 '15 at 7:14

























                answered Jul 30 '15 at 7:01









                H.D.H.D.

                166313




                166313























                    3














                    If anybody still can't figure out, why this is happening:
                    The Conlabz Useroptin extension (http://www.magentocommerce.com/magento-connect/newsletter-double-opt-in-for-customers.html) can cause this behavior aswell.



                    Update 1.1.0 of said extension adds 1.9 compatibility






                    share|improve this answer






























                      3














                      If anybody still can't figure out, why this is happening:
                      The Conlabz Useroptin extension (http://www.magentocommerce.com/magento-connect/newsletter-double-opt-in-for-customers.html) can cause this behavior aswell.



                      Update 1.1.0 of said extension adds 1.9 compatibility






                      share|improve this answer




























                        3












                        3








                        3







                        If anybody still can't figure out, why this is happening:
                        The Conlabz Useroptin extension (http://www.magentocommerce.com/magento-connect/newsletter-double-opt-in-for-customers.html) can cause this behavior aswell.



                        Update 1.1.0 of said extension adds 1.9 compatibility






                        share|improve this answer















                        If anybody still can't figure out, why this is happening:
                        The Conlabz Useroptin extension (http://www.magentocommerce.com/magento-connect/newsletter-double-opt-in-for-customers.html) can cause this behavior aswell.



                        Update 1.1.0 of said extension adds 1.9 compatibility







                        share|improve this answer














                        share|improve this answer



                        share|improve this answer








                        edited Aug 4 '15 at 9:56

























                        answered May 28 '15 at 10:24









                        loeffelloeffel

                        501517




                        501517























                            3














                            I have an extension that was overriding the AccountController.php and was having the same issue for Magento Platforms below 1.9.1



                            My solution was;



                            if (version_compare(Mage::getVersion(), '1.9.1', '<=')) {        
                            $customer->setPasswordConfirmation($request->getPost('confirmation'));
                            }

                            if (version_compare(Mage::getVersion(), '1.9.0', '>=')) {
                            $customer->setConfirmation($request->getPost('confirmation'));
                            }





                            share|improve this answer




























                              3














                              I have an extension that was overriding the AccountController.php and was having the same issue for Magento Platforms below 1.9.1



                              My solution was;



                              if (version_compare(Mage::getVersion(), '1.9.1', '<=')) {        
                              $customer->setPasswordConfirmation($request->getPost('confirmation'));
                              }

                              if (version_compare(Mage::getVersion(), '1.9.0', '>=')) {
                              $customer->setConfirmation($request->getPost('confirmation'));
                              }





                              share|improve this answer


























                                3












                                3








                                3







                                I have an extension that was overriding the AccountController.php and was having the same issue for Magento Platforms below 1.9.1



                                My solution was;



                                if (version_compare(Mage::getVersion(), '1.9.1', '<=')) {        
                                $customer->setPasswordConfirmation($request->getPost('confirmation'));
                                }

                                if (version_compare(Mage::getVersion(), '1.9.0', '>=')) {
                                $customer->setConfirmation($request->getPost('confirmation'));
                                }





                                share|improve this answer













                                I have an extension that was overriding the AccountController.php and was having the same issue for Magento Platforms below 1.9.1



                                My solution was;



                                if (version_compare(Mage::getVersion(), '1.9.1', '<=')) {        
                                $customer->setPasswordConfirmation($request->getPost('confirmation'));
                                }

                                if (version_compare(Mage::getVersion(), '1.9.0', '>=')) {
                                $customer->setConfirmation($request->getPost('confirmation'));
                                }






                                share|improve this answer












                                share|improve this answer



                                share|improve this answer










                                answered Nov 7 '15 at 9:52









                                BENN1THBENN1TH

                                5941516




                                5941516























                                    2














                                    For me neither $this->getPasswordConfirmation() nor $this->getConfirmation() worked. Both returned an empty string. So I ended up in accessing the POST parameter directly, in /app/code/core/Mage/Customer/Model/Customer.php (yes, better use a copy in /app/code/local):



                                    if (isset($_REQUEST['confirmation']))
                                    $confirmation = $_REQUEST['confirmation'];
                                    else
                                    $confirmation = $this->getPasswordConfirmation();





                                    share|improve this answer



















                                    • 1





                                      ha ha good crack :)

                                      – Keyur Shah
                                      Nov 14 '16 at 19:37
















                                    2














                                    For me neither $this->getPasswordConfirmation() nor $this->getConfirmation() worked. Both returned an empty string. So I ended up in accessing the POST parameter directly, in /app/code/core/Mage/Customer/Model/Customer.php (yes, better use a copy in /app/code/local):



                                    if (isset($_REQUEST['confirmation']))
                                    $confirmation = $_REQUEST['confirmation'];
                                    else
                                    $confirmation = $this->getPasswordConfirmation();





                                    share|improve this answer



















                                    • 1





                                      ha ha good crack :)

                                      – Keyur Shah
                                      Nov 14 '16 at 19:37














                                    2












                                    2








                                    2







                                    For me neither $this->getPasswordConfirmation() nor $this->getConfirmation() worked. Both returned an empty string. So I ended up in accessing the POST parameter directly, in /app/code/core/Mage/Customer/Model/Customer.php (yes, better use a copy in /app/code/local):



                                    if (isset($_REQUEST['confirmation']))
                                    $confirmation = $_REQUEST['confirmation'];
                                    else
                                    $confirmation = $this->getPasswordConfirmation();





                                    share|improve this answer













                                    For me neither $this->getPasswordConfirmation() nor $this->getConfirmation() worked. Both returned an empty string. So I ended up in accessing the POST parameter directly, in /app/code/core/Mage/Customer/Model/Customer.php (yes, better use a copy in /app/code/local):



                                    if (isset($_REQUEST['confirmation']))
                                    $confirmation = $_REQUEST['confirmation'];
                                    else
                                    $confirmation = $this->getPasswordConfirmation();






                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Apr 13 '16 at 12:29









                                    AnseAnse

                                    15018




                                    15018








                                    • 1





                                      ha ha good crack :)

                                      – Keyur Shah
                                      Nov 14 '16 at 19:37














                                    • 1





                                      ha ha good crack :)

                                      – Keyur Shah
                                      Nov 14 '16 at 19:37








                                    1




                                    1





                                    ha ha good crack :)

                                    – Keyur Shah
                                    Nov 14 '16 at 19:37





                                    ha ha good crack :)

                                    – Keyur Shah
                                    Nov 14 '16 at 19:37











                                    0














                                    it's because of this change in 1.9.1 update. You have to update your extensions code
                                    -Customer passwords are no longer stored in clear text during registration.






                                    share|improve this answer
























                                    • I see, I'll check the extension codes. Thanks!

                                      – Bill
                                      Dec 8 '14 at 6:52


















                                    0














                                    it's because of this change in 1.9.1 update. You have to update your extensions code
                                    -Customer passwords are no longer stored in clear text during registration.






                                    share|improve this answer
























                                    • I see, I'll check the extension codes. Thanks!

                                      – Bill
                                      Dec 8 '14 at 6:52
















                                    0












                                    0








                                    0







                                    it's because of this change in 1.9.1 update. You have to update your extensions code
                                    -Customer passwords are no longer stored in clear text during registration.






                                    share|improve this answer













                                    it's because of this change in 1.9.1 update. You have to update your extensions code
                                    -Customer passwords are no longer stored in clear text during registration.







                                    share|improve this answer












                                    share|improve this answer



                                    share|improve this answer










                                    answered Dec 6 '14 at 10:53









                                    javierjavier

                                    11




                                    11













                                    • I see, I'll check the extension codes. Thanks!

                                      – Bill
                                      Dec 8 '14 at 6:52





















                                    • I see, I'll check the extension codes. Thanks!

                                      – Bill
                                      Dec 8 '14 at 6:52



















                                    I see, I'll check the extension codes. Thanks!

                                    – Bill
                                    Dec 8 '14 at 6:52







                                    I see, I'll check the extension codes. Thanks!

                                    – Bill
                                    Dec 8 '14 at 6:52













                                    0














                                    I have a same issue as I am using third party extension for checkout so this issue has to come



                                    I have solved that error by doing following steps




                                    1) in my module I search for confirmation



                                    2) check that it is setting data for customer model



                                    3) then change key to password_confirmation from confirmation




                                    I follow above steps to debug the issue and solved it.






                                    share|improve this answer




























                                      0














                                      I have a same issue as I am using third party extension for checkout so this issue has to come



                                      I have solved that error by doing following steps




                                      1) in my module I search for confirmation



                                      2) check that it is setting data for customer model



                                      3) then change key to password_confirmation from confirmation




                                      I follow above steps to debug the issue and solved it.






                                      share|improve this answer


























                                        0












                                        0








                                        0







                                        I have a same issue as I am using third party extension for checkout so this issue has to come



                                        I have solved that error by doing following steps




                                        1) in my module I search for confirmation



                                        2) check that it is setting data for customer model



                                        3) then change key to password_confirmation from confirmation




                                        I follow above steps to debug the issue and solved it.






                                        share|improve this answer













                                        I have a same issue as I am using third party extension for checkout so this issue has to come



                                        I have solved that error by doing following steps




                                        1) in my module I search for confirmation



                                        2) check that it is setting data for customer model



                                        3) then change key to password_confirmation from confirmation




                                        I follow above steps to debug the issue and solved it.







                                        share|improve this answer












                                        share|improve this answer



                                        share|improve this answer










                                        answered Jan 10 '17 at 7:48









                                        Murtuza ZabuawalaMurtuza Zabuawala

                                        12.5k73362




                                        12.5k73362























                                            0














                                            My solution was



                                            $confirmation = $this->getPasswordConfirmation(); // test works for Create, fails for Checkout
                                            if ($password != $confirmation) {
                                            $confirmation = $this->getConfirmation(); // test works for Checkout fails for Create
                                            if ($password != $confirmation) {
                                            $errors = Mage::helper('customer')->__('Please make sure your passwords match.');
                                            }
                                            }





                                            share|improve this answer




























                                              0














                                              My solution was



                                              $confirmation = $this->getPasswordConfirmation(); // test works for Create, fails for Checkout
                                              if ($password != $confirmation) {
                                              $confirmation = $this->getConfirmation(); // test works for Checkout fails for Create
                                              if ($password != $confirmation) {
                                              $errors = Mage::helper('customer')->__('Please make sure your passwords match.');
                                              }
                                              }





                                              share|improve this answer


























                                                0












                                                0








                                                0







                                                My solution was



                                                $confirmation = $this->getPasswordConfirmation(); // test works for Create, fails for Checkout
                                                if ($password != $confirmation) {
                                                $confirmation = $this->getConfirmation(); // test works for Checkout fails for Create
                                                if ($password != $confirmation) {
                                                $errors = Mage::helper('customer')->__('Please make sure your passwords match.');
                                                }
                                                }





                                                share|improve this answer













                                                My solution was



                                                $confirmation = $this->getPasswordConfirmation(); // test works for Create, fails for Checkout
                                                if ($password != $confirmation) {
                                                $confirmation = $this->getConfirmation(); // test works for Checkout fails for Create
                                                if ($password != $confirmation) {
                                                $errors = Mage::helper('customer')->__('Please make sure your passwords match.');
                                                }
                                                }






                                                share|improve this answer












                                                share|improve this answer



                                                share|improve this answer










                                                answered 15 mins ago









                                                RW-FairportRW-Fairport

                                                212




                                                212























                                                    -2














                                                    Hi Friends This Problem Can be resolved by doing below steps:



                                                    Step 1: Open This file /app/code/core/Mage/Customer/Model/Customer.php

                                                    Step 2: Find This line in Customer.php $confirmation = $this->getPasswordConfirmation();
                                                    Step 3: Replace That that line with $confirmation = $this->getConfirmation();



                                                    Your Problem is now Resolved.






                                                    share|improve this answer





















                                                    • 3





                                                      Unless this truly is a core bug, I wouldn't recommend changing core files.

                                                      – Andrew Kett
                                                      Jan 1 '15 at 3:16
















                                                    -2














                                                    Hi Friends This Problem Can be resolved by doing below steps:



                                                    Step 1: Open This file /app/code/core/Mage/Customer/Model/Customer.php

                                                    Step 2: Find This line in Customer.php $confirmation = $this->getPasswordConfirmation();
                                                    Step 3: Replace That that line with $confirmation = $this->getConfirmation();



                                                    Your Problem is now Resolved.






                                                    share|improve this answer





















                                                    • 3





                                                      Unless this truly is a core bug, I wouldn't recommend changing core files.

                                                      – Andrew Kett
                                                      Jan 1 '15 at 3:16














                                                    -2












                                                    -2








                                                    -2







                                                    Hi Friends This Problem Can be resolved by doing below steps:



                                                    Step 1: Open This file /app/code/core/Mage/Customer/Model/Customer.php

                                                    Step 2: Find This line in Customer.php $confirmation = $this->getPasswordConfirmation();
                                                    Step 3: Replace That that line with $confirmation = $this->getConfirmation();



                                                    Your Problem is now Resolved.






                                                    share|improve this answer















                                                    Hi Friends This Problem Can be resolved by doing below steps:



                                                    Step 1: Open This file /app/code/core/Mage/Customer/Model/Customer.php

                                                    Step 2: Find This line in Customer.php $confirmation = $this->getPasswordConfirmation();
                                                    Step 3: Replace That that line with $confirmation = $this->getConfirmation();



                                                    Your Problem is now Resolved.







                                                    share|improve this answer














                                                    share|improve this answer



                                                    share|improve this answer








                                                    edited Apr 13 '16 at 12:59









                                                    7ochem

                                                    5,77293768




                                                    5,77293768










                                                    answered Jan 1 '15 at 1:25









                                                    Mag KartMag Kart

                                                    11




                                                    11








                                                    • 3





                                                      Unless this truly is a core bug, I wouldn't recommend changing core files.

                                                      – Andrew Kett
                                                      Jan 1 '15 at 3:16














                                                    • 3





                                                      Unless this truly is a core bug, I wouldn't recommend changing core files.

                                                      – Andrew Kett
                                                      Jan 1 '15 at 3:16








                                                    3




                                                    3





                                                    Unless this truly is a core bug, I wouldn't recommend changing core files.

                                                    – Andrew Kett
                                                    Jan 1 '15 at 3:16





                                                    Unless this truly is a core bug, I wouldn't recommend changing core files.

                                                    – Andrew Kett
                                                    Jan 1 '15 at 3:16





                                                    protected by Community Feb 8 '15 at 6:20



                                                    Thank you for your interest in this question.
                                                    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



                                                    Would you like to answer one of these unanswered questions instead?



                                                    Popular posts from this blog

                                                    Alcázar de San Juan

                                                    Griza ansero

                                                    Heinkel He 51