Be aware that Content Type deployment via Features using declarative XML doesn't work with inheritance changes. For example, your content type 'Letter' is deployed via a Feature using XML. You use this content type in various locations in your site collection. You add a new field to your content type using XML and redeploy via the Feature. Your original content type that is used in lists doesn't change, however if you add the updated content type to a new list it displays the new field.
You can get around this limitation via SharePoint's OM and a couple of people have created a stsadm extension. The first link also has a great explanation of the limitation. http://soerennielsen.wordpress.com/2007/09/11/propagate-site-content-types-to-list-content-types/ http://stsadm.blogspot.com/2008/05/propagate-content-type-changes.html Note: This doesn't (or shouldn't) happen if you create the content type through the UI. When you add a new field to a content type that has been created in the UI then inheritance should be honoured. Just thought I would point you to a problem when using Content Types deployed via Features and declarative XML. Clayton James FlarePoint Pty Ltd |t +61 7 3821 7178 |f + 61 7 3821 7175 |m 0402 463 276 | w http://www.flarepoint.com.au<http://www.flarepoint.com.au/> From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Paul Turner Sent: Thursday, 5 March 2009 8:55 PM To: ozmoss@ozmoss.com Subject: RE: Content types ... Same problem here... I'd say it is a bug... drives me nuts. :( Clearing/deleting the content type and redeploying the feature fixes it but it is painful. Regards Paul Turner Senior Solutions Specialist M: 0412 748 168 P: 08 8238 0912 F: 08 8234 5966 A: 66 Henley Beach Rd, Mile End SA 5031 E: paul.tur...@dws.com.au<mailto:paul.tur...@dws.com.au> W: www.dws.com.au<http://www.dws.com.au/> [cid:image001.png@01C99DDE.EEF6C4E0] ADVANCED BUSINESS SOLUTIONS LTD This email and any files transmitted with it are confidential and are only for the use of the person to whom they are addressed. If you are not the intended recipient you have received this email in error and are requested to delete it immediately. Any opinion expressed in this e-mail may not necessarily be that of DWS Pty Ltd. Please consider the environment before printing this email. From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Uzma Naz Sent: Thursday, 5 March 2009 9:10 PM To: ozmoss@ozmoss.com Subject: RE: Content types ... Thanks for the reply Paul, in a way it's good to see that I'm not the only one seeing these problems! The sites are publishing sites, but have a sneaky feeling that they originally were WSS ones with features enabled. Will note down your comments and check on how to create content type features for future plans! Many thanks, Uzma ________________________________ Date: Thu, 5 Mar 2009 08:50:53 +1100 From: paul.no...@ceosyd.catholic.edu.au Subject: RE: Content types .. To: ozmoss@ozmoss.com Hi Uzma, Are the doc libraries on publishing sites, or WSS sites with publishing feature enabled? I have seen this in our farm too. At first I thought it may have been due to accidental changes to the content types on the doc libraries. For example, if someone inadvertently made changes to an attached content type via the doc library (instead of at the site collection level) then the content type would not inherit pushed down changes. It's almost as though inheritance gets broken. It also seems that not all changes get pushed through, all the time, but this may be more of a bug than a configuration issue. The other thing I noticed is that you can receive an error when opening or creating docs because of a template mismatch. Had you provided a custom form for the content type? If so, then this could also be your problem. Also, I would recommend deploying your content types as features. This seems more secure and easier to manage/migrate. Regards, Paul Online Developer, ICT CEO Sydney From: ozmoss@ozmoss.com [mailto:ozm...@ozmoss.com] On Behalf Of Uzma Naz Sent: Wednesday, 4 March 2009 10:59 PM To: ozmoss@ozmoss.com Subject: Content types .. Hey guys, Having a blonde moment... I'm having troubles with Content Types on my Intranet. I have a document based content type which has 3 fields, let's call it Letters. About 50 sites have content type management enabled and I have added Letters content type to the site A. I've always thought that when you update the content type from the site home, inheritance kicks in and all sites are updated. So I've added a new custom column to the content type Letters from the site root, hit OK ensuring all sites with this content type is enabled. I check the content type on a site A and the field has not been updated. However if I remove the content type and add it again, the new fields are added. Have I set something up incorrectly on the Intranet or is this simply just "SharePoint". I understand the importance of locking down metadata before mass creating sites, but when a situation occurs when you need to update a content type that *should* aggregate across the collection.... and it doesn't... what does one do? Maybe I'm missing a vital point in this?? Uzma ________________________________ Windows Live just got better. Find out more!<http://clk.atdmt.com/UKM/go/134665375/direct/01/> ________________________________ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Windows Live just got better. Find out more!<http://clk.atdmt.com/UKM/go/134665375/direct/01/> ________________________________ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists ________________________________ Support procedure: https://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.237 / Virus Database: 270.11.6/1980 - Release Date: 03/02/09 23:02:00 -------------------------------------------------------------------------------- Support procedure: http://www.codify.com/lists/support List address: ozmoss@ozmoss.com Subscribe: ozmoss-subscr...@ozmoss.com Unsubscribe: ozmoss-unsubscr...@ozmoss.com List FAQ: http://www.codify.com/lists/ozmoss Other lists you might want to join: http://www.codify.com/lists
<<inline: image001.png>>
