you meant to avoid 404 page? mmh, It does not seem to work..maybe I
misunderstood.
carlo
On 9 Apr, 17:07, mdipierro wrote:
> You can set
>
> auth.settings.on_failed_authorization = URL(...)
--
To unsubscribe, reply using "remove me" as the subject.
You can set
auth.settings.on_failed_authorization = URL(...)
On Apr 9, 7:02 am, Yarko Tymciurak
wrote:
> On Apr 9, 6:07 am, carlo wrote:
>
> > I think I have found the problem:
>
> :-) Yes, you did!
>
>
>
> > in the models folder I had 3 files: db.py, lastdb.py, menu.py.
> > Lastdb.py was an o
thank you, I knew all you said but I did not focus enough on the
"double" model issue oops!
About the 404 error page your link is broken but browsing the manual I
think you pointed me to the routes_onerror solution.
Thank you for bridging the execution stream clearly,
carlo
On 9 Apr, 14:02, Ya
On Apr 9, 6:07 am, carlo wrote:
> I think I have found the problem:
:-) Yes, you did!
>
> in the models folder I had 3 files: db.py, lastdb.py, menu.py.
> Lastdb.py was an old copy of db.py but, as far as I remeber, there was
> no "auth.settings.actions_disabled.append('register')" in it.
>
> Af
I think I have found the problem:
in the models folder I had 3 files: db.py, lastdb.py, menu.py.
Lastdb.py was an old copy of db.py but, as far as I remeber, there was
no "auth.settings.actions_disabled.append('register')" in it.
After I deleted lastdb.py it worked as expected: I think that
lastd
thank you all.
Thadeus:
in my model below the place Auth tables are created;
Massimo:
no I do not have my register action, everything is web2py Auth out of
the box.
Yarko:
Definitely not routes fault: I commented my routes but I still can
access the registration page.
I am down at debugging, lat
On Apr 8, 4:43 pm, carlo wrote:
> thank you Yarko for replying. Well it is really a strange behaviour, I
> am trying to isolate the problem.
Try with just a fresh app first - just a clone of "welcome" with auth
enabled, auth.requires_login() set for default/index, and not more.
Then try appendi
Do you have your own register action? If you do the append statement
would be ignored.
On Apr 8, 4:43 pm, carlo wrote:
> thank you Yarko for replying. Well it is really a strange behaviour, I
> am trying to isolate the problem.
>
> For now I have the feeling that my problem ha something to do wit
Where are you including auth.settings.actions_disabled.append('register') ?
-Thadeus
On Thu, Apr 8, 2010 at 4:43 PM, carlo wrote:
> thank you Yarko for replying. Well it is really a strange behaviour, I
> am trying to isolate the problem.
>
> For now I have the feeling that my problem ha som
thank you Yarko for replying. Well it is really a strange behaviour, I
am trying to isolate the problem.
For now I have the feeling that my problem ha something to do with
routes.py, this is my routing rule:
routes_in = (('/$f', '/init/default/$f'),)
routes_out = (('/init/default/$f', '/$f'),)
I've just tried this in both trunk, and 1.76.5, and in each I get a
"404 NOT FOUND" when I hit "register"...
Perhaps say more about what you are doing that you think this does not
work...
On Apr 8, 10:05 am, carlo wrote:
> Following the manual I put this statement in my model file but it
> seem
11 matches
Mail list logo
