From philipp at weitershausen.de Sun Oct 7 19:44:12 2007 From: philipp at weitershausen.de (Philipp von Weitershausen) Date: Sun, 07 Oct 2007 19:44:12 +0200 Subject: [z3-five] Retiring this list Message-ID: Since Five has been an integral part of Zope 2 for three releases now, and Zope 2 development is pretty much driven by the Five effort (bringing the Zope 3 libraries to Zope 2), I propose to retire this list. It hasn't seen much traffic lately anyway. Messages about the development *of* Five should go to the zope-dev at zope.org instead, where we will likely soon also be discussing Zope 3 matters. Messages about the work *with* Five should to go zope at zope.org or zope3-users at zope.org if they concern a particular Zope 3 library. Silence is assent. -- http://worldcookery.com -- Professional Zope documentation and training From plone at hannosch.info Sun Oct 7 19:48:20 2007 From: plone at hannosch.info (Hanno Schlichting) Date: Sun, 07 Oct 2007 19:48:20 +0200 Subject: [z3-five] Retiring this list In-Reply-To: References: Message-ID: Philipp von Weitershausen wrote: > Since Five has been an integral part of Zope 2 for three releases now, > and Zope 2 development is pretty much driven by the Five effort > (bringing the Zope 3 libraries to Zope 2), I propose to retire this > list. It hasn't seen much traffic lately anyway. > > Messages about the development *of* Five should go to the > zope-dev at zope.org instead, where we will likely soon also be discussing > Zope 3 matters. Messages about the work *with* Five should to go > zope at zope.org or zope3-users at zope.org if they concern a particular Zope > 3 library. +1 From optilude at gmx.net Sun Oct 7 19:53:23 2007 From: optilude at gmx.net (Martin Aspeli) Date: Sun, 07 Oct 2007 18:53:23 +0100 Subject: [z3-five] Retiring this list In-Reply-To: References: Message-ID: Philipp von Weitershausen wrote: > Since Five has been an integral part of Zope 2 for three releases now, > and Zope 2 development is pretty much driven by the Five effort > (bringing the Zope 3 libraries to Zope 2), I propose to retire this > list. It hasn't seen much traffic lately anyway. > > Messages about the development *of* Five should go to the > zope-dev at zope.org instead, where we will likely soon also be discussing > Zope 3 matters. Messages about the work *with* Five should to go > zope at zope.org or zope3-users at zope.org if they concern a particular Zope > 3 library. > > Silence is assent. *silence* Martin -- Acquisition is a jealous mistress From faassen at startifact.com Wed Oct 10 13:57:43 2007 From: faassen at startifact.com (Martijn Faassen) Date: Wed, 10 Oct 2007 13:57:43 +0200 Subject: [z3-five] Retiring this list In-Reply-To: References: Message-ID: Philipp von Weitershausen wrote: > Since Five has been an integral part of Zope 2 for three releases now, > and Zope 2 development is pretty much driven by the Five effort > (bringing the Zope 3 libraries to Zope 2), I propose to retire this > list. It hasn't seen much traffic lately anyway. > > Messages about the development *of* Five should go to the > zope-dev at zope.org instead, where we will likely soon also be discussing > Zope 3 matters. Messages about the work *with* Five should to go > zope at zope.org or zope3-users at zope.org if they concern a particular Zope > 3 library. +1 Regards, Martijn From philipp at weitershausen.de Thu Oct 11 14:28:43 2007 From: philipp at weitershausen.de (Philipp von Weitershausen) Date: Thu, 11 Oct 2007 14:28:43 +0200 Subject: [z3-five] THIS AREA IS CLOSED Message-ID: As of now, this list is no longer in use. Messages about the development *of* Five should go to the zope-dev at zope.org. Messages about the work *with* Five should to go zope at zope.org or zope3-users at zope.org if they concern a particular Zope 3 library. Feel free to unsubscribe. -- http://worldcookery.com -- Professional Zope documentation and training From sw at gocept.com Tue Nov 27 10:49:35 2007 From: sw at gocept.com (Sebastian Wehrmann) Date: Tue, 27 Nov 2007 10:49:35 +0100 Subject: [z3-five] Bug in AbsoluteURL Adapter Message-ID: <474BE82F.1060006@gocept.com> Hi there, while using the AbsoluteURL Adapter in a view, it only returns the path of the object, not the URL. This is because the object does not have a request and therefore the method absolute_url() used by the adapter cannot call the physicalPathToURL() method. Because we always have the request object in this adapter we can call the physicalPathToURL() method directly and convert the physical path of the object and return it. Here is a diff with the fix: Index: browser/absoluteurl.py =================================================================== --- browser/absoluteurl.py (Revision 81990) +++ browser/absoluteurl.py (Arbeitskopie) @@ -35,8 +35,8 @@ self.context, self.request = context, request def __str__(self): - context = aq_inner(self.context) - return context.absolute_url() + path = self.context.getPhysicalPath() + return self.request.physicalPathToURL(path) __call__ = __str__ Any comments? -- Sebastian Wehrmann gocept gmbh & co. kg ? forsterstrasse 29 ? 06112 halle/saale ? germany www.gocept.com ? work. +49 345 122988912 ? fax. +49 345 12298891