如何有效地将内容类型部署到内容类型中心

发布于 2024-09-27 16:30:19 字数 385 浏览 0 评论 0原文

我已经设置了一个内容类型中心,并通过创建测试内容类型并观察其发布到客户端站点来测试联合是否正常工作。

然后,我部署了我实际上有兴趣发布到中心(通过功能)的内容类型以及它们所依赖的网站栏。

我收到错误

内容类型“...”无法发布到此网站,因为功能“...”未启用。

我想部署具有可升级性和易于移植功能的内容类型开发、质量和生产环境。但我不明白该中心的好处是什么。

如果我必须激活部署功能,则在发布之前内容类型将已经存在于网站上。如果我必须使用 Web UI 在 Hub 站点上手动创建内容类型(哎呀!),我会遇到尝试手动保持三个景观同步的问题。

有没有一种方法可以有效管理到 Hub 的内容类型部署,同时仍然使用 Hub 发布内容类型?

I have set up a Content Type Hub and tested the syndication is working correctly by creating a test content type and watching it be published to the client site.

Then I deployed the content types I am actually interested in publishing to the hub (by way of a feature) along with the site columns they depend on.

I get the error

Content type '...' cannot be published to this site because feature '...' is not enabled.

I want to deploy content types with features for upgradability and ease of porting between dev, qual and prod environments. But am left not understanding what the benefit of the Hub is.

If I have to activate the deploying feature, the content types will already be on the site before publishing will take place. If I have to manually create the content types on the Hub site with the web UI (yuck!), I have the issue of trying to keep three landscapes manually synchronized.

Is there a way to efficiently manage content type deployment to the Hub while still using the Hub to publish the content types?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

陌上芳菲 2024-10-04 16:30:19

使用内容类型中心的优点是,它允许您在整个服务器场的多个网站集和 Web 应用程序上使用和重用内容类型。

由于您的所有网站集现在都使用相同联合内容类型的实例,因此如果将来您需要在内容类型中添加/删除/重命名列,则只需更新内容类型并重新订阅即可轻松完成此操作(然后允许 sharepoint 运行其计时器作业,并仔细检查更改是否已更新,因为您是细心的 SharePoint 管理员)。

我不确定您收到哪个错误,您的帖子中根本没有足够的上下文。但是,我认为您可能对联合内容类型的发布方式有些困惑。首先,您在网站集中打开内容联合中心发布功能,该功能包含您要在整个服务器场中重复使用的所有内容类型。接下来,您配置混合元数据服务,以便 SharePoint 将每个内容类型或多或少地加载到“内存中”。

执行此步骤后,您可以选择要订阅联合中心的网站集。为此,您需要打开内容类型发布网站集功能。注意:如果您的网站使用空白模板,则由于空白模板存在“缺陷”,您可能会收到如上所述的功能错误。请参阅我的帖子:http://www.thesharepointblog.net/Lists/ Posts/Post.aspx?ID=109

仅在您打开订阅功能并且内容类型中心计时器作业已运行并且订阅计时器作业已运行之后,您的网站集才会看到可用的内容类型。

至于在中心网站上手动创建内容类型,唯一的 OOB 方法是使用 UI。就我个人而言,我编写了一个实用程序,它可以完成我刚刚为我描述的所有操作,从创建初始内容类型到创建联合中心,将它们发布到所有网站集,以及最耗时的将它们与所有列表和内容相关联。订阅网站集上的图书馆。我原本打算让我的雇主公司出售它,但由于他们似乎不感兴趣,如果有足够的兴趣,我可以将其开源。

希望这有帮助。

The advantage of using the Content Type Hub, is that it allows you to use and reuse your Content Types over multiple site collections and Web Applications throughout your farm.

Because all of your site collections are now using instances of the same syndicated content types, if, in the future, you need to add/remove/rename columns within the content types, this is done as easily as updating the content type, and resubscribing (then allowing sharepoint to run its timer jobs, and double checking that the changes updated because you're a careful SharePoint administrator).

I am not sure which error you are receiving, there simply isn't enough context in your post. However, I think you may be slightly confused on how syndicated content types are published. First, you turn on the content syndication hub publishing feature on the site collection that holds all of the content types you are going to reuse throughout your farm. Next you configure the mixed metadata service, so that SharePoint loads each of your content types "into memory" more or less.

After this step, you get to choose which site collections you want to subscribe to the syndication hub. To do this, you need to turn on the content type publishing site collection feature. Note: If you use blank templates for your sites you may receive a feature error like you've described, due to a "flaw" with blank templates. See my post at: http://www.thesharepointblog.net/Lists/Posts/Post.aspx?ID=109

Only AFTER you've turned on the subscribing feature, And content Type Hub timer job has run, AND the subscribing timer job has run, will your site collection see the available content types.

As for manually creating content types on the hub site, the only OOB way of doing this is to use the UI. Personally, I wrote a utility that does everything I just described for me, from creating the initial content types, to creating the syndication hub, publishing them to all of the site collections, and most time consumingly, associating them with all of the lists and libraries on the subscribing site collections. I had intended for my employing company to sell it, but as they don't seem interested, I could open source it if there is enough interest.

Hope this was helpful.

再见回来 2024-10-04 16:30:19

这看起来确实是集线器的一个缺点。
我以前就亲眼目睹过。

如果您已将内容类型部署到中心,请检查内容类型元素的 INHERITS 标记是否设置为 TRUE。否则它将无法在集线器中工作。

<ContentType ID="xxxxx"
    Name="xxxx"
    Group="xxxx"
    Description="xxxx"
    Inherits="TRUE"
    Version="0">
</ContentType>

This looks like a shortcoming of the hub, indeed.
I've witnessed it before.

If you've deployed your content type to the hub, please check if the INHERITS tag of the content type element is set to TRUE. Otherwise it won't work in a hub.

<ContentType ID="xxxxx"
    Name="xxxx"
    Group="xxxx"
    Description="xxxx"
    Inherits="TRUE"
    Version="0">
</ContentType>
╰つ倒转 2024-10-04 16:30:19

不要忘记,您实际上可以在场之间同步内容类型 - 当您在单独的场上进行开发并且不想使用 PnP 框架来管理您的内容类型时,这尤其有价值...在某些情况下,内容类型可能已经存在于生产场中,并且您需要在开发和/或测试中获得它们的副本。

Don't forget that you can actually synchronize the content types BETWEEN farms -- this is especially valuable when you are developing on a separate farm and don't want to hassle with a PnP Framework for managing your content types... In some cases, the Content Type may already exist on the production farm and you need a copy of them on dev and/or test..

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文