Problem with login not lasting after page refresh

40 views
Skip to first unread message

monotasker

unread,
Oct 3, 2011, 12:04:11 PM10/3/11
to web...@googlegroups.com
I've got an alpha-stage language quizzing app at paideia.fluxflex.com that requires auth login for pretty well every controller to track students' performance. But today when I pushed new changes to the server the login no longer lasts past any page refresh. Even an ajax refresh of a component returns a "login" link instead of the expected contents. This affects the admin interface too, where I'm prompted for my admin login on every action (i.e., page refresh). But this only happens on the public server. When I run the app locally (on the rocket server) I have no problems. I've had a lot of minor trouble with fluxflex, so I'm not sure if this is a server-level problem or whether I've somehow introduced a bug. Any idea what would cause this kind of behaviour?

(I'm a bit panicked here because my students are supposed to be using the app! That's what I get for trying to use a devel site in a class.)

Thanks.

pbreit

unread,
Oct 4, 2011, 12:31:16 AM10/4/11
to web...@googlegroups.com
Might need to see some code. I went to your site and tried to register, login and reset password and the pages just seem to refresh without doing anything. Can you summarize the nature of the changes you made? Are you using version control?

MidGe

unread,
Oct 4, 2011, 1:11:14 AM10/4/11
to web...@googlegroups.com
monotasker,

I experience a similar problem but not on fluxflex, on webfaction, and, in my case it seems related to uswgi use.

I noticed also that the web2py logo (top left) is duplicated as if I was in a recursive mode when another logging is required (almost all pages).

Hope this help

monotasker

unread,
Oct 4, 2011, 1:58:37 PM10/4/11
to web...@googlegroups.com
I'm using git but none of the changes I made had anything to do with auth. I ended up pushing the app (identical code) to another fluxflex project (http://ianwscott.fluxflex.com/Paideia) and the login works fine. So it looks like the issue wasn't with my code update but with something on the server. I also re-initialized the faulty project with a new web2py installation on a cleaned directory, but had the same problem. So somehow there seems to be a server-level issue with that project. Unfortunately servers are largely a mystery to me, so I'm not sure how to go about fixing it. Thanks, though.

monotasker

unread,
Oct 4, 2011, 1:59:09 PM10/4/11
to web...@googlegroups.com
That confirms my conclusion that the issue it must be at the server level. Thanks.
Reply all
Reply to author
Forward
0 new messages