DD32 wrote:
On Tue, 29 Apr 2008 01:51:34 +1000, Kirk M <[EMAIL PROTECTED]> wrote:
Matt Moore wrote:
That fixed it, thank you.
DD32 wrote:
I've re-opened the bug with a patch
http://trac.wordpress.org/attachment/ticket/6460/6460.diff
If you remove the slashes, and then force a DB Upgrade, it should
work Allright
To force a database upgrade:
Browse to /wp-admin/options.php
Scroll down to "db_version"
Set it to a number one below current, eg, mine is 7796 so i'd set it
to 7795
Hit save changes
Continue to upgrade the DB and try the feeds again.
DD32,
Okay, I have to admit I'm confused here perhaps you could clear a couple
things up for me.
In WordPress there are 3 main ways to access a feed:
/feed/ = With permalinks
?feed=rss2 = For those without permalinks
wp-rss2.php = Directly load rss2
Some themes use the hardcoded filename, I believe that might be a left
over from the old days, I'm not sure.
But the most common use of it today is for directing feeds offsite, Eg,
Many people will have /feed/ and ?feed=rss2 redirected to feedburner,
But feedburner still needs to access it on the original site, So
feedburner loads the rss feed via wp-rss2.php instead.
In this case, /feed/ and ?feed would continue working, but wp-rss2.php
was showing a blank feed.
I think others have answered your other questions :)
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
Ah, that jives with what I saw in my header.php which appears to control
what feeds are detected by a browser and also explains why the other two
blogs were different from mine, one of which was not using permalinks. I
"burned" my feeds from day one, I just never dug into exactly how feeds
worked and how they might be controlled by a theme template.
Thanks for the info! A little bit wiser I am. :)
_______________________________________________
wp-testers mailing list
[email protected]
http://lists.automattic.com/mailman/listinfo/wp-testers
