CDB Web Design

I’ve seen several long winded explanations of how you have multiple installations of WordPress running through one database. I thought “it can’t be that hard…” so I had a quick go myself and I was right.

When you install WordPress, you change the wp-config-sample.php file to wp-config.php before you install WordPress. When you do this, you edit stuff like your database name, etc.

Go to line 57 and you’ll find:

$table_prefix  = ‘wp_’;

When doing multiple installations of WordPress, simply change it to something else. Yes, it’s as easy as that. For example:

$table_prefix  = ‘wp2_’;

Job done. Quickly.

Do you know what go really well together? Computersss and Guinesssss.

Hic…

In my short time in PHP I’ve come across several good, modern practices and one of those is the MVC (Model, View, Controller) Framework. If you’re a programmer you’ll probably know what this is already, but if not the you should have a look. I’m very new to the MVC model at this time so I’m by no means an expert.

The question came to me “should WordPress have an MVC Framework?”. MVC models allow re-skinning so that you can completely change the look of a site without affecting the underlying logic. WordPress does have a decent layer of absraction but’s it’s not a true MVC framework and is purposely simple. Is this the right way to go or should the core be re-written?

Personally, I like the WordPress core. If you’ve got a half decent knowledge of programming, you can do pretty much anything other than build a fully functional ecommerce solution (as there are much better tailored frameworks for that). As much of the internet is made up of information, it’s easy to see why WordPress has become so popular. I don’t think WordPress should go fully MVC as it does seem to work pretty well as it is.

If you have any comments on this matter then by all means feel free to leave them for me.