I tried adding a new Custom Style with the Panels Stylizer, and could get up to /admin/structure/stylizer/add. Upon choosing "Plain" or "Rounded Corners", pushing the "Continue" led me to a completely white screen, and I could not get to the /admin/structure/stylizer/add/settings page.
I had the Devel module On at that moment. De-activating Devel made the /admin/structure/stylizer/add/settings page available. So, the workaround is there.
It's not a major issue, because Devel will obviously not be there on the production site, but I wanted to bring it to your attention anyway. There are quite a few problems relating to the Devel module in a Panels environment in the issue queue, so I suppose this post doesn't add much to the discussion.
Comments
Comment #1
merlinofchaos commentedI run with devel.module on at all times, so it's not just devel.module that's doing it.
I know Devel for Firebug is known to have issues interfering with the AJAX, though to my knowledge they've fixed all those. I know that devel themer can be overly aggressive about adding devel information to theme layer things and cause problems.
When you get the whitescreen, what shows up in your error log?
Comment #2
modul commentedHi Merlin. I tried again:
- with Devel off, I get to the page with the colour wheel without a problem (admin/structure/stylizer/add/settings).
- with Devel on, that page remains completely blank, no error message, nothing. My browser's "View Source" doesn't show any source being generated.
I checked my Drupal logs, but there was nothing mentioned after "Devel module enabled". Are there any other logs I could check?
Comment #3
merlinofchaos commentedWith a whitescreen, there is usually a message in your server's error log. If you're running apache as a webserver, this is most often in /var/log/httd/error_log, but the actual location of this log varies depending upon OS and administrator preferences. When errors cause PHP to crash really badly, this is the only place where the error is written -- Drupal can't catch every error because sometimes PHP completely stops executing for the error and it's not possible for Drupal to catch it and log it using PHP.
Comment #4
modul commentedHi again, Merlin. I think you pointed in the right direction, and the problem appears to be linked to memory size. These are a couple of lines from what I found in my logs (in xampp\apache\logs\error.log) :
And Krumo / Devel appears to be the cause of it, memory hungry as it is :-). I suppose it's next to impossible to drastically cut either Devel's or Panel Stylizer's memory requirements, but it's good to know that problems can occur.
Can't restart my system right now, but if memory is the problem, it should not be too bad. Thanks for pointing me in the right direction. I'll keep you informed on what happens when I do restart my system (with more memory) later on.
Comment #5
Dave Sandilands commentedI get the same problem but I can get it to work without turning off Devel ; I just go into Devel settings and uncheck 'Display $page array' and disable the Krumo display.
Comment #6
japerryDrupal 7 is no longer supported, closing.