Answers.Body: <p>Upon looking at the <code>craft/runtime/logs/phperrors.log</code> I noticed the following error being reported:</p>
  
  <pre><code>PHP Fatal error:  Maximum function nesting level of '200' reached, aborting! in /Users/username/path/to/website/craft/app/framework/base/CModule.php
  </code></pre>
  
  <p>To fix the issue, I updated the following line in my <code>php.ini</code>:</p>
  
  <pre><code>xdebug.max_nesting_level=200
  </code></pre>
  
  <p>To something higher:</p>
  
  <pre><code>xdebug.max_nesting_level=500
  </code></pre>
  
  <p>This error might be thrown in other scenarios as well as this fix seems pretty specific to having XDebug installed. In any case, these steps helped me get it resolved.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2015-02-08T00:43:57.460Z
Answers.LastActivityDate: 2015-02-08T00:43:57.460Z
Answers.UserDisplayName: Ben Parizek
Body: <p>Just ran into this error while developing a plugin.  Not doing much of anything special, just editing and renaming a few templates.</p>
  
  <p>What could cause this error to happen?</p>
  
Tags: <error-message>
Title: Undefined property: Craft\WebApp::$cache
ThreadText: # Undefined property: Craft\WebApp::$cache
  
  (Asked by: username_0 on 2015-02-08)
  
  Just ran into this error while developing a plugin. Not doing much of anything special, just editing and renaming a few templates.
  
  What could cause this error to happen?
  
  **Tags:** error-message
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2015-02-08. Score: 3
  
  Upon looking at the `craft/runtime/logs/phperrors.log` I noticed the following error being reported:
  
  ```
  PHP Fatal error:  Maximum function nesting level of '200' reached, aborting! in /Users/username/path/to/website/craft/app/framework/base/CModule.php
  
  ```
  
  To fix the issue, I updated the following line in my `php.ini`:
  
  ```
  xdebug.max_nesting_level=200
  
  ```
  
  To something higher:
  
  ```
  xdebug.max_nesting_level=500
  
  ```
  
  This error might be thrown in other scenarios as well as this fix seems pretty specific to having XDebug installed. In any case, these steps helped me get it resolved.
  
  
  ---
  
  