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 have mini panels that are included in Features and exported into code. Upon updating to Panels 7.x-3.6, the admin UI (/admin/structure/mini-panels) shows an empty list. When I re-export the Features containing the mini panels, they are deleted from the exported code. Once that happens, the mini panels are gone from the site altogether and only recoverable via code reverts.
Putting the priority at Major as the potential for data loss exists. Downgrading fixes the problem, but then we don't have the security update.
| Comment | File | Size | Author |
|---|---|---|---|
| #5 | 2787113-mini-panels-disappear.patch | 559 bytes | generalconsensus |
Comments
Comment #2
ladybug_3777 CreditAttribution: ladybug_3777 commentedI have the same exact issue.
Comment #3
bernd.horn CreditAttribution: bernd.horn commentedWe may be hitting this issue as well. I have narrowed an issue down to commit 87dd920. Once I apply this commit mini-panels applied to a node disappear from the rendered page.
/admin/structure/mini-panels also does not show the mini-panels until "Apply" is performed.
Comment #4
generalconsensus CreditAttribution: generalconsensus at Forum One commentedAdd fix to badly placed return statement, which will incorrectly return prior to loading feature-based mini panels
Comment #5
generalconsensus CreditAttribution: generalconsensus at Forum One commentedFix to file location
Comment #6
sjancich CreditAttribution: sjancich commented#5 fixes the issue for me.
Comment #7
ladybug_3777 CreditAttribution: ladybug_3777 commentedI will test out your patch... but in case this helps someone, in order to fix this manually I took the following steps:
I went to our dev environment (Where my mini panels still existed) and grabbed the export code for them. I then imported the mini panels onto my local machine where my panels had been deleted. Importing just one mini panel caused them all to re-appear magically. I then was able to put them back into the correct block assignments and all appears to be OK. (My feature is back to being "Default").
I'm now going to look at the patch and I'll report back with what I find.
Comment #8
PapaGrande#1391450: Panels does not hide an empty mini panel is what broke this.
Comment #9
dsnopekComment #10
sjancich CreditAttribution: sjancich commentedladybug_3777, another workaround is to simply create a mini-panel via the UI.
Comment #11
japerryComment #12
ladybug_3777 CreditAttribution: ladybug_3777 commentedThe patch in #5 seems to do the trick! Thumbs up!
Comment #13
ladybug_3777 CreditAttribution: ladybug_3777 commentedoops didn't mean to knock down the priorty with my comment. That was an accident.
Comment #14
ladybug_3777 CreditAttribution: ladybug_3777 commentedComment #15
dsnopekI actually don't think this is related to #1391450: Panels does not hide an empty mini panel.
Basically, if you have no Mini Panels in the database, it won't ever show the Mini Panels in code because of the early return in
panels_mini_load_all().I'm able to reproduce this by putting all my Mini Panels in code. As soon as revert them all, then they disappear from the list at
/admin/structure/mini-panelsApplying the patch fixes it and my Mini Panels appear again!
Comment #16
dsnopekTargeting 7.x-3.7 rather than 7.x-3.8
Comment #17
PapaGrande@dsnopek, you are correct. It was actually commit 1432d0c0 from #2391073: panels_mini_load & friends need caching
Comment #18
PapaGrandeReading #2391073: panels_mini_load & friends need caching, particularly comment #8, I'm very curious why @mikeytown2, @joelpittet, or @japerry never saw this issue. We need to get their input before we just rip out those three lines.
Comment #20
japerryYes, that cache cid return totally is the culprit. Fixed.