Default RSS feed dead since upgrading to WordPress 2.7.1

I have this problem with one of my sites too – I can’t get my feed to validate no matter what I do. Strangely, this isn’t theme dependant, I get it no matter which theme I select.

There are various feeds available, try them all and see if any of them validate:

/feed/
/feed/rss/
/feed/atom/

There’s one more which I can’t remember.

When I view the page source from my feed, it looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="https://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="https://wellformedweb.org/CommentAPI/"
	xmlns:dc="https://purl.org/dc/elements/1.1/"
	xmlns:atom="https://www.w3.org/2005/Atom"
	xmlns:sy="https://purl.org/rss/1.0/modules/syndication/"
	>

When I view the page source from another site’s working feed, it looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="https://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="https://wellformedweb.org/CommentAPI/"
	xmlns:dc="https://purl.org/dc/elements/1.1/"
	xmlns:atom="https://www.w3.org/2005/Atom"
	xmlns:sy="https://purl.org/rss/1.0/modules/syndication/"
	xmlns:media="https://search.yahoo.com/mrss/"
	>

The only difference between the two in Firefox’s page source viewer is that mine is shown with syntactic highlighting and the working feed is not (plus the working feed has an extra git about yahoo search, but I figure that’s not relevant).

I’m almost suspecting some weird line feed or carriage return problem. Because I can see no relevant difference between the working code and mine.

Oh, and to answer the question, the other feeds seem borked as well. So is my comments feed.

Although I don’t know what application to use to “view” an atom feed.

@karcher – View Source on your feed and look closer at the very beginning.

<?xml version="1.0" encoding="UTF-8"?>

All them spaces before the <?xml are your first main issue that needs to be fixed. Check any files that you may have recently edited (theme files, wp-config.php for instance) and make sure you have no white spaces (or line feeds) before the opening <?php or after the final ?> marks.

Well, validator.w3.org says all my feeds are valid.

Not sure why firefox, feedvalidator and other apps pulling my feed into places like facebook don’t like it.

well crud, the post editor here ate all my leading spaces in my earlier reply. Guess you’ll have to trust me ??

fixed now, I see.

Yep. Before I saw your post I saw another response to a different mal-formed xml problem that mentioned the wp-config. I had edited it through my ftp app, which I *won’t* be doing again.

I re-started with the 2.7.1 wp-config-sample.php, edited for my data, and re-uploaded it, and that seemed to fix the problem. Although Firefox continued to whine until I restarted it.

Thanks!

I’m having the same problem that people are describing here about the parsing error related to having a blank first line.

But I don’t know where, in all of the wp or theme files, this file is located so that it can be fixed. Can someone tell me where it is located?

deja vu:

Check any files that you may have recently edited (theme files, wp-config.php for instance) and make sure you have no white spaces (or line feeds) before the opening <?php or after the final ?> marks.

I think I’ve opened every file in wp and in the them and can’t find what the feed validator is saying.

1.
2. <?xml version=”1.0″ encoding=”UTF-8″?>
3. <rss version=”2.0″
4. xmlns:content=”https://purl.org/rss/1.0/modules/content/&#8221;
5. xmlns:wfw=”https://wellformedweb.org/CommentAPI/&#8221;

[moderated: removed all the code]

https://feedvalidator.org/check.cgi?url=http%3A%2F%2Fwww.gbdesignconnection.com%2Fblog1%2Ffeed

Is there something in that feed validator that identifies the file?

I’m sorry, I’ve looked through again and again. Just feeling really dumb. If anyone can list out the file extension that would be great.

Did you notice the blank line 1 in what you pasted? That’s what is causing your error.

No, nothing in feedvalidator will tell you exactly what file to change. You either did this to one of your theme files or to wp-config.php (as noted multiple times already in this thread). If you’ve uploaded any plugins recently you’ll want to check them too.

Try changing your theme to the Default theme. Does the problem persist? If so, then check your wp-config.php or plugins. If the problem goes away then check your theme files (located under /wp-content/themes/YourThemesName)

Okay, I found the problem by going through the plugins. My server is yahoo and it installed some plugins from the beginning. When I upgraded to Atahualpa theme, something must not work anymore.

The plugin is somehow not editable. So I deactivated it.

It was called

Customizable Permalinks 1.0 from Yahoo Webhosting
Help drive and retain traffic to your site with the Customizable Permalinks plug-in, which enables you to give your readers easily understandable, static web addresses (URLs) for your pages. Customized permalinks make it easier for your readers to bookmark and share your blog posts. By Yahoo! Web Hosting.

Thanks, and sorry I missed it the first time through all the plugins. Thank you for the help.