I will be going through the steps on how I achieved the following:

1. Convert vBulletin 4 to bbPress (specifically, I converted from vBulletin 4.0.1 to bbPress 1.0.2)
2. Integrate WordPress with bbPress to share the same users table
3. Make the WordPress database contain the central user database (optional)

Preamble

I decided to test out bbPress using my existing vBulletin 4 installation. This is rather tricky due to the lack of converters out there; as of this post, there are no direct converters from vBulletin 4 to bbPress. I also wanted to integrate (share the user database) between bbPress and WordPress. This allows a user to sign up only once to access both your WordPress and bbPress installations.

In my case, I wanted WordPress to contain the central user database table. This meant that my bbPress forum would connect to the WordPress user table. Why? Merely a personal preference. This takes a little more work (then simply using bbPress’ user table) and has its limitations.

I will explain all of this in detail below.

Initial thoughts on bbPress

To be blunt bbPress’ basic, out-of-the-box features are primitive compared to all the major forums I’ve used – myBB, phpBB, vBulletin, and Invision. bbPress is a forum stripped down to its core – it doesn’t even come with basic viewing permissions (yet). It is a massive downgrade from vBulletin 4. If you’re like me, you will get a lot of headaches downgrading to bbPress.

However, we must keep in mind that bbPress is still in its infancy. When I mentioned that bbPress was primitive, I don’t really mean that in a negative way. The developers are taking the correct approach in creating a solid core before moving on to the bells and whistles. Look at where WordPress is today. Its userbase is incredibly large and supportive, and I don’t doubt that hundreds of quality plugins will be available for bbPress as well.

The limitations of converting

Converting from vBulletin 4 to bbPress isn’t without its speed bumps. Since there’s no official converter, it will not go as smoothly as one would hope.

The only solution (as of this blog entry), is to convert vBulletin 4 to phpBB3. Then from phpBB3 to bbPress. What happens along the way?

• All your members will default to either the member or administrator role. This means groups like moderators will become ordinary members and you’ll need to reassign their role
• Passwords won’t work. All members will need to reset their password (by having them click the reset password link in bbPress to have a randomly-generated password sent to their e-mail accounts)
• Certain features like attachments may not transfer over (bbPress is no where near as feature-rich as vBulletin 4 and therefore won’t be able to retain everything)

If you’re fine with the above and mainly want to transfer your posts and members, then keep on reading!

Converting vBulletin 4 to bbPress

As mentioned above, you will first need to convert vBulletin 4 to phpBB3.

Step 1: Install phpBB 3

Install a fresh copy of phpBB 3 in the same domain as your vBulletin 4 forum. For example, if your vBulletin is located at www.yoursite.com/forums, then phpBB must be also located at www.yoursite.com.

However, you may install phpBB3 to a different mySQL database. I recommend that you select a database where you want bbPress to be installed (you will see why in step 3).

The official phpBB download page can be found here.

Step 2: Download the vBulletin 3 to phpBB 3 converter

That is correct, the vBulletin 3 (not 4!) converter as that’s the latest version out there. You can download it here.

After you have downloaded the .zip file, simply upload the 2 folders to your phpBB directory.

Do not run the convert yet as you will run into errors. The fix can be found in the modified convert_vb30.php file which can be find here (thanks for the fix excelcoder!) Be sure you rename that file before uploading it!

Proceed to run the converter. Instructions can be found at the official phpBB forum here. Basically, you will need to provide certain information such as where your current vBulletin folder is located and the database information.

Your conversion should go smoothly. The converter will probably tell you that the search index hasn’t been built yet. Don’t worry about this; when you convert to bbPress later, search will work. You may notice that viewing permissions aren’t functioning properly, for example, hidden forums are visible to all regular members. Don’t bother to tinker around in phpBB’s admin control panel to fix the permissions. When you convert from phpBB 3 to bbPress, you’ll just run into the same problem.

As long as all your posts are present and displaying properly, and all the members are transferred, proceed to the next step.

Step 3: Download the phpBB3 to bbPress converter

Instructions on running this converter and the download link can be found in the bbPress support forum here (thanks wmnasef!) I’ll summarize the steps here:

1. Download and install bbPress. bbPress can be installed anywhere including a different domain. Use the database I mentioned in step 1! (Reason: the converter requires the phpBB forum to be installed in the same database as bbPress in order to run.)
2. Download the converter
3. Upload phpbb3tobbpress.php into your phpBB3 directory
4. Upload _phpbb3_pass.php into the bb-plugins directory
5. Run the phpbb3tobbpress.php, for example, http://www.yourforum.com/phpbb3/phpbb3tobbpress.php

Everything should convert smoothly. At this point, you’re probably looking at the admin panel and banging your head against your desk thinking – where are the bloody features?! Well, since you’re already there, be sure to set the appropriate members to the moderator role, etc.

WordPress Integration

WordPress integration allows both your bbPress forum and WordPress blog to share the same user database table. If you’re using the default prefixes, then the bbPress user table is named bb_users, and wp_users for WordPress.

If you followed my Converting vBulletin 4 to bbPress guide above, then all your users are currently residing in bb_users.

In the following, I will go through the steps for integrating bbPress with WordPress, regardless of whether you choose bb_users or wp_users as your main user table.

Step 1: Login to your bbPress

Once logged in, click on the Admin link. Click on the WordPress Integration tool (Settings > WordPress Integration).

Step 2: Set User Role Map

For WordPress administrators, the bbPress role would be bbPress Key Master. Everybody else should be set to bbPress Member. Click Save Changes and return to the same page.

Step 3: User Integration > Cookies (part 1 – the form)

Farther down the page, you should see an area named Cookies. Cookies allow users to login at your WordPress blog without having to login a second time at your bbPress forums, and vice versa.

I’ll divide cookie setup into 3 separate steps to make things easier.

The first part with the form contains instructions that are relatively straightforward and involve minor copy-and-pasting.

Step 4: User Integration > Cookies (part 2 – the plugin)

Near the bottom, it will ask you to install a bbPress plugin for WordPress. The easiest way to do so is in the admin area of your WordPress and clicking Plugins > Add New. Simply search for bbPress Integration and install it. What this plugin does is give you a simple piece of code to add to the config file for WordPress (wp-config.php). Save the file, but don’t close it yet!

Step 5: User Integration > Cookies (part 3 – the config files)

This is the final step for setting up cookies. It involves additional edits that you need to apply to wp-config.php and bbPress’ config file (bb-config.php).

First, access these randomly-generated constants. Find the related code in wp-config.php and paste the constants into it. Do the same for bb-config.php.

Step 6: User Integration > User Database

Step 2 is critical before you can perform this next step so make sure user roles have been mapped.

Note: the following assumes that you are using the default prefixes: bb_ for bbPress and wp_ for WordPress. If not, substitute the following instructions with your own prefixes.

The table prefix you select may depend on 4 different scenarios:

1. Both your WordPress and bbPress have no registered members except for yourself. Either bb_ or wp_ will work depending on your personal preferences.
   
2. WordPress contains all your users. Use wp_.
3. bbPress contains all your users. Use bb_.
4. bbPress contains all your users but you want to use the user table in WordPress. Use wp_ and do step 7.
   

If you chose scenario 4, hit Save Changes, and move on to step 7.

Otherwise, you’re basically done! Just fill out the advanced database settings if your WordPress is installed on a different database than bbPress. Hit Save Changes and skip the rest of this guide.

Step 7: Renaming users and usermeta tables

This step is required for scenario 4 (as outlined in step 6) because if you set the table prefix to wp_ and do nothing else, the threads and posts in bbPress will no longer be linked to the original user from the bbPress user table. That’s because at this point, bbPress is accessing all posts/threads in the bbPress database while attempting to access the users from the WordPress database.

For this step, you’ll need access to phpMyAdmin.

If bbPress and WordPress are installed on the same database, you can execute a simple SQL query such as:

RENAME TABLE wp_usermeta TO wp_usermeta_ignore;

RENAME TABLE wp_users TO wp_users_ignore;

RENAME TABLE bb_usermeta TO wp_usermeta;

RENAME TABLE bb_users TO wp_users;

This basically swaps the user tables (and their related usermeta data) by renaming the tables. The bbPress user and usermeta tables basically replace the WordPress counterparts (the code simply renames the original tables instead of deleting them).

After upgrading to WordPress 2.9.1, I encountered a problem when using the media file uploader. Any attempts to upload an image would return an HTTP error:

WordPress Media File uploader

There are many solutions out there, but unfortunately none of the ones listed worked for me. I did find a very simple fix however.

HTTP error fix

The answer was right in front of me! Specifically, in the uploader popup window:

You are using the Flash uploader. Problems? Try the Browser uploader instead.

The Browser Uploader worked perfectly fine for me.

Time to make this blog more personal so I’ll talk and empty my mind here a bit for is this not where random lies?!

I finally updated WordPress from 2.3 (yeah, it’s been a while) to 2.8.4. Never thought WordPress could get any better than before; the dashboard is much more pleasing to the eye and it looks like there is a bunch of useful new features like the Media library. Can’t wait to play around with the GUI and get used to everything. Unfortunately, the custom WordPress theme I was using wouldn’t cooperate with the new upgrade so I’m going to use Thematic for now and perhaps customize it heavily over the next little while. We’ll see.

Hmm. It seems as though I haven’t done anything web-related in a while. Like web design. Kinda itching to crack open Photoshop and work off the rust. Maybe hit two birds with one stone by entering some contests at 99designs. A little extra cash wouldn’t hurt.

I brainstormed some interesting blog material on paper over the months and I’ll probably start posting some of them up here. Topics mainly on technology and the internet. Maybe I’ll even start up a little portfolio of my digital works here.

I’ve also returned to an idea I wrought up nearly 3 years ago which I’ve been planning (something I love to do) on and off (more off then on). It has to do with ‘web 2.0′ and folksonomies and the like. I hope posting about it here will motivate me to actually polish it off and shift it into development mode. Haha, who am I kidding?

There are many things that I have grown interested in over the years and one of them is hockey. Today, I assembled a hockey net which was 45-minutes of fun (I love building things, it goes back to when I played with my first Lego set). I probably took longer than normal as the weather started off uncomfortably sunny and then started to drizzle). Now, I can practice wrist shots and the like in the comfort of my backyard. I will need to buy some plywood or something so that I can handle the puck more smoothly (rubber and concrete don’t mix). Before, I have been using one of those smart hockey balls, the kind Vincent Lecavalier supposedly uses in the off-season, but I’d rather get used to a puck since nothing can mimic a puck better than a puck. Of course, I still need to learn the nuisance of skating – my new Bauer 22s are barely worn in – which I’ve done only a few times the past winter in a nearly outdoor rink, but I’ll worry about that later. On a hockey-related note, I can’t wait for the NHL season to start! Canadian football just isn’t enough in this long and boring off-season.

That’s all for now.

I purchased a PHP book over 6 years ago and I only got through the first 20-30 pages before putting it down and letting it gather dust. After six long years, I finally faced a problem big enough for me to actually write a piece of code:

How to display two or more different WordPress sidebars (the column on the right) depending on the page a user is currently viewing?

The Problem

WordPress currently displays a single sidebar for all your templates (sidebar.php). My problem was that I wanted to use another sidebar (let’s call it sidebar2.php) as well. More specifically, I wanted this second sidebar to be displayed only on ‘Single Post‘ (the template that displays the full blog post; the webpage you are viewing now). Then, the first sidebar would be displayed for all the other pages.

Being the newbie programmer I am, I tried using the original sidebar include code that WordPress uses to display the sidebar in your templates:

<?php get_sidebar(); ?>

And then modified it:

<?php get_sidebar2(); ?>

Unfortunately, this did not work.

The Solution

Luckily, I stumbled upon this useful page at WordPress about ‘Conditional Tags,’ specifically this section.

Basically, it tells us that ‘Single Post,’ the page you are currently viewing, is defined by WordPress as ‘is_single()’. This is the page where I wanted to display the second sidebar. This also means that for every other page that was not ‘is_single()’, I would simply use the original sidebar include code to display the first sidebar as mentioned earlier.

Thus, a simple PHP if and else conditional statement will do the trick. I replaced <?php get_sidebar(); ?> from header.php (or wherever this code is included in your template) with:

<?php
if (is_single())
include (TEMPLATEPATH . ‘/sidebar2.php’);
else
get_sidebar();
?>

Note: The above code assumes that you have created and uploaded a WordPress template called sidebar2.php

In layman’s terms, if the current page you are viewing is ‘Single Post,’ then the second sidebar will be displayed. Else, the first sidebar is displayed for all other pages. This piece of code can be adapted in many different ways including displaying more than 2 sidebars and displaying sidebars for specific templates.

I guess this is a rather simple fix, but after hours of Googling for a solution, I noticed that a lot of other WordPress users experienced this same problem. Hopefully this article helps!