[Zope-CMF] CMF Tests: 4 OK
Summary of messages to the cmf-tests list. Period Mon Feb 15 12:00:00 2010 UTC to Tue Feb 16 12:00:00 2010 UTC. There were 4 messages: 4 from CMF Tests. Tests passed OK --- Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.6 : Linux From: CMF Tests Date: Mon Feb 15 20:55:52 EST 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-February/012619.html Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.6 : Linux From: CMF Tests Date: Mon Feb 15 20:57:52 EST 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-February/012620.html Subject: OK : CMF-2.2 Zope-2.12 Python-2.6.4 : Linux From: CMF Tests Date: Mon Feb 15 20:59:52 EST 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-February/012621.html Subject: OK : CMF-trunk Zope-trunk Python-2.6.4 : Linux From: CMF Tests Date: Mon Feb 15 21:01:52 EST 2010 URL: http://mail.zope.org/pipermail/cmf-tests/2010-February/012622.html ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Making GenericSetup property import less strict
Hi! Wichert Akkerman wrote: > I am running into an interesting problem: it appears to be impossible to > write a FTI that works in both CMF 2.1 and 2.2. The problem are content > icons: CMF 2.1 requires a content_icon property in the FTI to configure > the icon, while CMF 2.2 requires icon_expr. Unfortunately you can not > have both in your FTI since GenericSetup will abort when it encounters > an unknown property. The only two possible solutions are to have > separate FTIs for CMF 2.1 an CMF 2.2, or to not use icons at all. This should work: Just add 'content_icon'. CMF 2.1 knows that property and CMF 2.2 has some migration code that converts this to an 'icon_expr' property. HTH, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
[Zope-CMF] Making GenericSetup property import less strict
I am running into an interesting problem: it appears to be impossible to write a FTI that works in both CMF 2.1 and 2.2. The problem are content icons: CMF 2.1 requires a content_icon property in the FTI to configure the icon, while CMF 2.2 requires icon_expr. Unfortunately you can not have both in your FTI since GenericSetup will abort when it encounters an unknown property. The only two possible solutions are to have separate FTIs for CMF 2.1 an CMF 2.2, or to not use icons at all. I would like to propose a simpler alternative: modify GenericSetup to only log a warning when it encounters an unknown property instead of aborting. That way we get automatic backward and forward compatibility support, while not breaking anything. Unless there are any objections I intend to make this change in svn later this week. Wichert. ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
