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.

[roots549]

I think we are all OK up until part two of "IF YOU WANT TO USE VB For comments:" from the readme.

From there!

Code to swap out is NOT the same in all themes.

Using the default theme, line 34 of the index.php file. Swap that out with code provided in the readme.

The code to swap out looks like this:

<?php the_tags('Tags: ', ', ', '<br />'); ?> Posted in <?php the_category(', ') ?> | <?php edit_post_link('Edit', '', ' | '); ?> <?php comments_popup_link('No Comments »', '1 Comment »', '% Comments »'); ?>

With the classic theme it is line 23 of the index.php file, and there it reads identical to the content of the readme file.

In a custom theme I have the code is also in the index.php file, reads identical to the code in the default theme, the code above.

woohoo!
eric

[welovehiphop]

love the mod, and I want to use VB for comments as well.
Do I disable the comments on WP after inserting the codes?

[welovehiphop]

Also, Im inserting these in the vbulletin or wordpress templates? I have the new blog posts showing up in the forum, but am having a time getting the comments to work. What am I doing wrong?

[slinky]

Here is an interesting question. I'd like to use this modification on Wordpress MU but my site will only have one user table. I have multiple "blogs" but only for the admin user and nobody else. I just want to have the user directory in sync and don't plan on offering blogs to any of my users. Has anyone been able to successfully install this with MU installed with only the main user table?

Actually, I have gotten it to work. The only problem I'm having is that when the plugin is enabled, you can't login to WP and keep getting redirected to the forums URL.

[Khashyar]

Excellent Plug-in, Jafo, thank you for creating and sharing it.

XMan, I am receiving the same issue as you are.

When posting a blog article for the first time into VB, the encoding is fine.

But then, when editing a WP article, all of the characters do not translate to the edited version of the blog post in VB.

When WP was UTF-8, and VB was ISO 8859-1, question marks ("), the and symbol (&), and apostrophes (') converted to "?" in VB when I edited a WP post in WP.

So, I decided to change both WP and VB encoding to UTF-8 (since I have read that this is more universally used), and now edited WP posts post all characters OK, except for the "&" symbol, which displays in the edited VB post as "&amp;"

Again, I really appreciate the Plug-in, and this is going to be very useful for both my WP and VB installations.

I haven't activated the User Bridge or WP comment bridge yet, but I will try to activate and test this within a few days.

For now, I love the fact that my WP blogs post in VB, and that when I edit a WP blog post, the edits appear in the same VB post as well, without impacting VB replies to that bridged WP article.

Khashyar

Originally Posted by XManuX

Unexpected charset conversion pbr between Wordpress and vBulletin.
(I use Wordpress 2.7 but had also the pbr with 2.6.)

vBulletin (running for years) is using ISO 8859-1 and i had trouble with charset when publishing Wordpress post to vbulletin. Wordpress was configured for UTF-8 and i had to convert WP tables from UTF-8 to ISO and to set the charest to use into both wp-config.php and WP settings\reading\Charset.

Now everything is *almost* running fine :
- Creating a new post in Wordpress
- Publishing it in Wordpress
- Checking the posted version on vBulletin -> Characters with accents are OK "????..."

But something unexpected happens when editing Wordpress posts :
- Editing a previously published post
- doing some changes to the post (including Title and Post content itself) & publishing it again
- Post's characters are OK into WP, Post's title is OK in vB but characters with accents are not showing anymore into post's content in vB.

E.g. :
- Creating a WP post with title="testing (???)" and content="testing (???)" -> Ok in vBulletin.
- Opening this post into WP and modifying it : title="testing (???) - edit" and content="testing (???) - edit" -> title will display correctly into vB but post's content will display "testing (?) - edit"

Copy/paste of this text in a new post and publishing it works. editing a post doesn't.

Any ideas ?

[Candrews9]

I have installed Wordpress and vBulletin in two different MySQL databases. WordPress is ver 5.0, and vBulletin is sql ver 4.1.

To make this work, do I have to combine the two databases? Any tips on how to go about doing that? Which database should be the combined one?

Thank you!

[Khashyar]

Hi Cadre,

I have wordpress and VB in two seperate MYSQL databases (I believe that is standard)...

As long as the databases are in the same domain, then you should be fine.

It's a pretty easy install.

Khashyar

Originally Posted by Candrews9

I have installed Wordpress and vBulletin in two different MySQL databases. WordPress is ver 5.0, and vBulletin is sql ver 4.1.

To make this work, do I have to combine the two databases? Any tips on how to go about doing that? Which database should be the combined one?

Thank you!

[Khashyar]

Hi Everyone,

Again, I appreciate the effort that went into this plugin, and that Jafo is sharing it with all of us.

Everything seemed to be working fine with VB Bridge installed, and WP posts are posting correctly into the VB forum I chose.

However, today, I just noticed what I think is a bug: I also have "My Category order" plugin installed in WordPress (so that I can change the order of my categories in WP), but when I tried to change the order of categories again (after VB Bridge was installed), I received this error in Wordpress:

Table 'dalailamaforum.wp_terms' doesn't exist

The "My Category Order" Plugin should be accessing the DB table "wordpress.wp_terms," and so it looks like the WP/VB Bridge changed the database name reference in Wordpress to the VB database name without changing the database name to "wordpress."

I "Deactivated" the WP/VB bridge plugin to see if it was the casue of the error, and the error went away when I did.

My temporary work-around is when I want to change the order of categories, I deactive the WP/VB Bridge plugin, change the category order through "My Category Order" plug-in, and then reactivate the WP/VB Bridge again.

So, the two errors that I have found so far are:

1) WP/VB Bridge changes the reference to the database name in Wordpress (to the VB database name) without changing it back to the Wordpress database name after the WP/VB Bridge plugin is finished with its process.

2) When a post is edited in Wordpress, some characters do not import correctly into the corresponding VB post.

I do appreciate this plugin, and thank anyone who can help find fixes to these two bugs.

Khashyar

[AzzX]

Originally Posted by Khashyar

Hi Everyone,

Again, I appreciate the effort that went into this plugin, and that Jafo is sharing it with all of us.

Everything seemed to be working fine with VB Bridge installed, and WP posts are posting correctly into the VB forum I chose.

However, today, I just noticed what I think is a bug: I also have "My Category order" plugin installed in WordPress (so that I can change the order of my categories in WP), but when I tried to change the order of categories again (after VB Bridge was installed), I received this error in Wordpress:

The "My Category Order" Plugin should be accessing the DB table "wordpress.wp_terms," and so it looks like the WP/VB Bridge changed the database name reference in Wordpress to the VB database name without changing the database name to "wordpress."

Using the exact same wordpress plugin here www.ozsource.org but not experiencing that issue. A strange one.

[Khashyar]

That is odd, Azz.

I haven't modified any code in either software.

I wonder if this particular error is a result of the WP theme that I chose (I believe that each theme has its own corresponding .php files.

Are you experiencing the same edit issue that Xman and I are where some characters don't migrate correctly to VB?

Khashyar

QUOTE=AzzX;1698889]Using the exact same wordpress plugin here www.ozsource.org but not experiencing that issue. A strange one.[/QUOTE]