[Zope-CMF] GenericSetup Toolset problem
Hello, I've added a tool to my code base, and registered it in toolset.xml, gave it import/export logic, etc ... Thing is, it won't show up in my import tab. I've tried re-importing everything, but to no avail. How do I get the new tool registered (and created) into an existing site? Jean-François Doyon Data Dissemination Division | Division de la diffusion des données Data Management and Dissemination Branch | Direction de la gestion et de la diffusion des données Earth Sciences Sector | Secteur des sciences de la Terre Natural Resources Canada | Ressources naturelles Canada Ottawa, Canada K1A 0E9 [EMAIL PROTECTED] Telephone | Téléphone 613-992-4902 Facsimile | Télécopieur 613-947-2410 Teletypewriter | Téléimprimeur 613-996-4397 Government of Canada | Gouvernement du Canada ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
RE: [Zope-CMF] GenericSetup Toolset problem
On Zope 2.10.2 with CMF 2.0.0 BTW ... From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Doyon, Jean-Francois Sent: March 27, 2007 12:57 To: [EMAIL PROTECTED] Subject: [Zope-CMF] GenericSetup Toolset problem Hello, I've added a tool to my code base, and registered it in toolset.xml, gave it import/export logic, etc ... Thing is, it won't show up in my import tab. I've tried re-importing everything, but to no avail. How do I get the new tool registered (and created) into an existing site? Jean-François Doyon Data Dissemination Division | Division de la diffusion des données Data Management and Dissemination Branch | Direction de la gestion et de la diffusion des données Earth Sciences Sector | Secteur des sciences de la Terre Natural Resources Canada | Ressources naturelles Canada Ottawa, Canada K1A 0E9 [EMAIL PROTECTED] Telephone | Téléphone 613-992-4902 Facsimile | Télécopieur 613-947-2410 Teletypewriter | Téléimprimeur 613-996-4397 Government of Canada | Gouvernement du Canada ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Derived Content Types WebDAV
Charlie Clark wrote at 2007-3-27 13:28 +0200: having made my own content type which is derived from Document with three additional attributes, I've moved onto the exciting world of editing content via webDAV. It seems some methods have to be extended/ overwritten for this to work so I have added customised versions of the following getMetadataHeaders() # Document.py setMetadata() # Document.py getMetadataHeaders() # DublinCore.py _editMetaData() # DublinCore.py Is this a correct assumption? I would be quite surprised if these methods had much to do with WebDAV editing. Instead, I would look for PROPPATCH (and how it is implemented). -- Dieter ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
Re: [Zope-CMF] Re: Delete trouble
On 27 Mar 2007, at 20:57 , Dieter Maurer wrote: As so often, we have completely different views on how things should be: When I have an IObjectBeforeDeleteEvent subscriber which should update the unique ID tool, then it can assume that there is indeed a unique ID tool. And if the assumption is wrong, an exception should result. What makes you think you can make that assumption? This is Zope 2 all over again, where things just have to be there. That won't help making things more flexible. We have this situation here: there should be (and is) a unique id tool but the local registrations have not been performed. Nope, we're just not operating in a place where we can get to the tool. It's standard acquisition semantics. An exception is better than silently omit the update of the existing unique id tool. You could argue that the local id tool does not need to be updated as the complete site (including the tool) gets deleted. Indeed. But would the effect be different, if I used: plone_site.some_folder.manage_deleteObjects(). Or in other words, is attribute lookup entailed in traversal? No. If it is not (which I assume), then your defensive programming would hide inconsistencies in the unique id tool -- similar to a defensive try: except: pass. What kind of inconsistencies? We're deleting the thing anyway, what's the point to update it? ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
