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.# Summary
The panelizer module allows you to attach panels to any node in the system.
This module is blocked by the porting of Panels.
# Project URL
https://www.drupal.org/project/panelizer
# Where is the code?
In the 8.x-3.x branch.
# Estimated completion date
Target -alpha: Feb 5th, 2016
# Dependencies
# Who's doing the port?
- David Snopek (dsnopek), freelance
# What help do they need?
See open issues against the D8 branch:
https://www.drupal.org/project/issues/panelizer?version=8.x
# D8 roadmap
Milestone 1: Panels eco-system roadmap
The SCOTCH initiative needs to meet and create a new "Milestone 2" roadmap, now that we've completed the Panelizer goals for the "Milestone 1" roadmap.
# Background and reference information
N/A
Comments
Comment #2
webchickComment #3
webchickSounds like dsnopek is going to be starting on this soon, so it and Page Manager can be ported in concert with one another.
Comment #4
dsnopekYep, that's the plan! :-)
Comment #5
dsnopekAdded some links/references.
Comment #6
webchickAdding Panels eco-system roadmap to the list of resources, and updating the estimated completion date based on this doc to note that betas of various projects are tentatively scheduled for early Q1 2016.
Comment #7
DamienMcKennaFYI dsnopek has already started on some of the plumbing, so I'm updating this issue's status.
Comment #8
webchickThis is in the issue summary already, but just pointing out that work is happening at https://github.com/dsnopek/panelizer-d8-prototype atm.
Comment #9
dsnopekUpdated issue summary now that code is on D.o, and we've scaled back to an -alpha rather than -beta release for today-ish.
Comment #10
dsnopekWe released Panelizer 3.0-alpha1 last week! Changing status to reflect that. :-)
Comment #11
andypostRelated core issue, would be great to generalize handler for entity displays
Suppose display suite also has the same code base to override entity display,
so code duplication better to minimize by moving some code in core traits
Comment #12
dsnopek@andypost: I think that issue is a great idea! But I don't think it'll affect Panelizer too much. We basically completely replace the component building (with Blocks and Panels) rather than reusing it.
If the responsibility for building components was moved out of EntityViewBuilderInterface that would allow us to make Panelizer's code simpler (because we're forced to implement all those methods even though we don't actually have anything we can really do with them, so we have all this code proxying back to the original entity view builder) - but that would be a BC break, so it's not likely to happen in the Drupal 8 cycle.
Comment #13
DamienMcKenna8.x-4.0 is now available.