Viewing 9 replies - 16 through 24 (of 24 total)
  • Thread Starter d3d5x1

    (@deraxia)

    I tried that right now as per your recommendation, it didn’t work sadly.

    Was the original error before adding ob_clean(); the same as the one now?

    This feed does not validate.
    line 1, column 1: Blank line before XML declaration

    Like it says in that trac issue, this is caused by a plugin or theme. The best thing to do would be to disable your plugins then, if the problem clears up, reactivate them one by one until you narrow down which one is causing the problem. If it’s not a plugin, you can then check the theme by temporarily switching over the Twenty Eleven.

    If adding ob_clean; works for you, there’s nothing saying you can’t use it. Just be aware that future updates can/will overwrite your change and that the underlying problem in one of your plugins or your theme still exists.

    The text/html issue is actually fairly minor. While it’s best to try and find out what’s causing that specific problem, it won’t keep your feed from working or validating. Actually, even the whitespace problem, while it does prevent validation, is such a common problem that most feed readers will overlook it. For example, FeedBurner doesn’t seem to have an issue with your feed as it’s still properly updating.

    You can certainly try that plugin. However, looking at the code of it, all it seems to do is replace wp-blog-header.php with it’s own version. And the only difference between its version and the core version is the addition of ob_start(); and ob_end_clean();. The code is also a bit funky in places. For example, it doesn’t use nonces for the form on its admin page. Also, like with your current solution, the underlying cause of the problem would still exist.

    Okay, they seem to work but occasionally stop working – I cannot recognize the reason for this.

    Are you doing anything at all that might affect it? It could be that the issue is in a part of a plugin’s code that only runs under certain circumstances.

    You can certainly try that plugin. However, looking at the code of it, all it seems to do is replace wp-blog-header.php with it’s own version.

    Really? Wonder if I linked the right plugin…. the one I used scanned every file in your installation for white space

    Thread Starter d3d5x1

    (@deraxia)

    Right now, Feedburner isn’t showing anything except a blank page for my main feed, it is also failing to be read by any feed reader at the moment as I can see, and the comment feed is not showing the proper page for Feedburner, only a list of data.

    I’ve not done anything that might affect it, and have not even published a post in approximately 6-7 hours. When I last checked the feed, I believe it was working, although it is not now.

    I’ve been deactivating all plugins but to no avail. I’ll try that once more and hope something will show up.

    Right now, Feedburner isn’t showing anything except a blank page for my main feed, it is also failing to be read by any feed reader at the moment as I can see, and the comment feed is not showing the proper page for Feedburner, only a list of data.

    That’s weird. It was working 15 minutes ago.

    One problem with trying to troubleshoot the feed is that FeedBurning automatically pings your feed only every 30 minutes. If you temporarily disabled the redirect on your site’s actual feed, you can check for changes in real-time.

    @rev. Voodoo:

    From what I can tell, all it does is back-up the original wp-blog-header.php then replace it with it’s own version. It may have run through every file in the past though. For version 3.0 it has this changelog item:

    2010-09-19 release v3.0, need not to modify error in php files directly, it will use a good and simple way, it just modify wp-blog-header.php in blog directory.

    @big Bagel, ah, thanks…. that kind of defeats the purpose of the plugin for me…. a lazy man’s file fixer for bad plugins / my own sloppiness

    Thread Starter d3d5x1

    (@deraxia)

    Thanks for all the help everyone.

    I solved this for good by replacing my edited WordPress files back with the originals. Then instead of deactivating plugins one-by-one, I mass deactivated all of them, then reactivated them one-by-one.

    I then pinpointed the error to be coming from WP-Polls Version 2.62 by Lester ‘GaMerZ’ Chan. I am not sure why this plugin seemed to randomly act up, it may or may not be an issue with the plugin, however I plan to replace the files with a fresh copy from the repository and see what happens.

    My source now has not a single blank line, and all feeds are rockin’.

    Thanks again Big Bagel, I would’ve never tried to deactivate my plugins again if you didn’t recommend it.

    Awesome sauce. ??

    @deraxia
    That plugin shows support up to only 3.05 only and requires a server environment that supports AJAX…surprisingly, all do not.

Viewing 9 replies - 16 through 24 (of 24 total)
  • The topic ‘RSS Feeds Not Validating’ is closed to new replies.