By greg@beargroup.com on
Recently upgraded to 4.7.3 & also moved servers. Getting an error on both gsitemap & on all RSS feeds:
Trying this: http://www.realself.com/blog/feed or http://www.realself.com/gsitemap
Produces this error:
XML Parsing Error: xml declaration not at start of external entity
Location: http://www.realself.com/blog/feed
Line Number 3, Column 1:
Looking at the feed in feed validator confirms this.
http://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.realself.com%2Fb...
Looking inside the node module at the feed portion, I can't see what changed... I don't think this is my theme (although certainly not ruled out). What template would a feed throw to, just default right?
Comments
Browser Depenedent.
This appears to only be an issue in Firefox, not happening in IE which must be ignoring the top 2 lines. Still want to fix it...
Oy... it was me after all.
One of my modules had 4 blank lines after the closing PHP tag... ?>
Sensitive little bugger.
User error.
Same thing here
I had the same problem - a couple of line breaks at the end of a module after the ?> tag.
The way to check this is to have two browsers open to admin/module, using one as your control group and the other to turn off a few modules at a time. Test with a few modules turned off until you find which one(s) is causing the problem.
www.awdd.ca
same here
Had the same problem here - was not looking forward to going through all the modules and looking for extra line breaks.
Luckily i fixed it by removing the extra line breaks that i myself had mistakenly put in at the end of my template.php.
Being a noob, i had put a closing php tag at the end of my template.php file and it had a couple line breaks after it - now i am seeing that the closing tag is not needed at all.
Module Problem
In my case, this was being caused by a module in development stage for 6--"anonymous comment." I kept turning off modules and plugging the feed URL into feed validator (http://beta.feedvalidator.org/) until I had isolated the module causing the error. Turned off this module and everything worked fine after. Noted the bug on the page for that module.