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.I'm trying to get the pieces together to do another release soon. There are a number of key bugs, and a few improvements, that I think need to be resolved soon, so I'm going to list them under this issue.
Items to be included will have this issue listed as its parent.
Comments
Comment #1
DamienMcKennaAdded the list of issues.
Comment #2
DamienMcKennaAdded #2248781: "Integrity constraint violation" error updating file entities.
Comment #3
DamienMcKennaRemoved #2256351: og_theme and panelizer cause PDO , it's a dupe of #2248781: "Integrity constraint violation" error updating file entities.
Comment #4
DamienMcKennaAdded #2311453: Reverting a display in IPE doesn't match non-IPE behaviour.
Comment #5
DamienMcKennaRemoved the list, using issue parents to indicate the items to be included.
Comment #6
DamienMcKennaSome items are being moved into the v3.3 release cycle so that 3.2 can be released sooner: #2413267: Plan for Panelizer 7.x-3.3 release
Comment #7
DamienMcKennaAs a line in the sand, I've released v7.x-3.2-beta1.
Comment #8
naxoc CreditAttribution: naxoc commentedJust a quick heads up on the release notes on the beta. It says "Note: CTools v7.x-1.5 and Panels v7.x-3.6 are required." Should it be panels v7.x-3.5 which is the stable release right now?
Comment #9
DamienMcKenna@naxoc: Doh! Fixed. Thanks.
Comment #10
DamienMcKennaComment #11
nagy.balint CreditAttribution: nagy.balint commentedIt would be nice to have a new release that shows up on the module's page, as currently the last version that shows up as stable is 2 years old. (as beta 1 does not show up, and anyways that still had a critical flaw according to the notes)
Comment #12
DamienMcKennaI know, need to fix some more bugs first.
Comment #13
DamienMcKennaComment #14
MustangGB CreditAttribution: MustangGB commentedLast release was over 3 years ago, any chance we can get another one soon?
Comment #15
DamienMcKennaFYI after some internal discussion with other Panels-ecosystem maintainers we're going to jump to the next update being 7300, to match the naming convention suitable for a 7.x-3.x branch.
Comment #16
MustangGB CreditAttribution: MustangGB commentedThe list of child issues is pretty unwieldy to process at a glance, so I've updated the issue summary with the ones that remain to be fixed.
Also of note is that #2577031: Duplicated UUIDs after panelizer page override for specific node from node type template is blocked on #2750545: New displays saved via panels_save_display() don't reset the UUID, which means we're blocked on a new Panels release, see #2423733: Plan for Panels 7.x-3.6 release for further details.
Comment #17
DamienMcKennaI'm not worried about getting #2577031: Duplicated UUIDs after panelizer page override for specific node from node type template into 3.2 because all that's left is to uncomment a few lines of an existing test method.
Anything else need to go into 3.2? I think it's just about ready!
Comment #18
MustangGB CreditAttribution: MustangGB commentedI guess tracking remaining issues isn't needed anymore then as they all got fixed or pulled from the release.
Super excited for #2404999: Don't save records for default values!
Comment #19
DamienMcKennaOMG! It's out! https://www.drupal.org/project/panelizer/releases/7.x-3.2
Comment #20
dsnopekHuzzah! Thanks for all your hard work on this, Damien :-)