Closed (fixed)
Project:
Panels
Version:
6.x-3.x-dev
Component:
Mini panels
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
18 Mar 2010 at 21:57 UTC
Updated:
20 Nov 2010 at 23:13 UTC
Jump to comment: Most recent file
Comments
Comment #1
mgriego commentedComment #2
mgriego commentedComment #3
mgriego commentedComment #4
mgriego commentedReattaching patch with proper naming convention and status.
Comment #5
merlinofchaos commentedAwesome, I was thinking this needed to happen, so it's good to see a patch for it. Will try to review this when I get a chance.
Comment #6
mgriego commentedAlso, it would be good to add an update hook into panels_mini.install to either run _block_rehash() for each active theme, or, perhaps easier, just update the blocks table directly as in panels_mini_update_6300() to set cache to -1, which I guess would look like this:
This allows the proper settings to take affect for existing sites.
Comment #7
mgriego commentedWe have this running in production, and it has allowed us to re-enable block caching with no adverse affects.
Comment #8
mgriego commentedComment #9
sdboyer commentedLooks good, committed. Thanks!
Comment #11
drumrwaldo commentedI hope this is proper etiquette on here, but I was having the same issue described here (or so I thought: two-column layout is displayed as two rows) so applied the patch. I've verified the patch was applied and am using the appropriate panels version, but the behavior of my mini panels is as before. After patching the module and flushing the cache, my mini-panels displayed correctly for the first few page loads but now the issue is as before. Glad to provide any additional information if it would help, and again my apologies if it's not proper protocol to re-address a closed item. Thanks in advance for the help!
Comment #12
mgriego commentedIt sounds like you did not upgrade to a new version of Panels and chose to patch the module instead. Did you include the code from #6 as well and run update.php?
Comment #13
drumrwaldo commentedYou're right, I misread and thought the patch was applicable to the newest version of Panels. Updating the module and running update.php seems to have taken care of it. Thanks for taking the time to answer a stupid question!