- Issue created by @Kristen Pol
- 🇺🇸United States Kristen Pol Santa Cruz, CA, USA
That’s from the demo design system
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
This sounds a lot like 🐛 ApiLayoutController::getRegionForComponentInstance doesn't work well with nested components if there are multiple regions. Active . 🤔
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Looking forward to the additional info to reproduce this! 😊🙏
- 🇮🇱Israel heyyo Jerusalem
I also saw this issue outside xb-demo, and I didn't have any region enabled in my theme to be managed by XB.
- 🇮🇱Israel heyyo Jerusalem
I just checked, the POST request xb/api/v0/config/pattern doesn't contain the full tree of the selected component.
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
I see, so then … it must be a client-side problem? But the video in #6 does not show the request body, so it could still be the same back-end bug that causes the information the client sent to get lost 😅
I'm going to bet that this is a back-end bug, and just another symptom of #3534971-6: ApiLayoutController::getRegionForComponentInstance doesn't work well with nested components if there are multiple regions. → . Bumping the priority of that one. Odd that this was found so late!
- 🇧🇪Belgium wim leers Ghent 🇧🇪🇪🇺
Yeah then I'm 99% confident it's a duplicate of that other isssue. 😇
Let's first land that other issue, then test again here.