On a site with Simple Cache enabled I get this error every time Panels tries to fetch cached content if there is nothing in the cache:
recoverable fatal error: Object of class stdClass could not be
converted to string in
/sites/all/modules/panels/templates/panels-pane.tpl.php
on line 39.
It is only a 3.x-dev problem, no problem with version 3.2
| Comment | File | Size | Author |
|---|---|---|---|
| #15 | panels-cache-problem-655268-13.patch | 1.46 KB | kosmikko |
Comments
Comment #1
merlinofchaos commentedThis seems higher priority than minor.
Comment #2
Anonymous (not verified) commentedsubscribing. seeing same issue here with jan 21 build.
Comment #3
dicreat commentedsubscribing
Comment #4
stephthegeek commentedLooks like the same issue here: http://drupal.org/node/701914
Comment #5
Chad_Dupuis commentedsub - seems like the issue I'm having with the 3.3 release...
Comment #6
butler360 commentedAlso getting this issue. Rolling back to 3.2 fixes it, so I guess it's something in the 3.3 release.
Comment #7
dddave commentedUpdating (problem confirmed btw)
#702382: 3.3 Stops Fusion Theme System from Working With Panels seems to be a dub
Comment #8
bensemmel commentedHaving the same problem with version 3.x-dev...
Comment #9
skyredwangsubscribe
Comment #10
stieglitz commentedsame issue after adding google adsense to a pane.
Comment #11
Chad_Dupuis commentedIf it's helpful, I only have 3 panes and all 3 had a google ad in one of the blocks... So maybe there is something to that...
Comment #12
stieglitz commentedTurns out it wa not the adsense causing the problem. I believe it is the simple cache. I turned it off on the only pane which was custom content and it seems to have taken care of the problem. Perhaps it is a combination of custom content AND simple cache?
Comment #13
hughworm commentedSame problem, caused by a new line in panels/includes/plugins.inc line 73:
$content->content = $cache->content;which I think should read:
$content = $cache->content;(consistent with line 61) since it's the $content object that is in the cache.
That fixes it. Can someone do a patch?? Beyond me! :-)
Comment #14
dddave commentedAlthough this isn't a patch and I am unable to provide one, I think this approach could need the eye of someone familiar with the panels code. There might be some reason why this new line was introduced.
Merlin perhaps? ;)
Comment #15
kosmikko commentedHere's a patch for #13
Comment #16
butler360 commentedI tried that patch but it didn't work for me.
Comment #17
skyredwangset the status back to needs work since #16 reports the patch doesn't work
Comment #18
merlinofchaos commentedHmm. I can't see why #15 wouldn't work -- butler360 can you provide more information? Are you sure you applied the patch correctly? Are you sure you're experiencing the same problem?
Comment #19
merlinofchaos commentedIn fact, my tests reproduce the problem and fix the problem.
Comment #20
dddave commentedChanged the line manually and this fixed the problem. Unless the patch should do something in addition and not only change the line, this is rtbc.
Comment #21
merlinofchaos commented#15 committed to -dev.
Comment #22
butler360 commentedStrangely enough, when I updated to the dev version of Panels, I lost my homepage (a Panels page) on each site in my multisite config. Upgrading to ctools to dev fixed it and now everything works. Weird.
Edit: It works on some of my sites. On one platform, certain content still isn't rendered. When editing the panel page, the styling sometimes changes around and I get errors like these on occasion: http://drupal.org/node/621634 and http://drupal.org/node/455918
Edit2: Content isn't rendered if there's something in the title field but nothing in the body field. It worked before, though. It's not a big deal for me, as it can be worked around, though.
Comment #23
merlinofchaos commentedThis is probably because Panels tends to move its CTools version requirement up as new things happen. If you upgrade Panels without CTools, Panels will see that CTools is too old and remove itself. The alternative is crashing.
Comment #24
yann_riviere commented#15 works for me.
Comment #26
AntiNSA commented+1
Comment #27
shyam541 commentedBookmarking...