Early Bird Registration for DrupalCon Portland 2024 is open! Register by 23:59 PST on 31 March 2024, to get $100 off your ticket.
Problem/Motivation
The final push for moving page_manager functionality into core.
Proposed resolution
@todo
Remaining tasks
Sub issues to follow.
User interface changes
N/A
Comments
Comment #1
andypostMaybe assign this to page.module component?
Comment #2
dsnopekHere is the issue that @sdboyer made with his warnings about introducing a multi-stage router in Core: #2305199: Create a route for every variant and use a "route filter" to apply selection rules
Not sure if this issue is going to address routing, but linking just in case...
Comment #3
yched CreditAttribution: yched commentedCould we namespace the concept a bit ? PageDisplay ?
Core already has EntityDisplays, we should make the names sufficiently distinct.
Comment #4
Wim LeersTim, I think #2352155: Remove HtmlFragment/HtmlPage addressed this by introducing "page display variants", a page display variant selection event and making that a first-level citizen of Drupal's HTML rendering flow; rendering a HTML page is now always done by the selected page display variant plugin.
It's not entirely clear what this issue wants to do, but at least from a "make page manager feasible in D8" POV, that's all taken care of now AFAIK.
Comment #5
dsnopekSo, I was bugging Tim for a couple weeks to flesh this issue out! :-) Anyway, my understanding is that this issue was about trying to introduce as much of page_manager into core as possible, ie. display objects (which are different than display variants).
But since I don't know the status of this now, I'll leave it to Tim to re-open or leave as-is. It seems super unlikely that any of this work will happen before 8.0.0 in any case - it'd be more of an 8.1.x or later thing. Maybe we should re-open and up the version number?