[Zope-CMF] Re: [CMF-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support for configuring content type registry.
Hi Stefan! Stefan H. Holek wrote: Right, so at what point is the content-type-registry supposed to be added now? Plone Site creation breaks after this checkin with: File /Users/zope/plonehd/Products/CMFCore/utils.py, line 83, in getToolByName raise AttributeError, name AttributeError: content_type_registry The change that caused that error is now reverted on the 1.5 branch. It is also temporarily reverted on the trunk to give product developers some more time to update the setup machinery of their products. But CMF 2.0 will not be backwards compatible for code that depends on PortalGenerator because the new setup machinery is completely different. PortalGenerator, manage_addCMFSite and oldstyle configuration data (fti data, workflows - actions are already removed) will soon be removed completely from the trunk. 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: [CMF-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support for configuring content type registry.
Hi Tres! Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan H. Holek wrote: Right, so at what point is the content-type-registry supposed to be added now? Plone Site creation breaks after this checkin with: File /Users/zope/plonehd/Products/CMFCore/utils.py, line 83, in getToolByName raise AttributeError, name AttributeError: content_type_registry Plone needs to kick off a CMFSetup profile which creates all the tools before trying to use them. Over time, there will be *nothing* left in the PortalGenerator class: everything it used to do will be handled in a profile. For BBB, we should chat about what actually happens here. I can't see any need to remove code from PortalGenerator on the 1.5 branch. So far CMFSetup was an optional component of CMF 1.5. Are you sure you wanted to remove that code from the 1.5 branch? Regarding the trunk (CMF 2.0): Up to now I tried to keep manage_addCMFSite and PortalGenerator intact for BBB, but this becomes more and more a big burden. So meanwhile I would agree with dropping support for manage_addCMFSite, PortalGenerator and related code completely. This would mean that all products built on top of the CMF have to ship with a GenericSetup profile for CMF 2.0. 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: [CMF-checkins] SVN: CMF/branches/1.5/C CMFSetup: added support for configuring content type registry.
Right, so at what point is the content-type-registry supposed to be added now? Plone Site creation breaks after this checkin with: File /Users/zope/plonehd/Products/CMFCore/utils.py, line 83, in getToolByName raise AttributeError, name AttributeError: content_type_registry Thanks, Stefan On 14. Okt 2005, at 05:50, Tres Seaver wrote: Modified: CMF/branches/1.5/CMFDefault/Portal.py === --- CMF/branches/1.5/CMFDefault/Portal.py2005-10-13 21:01:27 UTC (rev 39122) +++ CMF/branches/1.5/CMFDefault/Portal.py2005-10-14 03:50:12 UTC (rev 39123) @@ -278,30 +278,6 @@ fti = FactoryTypeInformation(**t) tool._setObject(t['id'], fti) -def setupMimetypes(self, p): -p.manage_addProduct[ 'CMFCore' ].manage_addRegistry() -reg = p.content_type_registry - -reg.addPredicate( 'link', 'extension' ) -reg.getPredicate( 'link' ).edit( extensions=url, link ) -reg.assignTypeName( 'link', 'Link' ) - -reg.addPredicate( 'news', 'extension' ) -reg.getPredicate( 'news' ).edit( extensions=news ) -reg.assignTypeName( 'news', 'News Item' ) - -reg.addPredicate( 'document', 'major_minor' ) -reg.getPredicate( 'document' ).edit( major=text, minor= ) -reg.assignTypeName( 'document', 'Document' ) - -reg.addPredicate( 'image', 'major_minor' ) -reg.getPredicate( 'image' ).edit( major=image, minor= ) -reg.assignTypeName( 'image', 'Image' ) - -reg.addPredicate( 'file', 'major_minor' ) -reg.getPredicate( 'file' ).edit( major=application, minor= ) -reg.assignTypeName( 'file', 'File' ) - def setupWorkflow(self, p): wftool = getToolByName(p, 'portal_workflow', None) if wftool is None: @@ -336,7 +312,6 @@ self.setupTypes(p, PortalFolder.factory_type_information) self.setupTypes(p, Topic.factory_type_information) -self.setupMimetypes(p) self.setupWorkflow(p) def create(self, parent, id, create_userfolder): -- Anything that happens, happens. --Douglas Adams ___ 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 for configuring content type registry.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stefan H. Holek wrote: Right, so at what point is the content-type-registry supposed to be added now? Plone Site creation breaks after this checkin with: File /Users/zope/plonehd/Products/CMFCore/utils.py, line 83, in getToolByName raise AttributeError, name AttributeError: content_type_registry Plone needs to kick off a CMFSetup profile which creates all the tools before trying to use them. Over time, there will be *nothing* left in the PortalGenerator class: everything it used to do will be handled in a profile. For BBB, we should chat about what actually happens here. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDT+ew+gerLs4ltQ4RApXjAKCLzQLK4c4qgj5XmYThECDhwIWZ1gCeJlQS BoyUnKk80KdnhzvnMnmlwRQ= =jUqu -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
