[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 - DCWorkflow - Transition Guards - Documentation Bug, [Pending] http://www.zope.org/Collectors/CMF/394 - PortalFolder.py _verifyObjectPaste ignores executable security, [Pending] http://www.zope.org/Collectors/CMF/396 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] Re: GenericSetup uninstalling
Hi Florent! Florent Guillaume wrote: Is uninstalling part of the use cases that GenericSetup tries to handle? No. The setup tool doesn't even keep track of the installed profiles. It is just a merging tool. A snapshot represents the result of merging extension profiles (and custom TTW modifications) into a base profile. How would one go about registering what has to be done to remove an extension profile for instance? Has anybody worked in that direction? http://article.gmane.org/gmane.comp.web.zope.cmf/9194 describes a layer based approach. That might be the way to go, but I'm not sure. 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] Re: reindexing optimizations
Hi! Florent Guillaume wrote: Alec Mitchell wrote: 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']), This was the case in my initial code, but Yuppie changed it: http://svn.zope.org/trunk/CMFCore/TypesTool.py?rev=35903r1=35864r2=35903 I don't remember what the reason was, though I believe it was discussed a bit at the time on the lists. - This change was made 2 years ago, Zope 2.6.3 was not released yet. At that time a full reindex was the *only* way to update the metadata. - indexObject() doesn't call notifyModified() - addCreator(). So who ever modifies that code should make sure addCreator() is still called and indexed. See also http://mail.zope.org/pipermail/zope-cmf/2004-July/020818.html 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] CMF 1.5.5 released
The CMF developer community and Zope Corporation are pleased to announce the release of version 1.5.5 of the Zope Content Management Framework (CMF). This release marks the latest stable release in the CMF 1.5 series and should be suitable for production use. What is the CMF? The Zope Content Management Framework provides a set of services and content objects useful for building highly dynamic, content-oriented portal sites. As packaged, the CMF generates a site much like the Zope.org site. The CMF is intended to be easily customizable, in terms of both the types of content used and the policies and services it provides. Where do I get it? Download it from http://zope.org/Products/CMF/CMF-1.5.5 Points of interest include: - Windows ZIP file, http://zope.org/Products/CMF/CMF-1.5.5/CMF-1.5.5.zip - Unix tar/gzip archive, http://zope.org/Products/CMF/CMF-1.5.5/CMF-1.5.5.tar.gz - Release notes, http://zope.org/Products/CMF/CMF-1.5.5/README.txt - Change history, http://zope.org/Products/CMF/CMF-1.5.5/CHANGES.txt - Installation instructions, http://zope.org/Products/CMF/CMF-1.5.5/INSTALL.txt Where do I go to learn more? The CMF mailing list:mailto:[EMAIL PROTECTED] has many participants who are active in supporting the CMF. ...to report bugs? The CMF Collector:http://zope.org/Collectors/CMF is ths place to report bugs (please search for existing reports of your issue first!) - Jens Vagelpohl [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] CMF 1.5.5 beta phase
On 4 Nov 2005, at 00:18, Jens Vagelpohl wrote: I propose cutting 1.5.5beta this Sunday (November 6th) and having a beta phase lasting 2 weeks, mostly because I'll be in Detroit next weekend and probably won't be able to cut a final release. The weekend after that I'm back in Germany and ready to push out 1.5.5 final. As you've probably seen, 1.5.5 is now out and the 1.5 branch is back in business for changes. Florent, what are your requirements for the events changes you wanted to see in 1.5.5 originally? I'm wondering if that's really 1.6 material now that we have a 1.6 branch? Let me know if you want it in 1.5 and we can plan a 1.5.6 release, or if the 1.6 branch has made this unnecessary for 1.5. 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] CMF 1.5.5 beta phase
On 20 Nov 2005, at 16:06, Jens Vagelpohl wrote: On 4 Nov 2005, at 00:18, Jens Vagelpohl wrote: I propose cutting 1.5.5beta this Sunday (November 6th) and having a beta phase lasting 2 weeks, mostly because I'll be in Detroit next weekend and probably won't be able to cut a final release. The weekend after that I'm back in Germany and ready to push out 1.5.5 final. As you've probably seen, 1.5.5 is now out and the 1.5 branch is back in business for changes. Florent, what are your requirements for the events changes you wanted to see in 1.5.5 originally? I'm wondering if that's really 1.6 material now that we have a 1.6 branch? Let me know if you want it in 1.5 and we can plan a 1.5.6 release, or if the 1.6 branch has made this unnecessary for 1.5. I'm a bit uncertain about the time frame for 1.6, there are a number of constraints behind it. If the GenericSetup backport gets finished and a 1.6.0 release is made in not too long then I'll use that. Otherwise a 1.5.6 would be nice. I intended my changes to make it possible to use events by using super () in a number of places, but that won't even be possible for 1.6 because of these constraints (plone compatible and too much third- party products would break). So if there's a 1.5.6 I want to merge part of my changes into it (see http://svn.zope.org/CMF/branches/1.6/CMFDefault/File.py? rev=40207view=rev) so that I can at least monkey-patch the super() into place from my framework and start using events without waiting for Plone or CMF 2.0. Let's wait a bit and see how 1.6 goes. 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] CMF 1.5.5 beta phase
On 20 Nov 2005, at 16:24, Florent Guillaume wrote: Florent, what are your requirements for the events changes you wanted to see in 1.5.5 originally? I'm wondering if that's really 1.6 material now that we have a 1.6 branch? Let me know if you want it in 1.5 and we can plan a 1.5.6 release, or if the 1.6 branch has made this unnecessary for 1.5. I'm a bit uncertain about the time frame for 1.6, there are a number of constraints behind it. If the GenericSetup backport gets finished and a 1.6.0 release is made in not too long then I'll use that. Otherwise a 1.5.6 would be nice. OK, no problem. Just let me know when you think 1.5.6 is needed. 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: Zope 2 security and SimpleItem
Florent Guillaume wrote:
Florent Guillaume wrote:
I'm in the process of refactoring OFS to use new-style security
declarations (about time ;)), and I stumbled on something which may
or may not be a bug, I don't know, I'd like some else's opinion:
The class SimpleItem has the definition (it's been there since the
begining of time when SimpleItem was created):
__ac_permissions__=(('View', ()),)
The unusual thing here is () instead of ('',).
Hm I now realize that this may be there just to define the View
permission as available but that's all. But there's still a discrepancy
in the way SecurityInfo treats it.
Ok I got to the reasons for that, it all dates back to the origins of
SecurityInfo in December 2000 when it originally had methods that did
the work of both declareProtected and declareObjectProtected. I'll fix this.
Florent
Anyway I'm further in understanding securiy in Z2 than I've ever been :)
Florent
I think the intent here is that it be the object level protection,
equivalent to the modern declareObjectProtected('View').
Indeed, if the SimpleItem class had a
security = ClassSecurityInfo()
(even by itself without further security declaration), then
AccessControl/SecurityInfo, which has the code
# Empty names list sets access to the class itself, named ''
if not len(names):
names = ('',)
would actually turn the () into a ('',) and the rest of the end of
the security setup, in App/class_init.py, would set
SimpleItem.__roles__ = PermissionRole('View') and that would be it.
However SimpleItem does *not* have this ClassSecurityInfo, which
means that the code above is not called, and the final logic in
class_init.py does not turn an empty tuple into protect the object.
It means that SimpleItem does not have an object level protection of
View (but the default which is that only Manager has access), which
is probably as well but not clear from the code.
What do you think I should do?
- fix to use View?
- fix to use nothing?
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
