Subscribe to
Posts
Comments
NSLog(); Header Image

A Separate Feed

At The Sand Trap, we published a private "full entry" feed so that GolfWRX (one of our partners) could post the content to their forums. Our general subscribers just get the excerpts, of course, so they visit the site and see the ads (and to keep bandwidth down).

In MovableType, of course, I just created a separate template, published it to the hidden, password-protected directory, and that was that.

Can WordPress be made to publish a single, separate feed (RSS2 is fine)? If so, how?

12 Responses to "A Separate Feed"

  1. No, not without a plugin or making a copy of wp-rss2.php.

    Just do full content feeds and have FeedBurner mirror your feed. Then you get the best of both worlds -- full content and lower bandwidth than you're using now. 🙂

  2. Viper007Bond said on January 17, 2007:

    Just do full content feeds and have FeedBurner mirror your feed. Then you get the best of both worlds -- full content and lower bandwidth than you're using now. 🙂

    For a variety of reasons, FeedBurner isn't an option for TST. I may make a separate copy of wp-rss2.php and hack up feed.php or something to point to my copy.

  3. Or just link directly to your new file without editing feed.php. 😉

    Ex: http://nslog.com/wp-rss2.php

  4. Viper007Bond said on January 17, 2007:

    Or just link directly to your new file without editing feed.php. 😉

    The problem with that, it seems, is the same as problem two mentioned here. Any attempts to create a private feed (with a name like "lakjdfadflk.php") shows an empty feed.

    I copied wp-rss2.php to a new oddly named file. I edited the feed= line in that file to match the filename and added a new case to wp-feed.php's switch just in case. Then I'd load up the file and see an empty feed.

    I attempted to backport the patch mentioned in the above post to WP 2.0.7, but it seems other changes have been made to 2.0.8, because the diff didn't change anything when hitting even the standard wp-rss2.php. The same thing occurs - an empty feed.

  5. No, no. Here, save this as your crazy named file: http://nslog.pastebin.com/861284

    I just deleted the part to check to see if the excerpt should be displayed or not and forced it to always show the full content.

  6. Viper007Bond said on January 17, 2007:

    No, no. Here, save this as your crazy named file… I just deleted the part to check to see if the excerpt should be displayed or not and forced it to always show the full content.

    I know PHP. I did the same things you did. It displays an empty feed, as I said it did. The extra work I did was an attempt to work around the bug.

    It works for NSLog(); - it doesn't work for The Sand Trap. It behaves exactly the same way as the bug I linked to above (and wrote about before). Perhaps you didn't see the link: http://nslog.com/2007/01/10/sand_trap_misdirection_and_empty_feeds/.

  7. Oh, well I can't help you with a misbehaving server. 🙂

  8. Viper007Bond said on January 17, 2007:

    Oh, well I can't help you with a misbehaving server. 🙂

    Has nothing to do with the server. TST and this site are hosted on the same server. It's a known bug.

  9. But what's the difference between the two sites? Why would it perfectly fine here as well as on my PC and not on your other site?

  10. Viper007Bond said on January 17, 2007:

    But what's the difference between the two sites? Why would it perfectly fine here as well as on my PC and not on your other site?

    Did you read the description of the bug? It clearly explains that sites which use permalinks containing "%category%" fail to return the proper feed. This site (NSLog();) does not employ "%category%"; The Sand Trap does.

    It has nothing to do with "your PC."

  11. Erik J. Barzeski said on January 17, 2007:

    Did you read the description of the bug?

    No, not until just right now. I had only read this post 'cause you linked me to it and not the other one you linked to (was busy at the time).

    I also don't see what pretty permalinks have to do with a feed working right or not when you directly access the file, but then again, I'm not a developer of WordPress, so I don't know all of WP's quirks, especially when it comes to pretty permalinks. 😉

  12. 2.1 doesn't seem to fix this problem. I copied wp-rss2.php, renamed it "full_feed.php," and get an empty feed.

    The bug itself seems to be fixed - visiting wp-rss2.php itself works now.


Trackback URI | Comments RSS

Leave a Reply

Please abide by the comment policy. Valid HTML includes: <blockquote><p>, <em>, <strong>, <ul>, <ol>, and <a href>. Please use the "Quote Me" functionality to quote comments.