[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 mhammond - Windows DevelopmentMode penalty in CMFCore.DirectoryView, [Accepted] http://www.zope.org/Collectors/CMF/366 Pending / Deferred Issues - FSPropertiesObject.py cannot handle multiline input for lines, text attributes, [Deferred] http://www.zope.org/Collectors/CMF/271 - Can't invalidate skin items in a RAMCacheManager, [Pending] http://www.zope.org/Collectors/CMF/343 - workflow notify success should be after reindex, [Deferred] http://www.zope.org/Collectors/CMF/389 - Possible bug when using a BTreeFolder Member folder, [Pending] http://www.zope.org/Collectors/CMF/441 - Proxy Roles not Working/Applied to Worflow Transition Scripts, [Pending] http://www.zope.org/Collectors/CMF/449 - safe_html filters some tags which should probably not be filtered, [Pending] http://www.zope.org/Collectors/CMF/452 - purge_old in runAllImportSteps not working, [Pending] http://www.zope.org/Collectors/CMF/455 Pending / Deferred Features - Favorite.py: queries and anchors in remote_url, [Pending] http://www.zope.org/Collectors/CMF/26 - DefaultDublinCore should have Creator property, [Pending] http://www.zope.org/Collectors/CMF/61 - Document.py: universal newlines, [Pending] http://www.zope.org/Collectors/CMF/174 - portal_type is undefined in initialization code, [Pending] http://www.zope.org/Collectors/CMF/248 - CMFTopic Does Not Cache, [Deferred] 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, [Deferred] 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 - CMF needs View-based TypeInformation, [Pending] http://www.zope.org/Collectors/CMF/437 - Marker attributes should be deprecated, [Pending] http://www.zope.org/Collectors/CMF/440 ___ 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: 3 OK, 6 Failed
Summary of messages to the cmf-tests list. Period Thu Nov 23 12:00:00 2006 UTC to Fri Nov 24 12:00:00 2006 UTC. There were 9 messages: 9 from CMF Unit Tests. Test failures - Subject: FAILED (failures=3) : CMF-1.5 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:06:10 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003337.html Subject: FAILED (failures=3) : CMF-1.6 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:09:10 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003339.html Subject: FAILED (failures=3) : CMF-2.0 Zope-2.9 Python-2.4.4 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:10:40 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003340.html Subject: FAILED (failures=3) : CMF-2.0 Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:12:10 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003341.html Subject: FAILED (failures=3) : CMF-trunk Zope-2.10 Python-2.4.4 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:13:40 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003342.html Subject: FAILED (failures=3) : CMF-trunk Zope-trunk Python-2.4.4 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:15:10 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003343.html Tests passed OK --- Subject: OK : CMF-1.5 Zope-2.7 Python-2.3.6 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:03:09 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003335.html Subject: OK : CMF-1.5 Zope-2.8 Python-2.3.6 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:04:39 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003336.html Subject: OK : CMF-1.6 Zope-2.8 Python-2.3.6 : Linux From: CMF Unit Tests Date: Thu Nov 23 22:07:40 EST 2006 URL: http://mail.zope.org/pipermail/cmf-tests/2006-November/003338.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
Re: [Zope-CMF] Re: Getting started with CMF
Am 22.11.2006 um 17:37 schrieb Tres Seaver:
The following two commands create the absolute minimum product which
makes filesystem skins availalbe. Run this from your INSTANCE_HOME:
$ mkdir -p Products/myproduct/skins/myproduct
$ cat Products/myproduct/__init__.py EOT
from Products.CMFCore.DirectoryView import registerDirectory
registerDirectory('skins', globals())
EOT
You would then begin putting templates, scripts, etc. into the
'skins/myproduct' directory of the product, e.g.:
$ cat Products/myproduct/skins/myproduct/some_script.py EOT
## Script (Python) some_script
##parameters=
return 'Kilroy was here!'
EOT
Next, register that skin directory in your site's skins tool, by
adding
a Filesystem Directory View using the registered path. Finally, add
the 'myproduct' skins dir to the search path for your skin on the
skins
tool's Properties tab.
That is the business!
One slight addition to make it idiot-proof (or at least Charlie-
proof!) The Filesystem Directory View should be added in the sites
skins folders.
This all begs the question that if, as Jens suggests, file system is
the way to go, surely this process can be automated when creating a
portal?
Charlie
--
Charlie Clark
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-938-5360
GSM: +49-178-782-6226
___
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: Getting started with CMF
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24 Nov 2006, at 13:44, Charlie Clark wrote: This all begs the question that if, as Jens suggests, file system is the way to go, surely this process can be automated when creating a portal? Why? Not everyone who creates a portal wants to develop filesystem products. By the way, *any* code that has unexpected consequences (like creating a portal in the ZODB will create stuff on the file system) is insidious and broken by design. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFZwj4RAx5nvEhZLIRAqsLAJ9CsxyWhp8x6bCT5IohbDAY4U6IAgCcCY2s LBxsvkMdTlvHpadix6ZLHFQ= =Xj9b -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] Re: Getting started with CMF
Am 24.11.2006 um 16:00 schrieb Jens Vagelpohl: This all begs the question that if, as Jens suggests, file system is the way to go, surely this process can be automated when creating a portal? Why? Not everyone who creates a portal wants to develop filesystem products. I was extrpolating from your previous post about the correct way to do customisation: Or, and this is the more complicated but right way to do it, you create a filesystem product with a filesystem skin folders and maintain your new main_template on the file system. By the way, *any* code that has unexpected consequences (like creating a portal in the ZODB will create stuff on the file system) is insidious and broken by design. Agreed but if the consequences are explicit and not unexpected? If customisation through file system is indeed the right way then I don't see why this would be unexpected. Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 ___ 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: Getting started with CMF
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24 Nov 2006, at 16:22, Charlie Clark wrote: I was extrpolating from your previous post about the correct way to do customisation: Or, and this is the more complicated but right way to do it, you create a filesystem product with a filesystem skin folders and maintain your new main_template on the file system. It is true that the better way to store your customizations is in a filesystem skin. However, actions in the ZODB should *not* write back to the sile system. Granted, there are products that are made for that specific purpose (LocalFS etc), but allowing filesystem writes through the ZODB is a big security hole. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFFZw9ARAx5nvEhZLIRAowcAKC6aO6YfO3MxqviTxbURUHP13D3GgCeJk8V podUAGpEHlUIluHbqh5xiJU= =wgMm -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] Re: Getting started with CMF
Am 24.11.2006 um 16:26 schrieb Jens Vagelpohl: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 24 Nov 2006, at 16:22, Charlie Clark wrote: I was extrpolating from your previous post about the correct way to do customisation: Or, and this is the more complicated but right way to do it, you create a filesystem product with a filesystem skin folders and maintain your new main_template on the file system. It is true that the better way to store your customizations is in a filesystem skin. However, actions in the ZODB should *not* write back to the sile system. Granted, there are products that are made for that specific purpose (LocalFS etc), but allowing filesystem writes through the ZODB is a big security hole. I'm in total agreement with you regarding those dangers. This is also a presumably just a small part of the CMF work but it's nice to see this movement towards file system development (of code) and Tres' tip make it extremely easy for customisation to be done in the file system. Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 ___ 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] using adapters in workflow tool
hi folks, in support of more advanced uses of workflow, such as instance specified workflows, and non portal global policy settings, i was interested in modifying the workflow tool to support delegation of interaction with content objects to adapters for workflow chain lookup and workflow state storage. the adapter delegation also means it has basic support for applying workflows to non cmf content. i put together some pseudocode at the link below and was curious if there was interest in something like this. http://svn.objectrealms.net/view/public/cmfblackbird/trunk/ cheers, kapil ___ 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
