HST Configuration Editor Locking - Bloomreach Experience - Open Source CMS

This article covers a Hippo CMS version 10. There's an updated version available that covers our most recent release.


HST Configuration Editor Locking

Through the HST Configuration Editor, some parts of the HST configuration can be modified. Except for hst:workspace configuration, all other configuration items can be modified there. However, it is important to realize that the HST Configuration Editor modifies HST configuration outside the workspace. Since this is the configuration that developers bootstrap configuration changes to as well, we recommend to disable (see  Disable HST configuration editor in production in Channel Manager) the HST Configuration Editor in production environments. If this is not an option, extra care must be taken by developers when merging their local changes. 

How to get to the HST Configuration Editor?

The HST Configuration Editor is accessed through the chain link icon in the far right corner in the Channel Manager toolbar:


When opening the URL and Navigation Management, a webmaster sees a representation of the HST configuration : 


In the example above, the about sitemap item is selected, and apparently it is locked by the user  editor at 4/27/15. As of Hippo 7.9.0 the locking logic for the sections available in the URL and Navigation Management are:

  1. Inherited configuration items are recommended be configured to be immutable, see Lock inherited hst configuration nodes in hst configuration editor in production at  Channel Manager.
  2. Sitemap, Templates and Catalogs are either completely locked or completely unlocked.

So the locking in the HST Configuration Editor is rather coarse grained: a section that is editable is either completely locked or completely unlocked. Whenever a webmaster makes a change to one sitemap item, catalog item or template, they locks the entire sitemap, catalog or templates section. Note that the workspace sitemap has much more fine grained locking.

Did you find this page helpful?
How could this documentation serve you better?
On this page
    Did you find this page helpful?
    How could this documentation serve you better?