This mod bridges your Vbulletin users over to Wordpress. You can also use Vbulletin as your comment engine instead of the spammy one built into Wordpress. You can display the comments inline in your post. You need not use the comment feature, if your only interested in sharing users.
You can map your Vbulletin Usergroups to Wordpress Usergroups and those users will then be recognized as registered Wordpress users.
For example, user "Joe" registers at your forum and logs in. Joe then clicks on your Wordpress page. Joe is instantly added to the Wordpress user base with the permissions you set for his usergroup. In otherwords, if a user comes over belonging to the "Registered User" group, you can select that he is placed in the Wordpress "Subscriber" usergroup.
If you change a users group from vbulletin, it will automatically change in Wordpress.
Requirements:
DOES NOT and WILL NEVER support Wordpress MU.
Wordpress and Vbulletin scripts must reside on the same physical server.
Wordpress and Vbulletin must use the same domain name.
Stable Wordpress Version greater than or equal to 2.7.
DOES work for Vbulletin 3.7.
Does work for vBulletin 3.8.
Limitations:
Does not work for 4.x. Why? Because VB 4.x does not work for me. If they ever make that product worth a shit, I might support it.
Please don't ask if it works for any BETA versions of Vbulletin. I do not know and will not convert this to the latest version of VB (whatever it is at the time you are reading this) until the version is released as non-beta.
Does not work with XMLRPC.
Chances are, this will not work when VB and Wordpress are located in different sub domains. I.E. forum.yoursite.com - blog.yoursite.com. Cookie issue.
I did the best I could in determining your forums file path with the script. There may be certain script setups that cannot find the file path properly, in which case you may get errors that the script cannot find or open /config.php. If this is the case, please HARDCODE your ABSOLUTE path to the forum in vbridge.php.
To do this find:
Code:
## If you are having path problems, uncomment this next variable and define the path
## NO TRAILING SLASH!
# $vwd = '/some/path/to/your/forum';
And uncomment the last line, and change the path to your forums path:
Code:
## If you are having path problems, uncomment this next variable and define the path
## NO TRAILING SLASH!
$vwd = '/some/path/to/your/forum';
Common Mistakes When Installing:
Using two different host names causes problems. If your forum URL contains www.yourdomain.com, then your wordpress blog URL MUST contain the www. part of www.yourdomain.com also. This goes for any other host name. Browsers are finnecky when it comes to cookies (as they should be).
Editors generally EDIT, not write. In Wordpress, editors don't show up in the post author drop down. This has nothing to do with this plugin, that is Wordpress code.
Make sure you DO NOT create a subdirectory for this plugin in the wp-content/plugins directory. Just upload it directly there..
If you do not map users before you turn auto-integrate on, the plugin has no idea whether your allowed into the dashboard.
If you all of a sudden can't login to the dashboard, see the above two common mistakes.
FOLLOW the directions and make a test post first. Being in a rush and not testing will most likely turn out bad for you.
UPDATES:
Changelog is included in download, here is the most recent changes:
3/09/2009
Added code to process scheduled posts
Addressed code where links and images would not show up properly in VB
Added new table called vb_forumid for scheduled posts
Reduced redundant calls when dealing with forum excerpts
If you use this plug-in, and find it useful, please support us by nominating us for Mod Of The Month (MOTM) in the top right corner of this thread, or feel free to donate.
Are there any issues with upgrading Wordpress to version 3.0 after this bridge has been installed? I don't really want to try it without some proof/steps to take to make things run smoothly.
Due to an irritating lack of reply (Which seems to be quite the norm on this website for anything other than a simple question...), I went and upgraded blindly.
It worked fine, no problems upgrading. Backup everything first though!