WordPress.org

Ready to get started?Download WordPress

Forums

Feed Validator Puking On My Feed (4 posts)

  1. DeadIntoIt
    Member
    Posted 8 years ago #

    Did a lot of exasperating searching before I posted this ........

    Problem:
    Feed Validator here:
    http://www.feedvalidator.org/

    Returns report from submitting my feed URL
    http://michaels-blog-musing.com/?feed=rss2

    saying:
    Warning
    This feed is valid, but may cause problems for some users. We recommend fixing these problems.

    line 29, column 3: Avoid content:encoded (2 occurrences) [help]

    <content:encoded><![CDATA[I’ll use a RANT I started and never fi ... ^
    line 44, column 3: wfw:commentRSS should be wfw:commentRss (2 occurrences) [help]

    <wfw:commentRSS>http://michaels-blog-musing.com/2006/06/05/test-post-as-i ... ^
    line 54, column 28: guid should not be blank [help]

    <guid isPermaLink="false"></guid>
    =================

    The first issue appears to be because I used an apostrophe in the word "I'll". It puked at that.

    The second issue appears to be a case sensitive issue with <wfw:commentRSS> according to this validator the RSS should be Rss << with lowercase s instead of uppercase.

    My question is regarding the first 2 issues is, will these actually cause users to see wierd code when there is an apostrophe in a post or comment.

    And

    Will the UPPERCASE S's make any difference.

    As for the third issue, when it says:

    line 54, column 28: guid should not be blank [help]

    <guid isPermaLink="false"></guid>
    Is it referring to the word false or the fact that there is nothing between the beginning and ending guid tag?

    If it is something that is supposed to go in there is there someplace in the admin to change it so that element is present?

    Thanks,

    Mike

  2. Samuel Wood (Otto)
    Tech Ninja
    Posted 8 years ago #

    line 29, column 3: Avoid content:encoded (2 occurrences) [help]

    This one is the feed validator being overly picky. It just doesn't like content:encoded. You can safely ignore this.

    <wfw:commentRSS>http://michaels-blog-musing.com/2006/06/05/test-post-as-i ... ^

    Yes, you guessed correctly. Change the RSS to Rss and feed validator is happy again. Easily done, just edit wp-rss2.php and look towards the bottom of the file.

    line 54, column 28: guid should not be blank [help]

    A lot of people get this one. The cause is the "Hello World!" post that WordPress has by default on a new installation. It's not a complete post and has no proper permalink. Delete that first default post and this problem will disappear.

  3. DeadIntoIt
    Member
    Posted 8 years ago #

    Thanks Otto42. I like the straight forward way you addressed the resolution for this issue.

    All fixed .... well except for the picky validator #1 issue.

    Appreciate the help.

  4. tuttosoftware
    Member
    Posted 8 years ago #

    Is there a solution to the #1 issue ?

Topic Closed

This topic has been closed to new replies.

About this Topic