Releases for Drupal vB

Be sure to backup your database(s) in front of upgrading to 2.x, and ensure to run update.php afterwards.

Changes since DRUPAL-5--2-0-RC-3:

• #131089 by sun: Fixed docs about cookiedomain.
• #131089 by sun: Fixed dual login; unable to unserialize vB's datastore options.
• #253076 by sun: Fixed database connection errors when db is not setup properly.
• Updated implementation notes in documentation.

Changes since DRUPAL-5--2-0-RC-2:

• #253652 by sun: Fixed invalid passwords in vB after exporting users.

Changes since DRUPAL-5--2-0-RC-1:

• #253030 by mistlethrush, sun: Fixed user passwords not updated during export.
• #253200 by sun: Fixed missing database table prefix after upgrading to 2.x.
• #253076 by sun: Fixed fatal error if db connection is not valid.
• #253521 by sun: Fixed SQL error if vB user profile contains additional fields.
• #253653 by sun: Added warning to user export action.
• Code clean-up for block configuration/output.
• #253652 by sun: Fixed invalid passwords in vB for new/updated/exported users.

Changes since DRUPAL-5--2-0-BETA1:

• #250439 by sun: Fixed database table prefix must not be required.
• #177074 by sun: Fixed login to vB admin cp after user export.
• Added vB variables (options) output for development/debugging.
• #130048 by sun: Fixed vB user creation failed due to mysql-specific function.
• Code clean-up, primarily regarding drupalvb_set_login_cookies().
• #249901 by sun: Changed drupalvb_create/update_user() function signatures.
• #252677 by sun: Added validation to prevent users from registering existing vB usernames.
• #142368 by sun: Fixed login error if default language is not English.
• #121148 by sun: Added lazy instantiation of existing vB users in Drupal.

Changes since DRUPAL-5--1-2:

• Complete module re-write.
  #131877 by sun: Fixed warning messages if config.php could not be found.
  #119327 by sun: Fixed wrong forum path due to missing database access.
  #130048 by sun: Fixed fatal error on mysqli by implementing new database interface.
  #119334 by sun: Fixed SQL errors due to wrong db_url.
  #114718 by sun: Fixed table not found error due to wrong table prefix.
• Fixed wrong include path for drupalvb.inc.php.
• Fixed PHP fatal error in user export action.
• Added variable to switch db connection only when necessary.

Be sure to backup your site/database in front of upgrading to this code, and ensure to run update.php afterwards. Please report any issues you find in the issue queue.

Changes since DRUPAL-5--2-0-RC-2:

• #253652 by sun: Fixed invalid passwords in vB after exporting users.

Changes since DRUPAL-5--2-0-RC-1:

• #253030 by mistlethrush, sun: Fixed user passwords not updated during export.
• #253200 by sun: Fixed missing database table prefix after upgrading to 2.x.
• #253076 by sun: Fixed fatal error if db connection is not valid.
• #253521 by sun: Fixed SQL error if vB user profile contains additional fields.
• #253653 by sun: Added warning to user export action.
• Code clean-up for block configuration/output.
• #253652 by sun: Fixed invalid passwords in vB for new/updated/exported users.

Changes since DRUPAL-5--2-0-BETA1:

• #250439 by sun: Fixed database table prefix must not be required.
• #177074 by sun: Fixed login to vB admin cp after user export.
• Added vB variables (options) output for development/debugging.
• #130048 by sun: Fixed vB user creation failed due to mysql-specific function.
• Code clean-up, primarily regarding drupalvb_set_login_cookies().
• #249901 by sun: Changed drupalvb_create/update_user() function signatures.
• #252677 by sun: Added validation to prevent users from registering existing vB usernames.
• #142368 by sun: Fixed login error if default language is not English.
• #121148 by sun: Added lazy instantiation of existing vB users in Drupal.

Changes since DRUPAL-5--1-2:

• Complete module re-write.
  #131877 by sun: Fixed warning messages if config.php could not be found.
  #119327 by sun: Fixed wrong forum path due to missing database access.
  #130048 by sun: Fixed fatal error on mysqli by implementing new database interface.
  #119334 by sun: Fixed SQL errors due to wrong db_url.
  #114718 by sun: Fixed table not found error due to wrong table prefix.
• Fixed wrong include path for drupalvb.inc.php.
• Fixed PHP fatal error in user export action.
• Added variable to switch db connection only when necessary.

DO NOT USE THIS RELEASE. Update to RC3 instead.

Be sure to backup your site/database in front of upgrading to this code, and ensure to run update.php afterwards. Please report any issues you find in the issue queue.

Changes since DRUPAL-5--2-0-BETA1:

• #250439 by sun: Fixed database table prefix must not be required.
• #177074 by sun: Fixed login to vB admin cp after user export.
• Added vB variables (options) output for development/debugging.
• #130048 by sun: Fixed vB user creation failed due to mysql-specific function.
• Code clean-up, primarily regarding drupalvb_set_login_cookies().
• #249901 by sun: Changed drupalvb_create/update_user() function signatures.
• #252677 by sun: Added validation to prevent users from registering existing vB usernames.
• #142368 by sun: Fixed login error if default language is not English.
• #121148 by sun: Added lazy instantiation of existing vB users in Drupal.

Changes since DRUPAL-5--1-2:

• Complete module re-write.
  #131877 by sun: Fixed warning messages if config.php could not be found.
  #119327 by sun: Fixed wrong forum path due to missing database access.
  #130048 by sun: Fixed fatal error on mysqli by implementing new database interface.
  #119334 by sun: Fixed SQL errors due to wrong db_url.
  #114718 by sun: Fixed table not found error due to wrong table prefix.
• Fixed wrong include path for drupalvb.inc.php.
• Fixed PHP fatal error in user export action.
• Added variable to switch db connection only when necessary.

Be sure to backup your site/database in front of upgrading to this code, and ensure to run update.php afterwards. Do not use in production environments yet.

Changes since DRUPAL-5--1-2:

• Complete module re-write.
  #131877 by sun: Fixed warning messages if config.php could not be found.
  #119327 by sun: Fixed wrong forum path due to missing database access.
  #130048 by sun: Fixed fatal error on mysqli by implementing new database interface.
  #119334 by sun: Fixed SQL errors due to wrong db_url.
  #114718 by sun: Fixed table not found error due to wrong table prefix.
• Fixed wrong include path for drupalvb.inc.php.
• Fixed PHP fatal error in user export action.
• Added variable to switch db connection only when necessary.

Development snapshot of Drupal vB v2 for Drupal 5.x.

Be sure to backup your site/database in front of upgrading to this code. Do not use development snapshots in production environments.

Note: This will be the last release of the 5.x-1.x series. A completely overhauled v2 is right on the way.

Changes since DRUPAL-5--1-1:

• #205572 by sun: Fixed PHP fatal error if config.php does not exist.
• #121148 by kkronyak: Fixed wrong redirection paths in drupalvb_action_handler().
• #194204 by sun: Removed positive status messages after login, registration, aso.
• #128322 by sun: Added docs about cookie domain.
• Updated documentation.
• Major code clean-up.
• Further code clean-up; added PHPdoc blocks.

Simple bugfix to cache vB config array.

The module has finally been updated for 5.x. This includes the database prefixing and user exporting patches submitted by valcker and some new configuration options for site owners to control the level of account integration between Drupal and vBulletin. Enjoy!

Last update of the 4.7 version before moving onto 5.0. This version finally includes valcker's old patch for database prefixing, slightly modified. Cheers!

Alrighty... added in a few new features, including an action handler by valcker that allows for exporting of users from Drupal to vBulletin and a few new settings to allow admins control over what dual login/account synchronization features they want enabled.

Bug fix for password generation, too... I had to revert a previous fix... and I just realized I might have to debug the fix for the bug. hehe We'll see.

First release with new project deployment system. Packaging up the previous stable release with two issue fixes. (Still no support for vB database prefixes, but I still have the patch somewhere! No support for 5.0 yet.)

The module should now be operational.