Integration with vBulletin - Complete Wordpress/Vbulletin Bridge - Share Users And Postings

DOES NOT WORK FOR Vbulletin 4.x

This version probably no longer works for Wordpress 3.x. I have started developing this product over and have released the NEW version here:

http://www.lampwrights.com/showthread.php?t=41

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.5.
• If your WP login name is the same as your VB username, this user will NOT be ported! If this was the case, you could lose your WP admin rights if there was an error, or if you deactivated the plugin.
• DOES work for Vbulletin 3.7.

Limitations:

• 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.
• If you delete a user, you must do so in both Wordpress and Vbulletin.
• If you are using XMLRPC to post with applications such as Windows Live Writer, you must change the password of the author in the WORDPRESS admin cp, after the user is ported over from VB. If you are not integrating users, then you do not have to.
• 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:
  
  

   ## 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:
  
  

   ## 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 the admin username in Vbulletin is the same as the one in Wordpress (i.e. Admin), that user will NOT be able to login to the WP dashboard.
• 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.
• When you create a test user in VB to test mapping users, the test user MUST have an email address. If a VB users email address is blank, they will not map.

UPDATES:

01/03/2007 - Fixed the unlock_tables() issue on some setups.

01/03/2007 - Fixed a bug in the script that if you used a MySQL database prefix, integration would not work. Please see this post for more information! Special thanks to axisoverdrive for giving me access to his server and letting me troubleshoot the issue!

01/05/2007 - Fixed issue where if a user saved (not published) and published later, the post would not be added to the forum.

01/05/2007 - When a post is edited, it will also be edited in the forum.

01/08/2007 - Modified slightly so when posts are edited, so are the titles (if edited).

02/07/2007 - Major modifications to new version (now 2.05). The list follows:

• Reworked the code so it uses the $vbulletin object throughout the code especially during the bridging process.
• Users are bridged whether they checked the "Remember Me" box or not.
• Removed a couple of SQL calls that became redundant.
• Addressed a bug where if a user logged out of the dashboard, it only logged them out of VB.
• Added Inline Comments capability. Comments posted to the forum (using VB for comments) will now appear at the bottom of a WP Post when viewing the post.
• Author user names can now be linked to their VB profile page if desired.
• Added option to turn off posting to forum. All this really does is remove the "Select Forum To Post To" option when writing a post. (There you go AxisOverdrive )
• The $vbulletin object should now be available in all templates and most plugins.
• Fixed a bug where deactivating any plugin would semi deactivate this plugin.
• With the reduction in SQL calls, and the removal of now unnecessary variables, speed and memory use should be improved.
• PLEASE READ THE UPGRADE INSTRUCTIONS IF UPGRADING!

07/17/2007

• Fixed problem where upload iframe was a bit mangled.
• Fixed problem where users had to refresh the dashboard once after logging in.
• Fixed problem that arose from Wordpress 2.2.1 upgrade that would not allow activation.
• Fixed logout issue where users would still be logged into Wordpress.
• When a Wordpress post is deleted, so is the thread it created.
• Added option to allow thread posted from Wordpress article to be truncated, with a linkback to the article.
• Fixed issue when user re-activates plugin, and vb_threadid column already exists. Now checks for column first.
• Removed a stray VB_Init() call.
• Forums that do not allow threads will not be selectable in the drop down menu when writing a post.
• Forums are listed out in a parent/child nested pattern.
• (Note: 367 downloads of version 2.05)

11/29/07 - 3.00

• Added TABLE_PREFIX throughout the script instead of the get_option('vbb_VBPRX') call. get_option('vbb_VBPRX') is now deprecated.
• Addressed path issues by establishing $vwd first. If for some reason there are path issues on an install, the path only needs to be manually changed once, at the beginning of the script.
• Removed call to admin_db.php which seems to no longer be necessary.
• Changed all queries to the VB database to be handled by the $vbulletin object. This should facilitate multiple database configurations.
• Added limited XMLRPC support.
• Had to include a basic copy of the functions_wysiwyg.php file (functions_wysiwyg2.php) with a minor change in the sanitize_url function (now sanitize_vburl) as it conflicts with a new WP function of the same name. Otherwise, this is identical to the VB release. This was necessary to keep formatting somewhat uniform between the two.
• Removed unnecessary globals.
• Changed the global.php call so it always loads. $vbulletin should be available throughout the code (via global in functions).
• Edited some code around wysiwyg functions of VB, and conversions to vbcode.
• Added "Turn Plugin On" option.
• Fixed an issue with the forum list on the "Write Post" page. Default forum was not being auto selected in some cases.
• Modified from BETA so that the new functions_wysiwyg2.php file is loaded using the WP ABSPATH constant. Requires the plugin to stay in the plugins directory.
• Fix an error message when a post was deleted in VB, then edited in WP.

12/10/07 - 3.01

• Fixed two <? tags that should have been <?php (pointed out by Amenadiel)

03/31/08 - 3.02

• Fixed media-upload clash for new version of Wordpress (2.5).
• Added fix that will now delete threads in VB when the post is deleted in WP and not using Ajax delete.
• Added code to insert a default email address if VB users email address is blank upon bridging.

04/20/08

• Fixed a bug in user roles for the new version 2.5.1 of Wordpress.

05/08/2008

• Fixed issue where CSS was munging scrolling text box when selecting a forum during a post
• Fixed an issue where content encoding was getting screwey between WP and VP creating a lot of unintended characters (only on PHP installs where utf8_decode() exists (most)).

05/08/2008

• Fixed issue where post count of a user did not change

Sites Using This Plug-In:

• http://www.jeffsrecipes.com
• http://www.worldwidecreations.com
• http://www.xboxcircle.com
• http://www.detailuniversity.com
• http://www.daggersden.net/
• http://www.talkbronx.com/
• http://www.czeta.it

(PM me if you want to add your site here)

Special Thanks:

axisoverdrive - Debugging Help, Kyraal - Paypal Donation, Kalina - Paypal Donation, Wildcard27 - Paypal Donation, Shri - Paypal Donation, pspcrazy - Paypal Donation, Tomahoochi - Paypal Donation.

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.

[Semjaza]

Ah, well, I can log out and have it posted. It's really no big deal. Thanks.

As for the vb_threadid issue, I just created the field myself and it all works perfectly now. Thanks for an awesome product.

[Jafo232]

Originally Posted by Semjaza

Ah, well, I can log out and have it posted. It's really no big deal. Thanks.

As for the vb_threadid issue, I just created the field myself and it all works perfectly now. Thanks for an awesome product.

No problem, now please click install.

[CaraEurope]

Hello,

I just tried to install the bridge in our newsblog http://www.jdk.de/de/news

Everything is just fine - but we have one big problem: Trackbacks do no longer work. When a trackback is sent to the URL of the blogarticle a vbulleting error message shows up (URL not on POST whitelist).

Is there any chance to find a solution for this?

Regards,
Dennis

[Jafo232]

This plugin does not support trackbacks.

[CaraEurope]

I saw that actually trackbacks are not supported. I think a Wordpress-Plugin which disables (or in this case just destroys) basic Wordpress features is a kind of useless.

Is there any module available where this bridging thing is disabled, but the threads are created in vB and the comments are shown in wordpress?

Or has anyone a hint for me how to modify the plugin to get this?

Thanks in advance!

Dennis

[tekknikal]

I noticed that a number of people experienced the issue where you cannot login to the wordpress control panel after install.

I am experiencing this same issue.

If anyone can comment on how this is fixed, it would be very helpful. I've been trying for hours and can't seem to figure it out

update #1:
i wiped everything from my server and started again.
i created a new sql db with one user, and that user act is used to access the db in both vb and wp.
my vb version is 3.6.5. my wp version is now 2.1.2.
i am running sql 4.1.20 set as mysqli in vb and php 5.2.1.
i installed a fresh copy of WP and a fresh copy of VB
i utilized vb prefixes in the vb install, and referenced it accordingly in the bridge install.
so far, everything works ok. my next step will be to use vb for the comments.
im not sure if its ok to use the same db user acct for both wp and vb to acces the db, but as i said, everything seems to work properly so far.
update #2:
i modified the classic template and everything seems to work. not sure what the problem was....

[AmbitiousLemon]

Originally Posted by daystorm

WordPress database error: [Duplicate column name 'vb_threadid']
ALTER TABLE wp_posts ADD vb_threadid INT(10)

Unable to add cookies, header already sent.
File: /home/admin/domains/bostonerotic.net/public_html/board/press/wp-includes/wp-db.php
Line: 121

Though, if I hit the back button, the plugin is activated. Though, if I try to publish, I get this error from the podcast plugin (these two may just clash, hopefully you can recommend a fix).

Warning: Attempt to assign property of non-object in /press/wp-content/plugins/podpress/podpress_admin_class.php on line 540

Warning: Cannot modify header information - headers already sent by (output started at /home/admin/domains/bostonerotic.net/public_html/board/includes/class_core.php:3036) in /press/wp-includes/pluggable.php on line 275

"Unable to load O.".

Now activating anything with the vb bridge active still returns the first error about the duplicate thread and header.

I am experiencing this same problem. The bridge conflicts with every other plugin (even hello dolly). The errors are as described in the quote above. I get the vb_threadid mysql error message, the headers error, and then then "Unable to load O." error when trying to use admin pages created by any other plugin (admin pages for themes, widgets, ecommerce, anything).

Since this plugin conflicts with every single other plugin I think its fair to say this isn't just a situation with someone else's code. This is such a nice and elegant plugin I would really like to see it play nicely with others.

I have a test forum I could give you full access to (wp-admin, vb admin, ftp, shell) if you would like to see this bug in action. PM, IM, or email me for details.

Thank you!

[EDIT]Looking into this a bit more I was able to get rid of the "Unable to load 0." by upgrading to your latest version, but there are persistent problems elsewhere. The database and headers error listed above happen every time you activate any plugin. The plugin is properly activated though, so this is just a nuisance rather than something causing a loss of unctionality.

The next error is in how certain parts of the wordpress admin interface is displayed. To me this is most noticeable in the shopping cart plugin. I can not edit any products. The area of the screen which re-draws to show the edit area instead displays the wordpress-admin dashboard. This, however, is not the only place this type of error occurs. The upload interface on the page edit pages similarly shows the wordpress-admin dashboard. The commonality between these two sections is they both have fields to upload a file.

Any chance we could get these bugs fixed?

[kirstyd]

Thanks for the plugin; I've got it working so vb users can comment on the wordpress blog :up:

However it's not quite how I wanted it to work.

This works ok:
primary group "Registered Users" -> "subscribers"

But this doesn't:
primary group "Registered Users" -> "Do Not Map"
additional users "Custom Group" -> "subscribers"

I wanted just the custom group to be able to comment rather than all registered users but can't get that to work. I'm guessing that since everyone in the "Custom Group" is also a "registered user" that the "do not map registered users" bit kicks in first?

Is there a way round this please?

thanks
kirsty

[Jafo232]

The mapping only works for PRIMARY user groups, not secondary.

[kirstyd]

Originally Posted by Jafo232

The mapping only works for PRIMARY user groups, not secondary.

Fair enough.

thanks
kirsty