Details
-
Improvement
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
Quasar
-
Puma Sprint 252
Description
A long time ago, we had the HST Configuration Editor. That was a low-level editor to manipulate HST configuration directly on JCR Nodes via the CMS. This has been dropped a long time ago
However, there is still code that accounts for the fact that the 'HST Configuration Editor' was able to modify main hst configuration nodes like hst:sitemap, hst:pages, etc. This however is never possible any more.
Therefore, code that checks user locks on hst:sitemap, hst:pages, etc is not needed any more (and neither the publishing in case these nodes have changed, but for now we focus on the HST Model loading only)
Also since HSTTWO-3959, the code didn't work anymore any way:
The code
new ChannelLazyLoadingChangedBySet(site, this, ch, hstNodeLoadingCache)
in HstSiteService has the hst:site node as argument while the ChannelLazyLoadingChangedBySet expect the hst:configuration node
Since this is really confusing, also backport this to 14.5