New answers tagged content-type-hub
Alternatively, you can provision your lookup column with a feature receiver everytime you create a new website. You just need to make sure you have the lookup list available somewhere (which, by the way, CAN BE in a different web site). There is a quick and easy to implement guide which you can find here: ...
Lookup columns will only lookup data in lists in the same site/web. When the content type hub functionality deploys your content type to other sites, the lookup list does not exist there, so the column is removed. The best way to do this is to use a managed metadata term set instead. The term set is globally available to all site collections. So you can add ...
The neatest way to do this is probably with content type inheritance. Start with your base content type that you want to be used in most sites. Then create a "sub" content type which inherits from the base content type, but add in the extra choice fields that you want to use in only in some sites. The just use your base content type on sites that only ...
I think that's the default behavior of publishing content types (as a whole, I think that's the idea), I don't know a way to publish the content type excluding columns, so my recommendation is unsubscribe your special subsite from the Content Type Hub or everytime you publish your content type it'll erase your special choices and you'll have to recreate it ...
I think Content Type hub is best solution because even you can create content types using features across site collections, however any updates made to the content types cannot be easily propogated to different site collections. Only CTH will give you this functionality. Content Types Synchronization across Site Collections
You would need to create a site collection scoped feature that would create them and add them to the content type gallery if you are not going to use a content type hub. This makes upkeep much more complex, so I'd encourage the use of a hub if possible.
Top 50 recent answers are included