Comments on: Plug-in fix-rss-feed

By: willo

willo — Thu, 04 Mar 2010 19:26:19 +0000

What a lifesaver… that would have taken me hours. I donated… thank you!

By: warren

warren — Tue, 16 Feb 2010 18:18:41 +0000

Hi there,

Looks helpful. Your plug-in finds hundreds of issues, mostly tail issues but I’m nervous to change so many files on a functioning site.

The Feedburner form feed error says:
The URL does not appear to reference a valid XML file. We encountered the following problem: Error on line 3: The processing instruction target matching “[xX][mM][lL]” is not allowed.

I also see it in a validator [feedvalidator.org] :
This feed does not validate.
line 1, column 1: Blank line before XML declaration

Since there’s only 1 error, I’m curious to figure out which specific files is the problem and what I can do to remedy it? I notice there does not exist a directory in the domain called “feed”. Is that just an alias?

Any help is much appreciated!

-w

By: Geoff Snyder

Geoff Snyder — Fri, 12 Feb 2010 12:11:44 +0000

I just want to make sure to stop by and say thank you for your plugin. Your plugin fixed my RSS feed problem. Although I only had a few small errors…this tool fixed everything very quickly. Thank you again!

Geoff

By: Andrew S.

Andrew S. — Mon, 08 Feb 2010 11:47:40 +0000

Thank you for that great plug-in, it erased all errors in my RSS feeds. Suggesting you to make the option to list WP theme pages, CSS styles etc. with the same problem. This will speed-up the site loading…

By: admin

admin — Fri, 22 Jan 2010 18:50:23 +0000

Please ensure that your feed content is not cached. It is possible that you see cached errors. In case of any questions regardless the plug-in, you can contact directly to author: flyaga@163.com

By: matt w

matt w — Fri, 22 Jan 2010 18:31:04 +0000

Hi. I’ve ran your plugin through my website and it doesn’t seem to fix anything. I manually set all permissions so that it could fix them, then set them back. It cleaned all the reported errors, but my feed is still showing the same error when accessing it from the browser.

Any idea what could it be?