Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
There were 2 problems:
1) ever since there is a <div class="selects"> container for the selects, the from-cache updates would cause the HTML to be put in the wrong location, thereby breaking the cache system
2) every since there is the ability to create new items in the hierarchy, there should've been a check that disabled the from-cache updates when that functionality is enabled. It is possible though to cache the per-level editability & item type settings, but for now, I'll ignore that, since you would also need proper cache invalidation for that too work, too. There's an issue for that already.
Comments
Comment #1
wim leersThere were 2 problems:
1) ever since there is a
<div class="selects">container for the selects, the from-cache updates would cause the HTML to be put in the wrong location, thereby breaking the cache system2) every since there is the ability to create new items in the hierarchy, there should've been a check that disabled the from-cache updates when that functionality is enabled. It is possible though to cache the per-level editability & item type settings, but for now, I'll ignore that, since you would also need proper cache invalidation for that too work, too. There's an issue for that already.