[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 tseaver - CMF needs View-based TypeInformation, [Accepted] http://www.zope.org/Collectors/CMF/437 - CachingPolicyManager awareness of File and Image does not work, [Accepted] http://www.zope.org/Collectors/CMF/496 yuppie - purge_old in runAllImportSteps not working, [Accepted] http://www.zope.org/Collectors/CMF/455 Pending / Deferred Issues - workflow notify success should be after reindex, [Deferred] http://www.zope.org/Collectors/CMF/389 - Discussions broken, [Pending] http://www.zope.org/Collectors/CMF/493 - components handler: export of placeless utilities is broken, [Pending] http://www.zope.org/Collectors/CMF/498 - CatalogTool._listAllowedRolesAndUsers() returns wrong result , [Pending] http://www.zope.org/Collectors/CMF/502 - Spinning browser when running a snapshot, [Pending] http://www.zope.org/Collectors/CMF/503 - GenericSetup import onto existing skins fails when adding new layers relative to old ones, [Pending] http://www.zope.org/Collectors/CMF/505 Pending / Deferred Features - CMFTopic Does Not Cache, [Deferred] http://www.zope.org/Collectors/CMF/295 - iCal support for CMFCalendar, [Pending] http://www.zope.org/Collectors/CMF/487 - components handler: support for sub-sites, [Pending] http://www.zope.org/Collectors/CMF/500 - components handler: support removing items, [Pending] http://www.zope.org/Collectors/CMF/501 - components handler: make 'interface' attribute optional, [Pending] http://www.zope.org/Collectors/CMF/499 ___ 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] CMF Tests: 11 OK
Summary of messages to the cmf-tests list. Period Sun Oct 7 12:00:00 2007 UTC to Mon Oct 8 12:00:00 2007 UTC. There were 11 messages: 11 from CMF Unit Tests. Tests passed OK --- Subject: OK : CMF-1.5 Zope-2.7 Python-2.3.6 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:30:09 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006557.html Subject: OK : CMF-1.5 Zope-2.8 Python-2.3.6 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:31:39 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006558.html Subject: OK : CMF-1.5 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:33:09 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006559.html Subject: OK : CMF-1.6 Zope-2.8 Python-2.3.6 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:34:40 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006560.html Subject: OK : CMF-1.6 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:36:10 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006561.html Subject: OK : CMF-2.0 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:37:40 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006562.html Subject: OK : CMF-2.0 Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:39:10 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006563.html Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:40:41 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006564.html Subject: OK : CMF-2.1 Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:42:12 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006565.html Subject: OK : CMF-trunk Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:43:42 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006566.html Subject: OK : CMF-trunk Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Sun Oct 7 21:45:12 EDT 2007 URL: http://mail.zope.org/pipermail/cmf-tests/2007-October/006567.html ___ 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: How to use upgradeStep?
Lennart Regebro wrote: On 9/25/07, Maurits van Rees [EMAIL PROTECTED] wrote: When you want to remove an index or column you can do that by editing the profile and adding remove=True to that index or column. So this upgrade can be represented as a profile edit. But applying the profile will empty the remaining indexes that are mentioned in that profile. So ideally I would want to apply the profile only once when installing and rely on upgrade steps to handle any further changes without applying that complete profile again. It seems the new upgrade steps do not really solve this particular use case then. (It can sure be handy for other things, no doubt about that.) But I had hopes to use them to work around this issue with catalog.xml. Apparently a workaround is no substitute for really solving the problem. ;-) Is anyone going to the sprints after the Plone conference who wants to take a shot at this with me? Preferably someone with commit rights. :-) Well, I made a monkey-patch that I haven't merged yet that only did that if the index definition had actually changed, and that was quite trivial. I would appreciate more people looking at this, since this was so easy I get suspiscious. :-) So at the Plone conf seems a good time. performing a full upgrade, then, would require reapplying the profile configuration and running the upgrade steps. reasonably the quickinstaller (or even the GS interface) could do this all as one step. Right. Or a warning could be displayed: This profile has upgrade steps available; do you want to run them? CPS listed all upgradeSteps whose version numbers where higher then the numbers of the last upgrades, and had a button to run them. You could also select which to run, and list old steps, and (re-)run them. Since this is a merge of the CPS functionality (and thanks for that Rob, I never understood why Nuxeo branched GenericSetup instead of improving the original one, maybe there was a good reason) sure. i can only speculate as to why nuxeo made that choice, but i will note that it allowed them to simplify the idea of version to that of the entire CPS stack. when i ported it back to GS, most of the work was adding support for per-profile versions, and per-profile upgrades. seems reasonable for nuxeo to have punted on this extra work, since CPS didn't require it. I hope there may be something similar here? yes, that interface was reproduced, with some changes to allow you to choose the profile for which you're running the upgrade steps. -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
[Zope-CMF] Re: GenericSetup: How to use upgradeStep?
Maurits van Rees wrote: Hi, I've been on vacation I took my time answering. Rob Miller, on 2007-09-06: okay, here's where things get off track. in GenericSetup, there is no such thing (yet, perhaps) as an upgrade profile. it's possible to define an extension profile and to USE it as part of an upgrade process (Plone has been doing this), but there's no special profile type that GS knows about. Understood. upgrade steps are not meant to represent simple profile edits. for those, you'd just change the profile and up the profile version number, no need for an upgrade step at all. How do you add a version number to a profile? You can add a version to an import step in import_steps.xml, but I do not see version info in the zcml of a profile. the profile version number goes into the metadata.xml file in the profile itself. Or do you just mean the version.txt? The quick installer uses that of course. GenericSetup does not use that anywhere as far as I see. actually, as i coded it GS _does_ fail over to using the version.txt version number if there is no version explicitly specified in the metadata.xml file. i've since become convinced, however, that this should not be the default behaviour; you should have to explicitly specify if you want to use the product version as the profile version. i don't think anyone has actually changed this in the code, but i haven't been paying much attention recently. -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
