One of the largest blogs I operate is actually a job posting board called JetEmployment. I decided to use WordPress (WP) as my content management system for this site as it is a proven and highly effective way to layout a site, get indexed by Google, and it is extremely SEO-friendly. Two months after launch, I was awarded with a PageRank of 4 and found that numerous internal pages were ranked and indexed too.
WordPress

WordPress Plug-Ins

Naturally, I added several WP plug-ins including the requisite Google Sitemaps, Akismet, and Kramer add ons as well as a few others. I included several widgets for social communities (removed today to speed up page loading) and have benefited from the implementation of these tools tremendously.

Jobs Were Posting, But Pages Were Not Loading Correctly

Recently, I noticed a pair of odd problems cropping up that made the site act quirky. The first one was a hang up which appeared every time I posted a new entry. The transfer from new-post.php to post.php did not happen — instead, I would get a blank white page which forced me to reload the site in order to proceed.

Upgrade to WordPress 2.2

The next problem was what triggered me to upgrade from WP 2.1.3 to WP 2.2; an arduous task I had been putting off (this upgrade involves swapping out more than 200 files). As I like to have jobs appear on the site on a scheduled basis, I load up most of the next day’s jobs the night before in order for them to appear in a staggered manner.

Scheduled Jobs — Where Are They?

Yesterday, not one of the scheduled jobs appeared as planned. Instead, they were held in queue with time added to each post. This means that once the time had arrived for the post to be listed, they weren’t. As each minute went by, time was added to the entry even though it clearly showed the time when that entry was to appear.

Deactivating and Reactivating Plug-ins

I searched all over the internet for assistance and although I did not find a direct answer I did receive a big hint — deactivate the plug-ins. So, I turned off all plug-ins and then began to test each one as I added them back in one-by-one. When I got to Kramer, that is where the problem manifested itself. So, I deactivated the plug-in and it remains off until I find a solution to the problem.

Problem Resolved, Sort Of

FYI — When a problem comes up on one of my sites I have a reputation for sticking with that problem until resolved. Yes, it took me several hours to locate and identify the quirk and it may take quite a bit more time before the final solution is discovered and implemented, but I’ll get back to it later rather than sooner.

Yes, it is time for me to work on some paying projects and let Mr. Kramer have his rest. His pingbacks will certainly be missed, but in its current state this plug-in is better left off.