- Issue created by @effulgentsia
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
🤯 I thought one of the goals was to allow people to test/play with this?!
Did @lauriii sign off on this?
Point 2 is inaccurate. Quoting myself from #3498340-2: Consider whether to store Component entities outside of config when in demo_mode → :
As of 📌 Create a specialized recipe to hold the XB demo Active ,
composer update drupal/experience_builder
within Drupal CMS will uninstall the XB module.And uninstalling the XB module also uninstalls all XB config entities (thanks you, config dependencies!).
👆 That includes XB
PageTemplate
config entities. - 🇫🇮Finland lauriii Finland
Turning on this setting would actually make the end-user visible site use XB for placing blocks which is not what we're trying to do The goal of the demo is to show case XB in the context of page building since that can be isolated to a single page that doesn't affect the live site. I think the issue and proposed solution make sense to me from that perspective.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
The goal of the demo is to show case XB in the context of page building since that can be isolated to a single page that doesn't affect the live site.
I'm fairly baffled 😅
We can also demonstrate the page template ability in the context of a single page, by making
\Drupal\experience_builder\EventSubscriber\RenderEventsSubscriber::onSelectPageDisplayVariant()
only use the XBPageTemplate
on the specific route(s) where we allow it if in demo mode. - 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
… because if I had known about that goal, I wouldn't have worked late to get 🐛 Empty global regions add unnecessary spacing to preview Active and 📌 PageTemplate: allow configuring which regions are exposed Active done 😥