sounds like a perfect solution
thank you!
p.s. I've made one enhancement: instead of fake email I created a catch-all
email for the domain, and will instruct the admin to specify a "real" email
for a new customer (like "customer.first_name.last_n...@mydomain.com") - it
will be a fake, of course
As far as I remember, it is possible add extra fields to auth_user table
+ you can make your own login form (phone/password)
+ you can retrieve record (and email that could be a fake) from auth_user,
using extra field (phone number) - db(auth_user.phone ==
form.vars.phone).select(auth_user.ema
seems to me that the ideal solution would be to allow an email field in
auth_user to contain something other than email (for example, a phone
number). but besides that I am not sure how to relax this requirement on
the email field in auth_user, this solution seems to be politically
incorrect, a
3 matches
Mail list logo
