Closed (outdated)
Project:
Panels
Version:
7.x-3.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
2 Dec 2011 at 09:26 UTC
Updated:
14 Jul 2026 at 01:09 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Letharion commentedDoes this happen on a clean install? Otherwise I need instructions for reproducing the issue.
Comment #2
stephenrobinson commentedI think editing a component may cause a panel page to white screen its contents may mean a cache clear or theme rebuild is missing from the code somewhere? Hard to say until it happens again...Cheers
Comment #3
stephenrobinson commentedwas on a new D7 site, not a migrated one
Comment #4
stephenrobinson commentedmanaged to simulate some errors:
Comment #5
Letharion commentedI'm not sure I understand #3.
So what did you do to get #4?
Comment #6
stephenrobinson commented#3 - I have built a new site, not migrated from a previous version, so very clean
#4 I just edited and saved a panel
Comment #7
Letharion commentedAha, that was easy. Can you reproduce it with -dev though? Cause I can't, so I'm guessing this is already fixed?
Comment #8
stephenrobinson commentedHi,
Dev gets rid of this error (saved twice, see output), BUT it has exposed the other issue that I couldn't remember, after you run update.php, panels become white screens until you clear the caches, this may be a core issue, don't know, the log output is:
Comment #9
Letharion commentedIs it is possible the "file 2011-12-02 14:00 The file public://ctools/css was not deleted, because" is part of a file permissions problem, which in turn causes the error message? I don't get any of these with the latest dev.
Comment #10
stephenrobinson commentedI am afraid this isnt the cause, I manually created the ctools/css folder, and got a white panel following viewing a panel page after running update.php with the following output (no ctools message):
Comment #11
stephenrobinson commentedI just rebuilt the theme registry, not cleared all caches, and this fixed it, perhaps drupal rebuild theme registry needs to be added to the end of the update.php procedure as this fixes the broken panel issues caused by the update.
Comment #12
stephenrobinson commentedoh, is using zen starter kit, if that is an issue....
Comment #13
Letharion commentedWell, I don't know since, like I said, I'm not seeing this issue.
As it's fixed for you, I'll set the issue to fixed, but maybe someone else with the same issue will show up.
While yes, it's possible the theme registry needs to be rebuild at some point, as far as know, there's nothing new in Panels that was added recently that would warrant that.
Comment #14
stephenrobinson commentedoh well maybe I will have to replace the panels with custom page.tpl.php files instead
Comment #15
westbywest commentedI also encountered this very problem, using the Omega starter theme with Drupal v7.9, ctools v7.x-1.0-rc1, and Panels v7.x-3.0-alpha3, and after running update.php to upgrade views and date module to most recent versions.
I saw error messages similar to those in #8. In addition, the layout for a node variant I had created disappeared entirely from the "Content" tab in the panel editor after running update.php, even tho my layout selection for that variant was still visible in the "Layout" tab. Triggering cache refresh (which presumably also triggers theme registry refresh?) would not restore the variant's layout.
I performed these steps to resolve the problem, although that was before I found this issue:
1. Deleted the node variant entirely.
2. Switched to Bartik theme (which should have triggered a theme registry refresh when I visited admin/appearance/list)
3. Upgraded to dev version of panels module
4. Cleared all cache (via admin_menu)
5. Switched back to Omega starter kit theme
6. Recreated node variant and its missing layout
I will try to be diligent about keeping my custom node variant preserved in a feature, to avoid future mishaps. Still, I can confirm that running update.php with panels v7.x-3.0-alpha3 and ctools v7.x-1.0-rc1 seemed to cause this problem.
Comment #16
merlinofchaos commentedIn panels.module in the function panels_theme() there is this code:
I'm not sure why that's there -- according to the commit it was 'Prevent warnings during update" but that was in Drupal 6. In Drupal 7 this may not matter.
Try removing that and/or comment it out and see if that helps.
Comment #17
stephenrobinson commentedWhen I rebuild registry and search for panels_flexible, I get these entries that are missing/don't mention "panels_flexible" when I run update.php
Comment #18
stephenrobinson commentedAfter update.php
In the cache table:
theme_registry:build:modules
theme_registry:mythemename
exist, but don't mention "panels_flexible",
ctools_css_cache is empty
Comment #19
stephenrobinson commentedI patched update.php to fix this...
Comment #20
merlinofchaos commentedDid you try doing what I said in #16
Comment #21
stephenrobinson commentedHi,
Did this with Drupal 7.10, and fixes the issue, without any errors being thrown,
Stephen :)
Comment #22
stephenrobinson commentedI see one of the fixes for D7.10 is "Fixed running update.php doesn't always clear the cache.", don't think so......
Comment #23
Letharion commentedI take it this got solved.
Comment #24
merlinofchaos commentedNot yet -- I'm waiting for feedback on #16 -- we need some testing to see if that MAINTENANCE_MODE test can simply be removed. According to the commit, things used to break during update.php but I think that may no longer be true.
Comment #25
bradjones1To those (like me) trying to follow along: Earl commented out the MAINTENANCE_MODE test proposed above at http://drupalcode.org/project/panels.git/commit/3cd0440e5aaf222657611cd4.... So it's in the -dev branch.
The D6 version of this issue/commit is here over on #979912: Panels cache getting stuck, getting white screen on my homepage panel..
@merlinofchaos: If you were looking for feedback as to whether this should stay gone, I just got tripped up by this issue after a DB update using update.php. To get things back to normal re: panels, I had to go in and set MAINTENANCE_MODE to 0 using drush. I agree I don't see much reason for this in the D7 version.
Comment #25.0
bradjones1typo
Comment #26
japerryDrupal 7 is no longer supported, closing.