Steps to reproduce:

  • Do a clean install of D7, using the standard profile
  • enable the ctools, page_manager, and panels modules
  • in page manager, enable the node view, and create a panels variant
  • Under content, add the following node components: title, body, comments, comment form
  • Save the variant
  • add a node, with comments enabled
  • type in the comment body field, and press 'preview'
  • WSOD! (after execution timeout)

Needless to say, preview works fine when the page manager variant is not present/disabled.


Ashlar’s picture

This has been duplicated in 7.x-1.0 as described in summary. Function nesting exceeded 200 at failure.

Ashlar’s picture

Version:7.x-1.x-dev» 7.x-1.0
Simmol’s picture

I have the same problem.

Panel Page with comments, when preview clicked "Infinite recursion" occur.
My investigation on the problem get to the point that the problem is:

in comment.module:
comment_preview() function calls node_view() for some reason ( i can't find any code using this data )

and the problem is node_view after some hooks call comment_preview again ...

netbek’s picture

Version:7.x-1.2» 7.x-1.0

I have the same problem described by OP with ctools 7.x-1.2 and panels 7.x-3.3 in D7.15. According to the Xdebug trace, it gets stuck in a loop in comment_node_page_additions() on line 742 and throws the nesting level error after a while. If commenting out lines 742-743 ($build = drupal_get_form(...)), the page is compiled without a PHP error but has invalid markup (comments panel content is duplicated). I've increased xdebug.max_nesting_level to 500 just to test, not as a permanent fix, but no luck. Saving a comment, not previewing, works as expected.

Edit: Until this is fixed, one could disable comment preview, or to keep the preview functionality, use AJAX preview, hide preview button with a CSS class in hook_form_FORM_ID_alter and show preview button with JS so it doesn't appear under non-JS circumstances. Ideal Comments provides some of aforementioned already.

netbek’s picture

Version:7.x-1.0» 7.x-1.2
jwilson3’s picture

Version:7.x-1.0» 7.x-1.x-dev

This exists in both 7.x-1.0 and 7.x-1.2, but the standard practice is that this needs to be fixed (and patched) off of 7.x-1.x-dev, thanks.

jwilson3’s picture

I had success using a recent snapshot of ajax_comments-7.x-1.x-dev

solipsist’s picture

Having this exact problem but it only happens on an EC2 instance, not on my Vagrant box. They're not identical but both run Ubuntu Lucid.

solipsist’s picture

Is there any known solution to this?

dwoolworth’s picture

Still experiencing this issue, anyone have a suggestion or help?

gargsuchi’s picture

Same issue here.