Sitecore 编辑器的预览站点

本文介绍了Sitecore 编辑器的预览站点的处理方法，对大家解决问题具有一定的参考价值，需要的朋友们下面随着小编来一起学习吧！ 问题描述

我们的内容编辑人员希望有一个指向主数据库的预览站点.该站点可用于预览网页在实时站点上的外观.用户对使用 Sitecore 中的预览"选项不太满意.此站点将指向 CMS 服务器并与 CMS 站点(用于内容编辑)分开.我们不能使用 CMS 站点来预览数据的原因是 HTML 缓存开始发挥作用，并且在呈现页面时不会立即更新内容.

Our content editors would like to have a preview site that would point to the master database. The site can be used to preview how the web page would look on the live site. The users aren't really comfortable using the 'Preview' option inside Sitecore. This site would point to the CMS server and be separate from the CMS site (used for content editing). The reason we can't use the CMS site to preview data is that HTML caching comes into play and content is not updated right away when a page is rendered.

通过设置一个单独的预览站点，我们计划在该站点上禁用缓存，并将其纯粹用于内容检查.我知道在站点部分的配置文件中有一个名为cacheHtml"的设置，它将在配置中设置为 false.我的问题是采用我们正在采用的方法是否安全.关闭预览网站的 HTML 缓存会导致任何不必要的问题吗?

By setting up a separate preview site, we plan to disable caching on this site and use it purely for content checking. I know there is a setting in the config files in sites section called "cacheHtml" which would be set to false in the config. My question is that is it safe to take the approach we are going with. Would turning off the HTML cache for the preview site cause any unwanted issues?

推荐答案

这是一个有效的方法.我有一篇关于它的博客文章:如何设置 Sitecore 预览站点以在发布前查看内容

This is a valid approach. I have a blog post on it: How to Setup a Sitecore Preview Site to Review Content Before Publishing

需要考虑的一件事是，如果您有 Lucene.NET 索引，除了 Web 数据库之外，它还需要基于主数据库.您可以在此处查看如何为 master 和 web 配置它们:跨主数据库和 Web 数据库配置 Sitecore 搜索索引支持

One thing to consider is if you have Lucene.NET indexes that would need to also be based on the master DB in addition to the web DB. You can see how to configure them for master and web here: Configure Sitecore Search Index Support across Master and Web Databases