I guess noone has experience with my particular problem. I traced through CookieCrumbler.py and found that modifyRequest() is raising CookieCrumblerDisabled. The caller __call()__ then catches this exception and returns silently. Why would my CookieCrumbler be disabled? I even deleted my Crumbler and created a new one and still got the same exception. I do see that sometimes disable_cookie_login__=1 gets appended to my URL when I try to login. Why does this happen? Is this related to my problem, even though I've seen this happen when my system was working properly? Thanks, Gordon
Gordon Lai wrote at 2004-10-19 18:11 -0700:
I guess noone has experience with my particular problem. I traced through CookieCrumbler.py and found that modifyRequest() is raising CookieCrumblerDisabled. The caller __call()__ then catches this exception and returns silently. Why would my CookieCrumbler be disabled?
Because the "login page" entry in its configuration is empty? -- Dieter
Eureka! No, it's been filled from the beginning, but your suggestion made me think further: I had been using an older CookieCrumbler where the login and logout pages reside alongside the CC object. After the problem began, I upgraded CC to 1.24 and saw that when I allowed it to create default login/logout pages, the pages were created within the CC object, as if the CC object was a directory. I tried specifying "../login.html" but that didn't seem to work. Your note prompted me to move my pages into the CC object and it now works. Thanks a lot! Gordon Dieter Maurer wrote:
Gordon Lai wrote at 2004-10-19 18:11 -0700:
I guess noone has experience with my particular problem. I traced through CookieCrumbler.py and found that modifyRequest() is raising CookieCrumblerDisabled. The caller __call()__ then catches this exception and returns silently. Why would my CookieCrumbler be disabled?
Because the "login page" entry in its configuration is empty?
participants (2)
-
Dieter Maurer -
Gordon Lai