[Zope-CMF] CMF Collector: Open Issues
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open efge - CMFSetup: provide non-ascii im- and exports, [Accepted] http://www.zope.org/Collectors/CMF/292 - CMFSetup doesn't correctly detect DCWorkflow on export, [Accepted] http://www.zope.org/Collectors/CMF/298 jens - FSPropertiesObject.py cannot handle multiline input for lines, text attributes, [Accepted] http://www.zope.org/Collectors/CMF/271 mhammond - Windows DevelopmentMode penalty in CMFCore.DirectoryView, [Accepted] http://www.zope.org/Collectors/CMF/366 mj - CMFSetup doesn't correctly detect DCWorkflow on export, [Accepted] http://www.zope.org/Collectors/CMF/298 Pending / Deferred Issues - Debuggable scripts, [Deferred] http://www.zope.org/Collectors/CMF/194 - CMFCalendar weekday locale issue, [Pending] http://www.zope.org/Collectors/CMF/237 - CMFCalendar: Events ending on midnight, [Pending] http://www.zope.org/Collectors/CMF/246 - Wrong cache association for FSObject, [Pending] http://www.zope.org/Collectors/CMF/255 - CMFSetup: Windows exports contain CR/LF, LF and even CR newlines, [Pending] http://www.zope.org/Collectors/CMF/266 - PortalCatalog.ZopeFindAndApply should probably also search in opaqueItems, [Pending] http://www.zope.org/Collectors/CMF/296 - WorkflowTool should recurse into opaqueItems, [Pending] http://www.zope.org/Collectors/CMF/297 - add External Methods to workflow script handling, [Pending] http://www.zope.org/Collectors/CMF/329 - Can't invalidate skin items in a RAMCacheManager, [Pending] http://www.zope.org/Collectors/CMF/343 - Workflow Tool exportation step fails with workflows which have scripts, [Pending] http://www.zope.org/Collectors/CMF/373 - CMFCore.Skinnable.SkinnableObjectManager can merge skin data, [Pending] http://www.zope.org/Collectors/CMF/375 Pending / Deferred Features - Favorite.py: queries and anchors in remote_url, [Pending] http://www.zope.org/Collectors/CMF/26 - Allow flexible date editing in Event.py (CMFCalendar), [Pending] http://www.zope.org/Collectors/CMF/40 - DefaultDublinCore should have Creator property, [Pending] http://www.zope.org/Collectors/CMF/61 - Make changeFromProperties accept sequences too, [Pending] http://www.zope.org/Collectors/CMF/99 - path criteria on Topic should honor VHM, [Pending] http://www.zope.org/Collectors/CMF/111 - Document.py: universal newlines, [Pending] http://www.zope.org/Collectors/CMF/174 - Permissions in PortalFolder: invokeFactory(), [Pending] http://www.zope.org/Collectors/CMF/175 - Add condition for transition's action like other action, [Pending] http://www.zope.org/Collectors/CMF/207 - Major action enhancement, [Pending] http://www.zope.org/Collectors/CMF/232 - portal_type is undefined in initialization code, [Pending] http://www.zope.org/Collectors/CMF/248 - Action._listsActions() should be more safe, [Pending] http://www.zope.org/Collectors/CMF/253 - Expose Document text_format metadata, [Pending] http://www.zope.org/Collectors/CMF/285 - customization of type of homefolder on creation, [Pending] http://www.zope.org/Collectors/CMF/288 - Allow contentFilter to use review_state, [Pending] http://www.zope.org/Collectors/CMF/294 - CMFTopic Does Not Cache, [Pending] http://www.zope.org/Collectors/CMF/295 - Wishlist: a flag that tags the selected action., [Pending] http://www.zope.org/Collectors/CMF/301 - CMFDefault should make use of allowCreate(), [Pending] http://www.zope.org/Collectors/CMF/340 - Nested Skins, [Pending] http://www.zope.org/Collectors/CMF/377 - CatalogVariableProvider code + tests, [Pending] http://www.zope.org/Collectors/CMF/378 ___ 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: CachingPolicyManager improvements
Dieter Maurer wrote: yuppie wrote at 2005-9-5 14:06 +0200: ... PortalTestCase is in the wrong layer. It makes assumptions about the way CMF works. Changes to the CMF might break PortalTestCase and create a dependency on a new Zope release. (We saw that problem already with the _refreshSkinData changes in CMF 1.5) It is not better to fix such problems at a single place (PortalTestCase) rather than in lots of individual tests (that happen to make similar assumptions)? Seems I didn't make my point clear: I wasn't arguing against PortalTestCase. The problem is that PortalTestCase is shipped with Zope, not with the CMF. But the correct implementation of PortalTestCase depends on the CMF version. Using PortalTestCase creates a circular dependency between Zope and CMF. Cheers, Yuppie ___ 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] [dev] CMF trunk dependencies
Hi! If there are no objections I'll make Zope 2.8.1 the required platform for CMF trunk/1.6 and remove the Zope 2.8.0 backwards compatibility code. Reasons: - I hope some day CMF-tseaver-z3_interfaces-branch will be finished and merged. To do that right we need the new Interfaces.bridge. - PluginIndexes, ZCTextIndex and ZCatalog have some new interfaces that are useful to write portal_catalog setup adapters. - The recently added i18n MessageIDs are ignored in Zope 2.8.0. Cheers, Yuppie ___ 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] [dev] CMF trunk dependencies
On 6 Sep 2005, at 11:19, yuppie wrote: Hi! If there are no objections I'll make Zope 2.8.1 the required platform for CMF trunk/1.6 and remove the Zope 2.8.0 backwards compatibility code. Reasons: - I hope some day CMF-tseaver-z3_interfaces-branch will be finished and merged. To do that right we need the new Interfaces.bridge. - PluginIndexes, ZCTextIndex and ZCatalog have some new interfaces that are useful to write portal_catalog setup adapters. - The recently added i18n MessageIDs are ignored in Zope 2.8.0. +1 - we still have the freedom to do so. jens ___ 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: Re: CachingPolicyManager improvements
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Alexander Limi wrote: On Mon, 05 Sep 2005 22:20:02 +0200, Geoff Davis [EMAIL PROTECTED] wrote: Alternatively you can create a function that checks the modification times for the content and for all portlets as well. Embed that composite time in your ETag and you're all set. ESI would be cool, too, but I'm not betting that we'll see that any time soon. The new PlonePortlets infrastructure could help here too, the plan is to have built-in caching parameters for each portlet here - so it can know whether it has fresh content or not, and feed that to external mechanisms like the ETags. Still science fiction, though. ;) (And before you ask - yes, we're putting it in the Collective shortly. :) FYI, we have a portlet cache implementation on CPSPortlets tied with the CPS event service for the cache invalidation : If you wanna check : http://svn.nuxeo.org/trac/pub/file/CPSPortlets/trunk/doc/cpsportlets-RAMCache-draft.txt And the implementation over there : http://svn.nuxeo.org/trac/pub/file/CPSPortlets/trunk/PortletRAMCache.py And the ESI support on the portlet there : http://svn.nuxeo.org/trac/pub/file/CPSPortlets/trunk/CPSPortlet.py We never tested it though in here ;) Maybe Jean-Marc ? Feel free to ask questions on the cps lists if you feel like... Cheers, J. - -- Julien Anguenot | Nuxeo RD (Paris, France) CPS Platform : http://www.cps-project.org Zope3 / ECM : http://www.z3lab.org mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66 -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iD8DBQFDHZ55GhoG8MxZ/pIRAs2EAJ4/xdEyt0M6upCl8rUXRXw5N862vwCeOatt n0TtyB0id4euD1fokf0HucQ= =gre6 -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] metadata project
Hi, I'm making a site that has a requirement for metadata and am unsure about the best way to proceed; whether or not to extend the CMF MetadataTool or create something afresh. Having looked at and played with the standard MetadataTool there are some things missing that I really need to have: 1) the ability to have different sets of metadata elements applicable to objects (but not based on that objects type), 2) the ability to configure the order in which metadata elements appear (when editing, searching etc.). And example of 1) is to have two sets of metadata elements: (food brand: 'colour', 'flavour', 'shape') and (car: 'size', 'horsepower', 'weight'). Now, for an uploaded object I want to choose which set of metadata to use. Any thoughts or insight would be greatly appreciated... It just feels like it would be a lot easier to implement my own tool. Many thanks, Mark ___ 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: CachingPolicyManager improvements
Florent wrote: There's also some text in the online help about caching complete web pages being a bad idea. And in the docstring of the source too. -PW ___ 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: CachingPolicyManager improvements
Geoff Davis wrote: RAMCacheManager has no good way to purge stale content. ZCacheable_invalidate()? (granted, in practice it's currently broken for skins... http://www.zope.org/Collectors/CMF/343 ) It's not just that RAMCacheManager has bugs. ZCacheable_invalidate, when called, invalidates everything in the cache associated with a given page template. That means that if you cache, say, a template that provides a view of a document, the only way to invalidate the view for a single document is to invalidate the view of _all_ documents. Not very useful. Yeah you can't invalidate individual views, but I don't think it would be too hard to change that code. I know I've also felt this would be useful to have in several cases. 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
