
We need a migration path from Panelizer to Layout Builder. Here's an issue where we can work on it.
Comment | File | Size | Author |
---|---|---|---|
#3 | interdiff-2969376-2-3.txt | 5.64 KB | phenaproxima |
#3 | 2969376-3.patch | 32.67 KB | phenaproxima |
#2 | 2969376-2.patch | 31.24 KB | phenaproxima |
Comments
Comment #2
phenaproximaHere's a sketchy first stab at migrating the Panelizer layouts stored in config only (entity view displays), done at the layout sprint this week at Acquia. There is some test coverage, but it needs to be greatly expanded. Just posting it here so I don't accidentally blow it away on my localhost.
Comment #3
phenaproximaExpanded the test coverage to assert that the migrated layout section actually looks the way we expect it to.
Comment #4
phenaproximaMigrated the entity_field block IDs to field_block.
I had to work around a limitation in core Migrate, which may be fixable over in #2684689: SubProcess process plugin doesn't support passing context values from source plugin.
Comment #5
damienmckennaI think this could be added to a 8.x-5.x branch.
Comment #6
damienmckennaComment #7
aolsen356 CreditAttribution: aolsen356 commentedIs anybody aware of a another place I can find documentation on upgrading from panelizer to layout builder?
Comment #8
damienmckenna@aolsen356: There isn't anything else right now, unless you want to get into working on the upgrade code itself.
Comment #9
darrell_ulm CreditAttribution: darrell_ulm as a volunteer commentedAdding a quick note to see if there have been any updates to this on upgrading from panelizer to layout builder?
Did any hear anything at Drupalcon 2019?
Comment #10
phenaproximaI've opened a sandbox project to work on this: https://www.drupal.org/sandbox/phenaproxima/3065457
Comment #11
aaronmchale@phenaproxima I love the play on words there with the sandbox project name "PaneLBizer"
Comment #12
phenaproximaThank you, Panelizer maintainers, for granting me commit access. I promise to use this power for good.
My plan is to leave every branch but 8.x-5.x alone. I won't commit any bugfixes or features to 5.x unless they directly affect the migration path to Layout Builder.
I envision the 5.x branch as being, effectively, the "end of the line" for Panelizer. My inclination is for the 8.x-5.x branch to ensure that pre-existing Panelizer layouts continue to work, but to remove the ability to add new layouts, edit existing ones, or enable Panelizer for entity view displays that don't already have it. Instead, panelized view modes will simply present a nice button: "Convert to Layout Builder".
So basically, moving to the 8.x-5.x version of Panelizer would "freeze" your layouts until you migrate them each to Layout Builder. Thoughts?
Comment #13
phenaproximaComment #14
phenaproximaThis should be a meta-issue.
Comment #15
phenaproximaWhy is this issue its own parent? :)
Comment #16
sylus CreditAttribution: sylus commentedI had a few questions about this upgrade path as have been trying out the latest dev release of panelizer and the automatic migrate to layout builder process.
a) The new layouts do get created but for components like page_title_block moved to the new layout config the following gets used:
You will end up getting a missing entity when trying to go to the layout library section and clicking on the template. This is because context_mapping is empty and I also think the block name has changed to.
b) When going on a specific piece of content and hitting the layout tab I also get a missing entity unless for some reason I purge content from key_value_expire. (Not sure about this one)
c) Aside from the above which can be manually fixed the larger problem is for the configuration that is house per piece of content itself and not a default template. Basically layouts that are stored in field_panelizer. For us we have hundreds of this pages so manual fixing is probably not feasible. Is this upgrade path going to be something that is supported?
Here is a P.R. I am working on to update our Distro with changes if helps: https://github.com/drupalwxt/wxt/pull/172/files
Comment #17
phenaproximaStatic contexts are a tricky part of this which I have to address separately, I think.
O_o Steps to reproduce might be very helpful here...
Yes. That's next on the list.
Comment #18
sylus CreditAttribution: sylus commentedHey just wanted to say really appreciate the work on this as everything is working great.
Am def really curious how going to solve static contexts and excited to see how is done.
Thx again for all your help
Comment #19
sylus CreditAttribution: sylus commentedHi I was just curious if there has been any progress on static contexts? I wish I could help with this but not sure where to start it.
I think it is the last blocker preventing us from fully working with new v4.0.0+ of Lightning from a fresh install perspective.
Any information would be helpful and again super appreciate you taking this on :D
Comment #20
zseguin CreditAttribution: zseguin commentedHello, I'm also running into this issue and curious about the update path for static contexts?
Comment #21
josephdpurcell CreditAttribution: josephdpurcell at Bounteous commentedI see some EXCELLENT work done here to migrate into Layout Builder -- to talk about this being generic I've created https://www.drupal.org/project/panelizer/issues/3087208.
Comment #22
phenaproximaI'm finally ready to tackle this. Opened an issue to address static contexts: #3091783: Support migrating static contexts
Comment #23
damienmckennaComment #24
clayfreemanThe referenced issue will be a blocker for stable 5.x release.
Comment #25
chrisgross CreditAttribution: chrisgross commentedDoes anyone know what the current status of this is? I've been trying to find a working migration path from a D7 distro using Panelizer to D9 w/Layout Builder, but have been thus far unsuccessful. Is this being abandoned or is here a functional patch out there that at least get me part of the way there?
Comment #26
candelas CreditAttribution: candelas as a volunteer commented@chrisgross have you find the way? I am trying that too.