Recursion error has existed for months - is there a plan to fix it? [#314660]

Today I installed 6.x - 0.14 and got:

While traversing node variables your recursion limit of 20 was hit 2151 times. For more information about this error goto http://drupal.org/node/230885. This error will not effect the operation of Content Template, but it may not show you all available variables on this page. This error will only appear on this page.

This I got after changing the limit from 10 to 20.

There are many people posting comments that they are having problems in a number of separate issue posts that users have posted about this problem.

Is there a plan to fix this?

If not, could I use 5.x.1.9.? One users says: "I went back to the last rev of contemplate and eh problem is gone 5.x.1.9."

Thanks

Comments

Comment #1

jrglasgow CreditAttribution: jrglasgow commented 29 September 2008 at 17:01

because I keep getting questions about this I have changed this from an error to a warning. This is not fatal, it is just a warning to let you know that there is a problem.

Comment #2

Anonymous (not verified) CreditAttribution: Anonymous commented 29 September 2008 at 17:49

Would it be worth turning this reporting off by default, and adding an option to display it for thoose who are interested?

I dont know if any other reports get generated in this way by contemplate, but i have seen this report for ages on th 5.X branch, and just ignore it. And as you say its not an error, so, out of sight out of mind ?

Comment #3

drupaloo-1 CreditAttribution: drupaloo-1 commented 29 September 2008 at 18:44

Hi,

Thank you for your response.

When I raised the limit to 20, Drupal became unresponsive for 10+ seconds. (I am running AMP and Drupal on a local XP Pro machine)

IMHO, in general, code that makes its run environment hang up for this long has a problem. This is a huge delay from a computer perspective.

I'll be the first one to admit that I do not know Drupal module development, and so I don't even know if this is being caused by Contemplate. The code could be in another module.

But the issue of whether the code should warn the user or not, is a side issue. Obviously it would be better to try to identify the cause of and fix the problem, in whatever module it may be, instead of focusing on whether or not to warn the user of the problem.