Publishing, Un-publishing, and Republishing
The creation of a content type for the publication in the content type hub is identical to that to create satisfied seize a collection of site of non-hub. However, when an administrator of collection of site creates satisfied seize the hub, SharePoint present of the additional options of configuration in the Content Type Settings
. Once you achieved the stages in the preceding section to indicate a satisfied type hub, the following stages show to create a new content type for the publication with another collection with site with subscriber.
- Open the Content Type Hub Site Collection.
- Navigate to the Content Type Gallery from the Site Collections Settings page.
- Click the Create link at the top of the page to create a new content type.
- Give the new content type a name, description, and parent and save it.
- I created a simple content type and inherited from the standard Item content type.
- Navigate to the Content Type Settings page, like that in Figure 2.
- Click the link to Manage publishing for this content type.
- The next page shows three options: Publish, Un-publish, and Re-publish (update).
- Choose Publish and click the OK button.
Note If
you receive an error about an incorrect proxy at this stage, then
either your site collection hub in the Managed Metadata Service is
incorrect (if it is a root site collection, use the / on the end of the
URL), or you need to change the URL using the following PowerShell
command:Set-SPMetadataServiceApplication "Managed Metadata Service" –HubUri http://site_collection_hub
- From the consumer site collection, navigate to the Site Settings page.
- In the Site Collection Administration section, click the Content Type Publishing link.
- If you do not see your published content type in the Hubs section, check the error log by clicking the link shown.
Note By
default, the consumer timer job runs every hour and the hub timer job
every 15 minutes. The consumer timer job looks after creating and
updating shared content types in consumer site collections; the hub
timer job notifies consumers of changes to existing shared content
types or the existence of new shared content types.
To stop publishing the content type at the hub, continue with the following steps:
- Navigate to the Content Type Gallery from the Site Settings page of the hub site collection.
- Select the published content type to view the settings for the content type.
- Click the Manage Publishing for This Content Type link.
- Click the Un-publish option and then the OK button.
Note You
cannot delete a published content type. In addition, changes to a
content type in the hub do not update the consumers until you republish
the content type.
Once a site collection administrator publishes
a content type, the timer jobs complete and the content type is
available to consumers, who may use the content type as if defined
locally. Site collection administrators of the consumer site collection
may inherit from the content type or use the content type in the sites
and lists of the site collection.
- Navigate to the Content Type Gallery in the consumer site collection.
- Scroll to find the Consumed content type in the gallery.
- Click the name of the Consumed content type to view the Settings page.
- Click the Advanced Settings link.
- By default, the Consumed content type is read-only; to allow changes to the Consumed content type, change the read-only setting.
The Error Log
When either the content type syndication
consumer or publisher timer job encounters an error, it reports an
error in the syndication error log—a list available under the Site
Administration section of the Site Collection Site Settings page.
Administrators may also access the error log from the link on the
Manage Publishing for This Content Type page.
Assuming the administrator did not disable the
setting to report syndication errors in the Managed Metadata Service,
SharePoint tries to be as verbose as possible in the syndication log. Table 1 depicts the columns in the error log.
Table 1. Columns in the Content Type Syndication Error Log
Title |
Error title |
Taxonomy Service Store ID |
GUID of the term store in the Managed Metadata Service |
Taxonomy Service Name |
Name of the Managed Metadata Service |
Content Type Subscriber Site |
Link to the consumer site with syndication error |
Syndication Item |
Content type that failed to synchronize |
Syndication Failure Stage |
Stage at which the syndication failed |
Syndication Failure Message |
Specific details about the error |
Syndication Failure Time |
Timestamp that the error occurred |
Sometimes the error log may report no errors
and after successful execution of syndication timer jobs, the consumer
site collection has no content types from the hub. The following list
identifies a few reasons for this that I have encountered during my
research:
- The document ID feature is enabled on either hub or consumer but
not on the other—this feature must be enabled or disabled on both.
- The Managed Metadata Service proxy is not configured to consume
content type publications—enable it from the properties of the Managed
Metadata Service.
- I came across one instance in which the consumer failed
with an error in the log about unknown site ID. This occurred when I
checked the option to consume content types in the properties of the
Managed Metadata Service proxy, post creation of the consumer site
collection. I remedied the issue by re-creating the site collection,
once the Consumer Web Application MMS proxy allowed the content type
consuming option.