Beside adding extra field, is it possible to split the table for auth_user?
For example, I want the profile to be broken in different tables based on
address, education, portfolio...etc. that someone can create a profile. And
add fields to that tables as that person see fit.
On Wednesday, De
Thanks a lot Massimo, in fact I've made testing on an existing user. Now
with requires=IS_NOT_EMPTY() the form ask to fill the company field.
Perfect.
For problem 2 I'm gone define my own auth_user table, have a nice day.
Il giorno mercoledì 4 dicembre 2013 16:29:14 UTC+1, Massimo Di Pierro ha
I cannot reproduce problem 1. There is nothing wrong in your code and
something else is causing the problem. Are you sure the issue is that "A
user can register without filling this field." or is it the users who
registered before the contraint was introduced do not have a company field?
Proble
Thanks James but also required=True don't have any effect. Perhaps I have
to make a custom form or register, do you know I can do it ?
Il giorno martedì 3 dicembre 2013 19:56:39 UTC+1, James Burke ha scritto:
>
> For problem no1, you could try using required=True instead of
> requires=IS_NOT_EM
For problem no1, you could try using required=True instead of
requires=IS_NOT_EMPTY()
For your second problem you can define the auth_user table yourself (from
web2py book):
Another way to do this, although not really recommended, consists of
defining your auth tables yourself. If a table is d
5 matches
Mail list logo
