[Zope-CMF] Re: Bug when removing state in DCWorkflow
Alexander Limi wrote: Can anybody familiar with DCWorkflow take a look at this? http://trac.plone.org/plone/ticket/5067 It used to work, and is a classic workflow change operation that I personally use all the time. CMF doesn't have a workflow pulldown, and has probably different ways of filtering displayed content. Can you configurm that the bug applies to pure CMF? Florent -- Florent Guillaume, Nuxeo (Paris, France) CTO, Director of RD +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ 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
[Zope-CMF] CMFonFive and CMF 1.6
I'm in the process of making CMFonFive support Zope 2.9/3.2. During the development of CMF, parts of CMFonFive has been sneakily added to CMF, adding significantly to the versioning spaghetti of Zope 2, Zope 3, Five and CMF. The only thing CMFonFive 1.3 (to be released soon) does is the fiveactions tool, which bridges Zope 3s menuItems to CMFs actions. The rest was moved into CMF with CMF 1.5.2. I would like to suggest that CMF 1.6 only supports Zope 2.9 (or only 2.8), and include CMFonFive in it, since figuring out what version to use now is already quite complicated. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ 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
[Zope-CMF] Re: GenericSetup: allowed_container_types
On 13 Dec 2005, at 13:50, yuppie wrote: Florent Guillaume wrote: On 13 Dec 2005, at 12:50, yuppie wrote: I'd propose to implement an update mode for list properties and to add an update file for each allowed container. Something like that: object name=MyContainer property name=allowed_content_types element value=MyType/ /property /object (Didn't have a look at the code. I guess this currently overwrites the list and maybe that's what it should do by default. But we could add an explicit mode=update to enforce an update mode.) Yes that was another option I'd considered but found more complex, but if you think it's ok I'll look at how to implement it. Yes, I prefer this option. It should be easy to implement and also useful for other properties. Workflow bindings are set in a similar way, see the example in the CMFTopic profile. The mode=update would be an attribute of property, right ? Yes. But just found that I already use purge=False for action handlers. I guess this is better than mode=update. I can't find any code for purge=False. Workflow bindings don't need that attribute - they are always in update mode if self.environ.shouldPurge() is False. Maybe it would be better to make the shouldPurge setting the default for properties as well. And override it with purge=True if necessary. Don't know. On the other hand the object importer and the skins layer importer check insert-before and insert-after. I'll reuse that, even if in my use case the list order doesn't matter. Florent -- Florent Guillaume, Nuxeo (Paris, France) Director of RD +33 1 40 33 71 59 http://nuxeo.com [EMAIL PROTECTED] ___ 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
[Zope-CMF] Re: [z3-five] Re: CMFonFive and CMF 1.6
On 1/4/06, Rob Miller [EMAIL PROTECTED] wrote: urgh. this isn't ideal for Plone. i'm assuming you've hit some specific problems w/ getting the current CMFonFive code to support both 2.8 and 2.9? can you provide a little more detail re: the compatibility issues? in the meantime, i'll bring this up on plone-devel. The menu implementation in Zope 3.0 and 3.2 are very different. I wouldn't describe this as a problem, it's just not compatible. :-) Zope 2 and Zope 3 now has versions synchronized. I'd like CMF to synchronize the versions as well, as the compatibility matrices grows exponentially. In theory CMFonFive would be able to support Zope 2.7 to 2.9, and CMF 1.4 to 1.6, but supporting any combination of this would require at least four different versions of CMFonFive. It's just a matter of how much work should be put into it. I personally will only make the versions CPS needs in the future, it would be very good if those version where the same as what Plone could use. -- Lennart Regebro, Nuxeo http://www.nuxeo.com/ CPS Content Management http://www.cps-project.org/ ___ 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
[Zope-CMF] Re: Bug when removing state in DCWorkflow
On Wed, 04 Jan 2006 15:27:48 +0100, Florent Guillaume [EMAIL PROTECTED] wrote: Alexander Limi wrote: Can anybody familiar with DCWorkflow take a look at this? http://trac.plone.org/plone/ticket/5067 It used to work, and is a classic workflow change operation that I personally use all the time. CMF doesn't have a workflow pulldown, and has probably different ways of filtering displayed content. Can you configurm that the bug applies to pure CMF? Yes, I can. The issue has several replies, one of which confirms the existence in plain CMF 1.5. There is also a patch from Dorneles to fix this, if any of you could review it, I would appreciate it. -- _ Alexander Limi · Chief Architect · Plone Solutions · Norway Consulting · Training · Development · http://www.plonesolutions.com _ Plone Co-Founder · http://plone.org · Connecting Content Plone Foundation · http://plone.org/foundation · Protecting Plone ___ 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
[Zope-CMF] Re: Bug when removing state in DCWorkflow
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Limi wrote: Can anybody familiar with DCWorkflow take a look at this? http://trac.plone.org/plone/ticket/5067 It used to work, and is a classic workflow change operation that I personally use all the time. Objects which have a no-longer-sane review_state have *never* had reasonable behavior: the workflow engine *can't* compute what to do with them. They have no transitions (which is why the workflow actions are gone), and they can't be fixed by the Update Security button, because there *is no state* to whose permission map they can be conformed. With respect, this is a Doctor! Doctor! problem, to which the appropriate response is Take the spoon out of the glass before drinking (i.e., write the simple script which repairs the broken instances *before* deleting the state). Best, Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDvEGj+gerLs4ltQ4RAiB2AKDSdO5Tk+Lcta5GDSWyG+7Etl+nxgCdG9t7 X++WNcIz85To/3zmzM9G4p0= =6jVx -END PGP SIGNATURE- ___ 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
[Zope-CMF] Re: [z3-five] Re: CMFonFive and CMF 1.6
Lennart Regebro wrote: On 1/4/06, Rob Miller [EMAIL PROTECTED] wrote: urgh. this isn't ideal for Plone. i'm assuming you've hit some specific problems w/ getting the current CMFonFive code to support both 2.8 and 2.9? can you provide a little more detail re: the compatibility issues? in the meantime, i'll bring this up on plone-devel. The menu implementation in Zope 3.0 and 3.2 are very different. I wouldn't describe this as a problem, it's just not compatible. :-) Zope 2 and Zope 3 now has versions synchronized. I'd like CMF to synchronize the versions as well, as the compatibility matrices grows exponentially. In theory CMFonFive would be able to support Zope 2.7 to 2.9, and CMF 1.4 to 1.6, but supporting any combination of this would require at least four different versions of CMFonFive. It's just a matter of how much work should be put into it. I personally will only make the versions CPS needs in the future, it would be very good if those version where the same as what Plone could use. this makes sense. i'm -1 on the final CMFonFive piece landing in CMF 1.6 itself, though. the original scope for CMF 1.6 was CMF 1.5 + GenericSetup, i don't see a compelling reason to complicate things by expanding that scope. if CMFonFive stays separate, then you can code it to support only Zope 2.9 without having to impose this same restriction on the CMF core. -r ___ 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
