[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 tseaver - "MailHost and CookieAuth setup scripts+tests", [Accepted] http://www.zope.org/Collectors/CMF/387 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 - "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 - "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 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
Re: [Zope-CMF] Re: [CMF-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support for configuring cookie auth and mailhost tools
On 21 Sep 2005, at 16:50, Jens Vagelpohl wrote: On 21 Sep 2005, at 11:48, Tres Seaver wrote: Log message for revision 38552: CMFSetup: added support for configuring cookie auth and mailhost tools This patch is broken, as I am finding out. Please don't put it on the head until it is fixed. In CMF 1.5 it's now impossible to add a "Configured CMF Site" because the patch did not include cleanups to remove the current MailHost/CookieCrumbler instantiation code in the CMFDefault.setuphandlers.py module and sufficient testing. I'm looking at it right now, but I'm sitting at the Vienna airport and might not be able to do too much. Just fixed the last bit; there were two distinct problems in combination with Zope 2.7.x and CMF 1.5.x. In general, CMFSetup changes should be verified against both the latest CMF 1.5 and the SVN trunk. In this particular case I was dismayed that the OP apparently never went into the ZMI to actually set up a CMF site using CMFSetup, which would have shown the problems immediately. 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
[Zope-CMF] XML in CMFDefault
Hi, I've just produced a proof-of-concept version of CMFDefault where the CMF produces XML documents, and then these are rendered in the browser (for my own ease!) with XSL. At the moment, this version supports moving round the site, viewing content and moving/deleting/clipboard stuff in the folder view. Is this something anyone else had looked at/was looking at, and/or is it more widely useful to anyone. Does anything like this fit more generally into CMF development? I've taken it as far as my interest will allow at the moment, but if anyone else is interested then collaborating would be good. --pete _ MSN Messenger 7.5 is now out. Download it for FREE here. http://messenger.msn.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-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support fo
Apologies! Although I had tested adding the configured site via the ZMI several times (though only on 2.8), the removal of the two lines in setuphandlers somehow got missed out when I posted the code and patches. It is true that I didn't try checking out a clean install, applying all the patches and re-testing: I think the unit tests gave me a false sense of security. If there's consensus on writing functional tests, then I'll happily submit one to check that the 'configured CMF site' works in the ZMI. --p On 21 Sep 2005, at 16:50, Jens Vagelpohl wrote: On 21 Sep 2005, at 11:48, Tres Seaver wrote: Log message for revision 38552: CMFSetup: added support for configuring cookie auth and mailhost tools This patch is broken, as I am finding out. Please don't put it on the head until it is fixed. In CMF 1.5 it's now impossible to add a "Configured CMF Site" because the patch did not include cleanups to remove the current MailHost/CookieCrumbler instantiation code in the CMFDefault.setuphandlers.py module and sufficient testing. I'm looking at it right now, but I'm sitting at the Vienna airport and might not be able to do too much. Just fixed the last bit; there were two distinct problems in combination with Zope 2.7.x and CMF 1.5.x. In general, CMFSetup changes should be verified against both the latest CMF 1.5 and the SVN trunk. In this particular case I was dismayed that the OP apparently never went into the ZMI to actually set up a CMF site using CMFSetup, which would have shown the problems immediately. jens _ The new MSN Search Toolbar now includes Desktop search! http://toolbar.msn.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: [CMF-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support fo
On 22 Sep 2005, at 11:55, computing project wrote: Apologies! Although I had tested adding the configured site via the ZMI several times (though only on 2.8), the removal of the two lines in setuphandlers somehow got missed out when I posted the code and patches. It is true that I didn't try checking out a clean install, applying all the patches and re-testing: I think the unit tests gave me a false sense of security. If there's consensus on writing functional tests, then I'll happily submit one to check that the 'configured CMF site' works in the ZMI. A functional test is not needed, all that was needed for the MailHost- specific problem was to change the DummyMailHost implementation in the tests to actually look like a Zope 2.7 MailHost. In the end the unit tests were misleading. The only complaint I really have is that the CMF1.5/Zope2.7 combo was neglected here. Since the next major CMF release will be a pretty big step it is important that CMF 1.5 stays supported because people might be using it for a while before they are ready to make the jump to the next CMF version. 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
[Zope-CMF] Re: [CMF-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support fo
Thanks that has made everything much clearer. I'll make sure I label clearly what conditions I've tested things under in future: I hadn't fully appreciated that the head might have different dependencies from the 1.5 branch, though the possibility seems obvious now you've pointed it out. Jens Vagelpohl wrote: On 22 Sep 2005, at 11:55, computing project wrote: Apologies! Although I had tested adding the configured site via the ZMI several times (though only on 2.8), the removal of the two lines in setuphandlers somehow got missed out when I posted the code and patches. It is true that I didn't try checking out a clean install, applying all the patches and re-testing: I think the unit tests gave me a false sense of security. If there's consensus on writing functional tests, then I'll happily submit one to check that the 'configured CMF site' works in the ZMI. A functional test is not needed, all that was needed for the MailHost- specific problem was to change the DummyMailHost implementation in the tests to actually look like a Zope 2.7 MailHost. In the end the unit tests were misleading. The only complaint I really have is that the CMF1.5/Zope2.7 combo was neglected here. Since the next major CMF release will be a pretty big step it is important that CMF 1.5 stays supported because people might be using it for a while before they are ready to make the jump to the next CMF version. 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 ___ 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: [CMF-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support fo
On 22 Sep 2005, at 12:55, pete wrote: Thanks that has made everything much clearer. I'll make sure I label clearly what conditions I've tested things under in future: I hadn't fully appreciated that the head might have different dependencies from the 1.5 branch, though the possibility seems obvious now you've pointed it out. Anyhow, thanks for the contribution, we need more people like you who jump in like that ;) 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] [dev] Topic changes: problems with revision 38002
On 21 Sep 2005, at 18:10, yuppie wrote: I see sporadic import errors caused by circular imports: While not documented in CMFTopic/DEPENDENCIES.txt, http:// svn.zope.org/CMF/trunk/?rev=38002&view=rev added a new dependency on CMFDefault's SkinnedFolder. Not sure how to resolve this. Personally, I don't see a problem with that dependency itself. I cannot come up with any sensible use case for using CMFTopic in an environment where CMFDefault and SkinnedFolder are not available. We could move the import into that setup method where the module is being used? Since this is in the PortalGenerator class it doesn't matter really. 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
[Zope-CMF] CMFSetup cookie crumbler setup still broken
Just noticed another debilitating problem with the new cookie crumbler setup driven by CMFSetup in both SVN trunk and the 1.5 branch. Symptom: In a new CMFSetup-created site, no one can log in at all. Ever. Problem: The CookieCrumbler.__call__ method is being registered as before traverse hook wrongly. Basically, the new cookie crumbler CMFSetup stuff wants to use the machinery for instantiating CMF Tools. This machinery relies on the fact that CMF tool constructors can be invoked without any argument, to be more precise, without an ID passed in because all those tools have unique IDs that are set at class level. The CookieCrumbler does not. When the traversal hook registration happens in CookieCrumbler.manage_afterAdd the ID is needed, but calls to self.getId() now return an empty string. A workaround could be to set an ID at class level, just like CMF tools do. But I am uncomfortable with that because the cookie crumbler is not known to have a unique ID as other tools have. Does anyone have a better suggestion? 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] [dev] Topic changes: problems with revision 38002
yuppie wrote at 2005-9-21 18:10 +0200: > ... > File "Products/CMFDefault/Portal.py", line 26, in ? > from Products.CMFTopic import Topic >ImportError: cannot import name Topic In a similar situation (with Archetypes) something like import Products.CMFTopic.Topic; Topic = Products.CMFTopic.Topic worked around the problem. -- 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
[Zope-CMF] Re: SVN: CMF/branches/1.5/C CMFSetup: added support for configuring cookie auth and mailhost tools
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florent Guillaume wrote: > Tres Seaver wrote: > >> Log message for revision 38552: >> --- CMF/branches/1.5/CMFSetup/xml/ccExport.xml2005-09-20 20:50:17 >> UTC (rev 38551) >> +++ CMF/branches/1.5/CMFSetup/xml/ccExport.xml2005-09-21 09:48:47 >> UTC (rev 38552) >> @@ -0,0 +1,13 @@ >> + >> +http://xml.zope.org/namespaces/tal"; >> +tal:define="cc_info context/getCookieCrumblerInfo" >> +tal:attributes="auth_cookie cc_info/auth_cookie; >> +name_cookie cc_info/name_cookie; >> +pw_cookie cc_info/pw_cookie; >> +persist_cookie cc_info/persist_cookie; >> +auto_login_page cc_info/auto_login_page; >> +logout_page cc_info/logout_page; >> +unauth_page cc_info/unauth_page; >> +local_cookie_path cc_info/local_cookie_path; >> +cache_header_value cc_info/cache_header_value; >> +log_username cc_info/log_username;" /> > > > Eww. Can we have instead of as the element name > please? Sure, go ahead and check it in, before anybody but Pete and I have snapshots which break. ;) Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDMxL/+gerLs4ltQ4RAjnQAJ0VrmaY58pkD/a040z3i9PHkKtvwwCgvDNA SRNvxaPRkE4lNUBriEtNhHs= =YdXM -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: CMFSetup cookie crumbler setup still broken
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jens Vagelpohl wrote: > Just noticed another debilitating problem with the new cookie crumbler > setup driven by CMFSetup in both SVN trunk and the 1.5 branch. > > Symptom: In a new CMFSetup-created site, no one can log in at all. Ever. > > Problem: The CookieCrumbler.__call__ method is being registered as > before traverse hook wrongly. > > Basically, the new cookie crumbler CMFSetup stuff wants to use the > machinery for instantiating CMF Tools. This machinery relies on the > fact that CMF tool constructors can be invoked without any argument, to > be more precise, without an ID passed in because all those tools have > unique IDs that are set at class level. The CookieCrumbler does not. > When the traversal hook registration happens in > CookieCrumbler.manage_afterAdd the ID is needed, but calls to > self.getId() now return an empty string. > > A workaround could be to set an ID at class level, just like CMF tools > do. But I am uncomfortable with that because the cookie crumbler is not > known to have a unique ID as other tools have. I don't think its name matters; noboty is going to refer to it in a template, for instance. > Does anyone have a better suggestion? We could '_setId' on the tool with the 'tool_id' attribute after creating it, if the tool does not derive from CMFCore.utils.ImmutableId. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software "Excellence by Design"http://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDMz53+gerLs4ltQ4RAkHRAJ44790Wa7RgNRzSYMPBKOdOp/hJOwCgi4sS +LfyfIMMKQiWPVcgImGmNBo= =UX/g -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
