I have loads of these in watchdog:
Cannot modify header information - headers already sent by (output started at /var/www/includes/bootstrap.inc:589) in /var/www/includes/common.inc on line 141
Also, sometimes (but quite often) when I access some of my feeds, I get this error:
Fatal error: Call to undefined function drupal_goto() in /var/www/modules/feedburner/feedburner.module on line 123
So sometimes redirection works, sometimes not.
Which led me to a temporary workaround, when I disable caching all above errors disappear and everything works OK. Somehow feedburner module is not compatible with caching. Can it be fixed? The site is much slower now with caching turned off. :(
Comments
Comment #1
dave reidI think I had this same problem with my site when I first upgraded from 0.5 to 1.x. I'm guessing it has to do with having the feed redirection check in either hook_menu or hook_init. I will check further into this.
Comment #2
Anonymous (not verified) commentedCool, thank you!
Let me just add that I'm available for assistance, don't hesitate to ask for help with testing.
For faster communication, you can contact me through linportal(at)gmail.com email address.
Cheers,
Comment #3
dave reidI think I've managed to test the crap out of Drupal caching with the FeedBurner module and think I have it fixed in the next development version being created by drupal.org in a couple of hours. Please let me know if this issues has been fixed for all of you!
Comment #4
furmans commentedI've just updated my site with the Oct 17, 2007 5.x-1.x-dev build and still see the problem with performance caching set to "normal".
Comment #5
dave reidfurmans, do you know if you've cleared your Drupal page cache since trying the latest build? Run TRUNCATE on your cache_page table if you haven't and let me know if the problem continues. On my own site that message went away since Drupal still had the old output from the erratic module cached.
Comment #6
furmans commentedI hadn't before, but clearing the cache (cache_page) still does not help. I'm available to help you debug this problem if you need more information. You can contact me through the contact form. Thanks.
Comment #7
dave reidI set up a new blank site for me to test caching and no extra modules to see if I can duplicate this error. I've been getting this error now on my blog since I updated but I have lots of other modules installed so I'm beginning to suspect that it may be another module conflicting with it. Will post results as soon as I get them. Any help from experienced Drupal-cache developers would be greatly appriciated.
Comment #8
dave reidComment #9
Pibu commentedI've been getting the error as described above with the cache set to normal. The status hasn't changed since oct the 19th? I'm available for helping to debug this problem.
Comment #10
dave reidSo I think I've figured it out. When drupal is NOT running a cached version of a page, the $_GET['q'] variable is set to the 'normal', non-aliased path. When drupal IS running a cached version of a page, $_GET['q'] is not normalized, and a lot of path functions, like drupal_get_normal_path and even drupal_goto are unavailable. I think I've managed to use a combination of fixes (using request_uri() and base_path() instead of $_GET['q'], alias table lookups) to make sure that I will always get the correct path of the page and will always be able to redirect. See #186910: Forum feeds not redirecting. Not going to mark this as fixed until it actually gets committed.
Comment #11
GloryFish commentedHi Dave,
I'm implementing the Feedburner module and am seeing this problem right now. Do you anticipate a release with the changes you describe in the near future? If no, do you think it would be possible to detail the changes you have made?
Thanks very much for the great work!
-Jay
Comment #12
dave reidThis issue should be solved in the new 6.x-1.0-alpha version. Please give it a try and let me know! It might take me a bit to get the whole module synced back to the Drupal 5 version, so I'm sorry if you don't have a Drupal 6 install to test it on.
Comment #13
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #14
benstallings commentedThis problem cropped up for me today when I updated to 5.x-1.x-dev ... not sure what version I was using before. It sure would be nice to know what changes you made! Disabling the cache fixes the problem, but I can't afford to keep it disabled; disabling the Feedburner module also fixes the problem. I'm going to try uninstalling and reinstalling the module, and if that doesn't help, I'll see if I can roll back to the previous version that was working for me before.
Comment #15
benstallings commentedUninstalling and reinstalling did not help. :-( Please advise. I'll try to downgrade to the previous version.
Comment #16
dave reidI committed a small fix for the 5.x-1.x version that should fix this error. Sorry for the long delay.