Forum Replies Created

Viewing 4 replies - 1 through 4 (of 4 total)
  • Yes, stats module did reactivate after 2.9 upgrade but shows no hits. So, I’m reasoning the plugin is broken with 2.9.

    Thanks very much InfoCynic.

    My feeds now validate!

    While I was fixing the WFW language, I noticed the code that uses <content:encoded>. While it does validate, I’ve found that the validators don’t like this syntax and recommend changing it.

    Have you done anything with this, or just left it alone?

    Thanks again for your help on the WFW thing!

    I also picked up this error trying to validate my feed. I asked FeedBurner support about this as I first noticed it as a problem with my FeedBurner feed.

    They explained in a post on their forum as follows:

    “However, a recent, largely undocumented change to this namespace has been causing feed validation errors for publishers whose feeds feature the “<wfw:commentsRSS>” version of the tag, which has been in use since at least 2003. The new syntax for this tag is:

    Code:
    <wfw:commentsRss>{comments feed URL}<wfw:commentsRss>”

    So, basically the RSS needs to become Rss.

    The post is located at: http://forums.feedburner.com/viewtopic.php?t=3781&highlight=wfw

    The question now is, what can be done about it? Can we fix this ourselves in the WordPress code? I’m a little nervous about trying this myself.

    Anybody know?

    Thanks much.

    I’ve got this same “content:encoded” problem on both of my WordPress blogs (www.farrellkramer.com/blog) and (www.talkingcommunications.com.)

    At first, I thought it was a problem with a plugin or FeedBurner, but now I believe it’s WordPress. However, I have validated my feeds before — I think a week ago — and this problem didn’t pop up.

    I wonder if there’s been some change to what constitutes a “valid” feed. Or perhaps something else changed.

    Any thoughts?

Viewing 4 replies - 1 through 4 (of 4 total)