toyg

uhm, you just need to add a few things.
where you have the query SELECT ID, post_title add , post_excerpt before “FROM”, and then replace the “output line with $output .= $before . '' . $post_title . ''. $post->post_excerpt . $after;

I’ve no idea what you’re talking about…

I’m banging something together right now. Might be ready tomorrow, or the day after that ??

The permalink structure is independent from the plugin (mine is actually very complex, btw). The only requirement is to add RewriteRule ^([A-Z]+([a-z]|[0-9])+){2,}$ /index.php?wikiword=$0 [QSA] to your htaccess.
I’ll fix the code as suggested ?? btw, the regex at the moment is far from perfect, any suggestion is very appreciated :))

Uhm, strange… I’ve changed the link anyway, now it should be ok.

Aggregators will certainly follow a redirection, and they usually define the feed format by its content, not its extension. So don’t worry ??
And anyway, theoretically speaking, sending an HTTP status like 301 (moved) , 302 (redirect) or 303 (see other) will signal to the client that there’s some content, but that content might be different from the one requested, so you can’t say you didn’t warn them ;).
You can gently send something like:
header(‘HTTP/1.0 302 Redirect’);
before redirecting with another
header(‘Location: /mynewfeed.rss’);

I use Shelley’s code on my site, and I have to say, WP should ship with it enabled by default. There’s no reason not to: it’s self-contained, very short (5 lines of code) and it wont’ even break validation.

redirect them with a mod_rewrite rule that catches all requests to index.rdf and redirects them to the new feed via some 30x HTTP code.
If you don’t know what I’m talking about, give a look at the Options/Permalink page, where it shows the stuff you should put in your .htaccess; it’s basically just a bit of regex. But please be nice, put a 30x header somewhere between the client request and you sending the new feed ??

(forgot to login, dammit ??

If you need someone to help with the tracker, I’m here.
And by the way, I’d strongly recommend an effort by the WP team to adopt some kind of automated doc-generator for the codebase, like PhpDocu.