Support for legacy preprocesses?

Created on 8 July 2025, 7 days ago

Problem/Motivation

Display Builder is avoiding as much as possible to interact with ThemeManager::render():

  • By design, Entity View Display integration is sometimes bypassing node.html.twig, user.html.twig, media.html.twig, field.html.twig...
  • By design, Page Layout integration is sometimes bypassing page.html.twig and region.html.twig
  • By design, Views integration is sometimes bypassing views-view.html.twig, views-view-field.html.twig...

So, preproces and suggestions related to those templates will not be executed.

Proposed resolution

This make Display Builder ready for the future, but this will also break with some contrib & custom developments.

Do we trigger some preprocesses (with invokeAll I guess) to alter the root of the sources data tree? What is happening is a root has many sources?

Let's avoid making ot configurable. We take the decision, and we implement it or not.

📌 Task
Status

Active

Version

1.0

Component

Main / Misc.

Created by

🇫🇷France pdureau Paris

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @pdureau
  • 🇫🇷France Grimreaper France 🇫🇷

    I would say, this will open the door to side effects and be big maintenance burden.

    I would vote for no support. We want to gain performance by no more have all those preprocesses.

Production build 0.71.5 2024