I get this error on any panels pages after updating to 3.3:
"recoverable fatal error: Object of class stdClass could not be converted to string in sites/all/themes/fusion/fusion_core/panels-pane.tpl.php on line 46."
It shows up several times and now parts of the page won't show up. I ran update.php and cleared the cache but it still persists.
Comments
Comment #1
Chad_Dupuis commentedI can confirm this as well. The panels appear blank a majority of the time:
Object of class stdClass could not be converted to string in /sites/all/themes/fusion/fusion_core/panels-pane.tpl.php on line 46.
All that line does is print $content so there has to be something going on internally or a change with the output from panels.
Comment #2
Chad_Dupuis commentedAn update, after a number of cache clears, etc. the data appears to show but the error hasn't gone away in watchdog...
Comment #3
Chad_Dupuis commentedCorrection, this is still happening, the content will load with multiple page loads in many cases but fairly often no content is showing up in the panes....
Comment #4
Chad_Dupuis commentedSomewhat intermittent. I notice though that the non-cached panels (like a google ad, etc.) always show on a page with multiple panels. The cached panels or views with caching enabled seem to have the problem - possibly related to http://drupal.org/node/703040 ?
Comment #5
sociotech commentedbutler360, Chad,
We haven't been able to reproduce the error condition yet. Could you provide some additional information?
What is the source of the content in your panes (e.g., Views, static content)?
What level of PHP error reporting are you running (e.g., E_ALL & ~E_NOTICE)?
What kinds of caching are you running (e.g., Panels, page, server)?
Also, as a troubleshooting measure, could you try temporarily removing the panels-pane.tpl.php template from Fusion Core and clearing your caches? It should result in the loss of some Skinr and other css styles but should still function. Currently that's the only place where we interact with Panels.
Thanks for you assistance.
Comment #6
butler360 commentedAlthough I can't switch back to 3.3 right now to test, the source was actually just "Custom Content" put in the panels. PHP error reporting is set to whatever the default is. I use boost for caching and I think I might have had the panels "Simple cache" on. I'll get back to you with better information later today, hopefully.
Also, I should mention that at first the two panes I had in an upper region wouldn't show. Then I cleared the cache and refreshed and the upper ones would show but the lower ones would not.
Comment #7
Chad_Dupuis commentedFirst, thanks for the response! I really appreciate all the work you've done with this system...
For me the content is all custom content and views. All of the blocks that don't show up (as best as I can tell) have caching turned for the blocks (the panels simple cache). So if I have say 6 panels on a page and 4 with caching on, I'll get 6 outlines (the pane border), 6 titles and only 2 of the blocks will have content. Oddly, if I reload and click around the site, log out and login (basically a bunch of random things) I can almost always get all the content to show at one point or another but then it will go back to blank. The blocks with custom content and no caching always appear to show up fine. I have regular drupal caching on and APC. Php is configured for - error_reporting = E_ALL & ~E_NOTICE
I will try removing the panels tpl file as soon as possible.
Comment #8
stephthegeek commentedLooks like this is the same issue, and not using Fusion there: http://drupal.org/node/655268
Comment #9
butler360 commentedI'm also noticing this on other themes not built with Fusion. Sorry I blamed it on Fusion! I saw fusion in the .tpl.php file and assumed it was this project since this is supposed to be a stable Panels release.
Comment #10
stephthegeek commentedNot a problem, I can understand the assumption. Hopefully an answer comes through in the Panels queue soon...