Hmm, I see that the framework does add the T translator to the Validator
class, so validation messages should be getting translated. There is
nothing special about Auth extra_fields -- the validators you add there are
no different from the validators added to other fields.
Can you give an
Amazing piece of work. Congratulations!
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the
This looks fantastic. A great example of a fantastic real-world app developed
with Web2py. Great job!
John
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
Though that breaks backward compatibility, as the interface for custom
validators is provided in the official documentation.
On Friday, April 5, 2019 at 2:07:22 PM UTC-4, Leonel Câmara wrote:
>
> The way validators are in 2.18.4 you need to do it like this:
>
>
> class
The way validators are in 2.18.4 you need to do it like this:
class IS_MEMBERSHIP_YEAR_END(Validator)
:
def __init__(self, error_message='Not a membership year end'):
self.error_message = error_message
def validate(self, value):
yearend = datetime.date(2018,9,30)
All my other error messages (from built-in validators) are auto-translated.
Including for the default auth_user fields (eg. username). Only the
extra_fields are not.
Is there a fix?
sexta-feira, 5 de Abril de 2019 às 18:56:10 UTC+1, Anthony escreveu:
>
> Note, this is due to the recent
Note, this is due to the recent refactoring of all built-in validators
(moved from web2py to pydal). Previously, all default error messages were
translated, but that is no longer the case. Although the automatic
translation was not documented, I would still consider this a break in
backward
Created a ticket: https://github.com/web2py/web2py/issues/2170
On Thursday, April 4, 2019 at 4:52:37 PM UTC-4, David Manns wrote:
>
> The table in question has a field:
>
> Field('Paiddate', 'date', requires = [IS_EMPTY_OR(IS_DATE()),
> IS_EMPTY_OR(IS_MEMBERSHIP_YEAR_END())]),
>
> The custom
I have confirmed that it is indeed a bug in web2py.
If I add
T.force('pt')
before
auth.settings.extra_fields['auth_user'] = [ Field('pagination', 'integer',
default=9, label=T('Pagination'), notnull=True, required=True, requires=
IS_INT_IN_RANGE(5, 51), ), ]
the validation messages all
Just writing to thank Massimo and the Web2py community, for answering all
my questions here and also building this awesome framework.
I'm proud to say my application, https://www.viewbase.com, is live! I was a
total beginner and literally learnt everything about web development while
building
No, I think it is a web2py bug. I reported it in Git.
sexta-feira, 5 de Abril de 2019 às 15:57:30 UTC+1, Kevin Keller escreveu:
>
> Wow that must be annoying.
>
> Did you find any workaround?
>
> On Thursday, 4 April 2019 21:25:10 UTC+2, João Matos wrote:
>>
>> When creating extra fields for
Found a solution (more a kludge).
Added
next = '/'
to login function in tools.py
Line 2831
# next = replace_id(next, form)
next = '/'
redirect(next, client_side=settings.client_side
quarta-feira, 3 de Abril de 2019 às 15:59:28 UTC+1, João Matos
Could you create a ticket for this please?
https://github.com/web2py/web2py/issues
Thanks!
On Thu, Apr 4, 2019 at 10:52 PM David Manns wrote:
> The table in question has a field:
>
> Field('Paiddate', 'date', requires = [IS_EMPTY_OR(IS_DATE()),
> IS_EMPTY_OR(IS_MEMBERSHIP_YEAR_END())]),
>
Wow that must be annoying.
Did you find any workaround?
On Thursday, 4 April 2019 21:25:10 UTC+2, João Matos wrote:
>
> When creating extra fields for auth_user, the validation messages for
> those fields are always in English. They don't comply with the translations
> available.
>
> This
Good group, really helped me to advance my proeject so much quicker. In
fact, couldnt have gotten here without them. Thanks!
On Thursday, 4 April 2019 22:40:51 UTC+2, Ari Lion BR Sp wrote:
>
> Hey, Carlos, thanks for having created this group. Now I can solve my
> questions Live
>
> :-)
>
>
>
Hello everybody.
I ask you because I can’t make queries in my database with the DAL as I
wish.
Here my context. I have two tables like this:
db.define_table(‘spare_parts’,
Field('name',…),
Field(‘best_price’,…)
Field(‘best_delay’,…)
db.define_table(‘supplier_choice’,
I have this html code for a page. My buttons appear at the center bottom.
I would like them to appear elsewhere such as bottom corners.
How do I do this?
{{=A('Proceed', _class='btn btn-large
btn-info',_style="font-family: 'Audiowide';font-size:
17 matches
Mail list logo
