i’m having a problem…
after the creation of a catalog rule - 50% discount rule / all products,
every time i’m saving something - anything.. like a new product or an attribute or a category etc
a strange error apears but the ‘save’ is done :
Cannot send headers; headers already sent in /home/SITE/public_html/FOLDER/app/code/core/Mage/Core/functions.php, line 191
In the frontend everything was ok (and the discount rule was working ) but now
after four times - saving & testing - i can’t see the admin panel neither the frontend..
magento is down
the problem is the same
when i’m clicking ‘save’ it takes a long time to renpond..
and the attached screenshot apears before the ...’headers already sent...’ message:
“There has been an error processing your request.”.
Cannot send headers; headers already sent in /home/SITE/public_html/FOLDER/app/code/core/Mage/Core/functions.php, line 191
I’m having the exact same issue… very odd. It happens everytime a record is saved. However, the site still remains up. It’s just a bit of a nuisance. Anyone have any idea whats causing this?
For exemple, as I’m saving changes on my product (add images), I will get the same error.
I tried to edit the configuration : that works without any problem. It seems that appears only when I’m editing the products.
“Cannot send headers; headers already sent in /home/my_user/public_html/website/app/code/core/Mage/Core/functions.php, line 191”
We’ve been running into this error ALOT lately. As for what “stop further rules processing” is, that just means that additional discount or price schemes cannot be applied. Basically, further deals don’t apply to the deal that you’re already receiving. We’re receiving the same warning about headers already being sent whenever I try to edit attributes, configuration and stores. It appears to be a caching issue because when I disable cache for EAV types and attributes it instantly breaks the installation, whereas if the message appears while editing a setting a simple reload fixes the problem. I tried deleting cache directory, and it broke the installation. The only way that I have found to fix it is to open functions.php comment out the ErrorHandler function, which will restore access to the admin section. Once in, I can reset the cache and everything works fine, well almost until I try to edit attributes, config or stores. But as said, these are mere nuasances and don’t break the installation like disabling the EAV cache does. I’m not sure if this is specific to the number of attributes we’ve created or not, but insight into this would be appreciated.
Great Explanation. I couldn’t have said it better… reason why I comment is because thats the exact same situation I’m in. I experience it sporadically while doing a variety of admin functions, if I just re-load the admin… the error disappears and the record I’m working on (product,attribute,category) works fine.
I’m having the same error message, but I can’t get to any of the frontend or backend… the error page is the only page that will load. I’m not a coder, but I’m willing to open up any file and tinker with it (saving original, of course).
Will you please explain what file to open and what to change? I wasn’t familiar with “comment out” the ErrorHandler in functions.php; if you could explain that, I’ll try it. Quite frankly, I’m at a loss and it seems there are several people experiencing this problem
(Cannot send headers; headers already sent in /home/xxxxxx/public_html/store/app/code/core/Mage/Core/functions.php, line 191)
Hi paco,
Yes, this does seem to be a serious ongoing battle with the magento cache that we have not solved yet. If you open up the file in your error message (app/code/core/Mage/core/functions.php) look for this function that starts on approximately line 167. Place this in front of it:
/*
No find the end of the function, should be around line 242-243. Place this before the start of the next function (function mageDebugBacktrace):
*/
Now you should have successfully commented out the function that is causing you problems. Save the file and try to go to your admin. It will definitely throw some error messages in your header area, but it will at least let you in. Go to cache management and enable if disabled and/or refresh. Now remove the changes you made to functions.php and it should look normal again. Hopefully someone will find out what is happening and provide a permanent resolution.
Dan, thank you so much for the explanation. While I’m pretty ignorant, it’s helping. After doing what you said, I’ve gotten this message now:
Warning: set_error_handler() expects the argument (mageCoreErrorHandler) to be a valid callback in /home/********/public_html/store/app/code/core/Mage/Core/Model/App.php on line 452
Catchable fatal error: Argument 1 passed to Mage_Core_Model_Store::setGroup() must be an instance of Mage_Core_Model_Store_Group, null given, called in /home/********/public_html/store/app/code/core/Mage/Core/Model/App.php on line 342 and defined in /home/********/public_html/store/app/code/core/Mage/Core/Model/Store.php on line 585
I’m using cPanel to access the database through phpmyadmin, so I’m trying to figure out where in the database to look to change Null to “void” or “no” or whatever it’s supposed to be. Or am I looking in the wrong place?
By the way, I don’t expect replies because I know your help is already above and beyond. I do appreciate your time. So in any event, thank you!
This is edited from what I wrote 7 hours ago. If you happened to have read it, I think I was too critical of Magento. I mean, Shazzam, they’ve made a free commerce solution that rivals professional software. It’s quite the digital contraption. If it works well, amen! If not, how can I complain? There are bugs to work out for sure before I could pitch Magento to my company for business use, but I am very excited about the potential of it.
SO… here’s an edited and more appropriate posting:
Okay, I went a-googlin’… and here’s what I found…
I went to “...functions.php...” at line 191 and deleted white space.
Now, I realize I’m almost totally ignorant to the whole coding and php world, but it seemed like a pretty simple fix once it was explained. That said, perhaps one of the Magento coders fixed it recently and it was a coincidence.
So check out those two links and start deleting whitespace. That’s all I can think of. Oh, and I went into my database and deleted several entries (a store, a website, etc.) just to try to get back to some sort of default setup.
Hope that all made sense.
I will try to find other posts with the same problem and offer this potential solution.
