Mark Headrick's Blog

I have updated my blog to WordPress v2.9 which was just released. I did the auto upgrade option again which seems to have worked well. Even so, once again I had to edit the /wp-includes/vars.php file to force $is_apache to true (see below) since the SERVER_SOFTWARE variable comes back as WebServerX instead of Apache.

// Server detection
 
/**
 * Whether the server software is Apache or something else
 * @global bool $is_apache
 */
//$is_apache = ((strpos($_SERVER['SERVER_SOFTWARE'], 'Apache') !== false) || (strpos($_SERVER['SERVER_SOFTWARE'], 'LiteSpeed') !== false)) ? true : false;
$is_apache = true;
/**
 * Whether the server software is IIS or something else
 * @global bool $is_IIS
 */
$is_IIS = (strpos($_SERVER['SERVER_SOFTWARE'], 'Microsoft-IIS') !== false) ? true : false;

I also had to edit the /wp-login.php file and add session_start(); at the beginning for the Register Plus plug-in to work properly as PHP sessions are not automatically started:

session_start();
/**
 * WordPress User Page

Other than the modifications above, which I have always had to do, the upgrade went smoothly.

Of course, I did perform a complete database and file backup before upgrading!

I have updated my blog to WordPress v2.8.1 which was just released. I did the auto upgrade option again which seems to have worked well. Even so, once again I had to edit the /wp-includes/vars.php file to force $is_apache to true (see below) since the SERVER_SOFTWARE variable comes back as WebServerX instead of Apache.

// Server detection
 
/**
 * Whether the server software is Apache or something else
 * @global bool $is_apache
 */
//$is_apache = ((strpos($_SERVER['SERVER_SOFTWARE'], 'Apache') !== false) || (strpos($_SERVER['SERVER_SOFTWARE'], 'LiteSpeed') !== false)) ? true : false;
$is_apache = true;
/**
 * Whether the server software is IIS or something else
 * @global bool $is_IIS
 */
$is_IIS = (strpos($_SERVER['SERVER_SOFTWARE'], 'Microsoft-IIS') !== false) ? true : false;

Other than the modification to vars.php which I have always had to do, the upgrade went smoothly.

Of course, I did perform a complete database and file backup before upgrading!

Hopefully this works correctly on my production blog the first try LOL.

Publish!

Update: It Worked! http://mhurl.com/1 links to this post now. The Longurl.org website and DestroyTwitter Twitter client are able to preview the link without any problem.  TweetDeck v0.26.1 and TwitterFox 1.8.1 are not able to.

I modified the WordPress Twitter-Tools plug-in to create the short-urls using my shortener before sending the tweet out about the post.

I have updated my blog to WordPress v2.8 which was just released. This time I tried the auto upgrade option. It seems to have worked well. Even so, once again I had to edit the /wp-includes/vars.php file to force $is_apache to true (see below) since the SERVER_SOFTWARE variable comes back as WebServerX instead of Apache.

// Server detection
 
/**
 * Whether the server software is Apache or something else
 * @global bool $is_apache
 */
//$is_apache = ((strpos($_SERVER['SERVER_SOFTWARE'], 'Apache') !== false) || (strpos($_SERVER['SERVER_SOFTWARE'], 'LiteSpeed') !== false)) ? true : false;
$is_apache = true;
/**
 * Whether the server software is IIS or something else
 * @global bool $is_IIS
 */
$is_IIS = (strpos($_SERVER['SERVER_SOFTWARE'], 'Microsoft-IIS') !== false) ? true : false;

There was some code I modified in the RSS Feed widget in /wp-includes/rss.php in previous versions; however, so far it looks like I may not have to reapply that code. After completing the upgrade I did notice that I had to upgrade the TinyMCE Advanced plug-in for WordPress 2.8 compatibility.

Other than the modification to vars.php which I have always had to do, the upgrade went smoothly.

Of course, I did perform a complete database and file backup before upgrading!

After reading Be Careful What You Post, this got me to thinking about something I’ve thought about fairly often. In the past there have been many things I’ve wanted to say or get off my chest that after thinking about it decided against making a post. The reason being, for good or bad, that anything you post, say in a tweet, or write in an “open” forum is there for all to view potentially. This includes past, current, or possible future employers or someone that knows someone who knows some person, company, or product you talked about. In this age, you know that anyone that is thinking about hiring you, that you currently work with, that you’ve just asked out on a date or whatever, is going to look your name up on Google or some other search engine or social network like MySpace, Facebook, or Twitter to find out what they come across.

Since I’ve been doing a lot of twittering lately (I think that addictive nature of my personality has, at the moment, grabbed a hold of Twitter), I sometimes wonder if people forget that what they say in @replies are completely open for public viewing. I also wonder about how private direct messages really are. I also wonder about the integrity of the authors/creators of all these Twitter clients and Websites that ask for a username and password.

So, I guess, in the end, unless you don’t care who might potentially read what you say and the possible repercussions if they do, well, then don’t post, tweet, or write it.