处理 Sitecore 6.4 克隆站点中的内部链接
我们正在尝试建立 Sitecore 6.4 架构，通过该架构我们可以从“存储库”站点克隆多个站点。
我们已经解决了许多有关数据结构的问题，但还剩下一个关键问题：
我们如何处理克隆站点中的内部链接？
克隆的想法是允许对小部分数据进行本地修改，但对主体内容进行集中编辑。直接在克隆项目中进行编辑会破坏从其父项目的继承，至少在编辑的字段中是如此。
但是：Sitecore 内部链接存储为 GUID。克隆整个站点时，其中的所有链接都将引用回父站点。当链接位于存储项目内容主体的富文本字段中时，这尤其成问题。使用指向克隆结构中相关项目的链接替换该链接将破坏该字段的继承。
在 Sitecore 提供更复杂的解决方案之前，是否有人开发出解决方法？看起来它需要对 LinkManager 进行重大扩展，并且可能需要一些令人遗憾的可靠链接规则。
欢迎提出想法、解决方案、想法。
编辑：交叉发布到SDN论坛，那里没有太多帮助。
We are attempting to establish a Sitecore 6.4 architecture whereby we clone several sites from a "repository" site.
We have addressed many issues regarding data structure, but are left with one key problem:
How do we handle internal links within a cloned site?
The idea of cloning was to allow local modification of small parts of data, but central editing of the main body of content. Editing directly in a cloned item breaks inheritance from its parent, at least in the field that is edited.
But: Sitecore internal links are stored as a GUID. When cloning an entire site, all links in it will refer back to the parent site. This is particularly problematic when the links are in a rich text field, storing the main body of content of an item. Replacing the link with a link pointing to the relevant item within the cloned structure will break the inheritance on this field.
Has anyone developed a workaround, until Sitecore provide a more sophisticated solution? It would seem that it would require significant extension of the LinkManager and possibly some regrettably solid rules for linking.
Ideas, solutions, thoughts welcome.
Edit: Cross posted to SDN Forum, not a great deal of help there.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我说的对吗？您希望克隆站点在克隆后是独立的？
因此，在存储库中，您有 /respository/home ，其中包含指向 /respository/home/product 的链接
一旦克隆，您希望它成为 /cloned/home ，并带有指向 /cloned/home/product 的链接（而不是 /respository/home/product ）
以下引用抛出了我对问题的理解，因为它似乎与此相矛盾 - “如果链接位于例如富文本字段中，则重写链接将破坏该字段的继承，从而失去拥有中央数据存储库的好处对于许多网站来说。”
使困惑！
Am I right in saying you want the cloned site to be self-contained once cloned?
So in the repository you have /respository/home with a link to /respository/home/product
Once cloned you want this to become /cloned/home with a link to /cloned/home/product (and not /respository/home/product )
The following quote is throwing my understanding of the problem, as it appears to contradict this - "If the link is in e.g. a rich text field then rewriting the link will break inheritance for that field, losing the benefit of having a central data repository for many sites."
Confused!