I wrote some code here extending auth to create different sessions...
Then I could create here the second instance of Auth...
However I strongly think you are right... do all that code is not worth...
too much code and handling to solve a minor problem...
the field in the auth table is much more simple to implement... hahahaha
Also I think I`d found another bug while trying to create all this code...
To set a different login page I did this:
auth_admin.settings.login_url = URL('controller', 'user', args='login')
However if you put a wrong user and pass... it is redirecting back to the
original default/user function and not the customized login_url...
Em segunda-feira, 10 de junho de 2013 11h04min18s UTC-3, Anthony escreveu:
>
> I started a discussion about it here:
> https://groups.google.com/d/msg/web2py-developers/E9ug6m6WHhE/XkPjiojqTOIJ.
> I was thinking it might be possible to just specify a base prefix which
> would get used both to name the session object and to prefix all the table
> names (the default would be "auth", which would replicate the current
> behavior). I didn't look too deeply to see if anything else would be
> required, but feel free to give it a shot.
>
> Anthony
>
> On Monday, June 10, 2013 1:04:29 AM UTC-4, André Kablu wrote:
>>
>> Thanks again Anthony! It is a good alternative. ..
>>
>> However It would be very good if we could use 2 auth...
>> As you can see I'd changed table names...
>>
>> I'll study auth class in deep to see if i can extend it and change some
>> function to make it accept some parameter so it would be possible to set
>> what session to use...
>>
>>
--
---
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
