After "playing" a while with web2py, i think i've found a very
interesting platform for solid and rapid web applications. But i have
to
port existing applications to web2py. I want to keep the authorisation
process for the users of these applications, wich is done by:
Login: XX
Password: Y
uses email and
password for the login process. If possible, i don't want to
confrontate my current users with a new login scheme/procedure.So my
question is, can this be easily done?
Greetings,
Paul (captainy)
On 26 Mai, 03:58, mdipierro wrote:
> I think you need to tell us more about the c
suggest you rename the login_name as 'username' and you replace its
> label with 'login_name'. web2py knows how to handle a username.
>
> On May 26, 11:44 am, captainy wrote:
>
> > Thanks Massimo,
> > thanks Yannick
>
> > sorry, it was my fault. Wha
suggest you rename the login_name as 'username' and you replace its
> label with 'login_name'. web2py knows how to handle a username.
>
> On May 26, 11:44 am, captainy wrote:
>
> > Thanks Massimo,
> > thanks Yannick
>
> > sorry, it was my fault. Wha
suggest you rename the login_name as 'username' and you replace its
> label with 'login_name'. web2py knows how to handle a username.
>
> On May 26, 11:44 am, captainy wrote:
>
> > Thanks Massimo,
> > thanks Yannick
>
> > sorry, it was my fault. Wha
to handle a username.
>
> On May 26, 11:44 am, captainy wrote:
>
> > Thanks Massimo,
> > thanks Yannick
>
> > sorry, it was my fault. What i'm talking about is authentication, not
> >authorisation. Perhaps it was little bit late last night...
> > So,
Hey Anthony,
i've tried this recipe and it works. In my opinion it's a common task in
modern web development to upload files in the "ajax-way". My problem is, as
with as other recipes in the book, the modification of a core file of the
web2py framework. What happens, if we do an update to a new
7 matches
Mail list logo
