Skip to main content

Magento Debug HEADERS ALREADY SENT error

When you  receiving the following error in  system.log file:

app\code\core\Mage\Core\Controller\Response\Http.php:44

 [1] \www.pawan.com\lib\Zend\Controller\Response\Abstract.php:727

 [2]  \www.pawan.com\app\code\core\Mage\Core\Controller\Response\Http.php:75

 [3]  \www.pawan.com\app\code\core\Mage\Core\Controller\Varien\Front.php:188

 [4]  \www.pawan.com\app\code\core\Mage\Core\Model\App.php:304

 [5]  \www.pawan.com\app\Mage.php:596

 [6]  \www.pawan.com\index.php:81

if you have no idea what file is causing this.


Here is the steps to debug.

That error is thrown from Mage_Core_Controller_Response_Http -> sendHeaders(). This function calls the super class function that actually does the check to see whether or not headers have already been sent, Zend_Controller_Response_Abstract -> canSendHeaders().


The Zend_Controller_Response_Abstract class handles, among other things, sending response headers and tracking the last time the headers were sent (and from what file and line). Here is what that function looks like, and where we'll make a change around line 316 to lib\Zend\Controller\Response\Abstract.php:


public function canSendHeaders($throw = false) {

     $ok = headers_sent($file, $line);

     if ($ok && $throw && $this->headersSentThrowsException) {

         #require_once 'Zend/Controller/Response/Exception.php';

         throw new Zend_Controller_Response_Exception('Cannot send headers; headers already sent in ' . $file . ', line ' . $line);

     }
    return !$ok;
}


To:


public function canSendHeaders($throw = false)

 {

     $ok = headers_sent($file, $line);

     if ($ok) {

         Mage::log('Cannot send headers; headers already sent in ' . $file . ', line ' . $line, null, 'pawanheserdsent.log');

     }

     if ($ok && $throw && $this->headersSentThrowsException) {

         #require_once 'Zend/Controller/Response/Exception.php';

         throw new Zend_Controller_Response_Exception('Cannot send headers; headers already sent in ' . $file . ', line ' . $line);

     }
    return !$ok;
}


This will log the error in /var/log/pawanheserdsent.log.


Comments

  1. Aanchal Kaura24 July 2018 at 03:54

    You explain better for this concept. I was looking for this tutorial from last week. Really thanks for this insightful blog post. This will helpful for me as I'm dedicated Magento developer. Keep Posting.

    ReplyDelete
  2. Unknown29 October 2018 at 21:48

    Nice article use in this blog post...good information sharing for post....Magento 2

    ReplyDelete
  3. Magento Extensions24 April 2019 at 00:47

    This comment has been removed by a blog administrator.

    ReplyDelete
  4. fletchermartin16 October 2019 at 02:49

    Use coupon code HLWN10 and get flat 10% off on web-to-print Magento extension from Brush Your Ideas.

    ReplyDelete
  5. Indian App Developer26 November 2019 at 02:23

    Pride of Indian app developers who are not only skilled in their technology but also keeps their promise to create a robust code for your solutions. Hire Indian App Developer and save your money! The current scenarios of technology have raised the status of app development in India.

    ReplyDelete

Post a Comment

Popular posts from this blog

Magento 2 product collection Filtering multi-select attribute values

  If you have multi-select attribute of product like below If you want filter value for this option Use below syntax to get product data: ->addAttributeToFilter('store_model', array('finset' => $params['store_model'])) finset key is used for multiselect attribute filter. $objectManager = \Magento\Framework\App\ObjectManager::getInstance(); $products = $objectManager->get('Magento\Catalog\Model\Product')         ->getCollection()         ->addAttributeToSelect('*')         ->addAttributeToSelect('store_brand')         ->addAttributeToSelect('store_model')         ->addAttributeToSelect('store_year')         ->addAttributeToFilter('store_brand', array('finset' => $params['store_brand']))         ->addAttributeToFilter('store_model', array('finset' => $params['store_model']))         ->ad...
6 comments
Read more

magento 2 best seller product display based on current category and subcategories

Magento 2 getting best seller based on category wise displaying i have done below for that to implement this functionality it is working fine for me. step 1 create block file in our module folder <?php namespace Pawan\Bestseller\Block; use Magento\Catalog\Api\CategoryRepositoryInterface; class Bestsellercategory extends \Magento\Catalog\Block\Product\ListProduct {     /**      * Product collection model      *      * @var Magento\Catalog\Model\Resource\Product\Collection      */     protected $_collection;     /**      * Product collection model      *      * @var Magento\Catalog\Model\Resource\Product\Collection      */     protected $_productCollection;     /**      * Image helper      *      * @var Magento\Catalog\Helper\Image     ...
6 comments
Read more

Integrity constraint violation: 1052 Column 'created_at' in where clause is ambiguous

When trying to filter sales order grid with From and To dates it was redirecting to dashboard.after that again i tried to open sales order grind it is generating reports in reports file it showing. "Integrity constraint violation: 1052 Column 'created_at' in where clause is ambiguous" means it is finding a another created_at field. because when we adding or joining the other table then it has also a field named as created_at. So below is the  solution for this error. magento that created_at is of the main_table not of my custom table. Find the below code in the sales order grid.php file. $this->addColumn('created_at', array(            'header' => Mage::helper('sales')->__('Purchased On'),             'index' => 'created_at',             'type' => 'datetime',             'width' => '100px',         )); ...
Post a Comment
Read more