If an autosave entry exists before enabling global regions for a theme, theme regions cannot be seen
Steps to reproduce:
* Enable XB
* Create a node
* View XB page builder for that node
* Notice there's no global regions
* Visit theme settings and enable XB for global regions
* Reload XB page builder, still no global regions
* You need to run this DB query delete from key_value_expire where collection like 'temp%'; and then reload.
In ApiLayoutController if there's no page template in page store, load it from the saved config entity.
Show commandsStart within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
changes
Comments
Comment #2
wim leersBoth @larowlan and I ran into this (see comments 17 and 19 on #3494114), so chances are very high that Drupal CMS users will run into this, too. So, bumping priority and tagging .
Comment #3
wim leersFYI, this is even slowing down work on other bugfixes: #3497747-10: Global regions containing only "dynamically missing blocks" (due to emptiness or access) cause malformed pages. 😬
Comment #5
larowlanStraight forward
Comment #6
wim leersMerge away!
Comment #7
wim leersComment #8
larowlan@wim leers I don't have access to merge
Comment #10
wim leersOdd! You have the same perms as most of us in this project! 😄
There are some GitLab bugs. We’ve had to reach out to GitLab admins before. Can you ask about this in the GitLab channel on Drupal Slack? 🙏
Merged for you!
Comment #11
wim leers