lonnieezell / Bonfire

Jumpstart your CodeIgniter web applications with a modular, HMVC-ready, backend.
http://cibonfire.com
1.39k stars 524 forks source link

Fatal error: Maximum function nesting level of '256' reached, #1221

Open cosmomathieu opened 8 years ago

cosmomathieu commented 8 years ago

After downloading and installing the 0.8.3 version of Bonfire and after building the blog module (by following the tutorial) I get the following error: Fatal error: Maximum function nesting level of '256' reached, aborting! in {base_path}\{app_path}\bonfire\ci3\core\Log.php on line 161

PHP version: 5.6.16

I tried to post this in the Bonfire forums but I couldn't register - the reg form tells me that I dint fill out a mysterious field that is no where to be found on the screen.

Thanks!

silverark commented 8 years ago

For the first issue you could increase the value of xdebug.max_nesting_level in your php.ini: http://xdebug.org/docs/all_settings#max_nesting_level That's where I've seen that issue from beforr. I set it to 1000 for a laravel installation

lonnieezell commented 8 years ago

When you tried to register at the forums was it at forums.newmythmedia.com? I noticed Thursday that the link on the Bonfire pages was causing issues with the captcha and changed it but it's possible it hasn't propagated yet...

Sent from my iPhone

On Mar 19, 2016, at 11:03 AM, Cosmo notifications@github.com wrote:

After downloading and installing the 0.8.3 version of Bonfire and after building the blog module (by following the tutorial) I get the following error: Fatal error: Maximum function nesting level of '256' reached, aborting! in {base_path}{app_path}\bonfire\ci3\core\Log.php on line 161

PHP version: 5.6.16 I tried to post this in the Bonfire forums but I couldn't register - the reg form tells me that I dint fill out a mysterious field that is no where to be found on the screen.

Thanks!

— You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub

cosmomathieu commented 8 years ago

@silverark I stupidly placed the method belonging to the Controller inside of the Model. Once I figured that out everything worked as intended. Thanks...

@lonnieezell No. It was here: http://forums.cibonfire.com/. Is this not the correct forum?