Problem/Motivation

When using something like default_content, the referenced entities for a node should include its inline blocks and other layout builder added content. This isn't the case. Because ContentEntityBase checks instanceof EntityReference. And layout builder added content is connected via a LayoutSectionItem.

Proposed resolution

Ideally we'd provide the referenced content in a seamless mechanism.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet

Comments

heddn created an issue. See original summary.

heddn’s picture

heddn
Primary language English
Location Illinois
commented
Issue summary: View changes
geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented

Just a thought: Roll a computed field which then will be a property with EntityReference type and done.
(If later that computed field optionally does a de-normalizing save to DB, we get views integration for free)
EDIT: I guess: Provide an EntityReference typed property on the LB field, implement EntityReferenceFieldItemListInterface, and done.

No, not so easy...

geek-merlin’s picture

geek-merlin
Primary language German
Location Freiburg, Germany
commented
Priority: Normal » Major

As of #2942975-122: [PP-1] Expose Layout Builder data to REST and JSON:API, this is crucial for exposing LB data via Rest/JsonAPi, so raising prio like the other issue.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

It woul likely be be far easier to solve that there with layout builder specific code than making this extensible.

Version: 9.1.x-dev » 9.2.x-dev

Drupal 9.1.0-alpha1 will be released the week of October 19, 2020, which means new developments and disruptive changes should now be targeted for the 9.2.x-dev branch. For more information see the Drupal 9 minor version schedule and the Allowed changes during the Drupal 9 release cycle.

Version: 9.2.x-dev » 9.3.x-dev

Drupal 9.2.0-alpha1 will be released the week of May 3, 2021, which means new developments and disruptive changes should now be targeted for the 9.3.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.3.x-dev » 9.4.x-dev

Drupal 9.3.0-rc1 was released on November 26, 2021, which means new developments and disruptive changes should now be targeted for the 9.4.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.4.x-dev » 9.5.x-dev

Drupal 9.4.0-alpha1 was released on May 6, 2022, which means new developments and disruptive changes should now be targeted for the 9.5.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 9.5.x-dev » 10.1.x-dev

Drupal 9.5.0-beta2 and Drupal 10.0.0-beta2 were released on September 29, 2022, which means new developments and disruptive changes should now be targeted for the 10.1.x-dev branch. For more information see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 10.1.x-dev » 11.x-dev

Drupal core is moving towards using a “main” branch. As an interim step, a new 11.x branch has been opened, as Drupal.org infrastructure cannot currently fully support a branch named main. New developments and disruptive changes should now be targeted for the 11.x branch, which currently accepts only minor-version allowed changes. For more information, see the Drupal core minor version schedule and the Allowed changes during the Drupal core release cycle.

Version: 11.x-dev » main

Drupal core is now using the main branch as the primary development branch. New developments and disruptive changes should now be targeted to the main branch.

Read more in the announcement.