Christmas Eve have just started at about 12:03 AM, when I logged on and saw that dreaded message:

Your Account Has Exceeded Its CPU Quota

So I did what all normal people do at first: I ignored it. Actually, I had a very good reason to at the time. Since it was 12:03 AM, I assumed that my nightly backup job (backup and compress files and databases) was causing the issue.

So after it happened the next day (a few times) I decided to do some investigation.

The Culprit – Comment Relish

HostMonster does a good job of providing some helpful information that you can use to figure out these issues. I went to the directory: cpu_exceeded_logs and sure enough there was a file with today’s (and yesterday’s) date in there. I opened it up and so a ton of referrences to comments on a Wordpress Blog:

/ramdisk/bin/php5 /home1/user/public_html/domain.com/wp-comments-post.php

That narrowed things down a little bit. The other helpful directory was mysql_slow_queries. Here I found the following query over and over again:

SELECT c.*, p.*
  FROM wp__comments c
  INNER JOIN wp__posts p ON p.ID = c.comment_post_ID
  LEFT JOIN wp__cr_emailed e ON e.email = c.comment_author_email
  WHERE e.email IS NULL AND c.comment_approved = '1'

It didn’t take too long to figure out that cr stood for Comment Relish.

A little bit of Googling showed me that in some circles, it’s not a very well liked plugin. Some more searching revealed something a bit more technically helpful.

So there you have it, disable Comment Relish and all is well with the world again.

Best of Both Worlds – Proper Fix Instead of Disabling

Now partly because this was a blog I was hosting for someone else and partly because I’m the type of person who’s never satisfied unless they have the answer to everything, I found a middle ground: Good server performance while still maintaining the functionality of the plugin.

So the main problem isn’t the query. Well maybe it is, but I didn’t want to go redesign the entire plugin. Wordpress performs tons of these queries all the time and they don’t seem to cause issues. The problem is with table indexes (or lack thereof).

Pulling up PHPMyAdmin showed me that there’s no indexes on cr_emailed.email or comments.comment_author_email; both of which are used above. So that’s a simple fix right? Actually, no. Adding an index to the comments table was simple enough; although some people rather not mess with the Wordpress core tables.

The problem is with the table used for Comment Relish: you can’t apply an index on wp__cr_emailed.email because it’s tinytext. Go ahead, try and there’s an error. I guess the author decided on tinytext because it would be smaller than varchar? Not sure if there’s a way arond this or not, but I really wasn’t in the mood to investigate. I’ve used varchar all my life and it’s served me well. So we simply get rid of it, then add the index:

ALTER TABLE `cr_emailed` CHANGE `email` `email` varchar(255);
ALTER TABLE wp_cr_emailed ADD INDEX ( email )

And voila!

Do I Need This With The New Version?

The short answer is yes!
Since this problem has arisen there has been a new version of the plugin put out the combats this problem; there are still many problems with this however:

1. Since this isn’t part of the official Wordpress Plugins, you don’t get the upgrade notice. So I didn’t even know I was running an old version.
2. The author has decided to use to very same 1.0 version number with the new version, so you can’t even tell if you running the old version without examining the code.
3. Although there has been a database fix that uses varchar instead of tinytext and applies an index, this fix is only for creation of a new database. So you won’t get the benefit is your table has already been created with the old code.

Hope this helps you folks who are as curious as I was or those who’ve disabled this plugin because of its issues but secretly miss what it does.

• Wordpress 2.5+ Upload Image Error – Finally Fixed!
• Yay! Wordpress 2.5. Almost Perfect
• Wordpress 2.5 – The Vista of Blog Platforms
• Moving Wordpress To A Different Domain
• Reward Your Regular Readers – Skip The Ads

Although it’s not really fair to compare DreamHost to 1and1 Hosting, let’s give it a shot:

Cron Jobs

I use these for my MySQL backups. Download a nice PHP script and set up a cron job to run said script at a scheduled time. Without cron jobs, I have to go through the hoopla of running some PsuedoCron stuff, which basically runs a script if a user visits your website after the script has been scheduled to run. This is fine for small scripts, but didn’t really fly much for my database backups, since the poor sap that happened to trigger the script would have to sit and wait for it’s completion, as it would appear to be something the website was loading.

Ruby On Rails

After working so much with CakePHP, I can’t help but be curious. I really doubt that I’m going to jump ship, but it’s good to have an environment to play with.

Space and Bandwidth

You got 500 GB of disk space to play with, and 5.0 TB of monthly bandwidth. This is enough to host at least a few good sized sites under one account. The unlimited Domains makes this a breeze.

FTP, MySQL, Customization

One of the things I hated about 1and1 was their auto generated FTP users, database names, and database usernames; e.g. u23029490 (come random set of numbers). Always having to look up something is never good. And of course with the base account, you could never add any users.

The also limited the number (go figure) and size of databases that you could have. 100 MB was the limit for size and I believe four (4) the number limit. This forced you to dump most of your work into one database and also use a lot of different prefixes. With applications such as Wordpress, CakePHP, ZenPhoto, etc. make things easier, because they allow a prefix configuration, but God help you if you were trying to import some legacy PHP application that you’d written back in the day.

Shell Access; Lovely, Beautiful Shell Access

Although I don’t really use it much, there are some times where it just comes it so handy. And with the advent of CakePHP’s Bake feature, it’s become damn near and essential tool. Prior to DreamHost I would have to Bake on my Windows environment, then upload to where I was really hosting.

Speed and Reliablity

Reliability, I’ve been told about, so I cannot speak on this for a year. Speed, I can attest to. DreamHost is way peppier than 1and1.

Final Thoughts

I should have done it sooner. If you’re still trying to make up your mind; if you’re still contemplating; let me help you out a big. Stop thinking, click here, and sign up for DreamHost.

• Automate MySQL Database Backup With WebCron – No Cron Jobs? No Problem – Part 2
• Importing Large MySQL Databases – When phpMyAdmin Let’s You Down – Get BigDump
• Gitting Started with Git – Quick and Dirty
• CakePHP Bake – Baking Models, Controllers and Views the CakePHP 1.2 Way
• Moving Wordpress To A Different Domain

General

1. Doug Boude presents DEMYSTIFYING JSON posted at Doug Boude (rhymes with ‘loud’)
2. sylv3rblade presents Stages of Software Development posted at Atma Xplorer, saying, “My take on the process of software development”
3. prakash presents A2Z Informative-Technology, Software, Internet, Tips, Ideas posted at A2Z Informative, saying, “Identifying the color code of an image on the screen is not an easy task. Usually it involves a multi step process and is time consuming. But this tool is able to find out HTML, RGB or HEX color of any pixel on the screen with just a single mouse click. This little tool is very useful for webmasters.”
4. Thorsten Ott presents Sourcebench – freelancer sites reviews posted at Sourcebench – building a better web.
5. Scott H presents 15 Web Sites College Students Can’t Live Without posted at College and Finance, saying, “Not specifically about design, but has a great list of web sites students love, including StumbleUpon which, in terms of developing a web site, can be quite useful.”
6. Raj Sheelvant presents Attention HR: Young workers demand Web 2.0 posted at IT Strategy, saying, “Why Web 2.0 infrastructure in corporations important to attract young talent”
7. aquariphile presents Choosing Between YUI CSS & Blueprint » By Don Albrecht » article » Ajax Bestiary posted at Ajax Bestiary, saying, “With all the recent hype surrounding the Blueprint CSS framework, The powerful YUI framework has been lost in the noise. Both frameworks are powerful, but, which framework is right for your project?”
8. edithyeung presents Want More Traffic? Find Out Here? posted at Edith Yeung.Com: Dream. Think. Act..
9. Amanda Harris presents Creating A Website For Your Charity posted at iBakeSale Blog.

Javascript

1. Doug Boude presents Client-Side Interactivity without Ajax posted at Doug Boude (rhymes with ‘loud’), saying, “this post has a Coldfusion approach to an Ajax alternative…”

That concludes this edition. Submit your blog article to the next edition of Web Development 2.0 using our carnival submission form. Past posts and future hosts can be found on our blog carnival index page.

Technorati tags: Web Development 2.0, blog carnival.

• Web Development 2.0 Carnival – September 24, 2007
• Web Development 2.0 Carnival – November 21, 2008
• Web Development 2.0 Carnival – December 26, 2008
• Websites on Wide Screen – How The Other Half Lives
• Another “What Is Ajax” Introduction

For the past three weekends, I’ve been away from my personal computer. The only life line I’ve had is my stock of Portable Apps on my 512MB USB disk. So I’ve been neglecting a few projects lately. But all of this has changed as of Friday. I’ve discovered XAMPP Lite. It’s just what it says it is, a Lite version of XAMPP. The beauty of this is that it can also run from a USB disk. There’s no install required. So partnered with XAMPP Lite, Mozilla Firefox, Portable Edition, NotePad++ Portable, and, FileZilla Portable I can take my development on the road to anywhere I can stick in my USB disk.

Added Bonus

I don’t have to tell you that running an Apache web server, PHP 5.0 and MySQL from a USB disk is not a great idea for a production environment. Disk access to the USB disk is much slower than a hard drive. This has an unexpected benefit that I’ve noticed with CakePHP. Queries that used to take 3 milliseconds and 4 milliseconds now take 300 milliseconds and 400 milliseconds.

So why am I excited about stuff running so slowly? When you have a table with 20 fields, but only regularly use five (5), CakePHP makes it so easy write $this->paginate() or $this->findAll(); to retrieve results that we sometimes forget the all 20 fields are being returned every single time. You see the debug say that “3 queries took 10 ms“. You don’t really think much of it, but when the debug window says “3 queries took 500 ms“, you realize that you need to do some work. It makes you think about things that normalizing databases, and caching models, controllers, and views.

Installing XAMPP

There’s not really much to it. You download XAMMP Lite, dump it in a folder. That’s the first part. Now the configuration is where you have to be careful. There are two possible configurations:

1. Root Directory Installation
   • Drop the XAMPPlite folder to the root of the USB Disk.
   • Modify your Apache and PHP configuration files as you normally would.
2. Sub Directory Installation
   • Drop the XAMPPlite folder in a folder of your choice.
   • Run setup_xampp.bat. This will go through every configuration file and set the path based on the drive letter and installation directory. The problem with this installation is that you’ll have to do this every time you move to a system with a different drive setup (eg. At home my USB is G:, at work it’s F:)
   • Modify your Apache and PHP configuration files as you normally would.

Everything else you do is as normal. Happy developing. At 130 MB you can’t go wrong. At 130 MB a pop, you can’t go wrong.

Source: XAMPP 1.6.3a [Apache Friends]

• Here’s a Quick Way to Use Multiple Local Roots With WAMP
• Fast CGI Installation
• CakePHP Installation Guide: Just Add Water and 2 Medium Eggs
• Browsers Have Multiple Personalities, Your Designs Should Too
• Installing A LAMP Web Server System With Fedora Core 6

As you guys know, I’ve recently discovered the marvels of rapid web development with CakePHP. This shall be the first in a long serious of CakePHP related material coming from me since I’ve now veered off on a slightly different focus.

After a short analysis, I’ve picked CakePHP as my framework of choice. I’ve been struggling through it for a few months now, but it’s by far better than the alternative of coding by hand (Yeah, I know I’m lazy). I’ve struggled through it so that you don’t have to.

Downloading – Stable or Alpha Version

Step one is downloading CakePHP. The first problem that you’ll run into is that there are two (2) versions to pick from: Stable 1.1 and Alpha 1.2. When I first started out, I needed to use CakePHP for a project instantly, so I decided to with the stable version because the word alpha scared me a little bit. I mean, it’s not even beta yet.

That was my big mistake. A lot of seasoned CakePHP developers will tell you that the alpha version is ready to go and can (and has been) used in production environments. There is of course the slim chance that some key function or component might change slightly, and you application may break on an upgrade for the alpha version, but that’s a chance that I’m willing to take. The alpha version has a lot more in place (emailing templates, authentication, pagination of results, etc), that it just makes everything worthwhile. Also, a lot of the newer tutorials you’ll find make specific reference to version 1.2. And let’s face it, version 1.2 is just way cooler.

If you’re just starting out, I still recommend the alpha version 1.2, because by the time you become well versed and need to crank out a web application or site version 1.2 may well be stable.

Upload to Server

One of the key things I was looking for with a PHP framework is compatibility with PHP 4.0. Some of my clients are on older servers and it’s harder to get someone who is already paying for a host to switch just because you said so. Here are the server requirements from the CakePHP manual:

• An HTTP server (like Apache) with the following enabled: sessions, mod_rewrite (not absolutely necessary but preferred)
• PHP 4.3.2 or greater. Yes, CakePHP works great in either PHP 4 or 5.
• A database engine (right now, there is support for MySQL, PostgreSQL and a wrapper for ADODB).

The manual recommends various methods of installation for development purposes and production environments. These recommendations are all well and good if you have your own server, but some things are simply not configurable with the shared hosts that most of us use these days.

I personally don’t see a problem with the development setup. The take the CakePHP folder and dump it the the www root of the site (if it’s the main site of course) or a subdirectory. The one tweak I would make, if your host allows, is to point your www root for that domain to the app/webroot/ folder.

These are recommended for security purposes, but I haven’t seen a problem with any installation that I’ve had. As a matter of fact, this is one of the few times that I’ve heard someone recommend this type of setup. Even well established packages like Wordpress, SMF, Zen Photo, phpBB, etc just need you to dump files in a folder.

There is something to be said about the recommended setup though. If you happen to run multiple installations of CakePHP and have different applications, in theory, all of them can share the same CakePHP base code and you’d have different application folders. But for right now, this is just a get up and get started guide. The only thing that you need to ensure is that the app/tmp directory and all subdirectories are writable.

Configuration

Everything you’ll need is in the app/config folder. The file core.php houses, well, core configuration settings. Here are a few of the main ones:

1. define('DEBUG', 3);

   set’s the debug level. Use 0 for production

2. define('CAKE_ADMIN', 'admin');

   You’re almost always going to need this, so you might as well uncomment it now. This sets up admin routing so you can have urls like site.com/admin/events/

3. define('CAKE_SESSION_STRING', 'DYhG93guVoUubWwiR2G0FgaC9mi');

   A random string used for CakePHP sessions. You need to change this into something unique or you might potentially leave holes in your app

Then we have the database.php file. Modify the following to suite your database configuration:

var $default = array(
'driver' => 'mysql',
'persistent' => false,
'host' => 'localhost',
'login' => 'username',
'password' => 'passowrd',
'database' => 'database name',
'prefix' => ''
);

I personally have a host that limits the number of MySQL databases that you’re allowed, so I’m forced to dump everything into one database. This makes the prefix option invaluable to me.

Lastly we have routes.php. This file is used to for URL routing. Consider the following:

Router::connect('/', array('controller' => 'contents', 'action' => 'view', 'home'));

This is going to route the homepage site.com/ to my contents controller and run the view action and pass to this the parameter home. This is the same as going to: site.com/contents/view/home/. We can also do some other marvelous things with routing, but I’ll save those for later.

Depending on what your setup is and where you host, you might have to make modifications to the .htaccess file. I haven’t narrowed down an explanation yet, but on various shared hosts, adding “RewriteBase /” solves a lot of problems, just keep that in mind.

Read more on the CakePHP manual.

Launch

Launch CakePHP and make sure your start up screen comes up. Then fire away are your Models, Views and Controllers.

• The Secret of CakePHP Advanced Routing – Even Better URLs
• Here’s a Quick Way to Use Multiple Local Roots With WAMP
• XAMPP Lite on USB Disk – Benchmark PHP and MySQL by Slowing Down Your Server
• Why My Wordpress 2.7 Install “Failed”
• CakePHP Bake – Baking Models, Controllers and Views the CakePHP 1.2 Way

I has finally occurred to me that I should have gotten my own domain name a long time ago. Really, I don’t know what I was waiting for, but it was about time. Since my focus is Web 2.0, WebDevelopment2.com was an obvious choice. I’ve already written about moving wordpress to a different domain, so moving to this domain was walk in the park. I loaded up PhpMyAdmin and exported my database. Pulled up Notepad++ and did a search and replace for my old URL to the new one. Saved the file, zipped it back up, and uploaded it to the server. Since I usually deal with large databases, I didn’t even bother trying to load into PhpMyAdmin. Bigdump is now my favorite database importer for MySQL.

Finally, I loaded up the .htaccess file on the old domain name and slapped in a RewriteRule with a 301 redirect to WebDevelopment2.com. And Viola, here we have Wordpress blog perfectly redirected, without losing a single inbound link. Sure, the Page Rank on the domain name is 0 (for now), but with a name like Web Development, it won’t be for long.

New Focus

I must admit, that when I started this blog I was only vaguely interested in web development and web design. My interests usually hop about like that. I started this blog when AJAX hit the scene. It was the next hottest thing and the birth of Web 2.0. However, coding AJAX, although not difficult, was tedious. And we all know, I don’t like tedium.

Lately, things have gotten a bit more serious, with respect to my interests in web development. But, I’m no less lazy. As a result, my focus (and hence the focus of this blog) is going to shift slightly. Many of you will not notice, but those of you who have been paying attention will see that something has changed. I’ve come to learn the beauty of web development frameworks, such as CakePHP for PHP (duh), Protoype and JQuery for Javascript and AJAX, and even Blueprint for CSS. Don’t worry, if you haven’t heard of any of these, you soon will. Being as lazy as I am, the DRY (Do not Repeat Yourself)Â principle naturally has you gravitating towards frameworks. If someone else; not just someone else, but an entire team of people, work on product for months and even years, I tend to think that they’ve done a better job than I ever code.

This is the new focus of my blog and I hope I don’t lose any of you guys and can bring greater quality and relevance to the things you read here.

• Moving Wordpress To A Different Domain
• Your Choice of Web Development Framework Doesn’t Matter
• Comment Relish Plugin + High CPU Usage – Fixed The Right Way
• Do We Not Understand What Bias Means?
• Here’s a Quick Way to Use Multiple Local Roots With WAMP

Then I noticed that not only posts were gone, but some settings reverted back to their original values. Upon closer inspection, I realized that certain entries in certain tables in the database were deleted. Hmmph, who knows what the problem was. So I figure that it should be a simple enough task to get a backup from my web host. I was wrong about that, very wrong.

Now let me first state that I was also wrong in not maintaining my own database backups. There is absolutely no excuse for this, so I take full blame for my problem. If I had a database back up, I wouldn’t have been in the situation that I’m in right now. Anyway, moving on. After over 4 days of moving back and forth with tech support, they were able to supply me with their earliest backup, which was dated the day after my database meltdown. So I was screwed, or was I?

There were two tools which saved my butt. First, FeedBurner. With FeedBurner, I was able to recover the titles and content for all of my posts, but simply going back to my feed. To accomplish this, I used Google Reader.

I had one other small problem: The links of my posts are not dependent on the date, by default, but on the category. This is where Google’s caching feature comes in handy. I used the post titles and searched for the web page in Google, by using the site: feature. This did two things: it gave me the link of my post, so I could see what was the main category. I could also view a cached version of the page to see any other relevant information.

So, something to note. FeedBurner + Google search cache = Instant Blog Back Up.

• How To Make PayPerPost and Google Adsense Play Nice – MightyAdsense Plugin Hack
• JavaScript Only Links, Why? Someone Tell Me Why, Please
• Automate MySQL Database Backup With WebCron – No Cron Jobs? No Problem – Part 2
• Why My Wordpress 2.7 Install “Failed”
• BloggerWave – Get Paid To Blog

Lava finally made the big step and “moved into her own place“. Moving domains is always such a hassle, but there are a few things that make the process a little bit easier. I was the Administrator during this move and I must say it was a little bit involved, but I think I got it done.

The Domain

The domain was purchase at 1and1.com. Why not NetSolutions, Yahoo, GoDaddy? Because they all have great promotional deals but then it’s upward of $8 to renew every year. 1and1 has a nice flat rate of $5.99 every year.

The host remained the same, since this particular hosts allows up to 10 domains pointing to it. All the files are simply dumped in a different sub folder. I both love and hate the idea of one consolidated host. It’s easier to manage: one login one set of administration and maintenance, cheaper than several different hosts. But if one sight goes down, they all go down. If a hacker gets into one, he damn well gets into all of them. The load on all of the sites is still very small and way under the allotted bandwidth limit. Most of them are blogs using Wordpress and we all know what a small physical footprint Wordpress leaves behind. If any one site seems to out grow things little family what it turns 18 or something, it will definitely be kicked out of the nest onto it’s on hosting package.

Copy Files

Now this should be the simple part. You copy everything into the folder that is going to house your new blog. There are a few minor changes that you might need to make. Depending on your previous setup you may need to edit the .htaccess file and change the RewriteBase option. But I do think that Wordpress will configure it for you when you set up your permalink stuff.

One change that is necessary is editing your wp_config.php file. If you’re changing databases, you need to make the changes here. If you’re not changing databases you still need to make the changes to the table prefix. I forgot to mention that we still need to keep the old database active (details to come later).

Database Migration

Moving the blog involved a little bit of work. There were two stages during this process. There was installing Wordpress and there was importing old data. Now frankly, I know I made some mistakes, but all in all, things went smoothly.

It’s funny how moving databases on the same host was actually more difficult. Well, I made it more difficult I guess. My limited shared host has a limit on the number of database you can have. So, to counter that I’ve decided to use a database to its fullest capacity before I create a new one. So different blogs will share the same database but use different table prefixes for identification. It’s a nice plan and it does work, but it makes imports a bit difficult.

Now because I still wanted the old blog up (reasons to come later) I couldn’t simply go into Wordpress and change the URL. Come on now, that would make things too easy. So I exported the database. I could not do a straight import because I needed to change the table names so that there would be two copies of each table with each having a different prefix. For example, I’m copying all the wp_ tables to wp2_. Sounds easy in theory, but it was a bit involved.

This is the process I ended up going through. I unzipped the exported DB file. Opened the file in a text editor. Now the uncompressed file was about 14 MB. I used Notepad++ to open it, and even with my new hardware it took a while. I then did a search and replace: wp_ to wp2_. This is so that when the script runs it will import into the newly specified table names. After the completed process I would have one bunch of tables wp_ and another wp2_ with the same structure and the same data. If anyone has a smoother method of doing this, I’m all ears. But I did a quick Google search for Copy MySQL Table and apart from console instructions (No shell access, cheap host) I came up short and it was 1:00 AM and I wanted to get to sleep.

So, the file was edited, I zipped it back up in GZip format with 7Zip and went to the host’s phpMyAdmin site and tried to do an import. Only to realize they don’t have the file import field. This was a bit of a pain. I would have had to copy and paste the data into the little form so that it would run the SQL commands. There was one problem with that though, the uncompressed file was 14 MB and there was no way that the browser could handle that without locking up. So importing that large database was another story: Importing Large MySQL Databases – When phpMyAdmin Let’s You Down – Get BigDump.

Database Configuration

No, we’re not installing a new version of Wordpress. You can do that later, after everything is settled, if a new version has come out and you want to upgrade. Or do it before, just not now. Now that your database has been imported properly, you need to make one minor change. Funny enough, this isn’t a change that I’ve seen documented anywhere else though. But it was necessary for me, who knows maybe I did something wrong. I needed to edit the database wp_options table and edit the option_value for the entries where the option_name is siteurl and host. I needed to change these to match the new domain. The first time I left out this step, every time I tried to do anything it just forwarded me back to the old blog. That’s it. I tried editing them from within Wordpress, but that didn’t seem to work either.

After that you’re good for the new database. You might need to update some links within your posts, but the next step will simply make this a preference. The only problem we have is that your ranking is going to suffer because you’re starting from scratch. If you have a good relationship with the people that have given you links, you may beg them to update some links or their blogroll. This would help you dramatically in rankings, but again it’s not a necessity.

Preserving Old Links

This is where the magic happens. People hate switching domains because, it’s a hassle, you lose your rankings for search engines and Technorati, etc, and most of all you lose all your inbound links and your visitors are left in the dark. Well, I can’t help you with the first parts, but that last part is a breeze.

There are two methods. The easy one and the easier one. The only thing is that your permalink structure needs to be identical, so don’t try to get fancy and switch them up just because it’s a new domain name.

For the easy one, we edit the .htaccess file and one line:

RewriteRule (.*) http://www.newdomain.com/$1 [R=301,L]

You add this somewhere after the line: RewriteEngine On

That’s about it really. What this does is that, whenever someone tries to access a link from the old site, it will forward them to the same URL on the new site. The excellent thing is that it will also forward search engines. It’s that great? That’s what the code 301 means. Eventually, they will actually update their database to reflect your new URL. This also keeps your from getting penalized for duplicate content by the search engines. There is only one minor issue with this and it’s just a cosmetic one: the old URL is still left in the browser window. Who cares right? Well I do. There is a workaround, which involves some template changes in your new blog. Basically it says if you have been forwarded by from the old URL, then reload the URL with that of the new one. Pay attention now, this isn’t the same thing. This is done in the browser and refreshes the screen. It’s not really a refresh since it is done before anything else is sent. This, to me is a bit clunky.

The easier one: This is the simplest method that I’ve seen. You can’t really get simpler than this. But it involves leave the old blog active, sort of. Funny enough, it’s called the Moving Your Blog Plugin. You install this on your OLD blog, activate it, go to the options, and enter the URL of the NEW blog (no trailing slashes) and that’s it dude.

Now if you’re like me and you’re on a host with limited database space, then you might want to do a little bit of house keeping. What I’ve done is deactivated all the old plugins, delete all posts and comments, and all files that I’ve ever uploaded (including unused themes – I went back to the classic). Now you’re saying that I’m defeating the purpose by deleting the posts, but actually the plugin doesn’t need the posts. I’m not sure exactly what it needs, but deleting posts and comments didn’t seem to harm it. That’s where most of the space is taken up anyway. I also went through the database and DROPped tables that were created for plugins that I’ve deactivated.

After that, you should have everything working perfectly.

• New Domain: WebDevelopment2.com, New Focus: Frameworks, CakePHP, Javascript, Web 2.0
• FeedBurner + Google search cache = Instant Blog Back Up
• Wordpress 2.5+ Upload Image Error – Finally Fixed!
• Here’s a Quick Way to Use Multiple Local Roots With WAMP
• Comment Relish Plugin + High CPU Usage – Fixed The Right Way

phpMyAdmin is a beautiful tool. It let’s you administer a MySQL Database without all the messy commands. Also, some host don’t even allow you access to those messy commands. So, once again, it’s a beautiful tool. You can pull up a window and run individual SQL commands on the database or you can run an entire SQL script. It’s really great. There is a wonderful export tool that allows you to back up your Database as plain text SQL file or a file in GZip format. I have seen exported files get up to 10 MB compressed, which is over 100 MB decompressed, given that it’s just a plain text file.

Importing MySQL Database

But one thing that is lacking is a proper import procedure. Currently, you can import a database by pasting the SQL statements in a form and clicking submit, or by uploading an SQL file through your browser. Now that’s all well and good, but there are some problems with this method. The main problem is with timeouts. Of these there are two kinds, there are browser timeouts and server timeouts. The second problem is file size. Another limit, which you don’t often read about, is the phpMyAdmin configuration limit.

Browser TimeOuts

Browsers have a limited time that they can be busy waiting for response from the server and when doing a database import this is exactly what is happening. Your browser does a little work of uploading the file. After that it’s up to the server. So while your browser says it’s busy it really isn’t. It’s just waiting for the PHP script (phpMyAdmin) to get back to it and say it’s done. With large databases, this can take a time.

There are a couple ways to get around this. In Firefox you can go to about:config and look for the setting that deals with the browser timeouts. Honestly, I even forget what the exact property is. If you use Internet Explorer (well maybe you need to be punished) you’re out of luck, because as far as I know (which is not much about IE) I think you need to go into registry to do this. If you’re browser times out, it simply stops and kills the connection. With no active connection there script on the server comes to a halt.

Server PHP Script TimeOuts

Now let’s say you’ve gotten over the problem of the browser timeout. Good for you. Now you’re hit with something you may not have control over. A lot of shared hosts don’t allow you to modify their PHP configuration settings, for good reason. And a lot of servers have very fixed limits on the length of time that a script can run for. If this is less than what you’re file needs to run, then you’re once again out of luck. There is no work around for this though, sorry.

File Size Limit

Servers have a fixed limit with respect of the size of file that can be uploaded through the browser. Back in the day, it was stuck at 2 MB. Right now, I’ve seen them maxing out at about 8 MB on average. So what do you do if your export file is 10.5 MB? You’re out of luck, that’s what. Now why don’t they modify their export utility to break files up into multiple sizes that can be handled through import? well, it’s too much work. It’s not their problem, get a better server I guess. Once again, you’re out of luck.

phpMyAdmin Limit

phpMyAdmin has a limit in their configuration file that limits the actual number of SQL commands that can be executed. It’s that simply. If your database goes beyond this, then once again, you’re out of luck.

Well not really. You could install your own version of phpMyAdmin on the server and configure it as you like. If this works for you, great. But if your problem is also one of those mentioned above, then again, you’re out of luck.

What Are Your Options?

Well, you could get off your cheap but and shell out some more money for a better server. A better server would give you access to shell commands. Then you could perform your mySQL queries on the command prompt. How do you go about importing a GZipped or even a plain database using this method? You got me. I was never a big fan of prompts if I could avoid them.

You could zip up your file and email it to support and have them import it for you. That’s actually the first option I came across when I had that problem. I called support, mad as hell, because I couldn’t import my database, which phpMyAdmin so willingly exported for me. They told me that I could email them the file or place it in a folder somewhere on the server by FTP and tell them where it is so that they have access to it. Now, that’s all well and good, but I go to support when something is broken. I don’t see why I need to contact them for something as trivial as importing a database? And in all honesty, I don’t like the idea of waiting.

Option number three: host your own server, where you can control everything. Enough said! So what do the rest of us do?

BigDump: Staggered MySQL Dump Importer

BigDump is the exact tool you need for the job. It solves ALL of the above problems.

Staggered import of large and very large MySQL Dumps (like phpMyAdmin 2.x Dumps) even through the web-servers with hard runtime limit and those in safe mode. The script executes only a small part of the huge dump and restarts itself. The next session starts where the last was stopped.

It’s a simple PHP script. You open it up, edit some variables to point to the database and some other stuff, close it, save it, upload it, upload your database file to the same directory and run the bloody thing from the browser. What does, is it basically it divides your file into sections specified by one of the options. And it runs these sections independently until it’s done.

The options involve:

• Database Server
• Database Name
• Database Username
• Number of lines you want to execute per session
  • You can make an educated guess, or you can just leave it at the default. If that doesn’t work, lower it and try again.
• How long to delay each session

It solves every single one of our problems. There is no file size issue because you’re uploaded the file via FTP. There is no server timeout because it imports in sections. None of these individual sections is going to timeout because they are so small. Now you’re thinking how about the browser timeout, there is no way to get around this right? Well, it’s not that hard. After the script runs on a session, it refreshes the browser window with a new URL. The URL is to the same file, except that it passes variables back to itself with the line it left off at, so it knows where to start again for the next session. It continues with this until it’s done. The new URL registers as a new session so the timeout is reset.

There is an option for the number of seconds to delay after each session. Some servers may frown on running all these commands right after the other. Give them a couple seconds to breathe and they’ll be fine.

Obviously, I don’t need to tell you guys that you don’t close the browser window. So BigDump saves us from the inadequacies of phpMyAdmin, although it is still a great tool.

Read what others have to day about BigDump:

• PHP MySQL SQL File Import with BigDump
• BigDump: Staggered MySQL Dump Importer
• How To Move a Large Database

• Moving Wordpress To A Different Domain
• Automate MySQL Database Backup With WebCron – No Cron Jobs? No Problem – Part 2
• Finally We’ve Moved To DreamHost – Quality Web Hosting
• New Domain: WebDevelopment2.com, New Focus: Frameworks, CakePHP, Javascript, Web 2.0
• Ajax Coding Challenge at About.com

A content management system or CMS allows a user to manage this content. Excellent description, I know. Basically the user simply edits the content of the web site and not the actual pages. They don’t need to know any HTML, they don’t need to deal with the structure of the website they simply edit content.

Xpert.com.au has a nice write up on CMS.

Advantages of a Content Management System:

• Decentralized maintenance.
• Designed with non-technical content editors in mind.
• Configurable access restrictions.
• Consistency of design is preserved.
• Navigation is automatically generated.
• Content is stored in a database.
• Dynamic content.
• Daily updates.
• Cooperation.
• Content scheduling.

As a web developer you have a decision to make. Do you go with an already existing CMS like Joomla or Drupal or do you design your own? Well, that depends on couple of things. How much content needs to be edited, what the user wants to do, what kind of system you have already established, etc.

Personally, I like Joomla. The problem with Joomla is that it lets you a LOT. Sometimes you don’t want the user to have all this functionality, it’s sometimes a bit of overkill. If the page is more or less static and the user may need to make simple changes from time to time, writing your own CMS makes sense. If the user wants a blog, I say go with Wordpress. I’m a huge advocate of not reinventing the wheel. They guys at Wordpress have been doing this for years now; they should know what they’re doing.

Basically folks, you need to analyze the task at hand and make an informed decision. OpenSourceCMS has a huge list of CMS programs that you can even test out on the website. When writing your own, you have to consider how long it’s going to take, whether you can do it effectively and efficiently. Prepackaged tools usually have all the fixings: file uploads, image stuff, etc. Simply decide what you need and what makes sense.

• From Mambo – Joomla! 1.0
• Dclick Ads – Another Quick Start Up Advertising Site
• Reader Input: Picking A CMS – Part 1
• Q&A With Joomla Development Leader
• Bad First Impression for Joomla

Just a quick note to recommend AutoMySQLBackup for your MySQL backup needs. This little gem does daily, weekly, and monthly backups. It handles all the backup rotations for you. It compresses the files, can backup to remote servers, email you logs, and much more.

Now if you’re like me and you’re on a shared host, here is an option for you. There is backupDB. I haven’t found something better than that thus far. One problem though, you have to have your own cron job to call it so that it’s automated.

• Automate MySQL Database Backup With WebCron – No Cron Jobs? No Problem – Part 2
• Automate MySQL Database Backup With WebCron – No Cron Jobs? No Problem – Part 1
• Comment Relish Plugin + High CPU Usage – Fixed The Right Way
• Importing Large MySQL Databases – When phpMyAdmin Let’s You Down – Get BigDump
• Gitting Started with Git – Quick and Dirty

The Linux platform used is Fedora Core 6. Some may claim that other distributions are better, they are more user friendly, etc. etc. And they would be right, however, In my opinion, as a production environment, you can’t beat Fedora Core 6. It is very stable and reliable and perfect for a stand alone web server. There are even instructions at the end to install a free web hosting control panel if you decide to resell hosting services.

They start out with downloading Fedora:

To install such a system you will need the following:

• Download the Fedora Core 6 DVD iso image or the 5 CD iso images from a mirror near you (the list of mirrors can be found here: http://fedora.redhat.com/download/mirrors.html), e.g. ftp://ftp.tu-chemnitz.de/pub/linux/fedora-core/6/i386/iso/FC-6-i386-DVD.iso
• an internet connection…

Then the installation process complete with a LOT of screen shots and detailed instructions of even how to set up IP addresses, firewalls, hosts, etc.

Then we install the components, MySQL 5.0, Postfix With SMTP-AUTH And TLS, Maildir, Apache2 With PHP5, ProFTPd, Webalizer, Perl Module, etc.

Whoa. You still with me? OK. In between all these installations there are details on the best configuration most of these components if they are not configured properly out of the box.

I ran through it (minus the Fedora Installation – which takes a while, trust me) and it took about an hour and a half.

This tutorial is incredible. I’ve never seen anyone go into such detail, except of course when we look up these instructions as seperate entities. The tutorial is detailed and easy to follow.

The good thing about this system is that you won’t need to touch it except to updates, which are just as easy as Windows updates. If you’re going to have a dedicated web server, I highly recommend taking a good hard look at this tutorial.

• Fast CGI Installation
• Gitting Started with Git – Quick and Dirty
• AJAX Client Engine (ACE) – Problems
• Give Me 15 Minutes and I’ll Make You A jQuery Expert
• Start The Year Off Right – Developing Web Applications with AJAX

Arrays to MySQL dates and back.

Simple conversion functions to change MySQL dates to arrays, arrays to MySQL dates.

• Stop Hating On PHP And Learn To Code Better
• MySQL & SQL Server Performance
• Zamzar – Free Online File Conversion
• JavaScript, XMLHttpRequest (Ajax) Cheat Sheet
• WYBISYG – What You Bake Is What You Get – CakePHP + FCKEditor

Alejandro Gervasio at DevShed writes:

Setting up the Foundation for an Extensible Website Engine with PHP 5
Building a dynamic website with a database backend is something that nearly every PHP programmer will need to do, usually sooner rather than later. If you haven’t done it yet (or even if you have), this two-part article series will show you how to develop a website engine that can generate pages on the fly from a simple database structure.

Since this is a two part series, I’m assuming that the portion on editing the database will some in the second part. But just to precede them for a minute, it can be seen that a simple backend could be designed. I would go one step further and insert HTML text into the database rather than simply text. In the backend it would be quite simple to incorporate a WYSIWYG editor such as FCKEditor of HTMLArea to allow users to edit the website easily.

• WYBISYG – What You Bake Is What You Get – CakePHP + FCKEditor
• The Secret of CakePHP Advanced Routing – Even Better URLs
• Reader Input: Picking A CMS – Part 1
• Top 5 Basic SEO Tips – You Can Do These Yourself
• Content Management Systems

I will definitely take Karl’s tests into consideration as I perform my own.

Karl Write:

Sidetracked with MySQL & SQL Server Performance
Here’s the short version:

1. This is only for inserting 500 rows into a 3 column table
2. InnoDB really seems screwed on Windows platforms running 5.x – Certainly don’t have anything conclusive, but I’d watch out
3. For my very simple test, MySQL on Linux blew SQL Server 2005 on windows out of the water.
4. On windows, ASP.NET’s connection to MySQL seems as fast as PHP’s

• Joomla Template Tip: Optional Modules
• XAMPP Lite on USB Disk – Benchmark PHP and MySQL by Slowing Down Your Server
• Comment Relish Plugin + High CPU Usage – Fixed The Right Way
• Browsers Have Multiple Personalities, Your Designs Should Too
• Automate MySQL Database Backup With WebCron – No Cron Jobs? No Problem – Part 2