Notice: Trying to get property of non-object in ctools_node_comment_form_content_type_render()

I'll see if I can reproduce it and get back to you if I can.

Not yet, but still keeping an eye out.

I was able to recreate with the export above, however, part of the problem appears to be that the context for the individual content panes needs to be re-saved. (Need to go into each pane and click 'save')

As a mention, I believe the comments and comment form will be included by default if you include node:content

The other problem I'm seeing seems to stem from checking 'Panel title' in the settings for the node content pane. After re-adding the node content pane, I was able to remove all errors.

It's difficult to say because I'm not 100% sure what you're trying to do. It may be a bug - but if it is, I think there's a way around it. I've also run into the problem before of needing to resave panel panes after an upgrade.

I checked in a fix that should be MUCH smarter about this.

I'm getting this with the current release, and looking at the code the immediate cause of the error is obvious: ctools_node_comment_form_content_type_render() starts by potentially setting $node to NULL, and then proceeds to unconditionally ask for $node->nid three lines later.

This is Panels Modules error. This is not related to CTools.

Basically you r not added properly context in your panel. if you want to display node comment in your panel.

goto add context option.

add node as context.

use appropriate node id for comment.

update and save the panel.

now every thing is working fine.

Jweown: yes its only warning error with ctools. basically i go through this all stuff.

in above function context perm must be a object. if its not a object so it display the warning error.

in Ctool module if $context perm is not a object then display appropriate error message.

Adding my export file. Oh, an I am using 7.x-1.0-rc1

Here's a patch to prevent NULL->nid being asked for.

I don't know what $block->delta should actually be in this case. I've set it to NULL, but maybe the property simply shouldn't be set?

Ah, yes, that's essentially the same problem.

Similar enough that I'm wondering whether the if ($node->comment) in ctools_node_comments_content_type_render() should in fact match the line in ctools_node_comment_form_content_type_render() which is if ($node->comment == COMMENT_NODE_OPEN) ?

Here's a patch for both functions. I still have no idea whether my $block->delta = NULL is correct for the empty node case, but I expect the functionality would match the current code (just without the warnings being thrown).

No, I don't know that #14 is relevant.

It sounded like they were looking into a reason why $context->data might not be set in the first place, but it seems highly unlikely that it would be the only possible reason.

The code I'm patching clearly expects that $context->data might be empty, so I'm just fixing an obvious bug in the code when that circumstance arises. I'm afraid I can't offer any insight into whether or not it was correct for that property to be empty at the time.

I suspect the "Comment form goes here" text really shouldn't be there.

If $node does not exist, we should jsut return no block and not render anything.

I think you are right Mr Merlin.

I'm using panels & panels everywhere along with adaptivetheme & at_panels_everywhere. It's when comments are not enabled but are shown as an ouput as part of the at_panels_everywhere theme in the main content area, this error appears

Trying to get property of non-object in ctools_node_comments_content_type_render() (line 26 of sites\all\modules\ctools\plugins\content_types\node_context\node_comments.inc

Perhaps you're wondering why add a pane with the comments then - when comments are disabled (for article content type). The at_panels_everywhere theme came with this pane being placed in the main content region by default.

It looks like the warning appears because there is no $context (or $node) variable available, if this makes sense.

This is strange because it happens when I try to render the comments for the node being viewed!
(plugin Node -> Node comments, "node being viewed").

In the actual panels, the comments show up, but the formatting is lost (zebra colors for example).

Can anyone point me in the right direction, so I can fiddle around a bit with the code and maybe find a workaround until a proper solution is found?

Hi jweowu,

Thanks for the reply. I am not sure that #22 solves my issue:

The "notice" disappears, and in the preview I get "Node comments go here."
In the panel, the comments appear but they are not rendered in the same way as the "normal" rendered node, but lose the layout completely.
Is this a completely different issue?
I am new to Drupal so it's hard for me to see where source of errors are...

I am still encountering this error. The attached patch is a bit simpler than #22. I added an if block to test for a NULL value in $node and then return a NULL value in $block if $node is NULL. Otherwise, the function does exactly what it did before my suggested patch.

Thank you for the guidance. I didn't mean to give myself "credit". I have included my initials in comments for changes I make to other's code for a long time just for my own benefit, but I will not do so when I submit code to any Drupal project. Sorry for any inconvenience.