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 hadn’t noticed it, but someone 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.
I’ve been a customer of GoDaddy for over four years. I know (now) their reputation isn’t the best, but I signed-up with them when I knew no better and to be honest I’ve never really had a problem with their service.
However, last week I started getting 500 Internal Server Error messages whenever I tried to access this blog or login to the WordPress Dashboard. This was a little surprising as I hadn’t made any recent changes.
In a recent blog comment I was asked if I happened to know why the inFocus theme doesn’t display blog post images on single blog post pages.
I too had noticed this when adding images to my blog posts and assuming this was, for whatever reason, how the developer intended it to be thought no more of it.
However, looking at the code it seemed simple enough to add this ability. You can see the quick-and-dirty fix here or read on for what is perhaps a cleaner solution.
Anyone who’s tried this has no doubt noticed that on switching the inFocus theme colour the social media icons in the sidebar may not match the new chosen theme colour. Well, no big deal really. But if you want the icons to match whichever inFocus theme colour you choose, try this.
Since switching to WordPress I’ve been using the WP-PostViews and Efficient Related Posts plugins. Although the inFocus theme I use now comes with its own popular posts and related posts widgets I much prefer the functionality of the aforementioned plugins.
For example, WP-PostViews displays popular posts based on post views whereas the inFocus version uses the number of comments to determine a post’s popularity. And while there appears to be little if any difference in how Efficient Related Posts and the inFocus version determine related posts, the latter does so on-the-fly whereas the former pre-determines them, thus reducing the load on the server.
Just last week I posted my solution for allowing users of the WebTreats inFocus theme for WordPress to choose how post excerpts are displayed. I am of course using this solution on my site. Yesterday I noticed some rather odd-looking URLs associated with a couple of the Read More links on my blog.
Since switching my blog from Blogger to WordPress I’ve been struggling with a new design. I’m pretty savvy with the coding, but if it’s one thing I’m not it’s a designer. Reluctant though I was to use a pre-built theme template I came across the one I’m using now and couldn’t resist. It’s simple yet elegant and in my opinion far superior to anything I’ve seen both in design and functionality.
Of course a template can’t cater for everyone’s needs and I’ve amended the code a bit to suit mine. One particular change I made was the way in which post excerpts are displayed. The theme uses the the_excerpt() function which either uses an explicit excerpt or the first 55 words of the post if one is not provided. I much prefer using WordPress’s <!––more––> quicktag in my posts in conjunction with the the_content(‘Read More’) function.