Posted by Ewan McLean on December 4, 2012 at 9:55am
6 followers
Jump to:
| Project: | Chaos tool suite (ctools) |
| Version: | 7.x-1.2 |
| Component: | Page Manager |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
This seems to have started as of a recent update.
Two parts to this, one is the behaviour when you click 'Update and Save' on the panel. For every menu that is set to display, a chunk of errors is displayed (sample below).
The other is the behaviour when you load the panel url with any other referrer/origin, on this occasion, each custom menu results in the error, and fails to display, but each standard menu (navigation, main) appears fine.
Here's the error:
Warning: Attempt to assign property of non-object in ctools_block_content_type_render() (line 152 of /home/republic/public_html/sites/all/modules/ctools/plugins/content_types/block/block.inc).
Warning: Attempt to assign property of non-object in ctools_block_content_type_render() (line 153 of /home/republic/public_html/sites/all/modules/ctools/plugins/content_types/block/block.inc).
Warning: Attempt to assign property of non-object in ctools_block_content_type_render() (line 162 of /home/republic/public_html/sites/all/modules/ctools/plugins/content_types/block/block.inc).
Warning: Attempt to assign property of non-object in ctools_block_content_type_render() (line 166 of /home/republic/public_html/sites/all/modules/ctools/plugins/content_types/block/block.inc).
Warning: Attempt to assign property of non-object in ctools_content_render() (line 289 of /home/republic/public_html/sites/all/modules/ctools/includes/content.inc).
Warning: Attempt to assign property of non-object in ctools_content_render() (line 293 of /home/republic/public_html/sites/all/modules/ctools/includes/content.inc).
Comments
#1
I also now get this error when using a views_slideshow block in a panel.
Warning: Attempt to assign property of non-object in ctools_block_content_type_render() (line 152 of /home/republic/public_html/sites/all/modules/ctools/plugins/content_types/block/block.inc).
Warning: Attempt to assign property of non-object in ctools_block_content_type_render() (line 153 of /home/republic/public_html/sites/all/modules/ctools/plugins/content_types/block/block.inc).
Warning: Attempt to assign property of non-object in ctools_block_content_type_render() (line 162 of /home/republic/public_html/sites/all/modules/ctools/plugins/content_types/block/block.inc).
Warning: Attempt to assign property of non-object in ctools_block_content_type_render() (line 166 of /home/republic/public_html/sites/all/modules/ctools/plugins/content_types/block/block.inc).
Warning: Attempt to assign property of non-object in ctools_content_render() (line 289 of /home/republic/public_html/sites/all/modules/ctools/includes/content.inc).
Warning: Attempt to assign property of non-object in ctools_content_render() (line 293 of /home/republic/public_html/sites/all/modules/ctools/includes/content.inc).
#2
I also have this warnings on a website I develop. I also use panels and menu_minipanels.
#3
I was having this same error thrown while editing/saving nodes. I used the same fix from this patch and my errors disappeared:
NOTE: Do not just apply this patch, since the line of code that's moved is not in the same place! I just went in an manually moved the code in my copy of the file instead of applying this patch. The file looks the same as in this patch, but the code to move is on line 145 as of the time I wrote this -- ver 7.x-1.2.
http://drupal.org/node/1739718#comment-6366456
To be bluntly clear:
1) Cut line 145 from the v7.x-1.2 block.inc file
2) Paste back after the bracket
3) Rejoice
4) Praise merlinofchaos for his ridiculously-incredible work, because he deserves every drop of support. (Where can I donate to him??) (edit: Buy his book! That's one way to support him. The link is on the right of www.angrydonuts.com )
(Sorry I don't know how to deal with proper patching routines. I'm swamped right now and don't have time to contribute my first Drupal patch! Bummer... that sounds cool.)
#4
The patch you reference has been committed, so I believe if you use the CTools -dev, you won't need to do any kind of patching at all.
#5
Automatically closed -- issue fixed for 2 weeks with no activity.