<p>Simplest solution is just to deactivate all debugger stuff in mamp's PHP settings -> <strong>Uncheck: Debugger Activate Xdebug</strong>.</p>

CC BY-SA 3.0
2016-02-27T23:32:19.253Z
That's the simplest solution provided that you're not using the debugger and/or never plan to.
Matt Stein
CC BY-SA 3.0
2016-02-27T10:50:33.807Z
2016-02-27T10:50:33.807Z
Herr_Hansen
<p>That error isn't a Craft or PHP error, it's coming from older versions of <a href="http://xdebug.org/">xDebug</a>.</p>

<p>It can happen on more complicated pages (lots of fields, tabs, etc.), but you can get around it by adjusting the <a href="http://xdebug.org/docs/all_settings#max_nesting_level">xdebug.max_nesting_level</a> to something higher than the default 100 or to upgrade xDebug to 2.3+, which has changed to the default value to 256.</p>

<p>Note that you don't have to have an active debug session going on in order to run into this, you just have to have the xDebug extension installed.</p>

CC BY-SA 3.0
2014-07-31T20:45:17.840Z
Thanks Brad. I set it to 250 on a whim, and all's well again.
Matt Stein
CC BY-SA 3.0
2014-07-31T20:54:06.940Z
WHO DEBUGS THE DEBUGGERS?!
Brad Bell
CC BY-SA 3.0
2014-07-31T20:55:36.357Z
Philosophy majors.
Matt Stein
CC BY-SA 3.0
2014-08-04T04:03:26.863Z
programmer psychologists
Luke Holder
CC BY-SA 3.0
2016-01-17T15:07:29.167Z
I am having the same issue but I don't know where to edit the "debug.max_nesting_level" setting. Can someone point me in the right direction?
user3818623
CC BY-SA 3.0
2016-01-17T19:46:37.120Z
@user3818623 it'll be in your php.ini file.
Brad Bell
CC BY-SA 3.0
2014-07-31T20:44:42.533Z
2016-01-13T03:27:44.403Z
2016-01-13T03:27:44.403Z
Brad Bell
<p>I can't seem to edit entry details all of a sudden: in this Products section (and <em>only</em> this one section), the page title and "Current Version" button will render, but the rest of the page is missing.</p>

<p><img src="https://i.sstatic.net/XEHV3.png" alt="enter image description here"></p>

<p>The only clue is this line from Craft's log:</p>

<blockquote>
  <p>[31-Jul-2014 19:07:36 UTC] PHP Fatal error: Maximum function nesting level of '100' reached, aborting! in /Users/gob/projects/gobias/craft/app/vendor/twig/twig/lib/Twig/Node.php on line 140</p>
</blockquote>

<p>I've loaded earlier MySQL backups, restarted MAMP Pro (PHP 5.5.10), cleared Craft's caches, tried different browsers and machines, and the problem persists.</p>

CC BY-SA 3.0
2014-07-31T20:43:19.097Z
Have you filed a bug through the dashboard widget? Looks like a bug to me...
Marion Newlevant
CC BY-SA 3.0
2014-07-31T20:44:33.613Z
Thanks @Marion—yes I did, and I'm actually asking here since Brad said it's come up before. Answer's on the way!
Matt Stein
<control-panel><error-message>
Why are some entry detail views empty in the control panel?
# Why are some entry detail views empty in the control panel?

(Asked by: username_0 on 2014-07-31)

I can't seem to edit entry details all of a sudden: in this Products section (and *only* this one section), the page title and "Current Version" button will render, but the rest of the page is missing.

![enter image description here](https://i.sstatic.net/XEHV3.png)

The only clue is this line from Craft's log:

> [31-Jul-2014 19:07:36 UTC] PHP Fatal error: Maximum function nesting level of '100' reached, aborting! in /Users/gob/projects/gobias/craft/app/vendor/twig/twig/lib/Twig/Node.php on line 140

I've loaded earlier MySQL backups, restarted MAMP Pro (PHP 5.5.10), cleared Craft's caches, tried different browsers and machines, and the problem persists.

**Tags:** control-panel, error-message
> **Comments:**
> **username_1**: Have you filed a bug through the dashboard widget? Looks like a bug to me...  
> **username_0**: Thanks @Marion—yes I did, and I'm actually asking here since Brad said it's come up before. Answer's on the way!  

---

## 2 answers

### Answer by username_3 on 2014-07-31. Score: 25 | Accepted answer

That error isn't a Craft or PHP error, it's coming from older versions of [xDebug](http://xdebug.org/).

It can happen on more complicated pages (lots of fields, tabs, etc.), but you can get around it by adjusting the [xdebug.max\_nesting\_level](http://xdebug.org/docs/all_settings#max_nesting_level) to something higher than the default 100 or to upgrade xDebug to 2.3+, which has changed to the default value to 256.

Note that you don't have to have an active debug session going on in order to run into this, you just have to have the xDebug extension installed.

> **Comments:**
> **username_0**: Thanks Brad. I set it to 250 on a whim, and all's well again.  
> **username_3**: WHO DEBUGS THE DEBUGGERS?!  
> **username_0**: Philosophy majors.  
> **username_4**: programmer psychologists  
> **username_5**: I am having the same issue but I don't know where to edit the "debug.max_nesting_level" setting. Can someone point me in the right direction?  
> **username_3**: @user3818623 it'll be in your php.ini file.  

---

### Answer by username_2 on 2016-02-27. Score: -1

Simplest solution is just to deactivate all debugger stuff in mamp's PHP settings -> **Uncheck: Debugger Activate Xdebug**.

> **Comments:**
> **username_0**: That's the simplest solution provided that you're not using the debugger and/or never plan to.  

---

