SharePoint 2007 网站模板内容类型

发布于 2024-07-14 10:08:58 字数 213 浏览 4 评论 0原文

我是 SharePoint 开发新手。 我们创建了一个基本站点模板,并使用该模板在同一服务器上的其他位置启动新站点。 这工作正常,但新创建的网站似乎“扁平化”了原始网站中创建的自定义内容类型。 我认为有一种方法可以保持原始内容类型继承完整,以帮助支持新网站上的任何必要修改。 他们仍然可以进行修改,但需要更长的时间,因为您必须单独访问每个列表。 有谁知道如何解决这个问题或知道更好的方法来解决这个问题?

I am new to SharePoint development. We have created a base site template and have used that template to start new sites in other locations on the same server. This works fine but the newly created site seems to "flatten" the custom content types created in the original site. I would think there would be a way to keep the original content type inheritance intact to help support any necessary modifications on the new site. They can still make the modifications but they take longer because you have to visit each list individually. Does anyone know how to fix this or know a better way to approach this?

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

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

发布评论

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

评论(2

浅紫色的梦幻 2024-07-21 10:08:58

您遇到的问题是从原始网站集移动到另一个网站集。 站点模板不存储站点的完整定义 - 仅存储与基础站点定义的差异。 从一个网站集移动到另一个网站集时,您会丢失基础网站定义并遇到内容类型丢失等问题。

网站模板和网站定义是您可以进行的两个单独的自定义。 您需要根据您的要求做出最佳决定。

网站模板

优点:

  • 通过 SharePoint 界面轻松创建和重用
  • 最适合最终用户
  • 网站模板是基础默认网站定义的自定义

缺点:

  • 对基础网站定义的依赖意味着 SharePoint 更新可能会破坏您的网站模板
  • 性能差,因为修改保存在数据库中,从数据库中读取并根据每个请求进行编译
  • 自定义选项有限

站点定义

优点:

  • 更难创建:涉及 XML 编码
  • 由开发人员和站点管理员
  • 独立 制作SharePoint 默认网站定义的数量,因此不受 SharePoint 更新的影响
  • 无限制的自定义选项

缺点:

  • 部署时难以修改
  • 可缓存在文件系统上,因此加载速度快

查看 Google for有关创建自定义站点定义的信息。

希望这可以帮助!

强尼

The problem you are having is the move from your original site collection to another. The site template does not store the complete definition of a site - only the differences from the underlying site definition. Move from one site collection to another and you lose the underlying site definition and run into problems such as the loss of your content types.

Site templates and site definitions are two separate customizations you can undertake. You need to make a decision based on your requirements as to which is best.

Site templates

Pro's:

  • Easy to create and reuse through the SharePoint interface
  • Ideal for end users
  • A site template is a customization of the underlying default site definition

Con's:

  • Dependency on underlying site definition means SharePoint updates could break your site templates
  • Poor performance since the modifications are held in the database and are read from the DB and compiled on each request
  • Limited customization options

Site definitions

Pro's:

  • Harder to create: involves coding XML
  • Made by developers and site administrators
  • Independent of SharePoint default site definitions so not affected by SharePoint updates
  • Limitless customization options

Con's:

  • Difficult to modify when deployed
  • Can be cached on the file system so is fast to load

Check out Google for info on creating custom site definitions.

Hope this helps!

Jonny

陌路黄昏 2024-07-21 10:08:58

执行此操作的最佳方法是创建一个网站定义,其中内容类型位于范围为服务器场的功能内。

蒂姆

The best way to do this is to create a site definition where the content types are within features whose scope is to the farm.

Tim

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