How come your feed is /wordpress/ but your blog is /blog/?
You doing that with .htaccess?
Thread Starter
rh2600
(@rh2600)
From what I understand:
If you want to access the feeds directly, the documentation tells you to point it at the absolute url:
http://www.abitcloser.com/wordpress/wp-rss.php
You can also access the feeds through permalinks
http://www.abitcloser.com/feed/
And that URL works for PHP and Sage
But I need to access a custom feed, which I think means I need to access it through an absolute:
http://www.abitcloser.com/wordpress/wp-customfeed.php
Under Options: WordPress address (URI):http://www.abitcloser.com/wordpress
Under Options: Blog address (URI): (URI):http://www.abitcloser.com
Under Options: Permalinks > Custom Structure
/blog/%postname%
I then use the static frontpage plugin to pull home.php and set up a wordpress index.php at root
so if you go to http://www.abitcloser.com you get home.php
if you go to http://www.abitcloser.com/blog/ you actually get a 404 page, which is designed to look like the blog homepage…
If you go to http://www.abitcloser.com/blog/blog_title then the permalinks kicks in and shows the blog title…
I stand/sit before you in awe. 🙂
Now then… do you have access to your apache logs? Better yet, can you tail -f ’em and watch what happens when you go after the feed with magpie or sage?
Thread Starter
rh2600
(@rh2600)
Hey thanks, I really appreciate your help. I’m not sure if awe is the right word, unless you are in awe of my foolhardy way of getting nice urls 😉
Tail reports on access_log
When Sage accesses http://www.abitcloser.com/wordpress/wp-rss.php
219.192.114.10 – – [24/Feb/2006:00:13:00 -0800] “GET /wordpress/wp-rss.php HTTP/1.1” 404 1889 “-” “Mozilla/5.0 (Sage)”
When Sage accesses http://www.abitcloser.com/feed/
219.192.114.10 – – [24/Feb/2006:00:12:52 -0800] “GET /feed/ HTTP/1.1” 304 – “-” “Mozilla/5.0 (Sage)”
When Firefox access http://www.abitcloser.com/wordpress/wp-rss.php
219.192.114.10 – – [24/Feb/2006:00:16:22 -0800] “GET /wordpress/wp-rss.php HTTP/1.1” 404 1889 “-” “Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.1) Gecko/20060111 Firefox/1.5.0.1”
So it is actually returning a 404 to FF too, but also attaches the data so FF still reads it?
Interestingly http://www.abitcloser.com is a 200
http://www.abitcloser.com/blog/ is a 400
So I can see why /blog/ is a 404, but the RSS feeds I cant.. hmmm.. is there anyway to stop 404 being send, bearing in mind we are redirecting them anyway?
Thread Starter
rh2600
(@rh2600)
Thread Starter
rh2600
(@rh2600)
Yup well… commenting that out has made my feeds readable again. So I guess my hackery was my own downfall.
So now instead of returning a 404, WP will return index.php with a 200. Feeds work again.
If you type in a valid url it still works, even it is outside the bounds of WP (ie gallery software)
Cheers for your help though…
Glad you got it sorted!
When in doubt, watching the logs usually gives me something to ponder.