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.Here is what we are up to for Panopoly 1.21:
Critical issues
Any issues marked critical need to get fixed before ANY release, even a security release:
https://www.drupal.org/project/issues/panopoly?priorities=400
These are mostly regressions, ie. things that worked in previous versions that we broke later.
In progress
#2293947: Make "Landing Page" into node + Panelizer (rather than a Page Manager page)
#2183937: Error on install of Panopoly-based install profile: "Column 'module' cannot be null" when profile starts with "e"
#1987386: Include Radix theme in Panopoly
Nice to have
#2155377: Only show one widget preview at a time when adding content in panels
#2166865: Removing non-required modules from .info / .make files
#2181079: Update to Navbar 1.8
Comments
Comment #1
populist CreditAttribution: populist commentedComment #2
populist CreditAttribution: populist commentedComment #3
populist CreditAttribution: populist commentedComment #4
dsnopekPanopoly 1.16 ended up being a security release - renaming hitlist!
Comment #5
dsnopekPanopoly 1.17 also ended up being a security release - renaming hitlist!
Comment #6
dsnopekRemoving #1965864: Support CKEditor in Panopoly now that I've postponed it...
Also, removing #2255095: Add "Crop" tool to Spotlight widget because it's just not that important compared to other things in the queue right now :-)
Comment #7
dsnopekRemoving #2115519: Undefined index: css in theme_panels_ajax_tab_ajax() (line 219 of panels_ajax_tab/panels_ajax_tab.module because it's a bug in our old layouts that have been switched to Radix Layouts.
Comment #8
dsnopekComment #9
dsnopekMoved #2155377: Only show one widget preview at a time when adding content in panels to "nice to have" since there's quite a bit of work necessary to finish it! I suspect it won't make 1.18.
But moved #1987386: Include Radix theme in Panopoly up to "in progress" because it's close and much less work is necessary to finish it.
Comment #10
dsnopekAlright! I think I've finally got the hitlist in order. All the "in progress" stuff has been recently updated with it's current status, and this should represent an actually accomplishable set of things for the next release. Maybe we'll actually pull off a normal release without a security vulnerability forcing us to release. ;-)
Comment #11
dsnopekPanopoly 1.18 ended up being a security release so renaming. However, we did manage to fix one of the things we wanted! So, removing.
Comment #12
dsnopek1.19 ended up being a security release, so renaming.
Comment #13
dsnopekWe ended up having to do 1.20 to force the packager script on Drupal.org to run again (because it messed up on packaging 1.19).
Comment #14
dsnopek1.21 ended up being a security release.
Comment #15
dsnopekI'm going to retroactively say this hitlist was for 1.19 (because that's really the last time it was current) and create a new one for the next version:
#2500427: Panopoly 1.26 hitlist