Sitecore 6.4 - 发布克隆

发布于 2024-10-25 08:27:46 字数 522 浏览 3 评论 0原文

根据我对克隆工作原理的理解,当对克隆的父级的更改发布到 Web 数据库时,该更改对于克隆也应该立即显而易见,因为克隆字段仅引用父级的字段。

然而,虽然我可以立即看到内容树中克隆的更改(已经在保存事件中),但发布父级似乎不会影响 Web 数据库中的克隆 - 旧值会被保留 - 至少暂时如此。发布克隆会将更改推送到网络上的克隆。

整个站点的增量发布并没有强制更新。

查看 Web 数据库的内容树中的克隆会显示该克隆包含旧数据(毫不奇怪)。

保存克隆,然后增量发布确实会强制更新网络上的克隆。

从所有这些我推测,克隆实际发生的情况是,当克隆本身被保存/发布时,它们的数据被读入网络数据库,而不是它们实际上只是引用指针。尽管主数据库克隆显然起到了参考的作用。

这似乎允许相当大的灵活性,并且我希望看到的功能可以在此基础上构建 - 当更新克隆的父级时,克隆的所有者会收到通知并可以选择是否接受更新。当前仅当克隆所有者覆盖字段时才可能出现此通知。

任何人都可以阐明这一点吗?

编辑:交叉发布到SDN论坛,没有回复。

From my understanding of how cloning works, when a change to a parent of a clone is published to the web database that change should be immediately apparent for the clone as well, as the clone fields merely reference the fields of the parent.

However, while I can see changes immediately in clones in the content tree (already on the save event) publishing the parent doesn't seem to affect the clone in the web database - old values are maintained - at least temporarily. Publishing the clone will push the change to the clone on the web.

Incremental publish of entire site didn't force update.

Viewing the clone in the content tree in the web database showed the clone with old data (unsurprisingly).

Saving the clone, then incrementally publishing did force the update to the clone on the web.

From all of this I surmise that what actually happens with clones is that their data is read into the web database when the clones themselves are saved/published, rather than that they are truly just reference pointers. Though the master database clones are apparently functioning as references.

This would seem to allow for a fair amount of flexibility, and the functionality I'd like to see could feasibly be built on top of this - that when a parent of a clone is updated an owner of the clone receives a notification and can choose whether to accept the update. This notification is currently only possible when the clone owner has overwritten a field.

Can anyone shed any light on this?

Edit: cross posted to SDN forum, no response there.

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

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

发布评论

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

评论(1

入怼 2024-11-01 08:27:47

有一些关于克隆和发布以及跨数据库克隆(尚不支持)的半官方信息。

关于发布:

发布将克隆数据转换为字段值。

关于跨数据库克隆:

Sitecore 6.4 UI 不支持跨数据库克隆,但这似乎是不可避免的。

参考:http://www.sitecore.net/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2010/10/Sitecore-CMS-6-4-Cloning.aspx

There is some semi-official information regarding clones and publishing and also regarding cross-database clones (which aren't supported, yet).

Regarding publishing:

Publishing converts cloned data to field values.

Regarding cross-database clones:

The Sitecore 6.4 UI does not support cross-database clones, but this seems inevitable.

ref: http://www.sitecore.net/Community/Technical-Blogs/John-West-Sitecore-Blog/Posts/2010/10/Sitecore-CMS-6-4-Cloning.aspx

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