On Wed, Apr 24, 2002 at 06:00:44PM +0200, Pascal Van Hecke (Yahoo) wrote: > Hi, > > I want to build a user interface that is intertwined with the actual site > (see also old posting at > http://marc.theaimsgroup.com/?l=midgard-user&m=101216685605970&w=2). > What I mean is that authenticated users will surf and see the same site as > when non-authenticated, apart from extra links such as: > > "delete this article", > "update this article", > "create new topic"... > > The way I was planning to do this, was to make a separate login page with a > form, where I could set the MidgardLogin cookie. > According to the explanation in > http://www.midgard-project.org/manual/en/function.auth-midgard.php, "The > Midgard code will not see the difference between a user logged in by HTTP > authentication or the cookie login". I don't want to bother my slightly > technofobic users with authentication request popups. > > However, when visiting other pages of the site after login, it appears that > $Midgard->user is not set, although the cookie has been set... this even > shows as I refresh my login page, without doing the post, but by retyping > the URL. Authenticated pages must have auth property set on. It may sense to redesign your application so that it has two trees actually: one non-authenticated and second with authentication enabled. So users will come to the first one and browse pages as is but if page code sees appropriate cookies it does redirect to authenticated tree (for example, foo.mysite.com/dir1/ redirects to foo/mysite/auth/dir1 where page /auth/ is active (mirrors /dir1/ by loading and executing original /dir1/ code) and auth-enabled).
-- / Alexander Bokovoy Software architect and analyst // SaM-Solutions Ltd. --- I never met a woman I couldn't drink pretty. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
