A previous theme I used for this site incorporated the collapsible sidebar lists I described in this post.
I’ve finally completed a plugin which provides the same functionality, but in a far more efficient and convenient way.
Some while back I described a method for retrieving and displaying individual post view counts from WordPress.com for those who use the Stats module for site views.
This involved amending the theme’s files and having proved quite popular I thought I’d wrap this functionality in a simple plugin.
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.
Having recently switched from SyntaxHighlighter MT to the SyntaxHighlighter Evolved plugin I was unable to get my custom Apache brush I use for .htaccess and *.conf files to work.
While searching for an answer I found another version of an Apache brush, but couldn’t get that to work either. Further digging and I learnt that I needed to write a plugin to use a custom brush with SyntaxHighlighter Evolved.
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.