Hard to help you without seeing the cod or the error tickets. There should be no difference between auth in sqlite or mysql. You should not save auth info a different database else you lose the ability to join the auth_user table with other tables and that is often an important requirement.
On Thursday, 6 February 2014 06:38:26 UTC-6, Austin Taylor wrote: > > I've tried creating another app and authentication works fine there with > the sqlite database, but when I try to use my mysql instance I run into > error after error. > > Right now I have Login, Forgot Username and Lost Password when I hover > over the login button. I don't know how to get it back to the default of > just register/lost password/login. > > I have no idea where the code could be that messed up my registration. It > was initially working but I tried creating another registration script that > seems to have messed everything up. > > I tried removing the script and creating a new app and cloning the > models/controllers but the old registration form which request a username > still pops up. > > Any help would be greatly appreciated!! > -- 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 Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
