Back in July 2011 I noticed a problem with the WordPress Jetpack plugin and page navigation on this site. With the Jetpack plugin activated page navigation worked only if I was logged-in as admin. When logged-out page urls were being incorrectly re-written and causing 404 Not Found errors.
Now, some 9 months after having first raised the issue a WordPress.org forum member seems to have found a possible cause.
Shortly after the release of WordPress 3 I offered a solution to broken page navigation conceivably caused by upgrading from version 2.
Recently, in an attempt to fix a long-standing and seemingly unrelated issue, page navigation reared its head once more.
I never did get to the bottom of the issue I was having with the Jetpack plugin and page navigation in WordPress. It seemed I would either have to do without site statistics provided by the Jetpack plugin or this site would have to forego page navigation.
That was until I discovered that the WordPress.com Stats plugin, the predecessor to Jetpack’s Stats module, could still be downloaded. Would using this plugin this fix the issue?
Page navigation is currently disabled on this site as it appears to be broken. The culprit appears to be the Jetpack plugin I use that incorporates WordPress.com Stats.
This site uses custom permalinks: /%category%/%postname%/. When navigating pages the URLs are incorrect. Instead of http://domain/page/2 they’re being re-written as http://domain/2 causing 404 Not Found errors.
I hadn’t noticed it, but it was recently pointed out that this site’s page navigation wasn’t working.
I’d upgraded to WordPress 3 a few weeks back and it quickly became clear that this was part if not all of the reason why, as page navigation worked perfectly after downgrading this site to WordPress 2.9.2.