Paged navigation & htaccess generation fails with "exotic" permalinks

[Joen]

I'm using the following permalink structure:

/journal/%year%/%monthnum%/%postname%

In /, I show excerpts, in /journal/ I have WP installed, and show the main blog stuff. My "Blog Address" is /.

When I use the "Next" / "Previous" Posts feature in /journal/, the resulting /journal/page/2/ shows a 404.

This is due to the htaccess expecting paged navigation only on the blog address, with the following rule.

RewriteRule ^{page/?([0-9]{1,})/?$ /index.php?&paged=$1 [QSA,L]}

A quick, manual edit fixes it:

RewriteRule ^{journal/page/?([0-9]{1,})/?$ /journal/index.php?&paged=$1 [QSA,L]}

I've had not had major problems with other aspects of rewriting, with these "exotic" URIs, so I have to ask: Is the above intentional? Or is it simply impossible to use paged navigation with different blog / WP URIs?

Proposed solution: If possible, allow Paged navigation in both blog URI and wp URI, "just to be sure".

In other words, just write both
RewriteRule ^{page/?([0-9]{1,})/?$ /index.php?&paged=$1 [QSA,L]
and
RewriteRule} journal/page/?([0-9]{1,})/?$ /journal/index.php?&paged=$1 [QSA,L]
with auto generation.

[Joen]

Made a mistake when reporting this: obviously this is a general error, not an Adminstration area. Also, I should have prioritized this higher -- it required quite a bit of shotgun debugging on my part to discover.

[Nazgul]

Is this still valid with the new rewrite system?

[markjaquith]

when you move WordPress into a subdirectory, you should stop accessing the subdirectory's index.php for blog-viewing purposes. This may work to some extent, but it's not intended.