Title: fatal error!
Last modified: August 20, 2016

---

# fatal error!

 *  Resolved [mcmikemn](https://wordpress.org/support/users/mcmikemn/)
 * (@mcmikemn)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/)
 * I’m getting the following error when trying to load my website:
 * Fatal error: ob_start() [[ref.outcontrol](https://wordpress.org/support/topic/fatal-error-698/ref.outcontrol?output_format=md)]:
   Cannot use output buffering in output buffering display handlers in /home/bardoproject/
   bardoproject.com/wp-content/plugins/network-latest-posts/network-latest-posts.
   php on line 1045
 * This started once I updated to NLP 3.5.4, and I’m running WPMU 3.5.1.
 * Help! And thanks. 🙂
 * [http://wordpress.org/extend/plugins/network-latest-posts/](http://wordpress.org/extend/plugins/network-latest-posts/)

Viewing 11 replies - 1 through 11 (of 11 total)

 *  Plugin Author [Jose Luis SAYAGO](https://wordpress.org/support/users/iluminatus/)
 * (@iluminatus)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3596981)
 * Hello, it may be due to your server’s PHP configuration. Could you please edit
   the .htaccess file to add this rule?: `php_value output_handler none`, it should
   look something like:
 *     ```
       # BEGIN WordPress
       <IfModule mod_rewrite.c>
       RewriteEngine On
       php_value output_handler none
       # WordPress rewrite rules down here
       [...]
       </IfModule>
   
       # END WordPress
       ```
   
 * Apparently there are some output handlers that doesn’t work well with output 
   stacking. Please test this and let me know how it goes.
 * Cheers.
 *  Thread Starter [mcmikemn](https://wordpress.org/support/users/mcmikemn/)
 * (@mcmikemn)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3596984)
 * Thanks for the fast response!
 * That, unfortunately, did not help, though. I added the value to .htaccess and
   reloaded the website, but still got the error.
 *  Plugin Author [Jose Luis SAYAGO](https://wordpress.org/support/users/iluminatus/)
 * (@iluminatus)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597026)
 * What bothers me is on line 1045 there’s no `ob_start()`. Could you please make
   a test in your server? upload a test.php file with this content:
 *     ```
       <?php
            echo "<h1>Handlers</h1>";
            var_dump(ob_list_handlers());
   
            echo "<h1>Output Buffering</h1>";
            var_dump(ini_get('output_buffering'));
       ?>
       ```
   
 * Then paste here the results. Output errors are difficult to debug because they’re
   related to different php configurations.
 *  Thread Starter [mcmikemn](https://wordpress.org/support/users/mcmikemn/)
 * (@mcmikemn)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597039)
 * results:
 *     ```
       Handlers
   
       array(0) { }
   
       Output Buffering
   
       string(1) "0"
       ```
   
 * And that’s with the .htaccess file still edited to contain the “php_value output_handler
   none” line.
 *  Plugin Author [Jose Luis SAYAGO](https://wordpress.org/support/users/iluminatus/)
 * (@iluminatus)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597047)
 * Now I want you to do something, could you please add to that file this:
 *     ```
       if( ini_set('output_buffering',4096) === FALSE ) {
       	echo "<h1>Can't Set</h1>";
       }
       /* This is the same as before */
       echo "<h1>Handlers</h1>";
       var_dump(ob_list_handlers());
       echo "<h1>Output Buffering</h1>";
       var_dump(ini_get('output_buffering'));
       ```
   
 * Let’s see if your server allows you to activate the output buffering.
 *  Thread Starter [mcmikemn](https://wordpress.org/support/users/mcmikemn/)
 * (@mcmikemn)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597073)
 * Can’t Set
 *  Plugin Author [Jose Luis SAYAGO](https://wordpress.org/support/users/iluminatus/)
 * (@iluminatus)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597082)
 * I’m wondering, do you have access to the **php.ini** file? If so, could you please
   set the output_buffering to 4096 like this:
 *     ```
       ; a value for this directive (e.g., output_buffering=4096).
       output_buffering = 4096
       ```
   
 * It would be nice if you can check the `memory_limit` it’s recommended to be at
   least 128M
 *  Thread Starter [mcmikemn](https://wordpress.org/support/users/mcmikemn/)
 * (@mcmikemn)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597131)
 * I found how to control my own php.ini under Dreamhost, and configured it to raise
   the memory limit to 128M and output buffering to 4096. I still get the error,
   though.
 * Here is my current test.php output:
 *     ```
       Can't Set
   
       Handlers
       array(1) { [0]=> string(22) "default output handler" }
   
       Output Buffering
       string(4) "4096"
       ```
   
 *  Plugin Author [Jose Luis SAYAGO](https://wordpress.org/support/users/iluminatus/)
 * (@iluminatus)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597132)
 * Hi, it can’t be set because your PHP configuration is using admin flags which
   avoids rewriting php.ini parameters. However, you’ve already set the handlers
   through the php.ini configuration file.
 * Have you tested the plugin to see if it keeps displaying the same fatal error?
 *  Thread Starter [mcmikemn](https://wordpress.org/support/users/mcmikemn/)
 * (@mcmikemn)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597133)
 * I thought that it did and it failed again, but I tested yet again right now and
   it seems to work fine. Thanks for walking me through the fix!
 *  Plugin Author [Jose Luis SAYAGO](https://wordpress.org/support/users/iluminatus/)
 * (@iluminatus)
 * [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597135)
 * Great news, I’m glad you got it working. Feel free to contact me again if you
   find any other issue.
 * Best regards.

Viewing 11 replies - 1 through 11 (of 11 total)

The topic ‘fatal error!’ is closed to new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/network-latest-posts_61c601.svg)
 * [Network Latest Posts](https://wordpress.org/plugins/network-latest-posts/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/network-latest-posts/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/network-latest-posts/)
 * [Active Topics](https://wordpress.org/support/plugin/network-latest-posts/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/network-latest-posts/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/network-latest-posts/reviews/)

## Tags

 * [fatal error](https://wordpress.org/support/topic-tag/fatal-error/)
 * [output buffering](https://wordpress.org/support/topic-tag/output-buffering/)

 * 11 replies
 * 2 participants
 * Last reply from: [Jose Luis SAYAGO](https://wordpress.org/support/users/iluminatus/)
 * Last activity: [13 years, 2 months ago](https://wordpress.org/support/topic/fatal-error-698/#post-3597135)
 * Status: resolved