Overview
Dropping a new component into a Global Region sends updated JSON to the server but the HTML returned from the server does not render the newly added component.
Steps
- Delete page title block
- Switch to the Library tab and drag and drop an SDC component into the focused region in the preview
- Observe that the JSON sent to the server contains the newly added component
- Observe that the HTML returned from the server does not have the newly added component
- Refresh the page - observe that the newly added component appears in the layers panel but not in the preview

| Comment | File | Size | Author |
|---|---|---|---|
| Drupal_Experience_Builder.png | 93 KB | jessebaker |
Comments
Comment #2
jessebaker commentedI've just done a fresh install on 0.x after merging in the global region work and I'm no longer seeing the issue.
I'm still working in this area. Will update this issue if I come across the issue again or have better steps to reproduce.
Comment #3
lauriiiI noticed this can happen page template config is invalid for one reason or another. This can be reproduced by trying to delete page title block. It was pretty confusing so we should keep this open.
Comment #4
wim leersWRT
PageTemplatevalidation#3505872: Page title block should not be required landed, so #3 cannot happen anymore.
#3501600-17: Split 1 PageTemplate config entity into N PageRegion config entities describes how we'll be able to drop most validation, probably all the validation that caused #3 in the first place.
So let's wait for #3501600: Split 1 PageTemplate config entity into N PageRegion config entities to land, and then re-assess this.
Related, at a different level
This is level up from #3485878: Server-rendered component instances should NEVER result in a user-facing error, should fall back to a meaningful error instead (+ log), but is comparable in intent. A "level up" in the sense that that is about individual component instances, and this is about a tree of component instances.
So let's wait for #3485878: Server-rendered component instances should NEVER result in a user-facing error, should fall back to a meaningful error instead (+ log) to land too, and then re-assess this.
Comment #5
lauriiiThe blocking issues have landed now.
Comment #6
wim leersTangentially related #3530857: ApiLayoutController::buildPreviewRenderable() always auto-saves regions regardless of $updateAutoSave value landed earlier today.
Comment #7
wim leers@mayur-sose, could you please check if this is still reproducible? 🙏
Comment #8
mayur-sose commented@wim-leers, I attempted to reproduce the issue, but was unable to do so. Here are the steps I followed:
I also tried several other scenarios to replicate the issue, but it did not occur in any of them.
Comment #9
mayur-sose commentedComment #10
wim leers🥳 Thanks, @mayur-sose! Crediting you for that :)