https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33832
--- Comment #15 from Brendan Lawlor <[email protected]> --- (In reply to Owen Leonard from comment #13) > It looks like the change to the template is not necessary and is causing JS > errors in the browser console. Including the password-checking JS doesn't > seem to cause a problem whether or not the password is being updated. Thanks for checking, Owen. I removed the change to the template. I also changed the Perl that I had mixed up with template toolkit syntax to check defined($newpassword). The reason we have to check if the new password is defined is because if the user leaves the input blank, the Perl script gets the param as an empty string. If you check the value of the empty string it evaluates to false. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
