ok, i finally found what was wrong. i didn't realize there were two such
settings. i was using the profile_fields and testing it on the register
screen. so, i have this now under the db.py model:
auth.settings.register_fields = ['prefix_title', 'first_name', 'last_name',
'gender', 'birthdate
Definitely works for me. Are you using the built-in Auth profile
functionality? If so, you'll have to do some debugging -- check
/gluon/tools.py around line 3646 (where the profile form is created and
auth.settings.profile_fields is passed to SQLFORM.
Note, you can also create a custom form in
On Monday, April 8, 2019 at 10:11:33 AM UTC-4, lucas wrote:
>
> students log into this site i've had. and they type all kinds of crazy
> stuff. i don't want to preserve what the students type because students
> are inconsistent when they login. so i want to force it to lowercase so at
> least
>
> because students are inconsistent
>
Ahahaha if it was only students our lives would be much easier.
On a more serious note, although most email systems are case insensitive
nowadays it is allowed by the RFC to be case sensitive so it can be a
different email. In the real world, I had t
and i also update web2py from 2.17 to 2.18.5, just in case.
On Monday, April 8, 2019 at 10:20:27 AM UTC-4, lucas wrote:
>
> i tried this before and after auth.define_tables and it had no effect:
>
> auth.settings.profile_fields = ['prefix_title', 'first_name', 'last_name',
> 'gender', 'birthdate'
i tried this before and after auth.define_tables and it had no effect:
auth.settings.profile_fields = ['prefix_title', 'first_name', 'last_name',
'gender', 'birthdate', 'zip', 'email']
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (
students log into this site i've had. and they type all kinds of crazy
stuff. i don't want to preserve what the students type because students
are inconsistent when they login. so i want to force it to lowercase so at
least i know what is definitely stored in the db.
--
Resources:
- http://
auth.settings.profile_fields = ['prefix_title', 'first_name', 'last_name',
...]
Anthony
On Monday, April 8, 2019 at 9:38:06 AM UTC-4, lucas wrote:
>
> hello one and all,
>
> i'm using web2py 2.17>.
>
> what is the best method to change the field order on the view's
> user/profile and user/regis
That's already the default behavior. If you wanted to preserve the case
entered by the user, you would do:
auth.settings.email_case_sensitive = True
Anthony
On Monday, April 8, 2019 at 9:40:52 AM UTC-4, lucas wrote:
>
> hello one and all,
>
> i'm using web2py 2.17>.
>
> what is the best method
I have defined the auth_table. And it does have username=True
But actually this makes me belatedly think, the issue could be related to
the various ways I am attempting to get the custom table to work with
registration, and the multiple db changes that are occurring as I play
around. So I thin
I notice in another thread you indicated you have a custom auth_user table.
Presumably you either have not defined the auth_user table at this point in
the code, or you have named it something else.
Anthony
On Tuesday, June 5, 2018 at 3:38:40 PM UTC-4, b.l. masters wrote:
>
> Hi
>
> I am using
Also does your define_tables call have a username=True keyword arg?
--
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
Is this running before auth.define_tables?
--
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 Goo
On Saturday, August 26, 2017 at 8:43:56 AM UTC-4, 黄祥 wrote:
>
> had you already tried ?
> *e.g. not tested*
> # after auth.define_tables()
> db.auth_user.email.unique = False
> or
> auth_table.email.unique = False
>
The issue is the IS_NOT_IN_DB validator, not the "unique" attribute (the
latter a
On Saturday, August 26, 2017 at 8:24:40 AM UTC-4, Andrea Fae' wrote:
>
> Hello, is it possible to get email field in auth_user table not unique? I
> don't use email form accessing but username.
> I don't want to create a custom auth_user table if it's possible.
>
You can do something like:
db.au
had you already tried ?
*e.g. not tested*
# after auth.define_tables()
db.auth_user.email.unique = False
or
auth_table.email.unique = False
if not work perhaps you can custom auth_table
ref:
http://web2py.com/books/default/chapter/29/09/access-control#Customizing-Auth
best regards,
stifan
--
Re
hey Anthony, yes I tried that and it worked in safari, chrome, and IE, but
not in Firefox. further research and testing many many suggestions later.
I came up with in the view, which essentially puts the value back to the
original after autocomplete does its little mess:
{{block head}}
jQuer
This might be of interest:
https://developer.mozilla.org/en-US/docs/Web/Security/Securing_your_site/Turning_off_form_autocompletion
On Tuesday, April 11, 2017 at 8:43:55 PM UTC-4, lucas wrote:
>
> hello one and all,
>
> I'm not sure of the mechanism here. using SQLFORM on auth_user table and
>
It's kind of a lost battle because browsers decided they don't want
websites to control autocomplete, which is really annoying sometimes, right
now my technique to avoid autocomplete includes hidden fields and stupid
values for the autocomplete attribute. Anyway you're not getting the
element y
Hi Anthony, thanks again for taking time out to explain and answered below
questions. I did define the customer table before auth tables were created
and used lazy_tables=False, it works this time when I put all the tables in
a single database without using CAS (i do need to share group/membersh
>
> 1st question: i want to use auth_user table to store my internal staffs
> and external customers info, so that I can leverage all the built-in
> authentication and authorisation functions provided by web2py out of the
> box (please let me know if I should not do that). I added some fields i
On Tuesday, May 31, 2016 at 4:24:20 AM UTC-4, Pierre wrote:
>
> I am trying to optimize things: I don't need to store anything in the
> session so I thought I could apply session.forget() once and that would be
> true for all application controllers functions
>
You must call session.forget() so
I am trying to optimize things: I don't need to store anything in the
session so I thought I could apply session.forget() once and that would be
true for all application controllers functions
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/
On Monday, May 30, 2016 at 6:56:30 AM UTC-4, Pierre wrote:
>
> Does *session.forget() *affects the way users
> login/logout/signup..etc ?
>
> should *session.forget() * be placed in every controller function or is
> there a way to apply it globally ?
>
Not sure what you're getting at with r
Does *session.forget() *affects the way users login/logout/signup..etc ?
should *session.forget() * be placed in every controller function or is
there a way to apply it globally ?
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (
oups.this was a bad idea. I will never do it again
I didn't know auth_user was so "ticklish" (especially under the arms)it
probably depends on the current user...
thanks Anthony
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/w
When a user is logged in, the user record (i.e., auth.user) is stored in
the session -- it does not get updated from the database on every request,
as that would require too many database hits. It will be updated the next
time that user logs in.
Anthony
On Sunday, May 29, 2016 at 2:43:02 PM UT
On Wednesday, April 6, 2016 at 2:06:11 AM UTC-4, Mark Graves wrote:
>
> Hey everyone,
>
> I saw a random bug in an app I'm working on, and I was wondering what the
> correct approach is.
>
> I have auth.settings.extra_fields["auth_user"] = [LIST_OF_FIELDS]
>
> later, I select that row and get it a
how to set string size in sql form
db.define_table('stud_personal',
Field('phone_no',string(10), requires=IS_NOT_EMPTY()))
is it correct?
On Thu, Mar 24, 2016 at 7:21 AM, Michael Beller wrote:
> yes - I think something like this could/should work:
>
> db.auth_user.first_name.
Sounds like it could be a cookie or session issue. Can you try using your
site from an incognito window?
--
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)
---
yes - I think something like this could/should work:
db.auth_user.first_name.readable = False
On Wednesday, March 23, 2016 at 8:49:42 PM UTC-4, Jerry Liu wrote:
>
> Thanks! It worked!
>
> I also want to hide First and Last Name fields. At least, I don't want
> them to be shown on the registrat
Thanks! It worked!
I also want to hide First and Last Name fields. At least, I don't want them
to be shown on the registration page. Any ideas?
On Wednesday, March 23, 2016 at 5:43:14 PM UTC-7, Michael Beller wrote:
>
> no changes should be required to any controller or view. Everything is
> h
no changes should be required to any controller or view. Everything is
handled by the line:
return dict(form=auth())
in the default controller (in combination with the default/user.html).
The line in db.py just tells auth whether to use a username or email.
On Wednesday, March 23, 2016 at 8:16
Not sure if I understood, you mean I still have to make changes on View and
Controller, right?
because adding this line doesn't change anything on login and registration
views.
On Wednesday, March 23, 2016 at 4:12:49 PM UTC-7, Michael Beller wrote:
>
> It's easier than that ... just change usern
It's easier than that ... just change username=True in db.py, all the
web2py components (e.g., log in form, auth_user table, log in menu, etc.)
will now support username ...
auth.define_tables(username=True, signature=True)
On Wednesday, March 23, 2016 at 5:46:38 PM UTC-4, Jerry Liu wrote:
>
You do not need another controller in my opinion. You can simply do:
def user():
if request.args(0)=='register':
response.files.append(URL('static','js/deal-with-fields.js'))
return dict(form=auth())
and then you put what you need in the deal-with-fields.js
On Friday, 31 July 2015 08:
Hi Derek,
Ive tried and its working...
Thanks (see attached)
i will just have to create a separate user registration view and not use
the default 'user/register' to have this function in my auth_user
registration
Thanks...
On Friday, July 31, 2015 at 2:30:56 PM UTC+8, Derek wrote:
> You w
Hi Massimo
On Wednesday, July 29, 2015 at 6:30:18 AM UTC+8, Wabbajack wrote:
> I have created a *factory,department,section and team* table in the
> database
> and a *factory* is on a *one to many* relationship with *department*
> a *department* is on a *one to many*
You will want to take a look at my example here:
http://www.web2pyslices.com/slice/show/1724/cascading-dropdowns-simplified
let me know if you have questions. You should be able to easily extend it
to do multi level cascading.
On Tuesday, July 28, 2015 at 3:30:18 PM UTC-7, Wabbajack wrote:
>
>
The problem is that what you want to do cannot be resolved server side. You
want the team dropdown to depend on the section, the section dropdown to
depend on the department, and the department dropdown to depend on the
factory.
There is no web2py syntax to do this because there is no way to ge
Ifigured out that the function worked because I defined the auth_user table
myself,
since this is not recommenden I customized the table by adding extra fields.
In my self defined table I had tthe following password field:
Field('password', type='password', length=512,
requires=[IS_STRONG(),CRY
done.
https://github.com/web2py/web2py/issues/904
thanks and best regards,
stifan
On Wednesday, April 8, 2015 at 7:44:21 PM UTC+7, Massimo Di Pierro wrote:
>
> can you please open a github ticket and reference this thread?
>
> On Monday, 6 April 2015 22:17:03 UTC-5, 黄祥 wrote:
>>
>> done.
>> https
can you please open a github ticket and reference this thread?
On Monday, 6 April 2015 22:17:03 UTC-5, 黄祥 wrote:
>
> done.
> https://github.com/web2py/web2py/issues/904
>
> attached that running fine (shown a format instead of an id) in prev
> version
>
> thanks and best regards,
> stifan
>
--
done.
https://github.com/web2py/web2py/issues/904
attached that running fine (shown a format instead of an id) in prev version
thanks and best regards,
stifan
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://cod
Hmm, I'm not sure what changed, but if it used to work, we should fix it.
Please submit an issue about this.
Anthony
On Monday, April 6, 2015 at 10:19:14 PM UTC-4, 黄祥 wrote:
>
> in the previous version, the same code can show the proper format of
> auth_user table, yet in the newest version can
in the previous version, the same code can show the proper format of
auth_user table, yet in the newest version can't. already test another
table too, it didn't showed the proper format in grid table (just show the
id instead of the proper format). or in the newest version the policy is
changed
Yes, as I mentioned, because you cannot set db.auth_user._format before
defining the other tables, you instead have to explicitly change the
"represent" and "requires" attributes of the other tables after they have
been defined. We should probably add a setting for db.auth_user._format to
avoid
yes, you are right, i defined the custom_auth after auth.define_tables(),
but the problem is when i put it before auth.define_tables() it return an
error
*e.g. no error but the result is not expected*
auth = Auth(db)
audit_from = db.Table(db, 'audit_from',
Field('created_from', default = req
For the "format" attribute to affect the "represent" attribute of linked
reference fields, it must be set before those reference fields are defined.
If you are setting the auth_user "format" attribute after calling
auth.define_tables(), then the auth_event table has already been defined.
Instea
Can you explain further what you are observing. I don't see how that code
could affect any data in your database table.
Anthony
On Wednesday, February 25, 2015 at 8:15:14 AM UTC-5, Gael Princivalle wrote:
>
> Thanks Anthony.
>
> But if I replacing my code with your suggested code I have crashed
Thanks Anthony.
But if I replacing my code with your suggested code I have crashed the
table:
discounts.table appears corrupted
db.define_table('discounts',
Field('user_id', 'reference auth_user', requires = IS_IN_DB(
db, db.auth_user.id,
lambda r: '%s %s' % (
The third argument to IS_IN_DB is the label argument, which can either be
Python string formatting (to which the Row object will be passed) or a
function that takes a Row object. You cannot use arbitrary Python code
inside Python string formatting. Try:
IS_IN_DB(db, db.auth_user.id,
la
I removed wizard from extra filed.
At least there is only one record inserted into organization table (before
that it inserted two), but wizzard still returns 0
On Thursday, February 12, 2015 at 11:28:20 AM UTC+1, mcamel wrote:
>
> Hi,
>
> It seems wizard is returning id=0 instead of the actual
Hi,
It seems wizard is returning id=0 instead of the actual organization id.
Try removing the wizard from extra fields to guess more.
Just in case, you can try this other syntax:
auth.settings.register_onvalidation.append(lambda form: add_organization(
form))
Regards.
El jueves, 12 de f
>
> Define it as Field('country', 'reference country') instead of
>> Field('country', db.country) -- the latter won't work if db.country hasn't
>> been defined yet.
>>
>
> Should I use 'reference table' instead of db.table in all table
> definitions or just in the definition of tables that refe
Hi Anthony,
Define it as Field('country', 'reference country') instead of
> Field('country', db.country) -- the latter won't work if db.country hasn't
> been defined yet.
>
Should I use 'reference table' instead of db.table in all table definitions
or just in the definition of tables that refe
>
> i like to ask the user for his country. So I added a field country to the
> auth_user table. but I like it to be a referenz to db.country which I
> define later in the db.py file. for some reason I get an error message when
> trying to do that.
>
Define it as Field('country', 'reference co
Actually, I'm not sure that is the problem. Are you getting a specific
error message? Can you show the auth_user and db.country code you are using?
On Friday, April 6, 2012 1:22:52 PM UTC-7, pbreit wrote:
>
> I think you need to make sure the auth tables is created before the
> db.country table
I think you need to make sure the auth tables is created before the
db.country table with this line:
auth.define_tables()
I'll try that.
On Jan 4, 12:46 pm, Anthony wrote:
> I just created a fresh app with the wizard and set
> registration_requires_approval=True (and removed the registration_id
> validator), and I had no problem registering, removing the "pending", and
> then logging in, so I'm not sure why you were
I just created a fresh app with the wizard and set
registration_requires_approval=True (and removed the registration_id
validator), and I had no problem registering, removing the "pending", and
then logging in, so I'm not sure why you were having a problem (are you
sure you entered the correct
I just created a basic application (Not using wizard), it appears that
the aforementioned functions are working.
I was just able to register, and cleared the pending registration key
and logged in. So it seems this might all be
pointing to the wizard. Not sure where/why. I'm migrating settings
f
I just created a new app using the app wizard. There is the auth.key
file in the private folder. I then registered, had to remove the
requires for the registration id field in the models/db.py file. I
was able to modify the record for myself and remove the 'pending' for
registration_key field.
>
> Bad news is that I still can't log into the application.
> I'm now getting 'Invalid Login' when I try to login after verifying
> the registration. Grr..
>
This line:
auth = Auth(db, hmac_key=Auth.get_or_create_key())
reads the auth hmac_key from the "auth.key" file in the /private folder
It's on the Registration Id field. This field is blank.
I removed all requires. Good news is that I can now update the
record. Bad news is that I still can't log into the application.
I'm now getting 'Invalid Login' when I try to login after verifying
the registration. Grr..
On Jan 4, 11:29 am
When an error occurs with a form submission, the form should be
re-displayed with an error message attached to the field that caused the
error. Where is the error being displayed? I notice you have
db.auth_user.registration_id.requires = IS_NOT_IN_DB(...). If the
registration_id field is left
I get it on any field. As soon as I hit submit, I get that error and
no updating takes place.
Here is my model db.py:
from gluon.tools import Auth, Crud, Service, PluginManager, prettydate
auth = Auth(db, hmac_key=Auth.get_or_create_key())
crud, service, plugins = Crud(db), Service(), PluginManag
I cannot reproduce this problem. Do you get the "value already in database
or empty" message specifically on the registration_key field, or on the
email or username field? Have you set any validators for
db.auth_user.registration_key (you can check by printing
db.auth_user.registration_key.requ
Thank you very much.
BC
On 5 nov, 18:00, Anthony wrote:
> On Saturday, November 5, 2011 12:15:02 PM UTC-4, Bianca Cadaveri wrote:
>
> > May I ask one more question ?
>
> > > web2py will pass the Row object for the record as the dictionary (the
> > Row class inherits from dictionary, so functions
On Saturday, November 5, 2011 12:15:02 PM UTC-4, Bianca Cadaveri wrote:
>
> May I ask one more question ?
>
> > web2py will pass the Row object for the record as the dictionary (the
> Row class inherits from dictionary, so functions as a dictionary in
> this
> case)
>
Several rows (i.e., the r
it is a list of dictionaries.
http://zerp.ly/rochacbruno
Em 05/11/2011 14:15, "Bianca Cadaveri" escreveu:
> May I ask one more question ?
>
> > web2py will pass the Row object for the record as the dictionary (the
> Row class inherits from dictionary, so functions as a dictionary in
> this
> cas
May I ask one more question ?
> web2py will pass the Row object for the record as the dictionary (the
Row class inherits from dictionary, so functions as a dictionary in
this
case)
When several rows are returned from a database query, is the result a
dictionnary of dictionnaries ? I thank you in
Thank you Anthony !!!
BC
On 4 nov, 01:52, Anthony wrote:
> On Thursday, November 3, 2011 8:31:10 PM UTC-4, Bianca Cadaveri wrote:
>
> > Thank you very much to both of you.
>
> > Is this way to write formats specific to Web2py : '%(first_name) %
> > (last_name) (%(id))' ?
>
> > I have never met b
On Thursday, November 3, 2011 8:31:10 PM UTC-4, Bianca Cadaveri wrote:
>
> Thank you very much to both of you.
>
> Is this way to write formats specific to Web2py : '%(first_name) %
> (last_name) (%(id))' ?
>
> I have never met before "%" followed by "()".
>
> It means : write "first_name last_
Thank you very much to both of you.
Is this way to write formats specific to Web2py : '%(first_name) %
(last_name) (%(id))' ?
I have never met before "%" followed by "()".
It means : write "first_name last_name" corresponding to "id", right ?
BC
On 3 nov, 22:40, Anthony wrote:
> If you specif
If you specifically want the username from the auth_user table:
db(db.auth_user.id==id).select().first().username
or the shortcut version:
db.auth_user[id].username
If you want to use the 'format' attribute of the auth_user table (which I
think defaults to '%(first_name) %(last_name) (%(id))',
On Sunday, October 23, 2011 11:20:40 AM UTC-4, lucas wrote:
>
> yes, putting the requires under the field worked great, thanx.
>
> well, i tried to just change the natural/ordinal order of the columns/
> fields in the database (postgresql in my case) but that didn't work.
>
Right. The forms will
yes, putting the requires under the field worked great, thanx.
well, i tried to just change the natural/ordinal order of the columns/
fields in the database (postgresql in my case) but that didn't work.
how can i direct the register/profile of auth to another view and how
do i customize that view
On Sunday, October 23, 2011 9:33:34 AM UTC-4, lucas wrote:
>
> hello one and all,
>
> playing with auth_user. trying to follow the manual with a bit of
> modification, thinking:
>
> auth = Auth(db)# authentication/
> authorization
> auth.settings.extra_fields['
@Bruno,
> are you creating the form object before or after this?
> You need to specify attributes before the creation of the form object.
Thanks for your reply, you were right, I had to put the lines of code
before form=
This works:
def user():
if request.args(0)=='profile':
Search the group for "broken migration".
This is happening to ALL of my tables. What am I missing here?
--Greg
On Aug 18, 10:25 am, Gregory Hellings wrote:
> I was using the following db.py (http://pastie.textmate.org/2389614)
> and db_auth.py (http://pastie.textmate.org/2389616) files in a project
> successfully in 1.95.*. When I up
It worked out, thanks! Thread closed.
2011/6/9 Anthony
> On Thursday, June 9, 2011 6:59:34 PM UTC-4, Thiago wrote:
>>
>> I have this auth_user table, and another table called activities. This
>> activities have 2 fields that are foreing keys to user (created by and
>> modified by). If I delete a
On Thursday, June 9, 2011 6:59:34 PM UTC-4, Thiago wrote:
>
> I have this auth_user table, and another table called activities. This
> activities have 2 fields that are foreing keys to user (created by and
> modified by). If I delete any user that created or modified one activity,
> the activit
I have this auth_user table, and another table called activities. This
activities have 2 fields that are foreing keys to user (created by and
modified by). If I delete any user that created or modified one activity,
the activity is deleted.
Do I have to put NO ACTION in all fields that is foreign
On Thursday, June 9, 2011 2:14:59 PM UTC-4, Thiago wrote:
>
> I'm new to web2py, but familiar to similar frameworks. I have a system that
> uses web2py builtin auth_user table. The problem is that I wanna use
> ondelete='NO ACTION' in my app (it is CASCADE by default), and I don't
> know how to
this should do it
Field('name','reference othertable',ondelete='NO ACTION')
On Jun 9, 1:14 pm, Thiago Carvalho D' Ávila
wrote:
> Hi,
>
> I'm new to web2py, but familiar to similar frameworks. I have a system that
> uses web2py builtin auth_user table. The problem is that I wanna use
> ondelete=
On Tuesday, April 12, 2011 12:01:26 PM UTC-4, Bob wrote:
>
> Thanks Anthony
>
> Hiding with javascript will not work because it will get submitted
> with javascript.
If you use an update form, the hidden password field should be
pre-populated, so when you submit, it shouldn't replace the pas
Thanks Anthony
Hiding with javascript will not work because it will get submitted
with javascript. But I will try the readable/writable trick, thanks
Bob
On Tuesday, April 12, 2011 9:59:00 AM UTC-4, Bob wrote:
>
> 2. In similar situation using SQLFORM. When updating the user it's
> logical to leave the password blank in case you don't want to change
> it. But SQLFORM crypts the blank and changes the password in the DB
If you pass the record id
On Tuesday, April 12, 2011 9:59:00 AM UTC-4, Bob wrote:
>
> Hello, could someone answer a couple of questions:
>
> 1. Is it possible to manually crypt the password in the same way that
> crud() does it?
> The reason is that I need to manually update the user with
> db().update() and can't use
Oh, shoot, I figured that might be the answer but only had
"register_onaccept" in my list.
I ended up writing a function since it seems assignments in lambdas are
difficult. I tried setattr() and a nested function to no avail. Any ideas?
def set_paypal_email(form):
form.vars.paypal_email=fo
auth.settings.register_onvalidation=lambda form:
manipulate_form_before_insert(form)
On Mar 24, 2011, at 6:06 PM, pbreit wrote:
> OK, I see. Is there some way to intercept the user/register form.accepts to
> set that default?
OK, I see. Is there some way to intercept the user/register form.accepts to
set that default?
default does a take a lambda but one without arguments, because the info is
used before the form is submitted so there is no data (r).
On Mar 24, 2011, at 5:30 PM, pbreit wrote:
> I don't think that's quite the behavior I'm looking for. I want it to 1)
> default.paypal_email=email upon regist
I don't think that's quite the behavior I'm looking for. I want it to 1)
default.paypal_email=email upon registration and 2) both email and
paypal_email editable independently in Edit Profile.
So this would be perfect:
Field('paypal_email', length=128, default=lambda r: r.email))
But
Field('paypal_email', length=128, writable=False, compute=lambda r:
r.email))
On Mar 24, 1:38 am, pbreit wrote:
> I can't seem to figure out a (good) way to have one of my auth_user fields
> default to another auth_user field. I only want the default to take place
> once so not "compute".
>
> I t
Thank for your help!
On Feb 11, 7:19 pm, mdipierro wrote:
> make sure you ALWAYS pass
>
> CRYPT(auth.setting.hmac_key)
>
> to CRYPT.
>
> On Feb 11, 9:50 am, aure wrote:
>
> > Hi everyone,
>
> > I have customised my table for authentificaition, as shown by Massimo
> > here:http://groups.google.co
make sure you ALWAYS pass
CRYPT(auth.setting.hmac_key)
to CRYPT.
On Feb 11, 9:50 am, aure wrote:
> Hi everyone,
>
> I have customised my table for authentificaition, as shown by Massimo
> here:http://groups.google.com/group/web2py/browse_thread/thread/f4ae0f4c5b...
>
> If I put CRYPT() before
99 matches
Mail list logo
