just in case it could be useful:

Index: tools.py
===================================================================
--- tools.py    (revision 1140)
+++ tools.py    (working copy)
@@ -396,6 +396,7 @@
         self.messages.invalid_email = 'Invalid email'
         self.messages.invalid_login = 'Invalid login'
         self.messages.invalid_user = 'Invalid user'
+        self.messages.invalid_password = 'Invalid password'
         self.messages.is_empty = "Cannot be empty"
         self.messages.mismatched_password = "Password fields don't match"
         self.messages.verify_email = \
@@ -1173,7 +1174,8 @@
             label=self.messages.old_password,
             requires=validators(
                      self.settings.table_user[passfield].requires,
-                     IS_IN_DB(s, '%s.%s' % (usern, passfield)))),
+                     IS_IN_DB(s, '%s.%s' % (usern,passfield),
+
error_message=self.messages.invalid_password))),
             sql.SQLField('new_password', 'password',
             label=self.messages.new_password,
             requires=self.settings.table_user[passfield].requires),


Sebastian E. Ovide


Sent from Dublin, Ireland

On Sun, Jul 19, 2009 at 7:28 PM,
sebastianovide+...@gmail.com<sebastianovide%2b...@gmail.com>
<sebastianov...@gmail.com> wrote:

>
> I have just tried and it is working fine for mismatched_password....
>
> but in case the old password is wrong the message is still "value not
> in database!"
>
> On Jun 25, 4:25 pm, mdipierro <mdipie...@cs.depaul.edu> wrote:
> > Try the trunk and the following customizations:
> >
> >         auth.messages.invalid_email = 'Invalid email'
> >         auth.messages.invalid_login = 'Invalid login'
> >         auth.messages.invalid_user = 'Invalid user'
> >         auth.messages.is_empty = "Cannot be empty"
> >         auth.messages.mismatched_password = "Password fields don't
> > match"
> >
> > Massimo
> >
> > On Jun 25, 7:35 am, "Sebastian E. Ovide" <sebastianov...@gmail.com>
> > wrote:
> >
> > > Hi,
> >
> > > Using Auth.change_password I noticed that if the 2 password do not
> match
> > > web2py is giving the message "invalid expression!" and if the password
> is
> > > not valid the message is "value not in database!". Is it possible to
> change
> > > those strings with some more user friendly ones ?
> >
> > > thanks
> >
> > > Sebastian E. Ovide
> >
> >
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to 
web2py+unsubscr...@googlegroups.com
For more options, visit this group at 
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to