WordPress.org

Ready to get started?Download WordPress

Forums

Feedburner: Unable to burn feed (8 posts)

  1. mlogos
    Member
    Posted 7 years ago #

    I am going round and round with feedburner and my host. Both are blaming WP. When trying to burn a feed, feedburner autodiscovers the feed but when I actually try to burn it, it returns a 404:null error. Here is my last message from feedburner:
    " have ran this by a few others hear at FeedBurner. You probably need to resolve this in your WordPress installation. If the autodiscover tags do in fact provide the correct address for your feed, then you need to determine why it returns a 404 error. Alternatively, if there is another address for your feed, you can put it in directly. Again, that would be driven by your WordPress installation."

    I have burned many feedes and this is the first time this has happened. I still don't think it's WP but has anyone else had this problem and solved it?

  2. Chris_K
    Member
    Posted 7 years ago #

    Without a link, hard to say, but I'd start by disabling any feedburner plugins (or .htaccess redirections) and ensuring that your feed, as provided by the blog, looks right and validates.

  3. mlogos
    Member
    Posted 7 years ago #

    Here is my .htaccess file:
    "
    # BEGIN WordPress
    <IfModule mod_rewrite.c>
    RewriteEngine On
    RewriteBase /
    RewriteCond %{REQUEST_FILENAME} !-f
    RewriteCond %{REQUEST_FILENAME} !-d
    RewriteRule . /index.php [L]
    </IfModule>

    # END WordPress
    "
    I have no feedburner plugins activated. The feeds will come up in a browser and look just the same in header.php as every other blog I have (except for the domain name of course).

  4. mlogos
    Member
    Posted 7 years ago #

    Sorry - I forgot to give you the url - http://articlesonblogging.wordpressguru.com/blog/

  5. Chris_K
    Member
    Posted 7 years ago #

    Discovery means that it found:
    http://www.articlesonblogging.com/blog/?feed=rss2 in your blog's header.

    However, browsing to that url results in a blank page -- which is clearly the real issue!

    You might try disabling all plugins. You might also check your web server's error logs and see if there's anything being reported.

  6. Samuel Wood (Otto)
    Tech Ninja
    Posted 7 years ago #

    How about actually making posts other than the default one before you try to get a feed?

  7. mlogos
    Member
    Posted 7 years ago #

    Who knew! Thank you for your great suggestions. I DID make a post and the feed burned. I was just doing it bass-ackwards. I was trying to get all the ancillary stuff finished before really getting into the theme, plugins, posting, etc.

    BTW HandySolo - I aksed my host about server logs and where to find them. The reply was that since they now use their own 404 pages and don't allow users to create their own, the logs aren't much use because a 200 will create a 404 entry.

    Huh??? I LOVE tech support! <G>

    Cathy

  8. Chris_K
    Member
    Posted 7 years ago #

    As always, I forget that little wrinkle. Thanks Otto42 :-)

    And wow, that's an interesting approach to avoiding log access. Sheesh.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.