<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Steve wrote:
<blockquote cite="mid4506EAFF.3070903@shic.co.uk" type="cite">I'm just
starting to look at Zope as a potential platform to implement a simple
authenticated web site... however I do not want to face users with the
standard web-browser dialogue, but rather my own log-in page. I've
established how to restrict access based upon permissions etc... and
I'm able to set/reset cookies based a form submission - but do not see
how to integrate an HTML login page with the standard Zope security.
<br>
<br>
I've read that I should use the "Cookie Crumbler" product... but after
I've added this to the folder that I intend to protect, I click on
cookie_authentication (the default name for the "Cookie Crumbler"
object) and I get the following error message:
<br>
--
<br>
<br>
An error was encountered while publishing this resource.
<br>
<br>
*Error Type: AttributeError*
<br>
*Error Value: aq_parent*
<br>
<br>
--
<br>
<br>
Is this a bug with "Cookie Crumbler" (version 0.3 downloaded from
zope.org used against Zope 2.9.4, python 2.4.3, win32)?
<br>
Am I barking up the wrong tree in hoping to have a slick-looking
"logon" page? Is this something commonly done using Zope? Is "Cookie
Crumbler" the right product? Would I be better hand-coding this
myself?
<br>
<br>
<br>
</blockquote>
Steve,<br>
Thats a weird one ... but cookie crumbler is great to get custom
login forms<br>
Did you try deleting it and adding another (cookie_authentication
object)<strong></strong> Maybe you added a property thats
non-existent? (login page id or something?)<br>
<br>
you can produce a fuller error traceback <br>
<br>
If necessary add<br>
<dtml-var error_tb><br>
to your standard_error_message (if using dtml) for a clearer error
expression<br>
<br>
<br>
<br>
<br>
<br>
<br>
</body>
</html>