Tag Info

Hot answers tagged

4

You don't need a content type hub with a single site collection. The benefit of the hub comes into play when you have multiple site collections in the same Web Application that share content types and you want to manage all of the content type updates in a single place (the hub).


2

So if this is happening to you you should first publish your content type, at your content type hub. From there you should click "Manage publishing for this content type" and you will see 3 options: Publish Make this content type available for download for all Web Applications (and Site Collections) consuming content types from this location. Unpublish ...


2

I just ran into this issue. While watching the SharePoint logs I found that the field in question was added locally to the site columns instead of added using the content type hub. So when trying to update the content type there was an error due to two columns with the same name (the one at the content type hub and the one local). The fix was to delete the ...


1

From an administrative and cost savings perspective, this makes total sense. I'd try make sure that each of the old farms has their own host name to give them the feeling nothing has changed regardless of where the farm and content resides. The biggest barrier that you said is really the organizational and political aspect. It is technically possibly to ...


1

One reason to beware of many content types is the impact it has on general site collection creation times. Each time a new site collection is created, all syndicated content types in connected hubs are copied down to it. So the more content types you have the slower it becomes to create site collections. In our staging environment, we found that once we ...


1

You shouldn't have any issues by updating the template. Just make the change in your content type hub and re-publish the content types. Documents that were created with the old template will not be updated to target the new template though. If that has to happen, they need to be updated manually.


1

I have only worked in SP2010, so not all of this may apply to SP2013. But at least in SP2010: A content type hub provides a centralized place to manage your content types (which I'm sure you've read about). You say that the number of content types you are using and the metadata for those content types is unlikely to change, but... what if they do? By ...


1

Resolution I sent a support ticket to Microsoft and after a few days of phone calls, we found a resolution. Below is the closing transcript of the issue from Microsoft: Issue Statement: Unable to publish Content Types through Content Type Hubs Scope Agreement: High as customer is not able to use the feature of content types on his production sites ...


1

This looks to me like when you deleted the content type you didn't actually delete the columns related to the content type. Now you are trying to publish a content type from the root with that 'DataObject' column in it but there already exists a 'DataObject' column in your site collection. Have you searched your site columns to ensure that you don't ...


1

I don't know if you still face this problem, but I just had the same problem and the solution might be of use to others as well. It appears to be due to the content type being created in an Enlish site (/sites/contenttypehub), and being succesfully published to (and showing up in) our English team site (/), but not to the Dutch subsite /vaktechniek. After I ...


1

Your sub sites will have the content types. Make sure that you have created the content types, and the hub, on the root site. You know that you are on the root site because if you go to site settings, you will see the "Site Collection Administration". Really the only possibility is that the hub is not coming from the root site of the site collection (I ...



Only top voted, non community-wiki answers of a minimum length are eligible