After I upgraded to Wordpress, I noticed that the below error was displaying on the Dashboard:

Warning: preg_match_all() [function.preg-match-all]: Compilation failed:
this version of PCRE is not compiled with PCRE_UTF8 support at offset 0  ...

I did some searching, and came across this site where it gave me an idea of where to start looking. To resolve the issue, I upgraded PHP (for the heck of it) and upgraded Apache from 2.2.4 to 2.2.14.  Apache v2.2.14 has PCRE v6.6 built-in, whereas before the upgrade it was using v5.5ish which was causing the problem.  After doing this and making some adjustments to my httpd.conf file (I had to uncomment modules that I commented out) and restarting Apache, all was good.

I’m upgrading from b2evolution to Wordpress.  Just due to the fact that Wordpress is simpler to use.  And the upgrade process isn’t as atrocious.

I’ll be trying to get my previous updates imported asap.

*Edit* – Import complete.  That was easier than I thought.

I had a little difficulty installing the MySQL gem for Ruby 1.9.1. I constantly received an error that said “/usr/local/lib/ruby/1.9.1/mkmf.rb:362:in `try_do’: The complier failed to generate an executable file. (RuntimeError) You have to install development tools first.”.

Well, after a couple of days of tinkering around on my server and several Google searches, the solution was found at the following site:

http://smangal.wordpress.com/2007/05/17/mysql-gem-on-centos/

If the above site is not available, the mysql-devel RPM had to get installed/updated. I did this through YUM. After getting that updated, the MySQL Ruby gem installed just fine.

I encountered an issue when trying to get WEBrick to start on my server:

[root@ip 13:07:59]script/server
/var/www/vhosts/nickthompson.name/httpdocs/emporium/config/boot.rb:18:in `require': no such file to load -- initializer (LoadError)
from /var/www/vhosts/nickthompson.name/httpdocs/emporium/config/boot.rb:18:in `'
from script/server:2:in `require'
from script/server:2:in `

There was no such thing as a ‘initializer’ gem to install (and trying to install it via gem install did not work) and after much tinkering around, this problem was resolved by installing Rails to 2.3.5. An upgrade of RubyGems to 1.3.5 was also done prior to this, but I don’t know if this contributed to the issue getting fixed.