Blog has been upgraded to WordPress v2.3.3
Thursday, February 7th, 2008WordPress has released a new security update and as such I have updated my blog to WordPress v2.3.3. I have also updated my plug-ins to their latest versions.
Mark Headrick’s BlogWordPress has released a new security update and as such I have updated my blog to WordPress v2.3.3. I have also updated my plug-ins to their latest versions.
Yes, that time again. A couple days ago, version 2.3.2 of WordPress was released which included some urgent security updates. While I was at it, I also upgraded a number of the plug-ins I use to their latest versions. I need to blog more, I actually do have a lot to blab on about, but now is not the time as I have raviolis cooking on the stove. Good stuff! ![]()
Oh yeah, Happy New Year!!
Wow… been a long time since I’ve posted anything new on my blog. Well, there are a number of reasons why and I’ll get into those in a series of posts rather than clumping everything into one huge post covering a variety of subjects. I am simply using this post to announce that I have upgraded my blog to version 2.3.1 of WordPress and using this post to test said upgrade. ![]()
I’ve updated my blog to WordPress v2.2.3 which includes a few security updates, a couple of which were high priority, and some bug fixes. Like before, I only updated the changed files. Since vars.php was one of the updated files, I did have to edit it and force the $is_apache variable to be true since on my server, the server_software variable comes back with WebServerX instead of Apache. Following is the part that I changed:
// Server detection //$is_apache = ((strpos($_SERVER['SERVER_SOFTWARE'], 'Apache') !== false) || (strpos($_SERVER['SERVER_SOFTWARE'], 'LiteSpeed') !== false)) ? true : false; $is_apache = true;
If I do not do this, then it will not modify the .htaccess file if I change the permalink structure.
I have also decided to reduce the possible annoyance factor when loading my website by not automatically playing the random MIDI file that is loaded into in the media player in the bottom-left frame. You now have to click play in order to hear the song. All other “play” links on the site will cause the player to automatically start playing.
I am aware that my site still uses those evil frames and how taboo it is these days to use them, not to mention the difficulties some search engines have with them. I’ll investigate my options… I just don’t like a seperate pop-up window, tab or browser to be created when clicking on a “play” link. It just makes browsing the site so.. disjointed. Hmmm..
I’ve updated my blog to the latest WordPress version 2.2.2 which included some security and minor bugfixes. All I did this time was replace only the changed files. In addition to these I also updated the /wp-admin/export.php file as that had a newer date than the one on my local test site. Everything seems to be working! ![]()