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.
First attempt at an upgrade path from Panel Nodes to Panelizer.
Comment | File | Size | Author |
---|---|---|---|
#6 | 0001-1353542-Upgrade-path-from-Panel-Nodes-to-Panelizer.patch | 2.98 KB | lotyrin |
panelizer_upgrade.patch | 2.1 KB | Letharion | |
Comments
Comment #1
merlinofchaos CreditAttribution: merlinofchaos commentedChanges in the variables have made this require a little rework. Also, 2,x being entity-aware has renamed the table used to panelizer_entity -- we probably need to detect which table to use (we can use db_table_exists) and behave appropriately.
Also, panel_node should be able to detect that its table no longer exists and remove its menu functions so that even if left enabled, it will cease doing anything.
Comment #2
merlinofchaos CreditAttribution: merlinofchaos commentedOh well the stuff I just said about 2.x only actually applies to the 7.x branch. But in 6.x I believe we're still changing the variables for features.
Comment #3
Letharion CreditAttribution: Letharion commentedComment #4
Letharion CreditAttribution: Letharion commentedWe did agree to put the code for this in the Panelizer module instead, correct?
Comment #5
DamienMcKenna@Letharion: that'd be the best place for it, IMHO.
Comment #6
lotyrin CreditAttribution: lotyrin commentedI need this for a project. This is against 7.x-3.x, if we like the approach I'll backport to 7.x-2.x.
Comment #7
Letharion CreditAttribution: Letharion commentedGreat that you are picking this up. The reason I haven't is that I don't actually need this anywhere, so my tests were completely artificial.
Un-assigning it since you're not the one doing review. I would assign it to Merlin, but I don't have such powers in this queue. :)
Comment #8
lotyrin CreditAttribution: lotyrin commentedDoesn't quite work. I forgot to even execute one of the queries... too large of a coffee:sleep ratio I guess.
Comment #9
codewatson CreditAttribution: codewatson commentedAny progress on the upgrade path? If panels is really going to depreciate panel nodes in the future then our site will really need this to work by then?
Comment #10
DamienMcKennaFYI I added a corresponding issue in the Panels issue queue to deprecate Panel Nodes once this is resolved: #1833984: Deprecate Panel Nodes in favor of Panelizer
Comment #11
sonicthoughts CreditAttribution: sonicthoughts commentedSo it looks like there is no longer any way to display a panel node format in a view. Has anyone been using this script against 3.1?