Well, after a 2-day programming blitz, I launched my first CodeIgniter website yesterday. It’s hosted on the keyword domain www.PremierLeagueShirts.com and is an affiliate site targetting those looking for English Premier League jerseys. While still under heavy construction, the primary features are now available for use. The remaining changes will mostly be cosmetic and UI-related.

Here are some of the features that I programmed into www.PremierLeagueShirts.com:

• SEO-Friendly URLS - Each and every URL is search engine friendly. Take for example some of these URLS:
  • http://www.premierleagueshirts.com/store/subcategory/Shop_By_Player/Beckham_David
  • http://www.premierleagueshirts.com/store/subcategory/Teamwear/Womens
• Product Search – While still quite simplistic, will return a list of products which matches the user’s query.
• Completely Database-Driven: All content is stored in the Premier League Shirts database. No real-time webservice calls to the main affiliate site which may slow down page loads.

And what’s left to come?

• Improved GUI – Yes, the UI is plain. But my goal was to get the site out there and crawled by the major search engines. Now that that’s done, I’ll see what can be done about the look-and-feel of the site.
• Improved Search – The site search currently only looks at the Product Name, and not the Brand, Category, or Description. This will be looked into.
• Stats – Record what products are being looked at, what’s being searched for, and store that all in the database. Spit that out onto new pages on the site for further crawling by Google.
• Additional Content – What is on the site right now is strictly affiliate products and their descriptions. Obviously Google may not like that so much, so will have to look at additional sources of related content.

So, what do you think so far? Since this is my first forray into the world of CodeIgniter, I’m please with what I’ve accomplished over the last 2 days.

The purpose of this post is to shed some light on a problem that I wracked my brain over for a few hours last night.

The problem: After installing Apache, PHP, and MySQL and configuring the Code Igniter framework, you get a blank web page when testing your first controller, model, and view.

What I discovered were two issues that, when combined, create the perfect storm of an installation problem:

1. First, MySQL is no longer enabled by default with PHP 5. Says the PHP website of MySQL in PHP 5:
   

   MySQL is no longer enabled by default, so the php_mysql.dll DLL must be enabled inside of php.ini. Also, PHP needs access to the MySQL client library. A file named libmysql.dll is included in the Windows PHP distribution and in order for PHP to talk to MySQL this file needs to be available to the Windows systems PATH.

   It’s been a LONG time since I’ve programmed in PHP let alone installed PHP, so this was news to me. Anyway, if check out the MySQL installation notes on the PHP website if you need help enabling MySQL.  

2. Unfortunately, that was the easy part. Once I had an error message to work with, Google lead me to the PHP website, and I was in the clear. But, for the longest time, I wasn’t even getting an error page. Remember, all I was getting was a blank HTML page. So what was the cause? Code Igniter…
3. Using some creatively placed die() calls, I found out that the application was dying when trying to connect to the database. (Previous to this, I had already double- and triple-checked my MySQL username and password in the Code Igniter configuration file, and had even tried out alternate accounts, like my MySQL root account.)What I found out was that the MySQL drivers in Code Igniter were suppressing errors when attempting database connections.

This is what the code looks like in the Code Igniter mysql_driver.php file:

function db_connect()
{
   if ($this->port != '')
   {
      $this->hostname .= ':'.$this->port;
   }
   return @mysql_connect($this->hostname, $this->username, $this->password, TRUE);
}
The “@” symbol before the mysql_connect() function call supresses any errors that may be returned. It is that symbol that wasted a good 2 hours of my life.Anyway, after I removed the “@” symbol from the code and re-tested my web application, PHP spit out the error message that I should have been presented with hours ago, and I was well on my way to fixing the problem.
 If you’re experiencing the same problem that I was, I hope this helps you correct it faster than I did! Best of luck.

Oh, and did I mention how much I prefer Code Igniter over Ruby on Rails? It’s messier, but with my C and Java background, it makes more sense than Ruby and Ruby on Rails does!