Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>If you're running a single instance of Sitecore to serve your site then the Lucene indexes on the web database are automatically updated when an item is published. [<strong>EDIT:</strong> Having read the document linked to by Kyle in his answer, I'm going to double-check that this isn't dependant on the history engine, which I add to projects as a matter of course]</p> <p>If you're running an old version of Sitecore (6.2 or lower) and are using the staging module to maintain one/several front-end servers and an authoring server then you'll need to add the <code>HistoryEngine</code> on the web database (or whatever publishing target you're using) and set the <code>Indexing.ServerSpecificProperties</code> setting to <code>true</code> (I'm not sure at what version this setting was introduced - if you don't see it then you should probably consider upgrading if possible).</p> <p>If you're running Sitecore 6.3 or above, I believe (and I haven't tested this yet) that the CD instances should automatically re-index content after a publish from the CM server as though it were a single instance due to the event syndication. I'll check this later.</p> <p>For anyone wondering what the <code>HistoryEngine</code> is, it's really just a very simple log of what has changed in the database and when. Whenever something changes, the event is recorded there. This allows pre-6.3 instances to keep a handle on what's changed when they're disconnected from the content authoring instance. If you're curious, enable it and have a look at the History table in the database.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload