Description

If I access myblog.com/blog, a 404 is thrown. I was forced to add a line to the htaccess file that redirects myblog.com/blog to myblog.com. I believe this request should be handled by the software though.

There are two options here, both should be given to the administrator.

The first is to REDIRECT to the root directory, the second is to simply SERVE the root directory.

This solves the SERVE solution, but not the REDIRECT, which I'm most interested in.

I want my recent posts to appear on the root, but inside the "blog" directory if someone clicks on it.

So:
www.mydomain.com holds my recent posts.

When you actually detail a post though, it brings you to:
www.mydomain.com/blog/2009/06/post-name or whatever your permalink structure is.

Permalinks allow this, but when you access www.mydomain.com/blog directly, a 404 is thrown. Instead, it should redirect to www.mydomain.com

Unless I'm missing something, this is impossible to accomplish without directly editing Wordpress's .htaccess file. Because permalinks allow for the static directory though, it should know how to handle them.

Unless I'm missing something, this is impossible to accomplish without directly editing Wordpress's .htaccess file. Because permalinks allow for the static directory though, it should know how to handle them.

No, you just need something like a custom page template, assigned to the /blog/ page:

Usually WordPress tries to keep the number of admin options to a minimum. Because what you want to do can be done so easily by a theme or plugin and because the need is so obscure, in my opinion it doesn't warrant an admin option.

So, shouldn't it force a redirect? It seems odd that the software so willingly allows me to create a dead URL. Creating a page to resolve the issue is an obscure solution that requires a ton of unnecessary, extra loading.

So, shouldn't it force a redirect? It seems odd that the software so willingly allows me to create a dead URL. Creating a page to resolve the issue is an obscure solution that requires a ton of unnecessary, extra loading.

Why should it force a redirect? There's no reason to assume that a request for /blog/ should redirect to /. Suppose the prefix is several pseudo-directories deep (e.g. /my/permalink/structure/%whatever%/); should WP redirect every request for each of those "directories" (/my/, /my/permalink/, and /my/permalink/) to the root? The current behavior of responding with a 404 makes the most sense for most situations.

There are millions of obscure things that WordPress lets people do; it's powerful and flexible that way. That doesn't imply that core should include an option for all of them.

exactly. and then, suppose you've a static front page, and place the blog on a page that resides in /blog. or suppose you use a structure with /blog in it, and you place an archives page over in /blog.

use a plugin that adds the redirect (the suggested page template above will be fine).