<div>Thanks a lot indeed, Mats and Pete, both suggestions are fine. :) </div>
<div> </div>
<div>I think these would make a nice recipe at </div>
<div><a href="http://zope-cookbook.org">http://zope-cookbook.org</a></div>
<div> </div>
<div>Best, </div>
<div> Miklós</div>
<div><br>-- <br> Miklós Prisznyák<br> Principal Consultant, owner<br> <a href="http://www.jegenye.com">http://www.jegenye.com</a> <br><br> </div>
<div><span class="gmail_quote">2006/6/7, James Taylor <<a href="mailto:j.cole.taylor@gmail.com">j.cole.taylor@gmail.com</a>>:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Miklos,<br>It's also possible to just build your own login page, and associate it<br>with a particular content object interface. I routinely build a
<br>simple Folder derivative for my own site like class SiteBase(Folder),<br>so that it implements an interface that I can put a view in front of<br>by letting my for="my.app.interface.ISiteBase". That way you can set
<br>up your own login form to be associated with your particular site base<br>object, if you don't want the login page to have to service logins for<br>the whole of your zope3 instance, but just a particular subsite.<br><br>
Pete<br><br>On 6/7/06, mats.nordgren <<a href="mailto:mats@ronin-group.org">mats@ronin-group.org</a>> wrote:<br>><br>> Miklos,<br>><br>> You should be able to customize the form '<a href="http://loginform.pt">
loginform.pt</a>' from<br>> zope.app.authentication.browser. In the session credentials plugin you can<br>> then specify the new login form name.<br>><br>> Cheers,<br>><br>> Mats<br></blockquote></div>