-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Headers already sent in Magento #25
Comments
Ok, so I understand a bit more about what's going on but I'm still stumped as to why the headers are already sent. Further debugging reveals Which is consistent with what I wrote/discovered above. I just can't pinpoint what's causing the issue. |
@kylecannon I'd be happy to donate some $$ if you can help me solve this issue. |
Even though this error occurs it technically doesn't cause any harm. I will see what I can do to get the error to subside. |
Thanks @kylecannon |
I have already fixed this error in my current project. For error track need some changes in core files Follow this link Now check var/log/system.log file. In log file you get exact file path and check that. I hope it will help you. |
I get the following when viewing a category page in Magento:
I've identified the issue to be somewhere around
VafJs_Submits
andVafJs_Loader_Ajax
classes in vafAjax.js.include.php.If you add a a simple
return "test";
statement right after thefunction main() {
declaration for both classes you don't get any Headers already sent... mesage. Which I supposed indicates that the problem reside ininclude()
.I'm pretty stumped to be honest, I also don't understand why you use output buffering and not just return a string from a a wrapping function in your included file.
The text was updated successfully, but these errors were encountered: