>> "manually create" these identical parent content types across multiple site >> collections?
The problem with manually creating content types is that you cannot control the Content Type ID used it is generated when you create the content type in different site collections. When deploying content types as features you specify the content type id your custom content types should use and the same content type id you specified is always used. It depends on what you are trying to do really, you can get away with manually creating content types in all site collections, but by developing and deploying the same content types using features you can ensure the same content type ids are used for the same common content types across all site collections, therefor avoiding issues you mentioned earlier regarding linking to parent content types and deploying to multiple site collections. Sezai Kömür Senior Developer - BEng, BSc - Microsoft Certified Technology Specialist - http://www.moss2007.com.au/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trevor Andrew Sent: Wednesday, 14 May 2008 10:54 AM To: [email protected] Subject: RE: [OzMOSS] RE: Content Types and Content Type Hierarchies Hi Sezai, Thanks for that ... So it sounds like I should very much be expressing my concern with a plan to "manually create" these identical parent content types across multiple site collections? Thanks for your very quick response. Cheers, Trevor Andrew From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Sezai KOMUR Sent: Wednesday, 14 May 2008 12:44 PM To: [email protected] Subject: RE: [OzMOSS] RE: Content Types and Content Type Hierarchies >> I assume best practice would suggest creating all Content Types once and >> once only and distributing them as features to all of the Site Collections >> that need them. Is this the best approach? Yes you need your base/parent content type deployed to all site collection which will make use of content types that inherit from your base content type. By deploying content types as features you can activate the same content type feature on all your site collections which need to use them, so the same Content Type IDs will be used in all site collections which should avoid issues. Sezai Kömür Senior Developer - BEng, BSc - Microsoft Certified Technology Specialist - http://www.moss2007.com.au/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Trevor Andrew Sent: Wednesday, 14 May 2008 10:29 AM To: [email protected] Subject: [OzMOSS] RE: Content Types and Content Type Hierarchies Hi All, Can I confirm my understanding of the correct use of Content Types across multiple site collections? My understanding is that the moment you create a content type that inherits from one of the base SharePoint content types (say Content Type A), via the user interface, a Content Type ID is created which is a concatenation of the parent Content Type ID and a GUID. Now if you create an attribute / column equivalent content type in another site collection, it will acquire a different Content Type ID. If you then create a further content type that inherits from Content Type A in one of the site collections, my understanding is that these "child" content types will not be deployable to the other site collection, even as features, because they won't recognise the "other version" of Content Type A as a valid parent. Is this correct, or will it "link up" correctly? I assume best practice would suggest creating all Content Types once and once only and distributing them as features to all of the Site Collections that need them. Is this the best approach? Kind Regards, Trevor Andrew p: (03) 9323 5246 m: (0407) 535 615 e: [EMAIL PROTECTED] ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com ------------------------------------------------------------------- OzMOSS.com - to unsubscribe from this list, send a message back to the list with 'unsubscribe' as the subject. Powered by mailenable.com
