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

THIS MOD IS NO LONGER SUPPORTED! PLEASE USE VERSION 4.0 FOR VB 3.8.x AND WP 2.7.x HERE.

Identical to this Mod here, but now for the Vbulletin 3.7 line.

If you install this PLEASE
Click Install.

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)

UPDATE:

I have become really busy these days with my work. It will be some time before I can address this plugin. Please stop PM'ing me, I just don't have time. 99% of the time, your PM can be answered by just reading through the posts in this thread.

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.

If you do install:

Please Click Install

Brought To You By: WorldWideCreations.com.

[AzzX]

Changing vb to use the UTF8 character set should fix that issue.

[SWFans.net]

Originally Posted by AzzX

Changing vb to use the UTF8 character set should fix that issue.

Already tried that one as well as the other way around (changing WP to ISO-8859-1), no joy.

[pypons]

Hi,
thanks for this fantastic plugin.

There is a solution for scheduled post ?
There is a new hook in wordpress for future post.
There is future_to_publish...

Check this link

Thanks!

[moethelawn]

I've had this bridge running for quite awhile and now Wordpress 2.7 and vB 3.8.1 with a custom homepage - it still works just fine

kudos to jafo

[pypons]

Originally Posted by moethelawn

I've had this bridge running for quite awhile and now Wordpress 2.7 and vB 3.8.1 with a custom homepage - it still works just fine

kudos to jafo

Hi moethelawn,

work fine with future scheduled post ?

[swiftor]

Thank you!

Originally Posted by Shaliza

It should be fine. My forum is installed on a subdomain, while WP is installed on the main domain. I'm having no problems with this.

[myHybridcar.com]

I installed this bridge the other day on 3.8 and everything (including vB posting) worked just fine. Then, for some reason, it stopped posting new comments into the forum (although new entries/threads worked just fine). The setting is still activated in the WP settings. What did I mess up?

[Separately, as I understand it a reply in vB should NOT post a comment under WP, is that correct?]

Thanks.

[roots549]

Has anyone figured out a way to get media files such as, images or youtube videos, that one posts in the wordpress blog to then appear in media format within the target vbull forum?

I have tried several wp plugins and so far, no luck.

thanks in advance
eric

[myHybridcar.com]

I seem to be a little confused about the abilities of the bridge. With everything enabled, this is how I understand it:

(1) Comments may only be posted using the vBulletin Reply to Thread page.
(2) Comments may NOT be posted using WordPress.
(3) Comments may NOT be posted using vBulletin Quick Reply.

Is this all correct? So, I have to disable both Quick Reply and WordPress commenting, neither of which are bridging?

The alternative option, if I understand it, is to allow WordPress to handle all commenting. If I do things this way, WordPress comments will not count towards a user's forum post count, and the comments can only be managed in WordPress Admin. Again, is this correct?

Thanks.

[rcadden]

Originally Posted by myHybridcar.com

I seem to be a little confused about the abilities of the bridge. With everything enabled, this is how I understand it:

(1) Comments may only be posted using the vBulletin Reply to Thread page.
(2) Comments may NOT be posted using WordPress.
(3) Comments may NOT be posted using vBulletin Quick Reply.

Is this all correct? So, I have to disable both Quick Reply and WordPress commenting, neither of which are bridging?

The alternative option, if I understand it, is to allow WordPress to handle all commenting. If I do things this way, WordPress comments will not count towards a user's forum post count, and the comments can only be managed in WordPress Admin. Again, is this correct?

Thanks.

1 and 2 are correct, though 3 is not - I have Quick Reply active and use it quite often on my site with no issues.

As mine is right now, when a post is published on wordpress, the corresponding forum thread is created, and comments on wordpress are pulled from the forum thread and displayed. the wordpress comments system is completely disabled/gone (at least on my site, obviously it's still 'there' in the backend).

You can safely *not* use the feature that maps vbulletin users with wordpress users - I'm not sure what the point of that is, but I turned it off with no ill effects.

Unfortunately, scheduled posting is still not working. The wordpress post goes up just fine, but the forum thread never gets posted, which means there's no way for readers to comment. I have to manually open the post and click publish, which is a huge pain.