Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
This error comes up when viewing the 'Template' page for a content type, with nothing particularly fancy.
What does this statement mean? It doesn't seem to mention what the implication is...
Any help much appreciated,
Chris.
Comments
Comment #1
jwade CreditAttribution: jwade commentedThere is another issue posted here regarding the same error: http://drupal.org/node/263630, but no one seems to know how to fix it!!
Comment #2
actdigital CreditAttribution: actdigital commentedI'm having this problem as well - which also results in the template being updated not sticking (the database isn't updated).
Any ideas?
Thanks!
-Michael
Comment #3
jrglasgow CreditAttribution: jrglasgow commentedIf you read issue #230885: CCK activates triggers Fatal error you will understand that in D6 we were having problems with PHP memory limit issues, a problem with recursion with CCK for D6. I put a user defined limit on the recursion depth, and set up an error message to let the user know that the limit was hit X number of times so they are aware that not all the variables available might not be shown in the variable list.
This problem has only occurred in the create template page so the error will only be shown there.
Comment #4
chrism2671 CreditAttribution: chrism2671 commentedIs there an easy way of lifting this limit? Or should I seek to increase the php memory limit?
Comment #5
itkadmin CreditAttribution: itkadmin commentedSame problem here, I'm not even sure what it means
Comment #6
jrglasgow CreditAttribution: jrglasgow commentedchrism2671,
You can change this limit at admin/settings/contemplate.
Comment #7
brad.bulger CreditAttribution: brad.bulger commentedwhat confuses me about the recursion limit is that the $depth variable is being incremented inside the foreach loop. if it is measuring how far down we are in calls to contemplate_array_variables() from within itself, shouldn't that just be $depth + 1 in the call? what's happening is that the "depth" is effectively the number of fields in the CCK type. am i misunderstanding what you are trying to catch?
Comment #8
dugh CreditAttribution: dugh commentedThe only thing I can add is that contemplate was working just fine a while back.
I did upgrade some modules, one of which probably introduced the problem. The modules I can remember include: date (v2), calendar (v2), global redirect (this causes new problems with og), og (7.3), and probably some others were updated too.
I would look at global redirect first.
Comment #9
chirale CreditAttribution: chirale commentedhttp://drupal.org/node/263630