• Resolved oswaltwang

    (@oswaltwang)


    Hey All,

    My site’s RSS2.0 feed (https://sunnytran.com/feed) will not pass XML validation and is very garbled also.

    I get the following errors when trying to validate:

    line 1, column 1: Blank line before XML declaration

    line 199, column 7: XML parsing error: <unknown>:199:7: not well-formed (invalid token)

    I have read dozens of posts about the blank line error, and have tried doing everything suggested. I have removed all blank lines outside <? … ?> from all files for the i3theme, wp-config.php, functions.php. I have deactivated all plugins and removed all widgets. My RSS still wont work correctly.

    If anyone has any other suggestions, I could really use some help.

    Thanks!

Viewing 10 replies - 1 through 10 (of 10 total)
  • wont even load in IE.

    have you tried switching themes and see if it works from there?

    if not, have you edited the wp-includes/feed-rss2.php file?

    Thread Starter oswaltwang

    (@oswaltwang)

    Whistler,

    Thanks for the quick response. I have tried switching to both the default and classic themes, but it still didn’t work.

    The only change I made to the wp-includes/feed-rss2.php file was to remove blank spaces which didn’t work. I previously tried another suggestion that added XSL transformation but that didn’t fix the problem either, so I reverted back to original file.

    I am completely stumped on this.

    The ads GoDaddy inserts in their free hosting accounts break the RSS feed. Search this forum for ‘godaddy free’ and you’ll see that you’re not alone.

    Thread Starter oswaltwang

    (@oswaltwang)

    LenK,

    Is anyone sure that GoDaddy is the cause of this problem? The XML source itself includes a blank line up front.

    I thought this source was generated by WordPress… I am a bit of a novice, but I don’t understand how the GoDaddy frame is infiltrating the XML source.

    Thanks.

    have you tried not using the godaddy stuff?

    Thread Starter oswaltwang

    (@oswaltwang)

    Unfortunately no,

    This is a test site before I put up the real thing. I suppose you guys are probably right and I will have to try non-ad-supported hosting.

    Thanks for all your help.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    It’s hard to tell whether or not you have the blank line problem when you’re using GoDaddy’s free hosting. GoDaddy’s free ad hosting breaks quite a lot of things, including most of WordPress.

    Still, if you do have the problem later, read and follow the instructions here:
    https://feedvalidator.org/docs/error/WPBlankLine.html

    I am in this exact same boat. I’m testing out WordPress on a Go Daddy free hosting account before I launch the real website on a paid Go Daddy hosting account.

    So, my question is, should I just stop worrying about the inability to validate the feed until I start using the paid version? In other words, will that solve all these invalid feed problems, or is Go Daddy in general the problem?

    I am using WordPress now thanks to Go Daddy suddenly changing its preferences in their Quick Blogcast program which I had been using for many months. After a very steep learning curve (for a non-tech minded person like me), I was just starting to feel comfortable with WordPress. But if Go Daddy isn’t going to really work with WordPress I’d like to know before I invest even more time (and money) in this.

    Thank you in advance for any assistance you might be able to offer.

    Moderator Samuel Wood (Otto)

    (@otto42)

    www.ads-software.com Admin

    GoDaddy works fine with WordPress, just not with their free ad-supported hosting.

    samlesher

    (@samlesher)

    I came up with a workaround to get WordPress RSS working correctly on GoDaddy free hosting accounts. I put the details in this post:

    https://www.samlesher.com/code/fix-broken-wordpress-rss-in-godaddy-free-hosting-accounts/

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘My RSS feed cannot pass XML validation’ is closed to new replies.