Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Idea summary
What is the problem to solve?
A major problem with core's content workflows using nested entities via Entity Reference is that changes to the nested entities will be published immediately, even when using an editorial workflow via Content Moderation.
Who is this for?
(Evaluators, site visitors, content authors, site managers, (advanced) site builders, frontend developers, backend developers, core developers, site owners, other?)
Result: what will be the outcome?
The solution to this would be to bring Entity Reference Revisions into core (or equivalent functionality) so that a child reference entity's changes can be tied directly to the parent entity's publication status.
How can we know the desired result is achieved?
(Usability test, a metric to track, feedback)
Comments
Comment #2
DamienMcKennaThis would also provide a solid base for other modules to build from, rather than people constantly building new nested entity architectures that don't work with revisions (Field Collection, Bricks, Stacks, etc).
Comment #3
BerdirPretty sure there are existing issues for this
Comment #4
DamienMcKennaYes, and I opened it ;-)
Comment #5
yoroy CreditAttribution: yoroy commentedReworked the issue summary to use the idea proposal template. Needs work to answer all the questions, thank you :)
Comment #6
hawkeye.twolfOne problem with ERR—and I think a blocker on bringing it into core—is that on some medium-to-small sites, especially those with many paragraphs per node, "revision bloat" degrades database performance. See core issue #2960887: Do not create field revisions when field data hasn't changed for details/explanation.
Comment #7
DamienMcKenna@derek.hawkeye.deraps: Thanks for opening that issue!