Hook, Line & Templates

By: Jason Craig on Jul 21, 2009 | No Comments

As web programming advances, it is imperative for the end user to do some research to see what options are available to them and how it could affect you and your coder. Let’s start with choices of forums. The two that I will be covering are Invision Power Board (IPB) and Vbulletin (VB).

I have used both and was equally impressed with the amount of features they contain for both end user and administrator. However, there is one significant difference that we need to talk about. The way they handle adding on themes and addons is completely different.

Let’s start with how each forums handles addons (aka plugins). IPB requires that you ‘hack’ or manually modify the PHP files in order to have the plugin work. Here’s a few reasons why I personally dislike this method:

• After installing a plugin(s) upgrading your forums to a newer release more than likely will render your installed plugins useless. You’ll have to go in and re-add the plugin by hand once again.
• Most plugins provide good instructions for installation for even those with zero PHP knowledge can install them with minimal error. However, missing a single “;” or “{” when copying and pasting from the instructions can render your site completely useless until the error is fixed.
• Some plugins require that you replace code *cringes*. Not only is this worrisome in itself but if you try to install another plugin that looks for the original code, you could find yourself pulling your hair out trying to get everything to work.

So with that in mind, here is why I like using VB:

• VB’s plugin system makes installation errors nearly a thing of the past by using hooks. The way you install a plugin is browse to the file on our computer and upload it. Once you activate it you’re good to go, nothing else to worry about.
• If you need to upgrade your forums, you don’t have to worry about rendering every plugin you installed useless. Only the ones that are not compatible will no longer work.

Let me move on to two other scripts that are not identical in operation, but I think after reading you’ll understand the point I’m attempting to make.

WordPress has to be the most popular blogging script on the market right now. Conversely, Oscommerce is another popular e-commerce script. Both are free and widely used all over the internet. Let’s do some vital comparisons between the two from a coder’s standpoint shall we?

Let’s take a look at WordPress:

• WordPress uses a system similar to that of VB. If you want to install one of the many free plugins available all you have to do is download it, and either upload it manually via FTP or through the admin backend. Activate it and you’re off and running. Even updating plugins is a snap with how the backend will alert users a new plugin is available and an option to upgrade them automatically.
• WordPress’s codex is available online for all to see and use. WordPress’s codes makes creating plugins relatively easy from a coding standpoint as well.

Now on to Oscommerce:

• Oscommerce is similar to IPB in they way it uses plugins or “contributions” as they’re called. Each contribution must be manually added in by modifying existing PHP code.
• Oscommerce’s handling of templates is by far my least favorite. Each template is hard coded in to the core files and includes images. The only benefit to this is, it makes for a straightforward installation. After installation is complete your new shiny site doesn’t need any additional work. The downside is this particular method makes upgrading your site, adding modules difficult and at times impossible.

As you can probably see, by using “hooks” software makers allow the open-source community to add useful features and options to the software without all of the headaches. I truly believe in the future web scripts will follow the path of WordPress and Vbulletin to make installing plugins, and upgrading your site easy. So for your next site, pay attention to the ways in which templating and plugin installation is done as it could cost you in the long run.

No related posts.

Comments (0)