[Pagekit-users] (no subject)

[<a4a...@te...>]

This is yet another question related to the required_login property of a page. 
At one point Anton Berezin had a very interesting suggestion (refer to his
'Registered users-only site with PageKit' posting).  Certainly, I think
something like this is a natural extension of the framework.  As a further
suggestion, this change could be accomodated by simply altering config syntax to
allow setting global page properties by including respective attributes in the
root <PAGES> tag.  Like so:

<PAGES require_login="recent">
  <PAGE id="public_page" require_login="no"/>
</PAGES>   

This configuration basically tells that every page on the site is to be
protected except the public_page.  

Now, onto another somewhat related question...  I've set up my simple web site
based on the sample PageKit code.  I only made a few changes such as use MySQL
to store sessions and added a bunch of my own code to do new user signup and
other related work.  The trouble that I'm getting into now is with a 'protected'
page.  Inside my configuration I set the page's require_login property to
'recent'. At first this seemed to have worked fine.  Whenever I hit the page it
requested me to login, and once I was logged in, I could access the page. 
However, if I logged in by going to my main login form directly, hitting the
protected page afterwards I'd still be asked to login.  This is somewhat
puzzling to me.  I've been trying to debug my modules but couldn't dig right to
the root of the problem just yet.  

Any suggestions/help would be highly appreciated! :)