[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 jens - Discussion replies removal, [Accepted] http://www.zope.org/Collectors/CMF/391 mhammond - Windows DevelopmentMode penalty in CMFCore.DirectoryView, [Accepted] http://www.zope.org/Collectors/CMF/366 regebro - fiveactionstool broken (Zope 2.9/3.2), [Accepted] http://www.zope.org/Collectors/CMF/392 Pending / Deferred Issues - CMFCalendar weekday locale issue, [Pending] http://www.zope.org/Collectors/CMF/237 - 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 - FSPropertiesObject.py cannot handle multiline input for lines, text attributes, [Pending] http://www.zope.org/Collectors/CMF/271 - PortalCatalog.ZopeFindAndApply should probably also search in opaqueItems, [Pending] http://www.zope.org/Collectors/CMF/296 - Can't invalidate skin items in a RAMCacheManager, [Pending] http://www.zope.org/Collectors/CMF/343 - CMFSetup: Workflow Tool export 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 - Proxy Roles does't work for a Script using portal_catalog.searchResults, [Pending] http://www.zope.org/Collectors/CMF/380 - WorkflowAction deprecated warning should not printed for WorkflowMethod, [Pending] http://www.zope.org/Collectors/CMF/388 - workflow notify success should be after reindex, [Pending] http://www.zope.org/Collectors/CMF/389 - came_from and VIRTUAL_URL problem, [Pending] http://www.zope.org/Collectors/CMF/393 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 - manage_doCustomize() : minor additions, [Pending] http://www.zope.org/Collectors/CMF/382 ___ 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] Catching logging during unittesting?
Hi All, Asking here 'cos I'm sure I saw someone talking about this recently. I'm unit testing something which does some logging. It's supposed to log, so ideally I'd like to test for that, but I'd also like to not have the log spew showing during tests runs, which seems to have started happening in Zope 2.8 :-S I tried using the LogInterceptor mixin, but that only works for zLOG, whereas I'm using what we should all be using: the new python logging module. Any ideas? cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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] CMF 1.6
Alec Mitchell wrote: to start using it immediately or risk strange breakages. Maintaining product compatibility between versions of CMF/Plone will become nearly impossible. I'm sorry, I really couldn't resist this... And that differs from other Plone releases how exactly? ;-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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: [dev] RFC: logging/reporting framework for GenericSetup
yuppie wrote: Or would be 'GenericSetup.content' enough? Yes, that looks nicer to me :-) Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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: CMF 1.6
Chris Withers wrote: Alec Mitchell wrote: to start using it immediately or risk strange breakages. Maintaining product compatibility between versions of CMF/Plone will become nearly impossible. I'm sorry, I really couldn't resist this... neither can I ... And that differs from other Plone releases how exactly? ;-) not at all, but that's what many people (including yourself?) didn't like so far. So maybe it's time for a change? ;-) Raphael Chris ___ 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] Test broken on 1.6 branch
Dammit, the tests are totally broken on the 1.6 branch. Don't people ever run the tests? sigh 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
Re: [Zope-CMF] Test broken on 1.6 branch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florent Guillaume wrote: Dammit, the tests are totally broken on the 1.6 branch. Don't people ever run the tests? sigh Automatic nightly tests should be running every day I guess to avoid this kind of problems. Florent, running CMF tests is not really costly, maybe we could try to make them run beside the CPS ones in house every night and send a mail with the results on this list ? 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 Mozilla - http://enigmail.mozdev.org iD8DBQFDfb68GhoG8MxZ/pIRAvqJAJ9FAx5vsJXnevMfqelpnh0ecapoEACdFkUs 2MSmMEfin4983tnmtVGAuT8= =m5bW -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
Re: [Zope-CMF] Test broken on 1.6 branch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 ok, I can add automatic nightly tests of CMF every night and send a mail on the zope-tests mailing list so that the summarizer will take them into account. Is it fine with everybody ? J. Julien Anguenot wrote: Florent Guillaume wrote: Dammit, the tests are totally broken on the 1.6 branch. Don't people ever run the tests? sigh O Automatic nightly tests should be running every day I guess to avoid this kind of problems. Florent, running CMF tests is not really costly, maybe we could try to make them run beside the CPS ones in house every night and send a mail with the results on this list ? 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 ___ 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 - -- 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 Mozilla - http://enigmail.mozdev.org iD8DBQFDfcM3GhoG8MxZ/pIRAnFVAJ44F5bu5EG+EndBAIrK45RoSZu1DQCfXDJk g9CWRun753UWgiOxbq4OFgE= =xtek -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: CMF 1.6
On Fri, 18 Nov 2005 00:37:47 -0800, Chris Withers [EMAIL PROTECTED] wrote: Alec Mitchell wrote: to start using it immediately or risk strange breakages. Maintaining product compatibility between versions of CMF/Plone will become nearly impossible. I'm sorry, I really couldn't resist this... And that differs from other Plone releases how exactly? ;-) And what, exactly, have you done to help Plone have less bugs? I know you get income from Plone consulting, how about making your workday better *and* pay back for the stuff you get for free? You are seriously starting to piss me off, Chris - as the only person in the Zope world so far. An achievement in itself, but not one you should be particularly proud of. -- _ 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: Test broken on 1.6 branch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julien Anguenot wrote: ok, I can add automatic nightly tests of CMF every night and send a mail on the zope-tests mailing list so that the summarizer will take them into account. Is it fine with everybody ? +1. 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 iD8DBQFDfdJH+gerLs4ltQ4RAhClAJwIsZXVuts7j8pjGJErq5TMgXdCnwCgjQqh cHcFiqa5tvHgpKLrW3copi4= =NkW1 -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: Test broken on 1.6 branch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: Julien Anguenot wrote: ok, I can add automatic nightly tests of CMF every night and send a mail on the zope-tests mailing list so that the summarizer will take them into account. Is it fine with everybody ? Note that the current breakage on the 1.6 branch is the kind of stuff that made me reluctant to borrow the trunk's CMFSetup/GenericSetup. In this case, it isn't really fair to complain about the test breakage, in that the whole point of the branch is to find and fix such things. I've just fixed a couple of things, which is more than the bandwidth I meant to spend on the 1.6 branch alredy. 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 iD8DBQFDfdjh+gerLs4ltQ4RAhgJAKCtlFno3mwglpcOUH6hCmREOy8TZACfVQ2u qNEIfvRJdu6TT7QdDZ5NRAw= =ECFr -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: CMF 1.6
Alexander Limi wrote: And that differs from other Plone releases how exactly? ;-) And what, exactly, have you done to help Plone have less bugs? *sigh* there's not a lot I can do, the problems with Plone are cultural. There seems to be a pervasive culture of monkey patching and bludegeoning code to meet functionality requirements while not worrying about software architecture, refactoring, scalability or performance except in passing fads. Yeah, sure it works out of the box like it should, and it has all the checkbox features, and it even looks pretty if that's the look you like, but try and do anything that doesn't ship out of the box and _doesn't_ involve the aforementioned code blugeoning and you end up with a solution that will only work for your specific project because of the Plone-wide assumptions you have to break to get it done. Either that or not give a damn about performance or maintainability and just make it work. Sure, it'll work for a few releases without change if you're lucky, but it'll likely be dog slow and pig ugly if you look behind the scenes. I'm sorry, that kind of coding just doesn't interest me. But, inspite of that, you will see the odd change I've made to try and help, and I try and provide simple tools like zdb, Stepper, MailingLogger, SimpleUserFolder and MailTemplates that people are free to use without any obnoxious GPHell licensing and without having to worry about some semi-formed ip assignment that may or may not stand up in any given court of law around the world. I know you get income from Plone consulting, how about making your workday better *and* pay back for the stuff you get for free? Because I can't. The win's we've had on the one big Plone-related (and there's not _much_ of Plone actually left now, sorry to tell you) project I work on have been by stripping out all the complexity so that code meets the _project_ requirements and doesn't worry about interacting with any of the myriad of Plone half-interfaces and semi finished rubbish that gets shipped as part of every release. You are seriously starting to piss me off, Chris Don't worry, the quality of code that ships in the Plone bundle has already done much to take me way beyond pissed off. I find it a tragedy that a project with such a large following can't manage to get anyone capable of actually standing back and taking a good hard look at the quality of some of your key components and sorting it out rather than tacking on the next whizz-bang feature in a similarly half-arsed manner. - as the only person in the Zope world so far. An achievement in itself, but not one you should be particularly proud of. Honestly, I'm sorry you feel that way but at least I make the distinction about what it is I'm pissed off about. The people in the Plone community are great, and I get on with the majority of them very well as far as I know, but sadly, that alone doesn't make them write good software. I am pissed off with the _software_ not the _people_ and if I thought there was a sane way I could make things better, I would. But again, honestly, I think the software that currently makes up Plone above the CMF, and even that could do with a good kick, is beyond help and would only really be improved by a ground-up rewrite. And finally, if you're pissed off with me, that's fine, I don't really give a monkeys how you feel towards me personally. Write some good software, then I might ;-) cheers, Chris PS: Sorry for the rant, I was hoping to avoid this heading to a list but the one liner I posted earlier was as good as I could make it, I even put the smiley in ;-) For Alex to reply like this has now got the response it deserved. Really, I was excited to try Plone 2.1 with all the hype about the quality being so much better and improved performance, but having just had to give up on another project involving Plone 2.1 and LinguaPlone because it was way too slow, particularly on Windows, and trying to fix any of the problems I found felt like playing some sick and twisted version of whack-a-mole, not to mention the fact that Plone still ships with failing unit tests that cause other product's unit tests to fail means that while I have loads of respect for the project in managing to grow such a large community, and particularly for the people who have the patience to take part, I have zero respect for the software that underpins it... -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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: CMF 1.6
On Fri, 18 Nov 2005 05:49:46 -0800, Chris Withers [EMAIL PROTECTED] wrote: snip rant / Rant accepted, and understood. Still, you could try to help out instead of *just* bitching. I am an expert bitcher myself, but at least I do something about it. Thread closed? Feel free to follow up with me in private email if there's anything we can do to facilitate you helping out. -- _ 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
Re: [Zope-CMF] Re: Test broken on 1.6 branch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tres Seaver wrote: Tres Seaver wrote: Julien Anguenot wrote: ok, I can add automatic nightly tests of CMF every night and send a mail on the zope-tests mailing list so that the summarizer will take them into account. Is it fine with everybody ? Note that the current breakage on the 1.6 branch is the kind of stuff that made me reluctant to borrow the trunk's CMFSetup/GenericSetup. In this case, it isn't really fair to complain about the test breakage, in that the whole point of the branch is to find and fix such things. I've just fixed a couple of things, which is more than the bandwidth I meant to spend on the 1.6 branch alredy. Tres please note, I wasn't the one complaining here. I just proposed to setup automatic tests for the CMF after a complain... 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 Mozilla - http://enigmail.mozdev.org iD8DBQFDfd98GhoG8MxZ/pIRAmC5AJ9AaPJ5kYhDwyTIhAYucxmBZIHmPgCfVsh+ 6+b0lK9x4G5VMApfvh8SPTk= =ZukQ -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: CMF 1.6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Guys, I'll ask that this end here on the zope-cmf list (well, Alex is entitled to one public rebuttal, I guess). We need to focus the list's discussion and attention on ways to improve the architecture, rather than engaging in a your code is crap flamewar. FWIW, the Goldegg work is largely aimed at making it possible to resolve the product vs. framework dichotomy in Plone, by making it possible to extract / reuse / reimplement features developed to meet a given need as Z3 components. I am *very* excited to be working with both Plone and CMF developers to make that happen. 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 iD8DBQFDfd74+gerLs4ltQ4RAs5hAKCIQ0rkwjlI1EGW2ewmqlREuIsO8ACfR62U xlpNSVCtCT52zb1pQ8KM3ls= =3KhU -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: Test broken on 1.6 branch
Tres Seaver wrote: Note that the current breakage on the 1.6 branch is the kind of stuff that made me reluctant to borrow the trunk's CMFSetup/GenericSetup. In this case, it isn't really fair to complain about the test breakage, in that the whole point of the branch is to find and fix such things. Well if the tests are expected to be broken, it shouldn't be called branches/1.6 but branches/genericsetup-backport. 1.6 is the name of an official branch, which should be clean. I've just fixed a couple of things, which is more than the bandwidth I meant to spend on the 1.6 branch alredy. Thanks. 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] GenericSetup uninstalling
Is uninstalling part of the use cases that GenericSetup tries to handle? How would one go about registering what has to be done to remove an extension profile for instance? Has anybody worked in that direction? 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
Re: [Zope-CMF] Catching logging during unittesting?
Answering my own question and cc'ing Vinay in since I was also talking to him about this... Chris Withers wrote: I'm unit testing something which does some logging. It's supposed to log, so ideally I'd like to test for that, but I'd also like to not have the log spew showing during tests runs, which seems to have started happening in Zope 2.8 :-S I added the following methods to our TestCase base class and then added the class below it: def _stopLogging(self): import logging root_logger = logging.getLogger() self.old_handlers = root_logger.handlers root_logger.handlers = [DummyLogger()] def _startLogging(self): old_handlers = getattr(self,'old_handlers',None) if old_handlers is not None: import logging logging.getLogger().handlers = old_handlers class DummyLogger: def handle(self, record): pass This can now be used in a unit test as follows: self._stopLogging() try: # stuff that ends up logging stuff self.assertRaises(AttributeError,self._runStep,'checkExpires') finally: checkExpires.DateTime = DateTime self._startLogging() Hope this helps someone else :-) cheers, Chris PS: Vinay: lemme know if there's a better way to do this... -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ 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] reindexing optimizations
Howdy CMFers, So, Sidnei has been plugging away at the AT reindexes things an obscene number of times issue today, and appears to have fixed many of the AT triggered indexing redundancies. There are however still a few places in CMF where some cataloging redundancy might be avoided. One obvious place is during object creation, where the following happens: *) TypesTool.constructInstance() is triggered **) A _setObject call results in CMFCatalogAware.manage_afterAdd() which triggers a full indexObject(). *) This is shortly followed by TypesTool._finishConstruction() *) Which calls CMFCatalogAware.notifyWorkflowCreated() *) Which in turn calls WorkFlowTool._reindexWorkflowVariables() **) Which does a CMFCatalogAware.reindexObject([idxs]) on workflow specific variables (with a full metadata update) *) And calls CMFCatalogAware.reindexObjectSecurity() which reindexes the object only on the security index, and doesn't touch metadata. **) TypesTool._finishConstruction() then does another CMFCatalogAware.reindexObject(). So we have two full reindexes, and three metadata updates. The last reindex appears to be there only to catch the change to 'portal_type' in _finishConstruction. So, this final reindexObject, might safely be changed to reindexObject(['portal_type', 'Type']), though the possibility exists that other indexed attributes added by 3rd parties may depend on the value of portal_type (say, I use an autogenerated Title which includes the Type). Additionally, almost immediately before this last reindexObject call, another reindexObject call has happened in notifyWorkflowCreated, which included a full catalog metadata update. As a result, updating the catalog metadata here is certainly redundant. Unfortunately, the CMFCatalogAware.reindexObject method provides no means of avoiding the duplicate metadata update, though it would be trivial to add and to use here. Another option suggested by Sidnei on IRC, which would avoid the potential issues with limiting the variables indexed in the final reindex. Would be to let CMFCatalogAware.manage_afterAdd know (presumably via some state variable) that it is being invoked through constructInstance/invokeFactory, in which case it could safely skip the initial indexing and allow _finishConstruction to take care of indexing the object fully on it's own at the end. In the long term we will probably be better served by delaying all indexing to transaction boundaries, though it will be a fair bit harder to implement, and may irk some developers who depend on immediate changes to the catalog on reindex. Alec ___ 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: upgrade question
Please forward this to the Plone Setup list, which deals with installation
and migration of Plone. The CMF team does not have the capacity to field
Plone questions, nor should they have to. ;)
http://plone.org/contact#setup
-- Alexander Limi
On Fri, 18 Nov 2005 14:08:55 -0800, Steve Giessler
[EMAIL PROTECTED] wrote:
Greetings,
I'm upgrading Zope 2.7.6 (with Python 2.3.5) and Plone 2.0.5 to Zope
2.8.4 (with Python 2.3.5) and Plone 2.1.1 (and PIL 1.1.5). This is all
being done on a RHEL 4 box. I installed all the new stuff and then I
copied my Data.fs file to the new instance/var directory. I then ran the
new Plone instance, went to mysite:8080/manage and in the ZMI migrated
my plone sites. During migration, each site gave me many pages of these
errors:
snippet
2005-11-18 12:46:04 INFO Zope.ZCatalog Finished migration of indexes for
clc/portal_catalog
2005-11-18 12:46:08 ERROR ExtendedPathIndex Attempt to unindex
nonexistent document with id -1984665228
2005-11-18 12:46:16 ERROR ExtendedPathIndex Attempt to unindex
nonexistent document with id -1984665227
2005-11-18 12:46:26 ERROR ExtendedPathIndex Attempt to unindex
nonexistent document with id -1984665226
2005-11-18 12:46:32 ERROR ExtendedPathIndex Attempt to unindex
nonexistent document with id -1984665225
2005-11-18 12:46:35 ERROR ExtendedPathIndex Attempt to unindex
nonexistent document with id -1984665224
2005-11-18 12:46:36 ERROR ExtendedPathIndex Attempt to unindex
nonexistent document with id -1984665223
2005-11-18 12:46:38 ERROR ExtendedPathIndex Attempt to unindex
nonexistent document with id -1984665222
snippet
but the sites still seem to run (the basic framework and skins, etc are
visible). When I hit my plone site though, I see this on the main page:
This site encountered an error trying to fulfill your request. The
errors were:
Error Type
RuntimeError
Error Value
maximum recursion depth exceeded
Request made at
2005/11/18 17:02:17.389 US/Eastern
And in the Zope log output I see:
2005-11-18 17:01:34 INFO Zope Ready to handle requests
/zope/main_instance/Products/CMFCore/TypesTool.py:275:
DeprecationWarning: getActionById() is deprecated and will be removed in
CMF 1.6. Please use getActionInfo()['url'] if you need an URL or
queryMethodID() if you need a method ID.
DeprecationWarning)
/zope/main_instance/Products/CMFCore/utils.py:186: DeprecationWarning:
__call__() and view() methods using _getViewFor() as well as
_getViewFor() itself are deprecated and will be removed in CMF 1.6.
Bypass these methods by defining '(Default)' and 'view' Method Aliases.
DeprecationWarning)
2005-11-18 17:02:16 ERROR Zope.SiteErrorLog
http://www.as.wvu.edu:8080/clc/index_html
Traceback (most recent call last):
File /zope/lib/python/ZPublisher/Publish.py, line 113, in publish
request, bind=1)
File /zope/lib/python/ZPublisher/mapply.py, line 88, in mapply
if debug is not None: return debug(object,args,context)
File /zope/lib/python/ZPublisher/Publish.py, line 40, in call_object
result=apply(object,args) # Type scr to step into published object.
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
109, in __call__
return method()
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
109, in __call__
return method()
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
109, in __call__
return method()
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
109, in __call__
return method()
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
109, in __call__
return method()
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
109, in __call__
return method()
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
109, in __call__
return method()
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
109, in __call__
return method()
--snip (excess removed)---
File /zope/main_instance/Products/CMFCore/PortalContent.py, line
100, in __call__
method_id = ti and ti.queryMethodID('(Default)', context=self)
File /zope/main_instance/Products/CMFDynamicViewFTI/fti.py, line
221, in queryMethodID
methodTarget = self.defaultView(context)
File /zope/main_instance/Products/CMFDynamicViewFTI/fti.py, line
189, in defaultView
obj, path = plone_utils.browserDefault(context)
File /zope/main_instance/Products/CMFPlone/PloneTool.py, line 1095,
in browserDefault
act = obj.getTypeInfo().getActionById('view')
File /zope/main_instance/Products/CMFCore/TypesTool.py, line 282, in
getActionById
target = action.action(context).strip()
File /zope/main_instance/Products/CMFCore/Expression.py, line 44, in
__call__
res = compiled(econtext)
File /zope/lib/python/Products/PageTemplates/Expressions.py, line
224, in __call__
v = var(econtext)
File
