In the issue
🐛
ApiLayoutController::getRegionForComponentInstance doesn't work well with nested components if there are multiple regions.
Active
, this NULL return was the reason of the issue.
Besides of fixing the issue, we've added...
if ($regionForComponentId !== XbPageVariant::MAIN_CONTENT_REGION && NULL !== $regionForComponentId) {
...to avoid breaking the code.
The error happened in...
if (!$page_regions[$regionForComponentId]->access('edit')) {
for being $regionForComponentId NULL
Review if this NULL makes sense and, if not, remove it appropriately.
N/A
Active
0.0
Internal HTTP API
LOL, I got to a very similar solution than the original issue.
That NULL should never happen now.
For robustness maybe we should throw an exception instead of returning NULL? But what should the UI do in that case? Is this recoverable?