Feed Redirect Problem

  • I’ve had WP 1.5 installed for a while in a subdirectory on my site. it’s still accessible at https://www.hoydnewsnetwork.com/skinny

    Now though, I’ve got it’s own domain for that directory, so you can get there at https://www.skinnyonsports.com

    The problem is this. The old feed was:
    https://www.hoydnewsnetwork.com/skinny/feed/rss2/

    The new feed is:
    https://www.skinnyonsports.com/wp-rss2.php
    or https://www.skinnyonsports.com/feed/rss2/

    I’ve got a redirect setup in my Cpanel to send the old feed to the new feed.

    One problem though is that this feed is a podcast and many of my subscribers still have the old feed and are using an older podcatching client – iPodder 1.1.4 (version 2.0 works fine).

    iPodder 1.1.4 returns a 301 unknown code when it trys to access the old feed.

    I will obviously announcing on my website and in the podcast for people to update to the new feed, but is there anything I can do to prevent losing listeners still with iPodder 1.1.4 and the old feed? Since Cpanel is telling my site to send the old feed to the new one, how do I make it so people using the old feed, won’t be sent and then I can create a copy of the feed at the old location?

    I don’t think that’s a very good solution or even if that’s possible, so any other advice would be appreciated.

    Thanks!

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

  • I just helped a podcaster do this very thing. You’ll want to create a script in your old location that scrapes your new feed every so often — I have Michael set up on a cron job that runs every 15 minutes — and copies it to a local cache if the feed has changed. Have a silent .htaccess rewrite from your old feed location to this local cache file, not a redirect but a rewrite so that podcast software doesn’t even know about the redirect.

    You might ask Michael what’s in play on his site… I’ve done my bid for King and country, so that’s all my contributions for today in those terms. Maybe someday I’ll turn it into a “recipe” type of thing.

    Thread Starter hoyd

    (@hoyd)

    Can you give me a bit of a hint… ??

    The problem is, when I add this line to my rewrite rules:

    RewriteRule ^skinny/feed/rss2/$ skinny.xml

    it doesn’t work. It actually gives me the feed for my other site that is in the root directory of my server, not the skinny directory. Also, could we not just use a rewrite to redirect to the new feed on the new site, or is that still considered a “redirect”. For example, could we not do:

    RewriteRule ^skinny/feed/rss2/$ https://skinnyonsports.com/wp-rss2.php

    Either way, that doesn’t work for me. It just points to my other blog as I mentioned above.

    However, this does work:

    RewriteRule ^test/test.htm$ skinny.xml

    So, I know that the rewrite is working – I’ve taken out that rewrite for now, that was just me testing to make sure I actually could get at least one rewrite to work.

    Any other help would be appreciated as I feel like I’m close! I have a feeling it’s due to rewrite rules in my root directory’s .htaccess file for the root WP install, and that’s throwing off the rewrite for the /skinny WP install.

    Thanks again!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Feed Redirect Problem’ is closed to new replies.