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.
Is PE going to be supported on D8 as well?
Is PE going to be supported on D8 as well?
Comments
Comment #1
DamienMcKennaI'm personally too busy right now working on D7 contrib projects to consider it.
Comment #2
DamienMcKennaFYI dsnopek worked out a proof of concept of Panels Everywhere for D8: https://github.com/dsnopek/panels_everywhere_poc
Needless to say, it'll definitely be possible and will be worked on once the port of Panels itself is done.
Comment #3
evanjenkins CreditAttribution: evanjenkins at ActiveLAMP commentedI have forked dsnopek's repo and started some more work here https://github.com/evanjenkins/panels_everywhere... I didn't have to change much but this is working so far with all the latest required modules.
Comment #4
DamienMcKenna@evanjenkins: That's excellent! Would you mind adding a README.txt that would provide some details of what works and how to use it? Thanks.
Comment #5
dsnopekFor the record: while my PoC (and @evanjenkins fork) use Page Manager, I really think that PE should define it's own config entity for storing variants and then use composition to pull in the Panels components and UIs that it needs. I discussed this with @merlinofchaos on IRC at some point in the past, and he lamented that D7 PE used Page Manager and agreed that this would be a better implementation.
Comment #6
dsnopekAlso, the stuff we're doing in
PanelsEverywhereDisplayVariant
to implementPageVariantInterface
and support page title and main content should just be merged intoPanelsDisplayVariant
in Panels. Even though it's PE that is giving the variant to core to render the page, (1) that interface is from core, (2) it's easy to implement and (3) other modules could potentially want to passPanelsDisplayVariant
s to core that don't come from PE, and I think Panels should support that. This should be made into an issue in the Panels queue.Comment #7
evanjenkins CreditAttribution: evanjenkins at ActiveLAMP commentedI agree! We will probably continue to push this forward and refactor. Project needed a different site template based on a context and your POC was a great jumping off point.
Comment #8
DamienMcKennaI've uploaded all of dsnopek's and evanjenkins' code to the 8.x-1.x branch, lets continue this discussion in separate tickets.