vbDrupal 4.7.3.1 (final) release

[elmuerte]

vbDrupal is a fork from the Drupal CMS which integrates Drupal with the vBulletin forum software.
This is the stable release of the next generation of the vbDrupal project. This generation is much more compatible with the stock Drupal releases than the previous generation. It has been rebuild from the ground up taking into account everything that we learned from the previous generation.
All third party modules and themes for Drupal should also work with this version of vbDrupal.

This version of vbDrupal is based on Drupal version 4.7.3.
It has been designed to work with vBulletin versions 3.5 and 3.6. A copy of the vBulletin software is required in order to use this piece of software.

More information and install and update instructions can be found in the README.html file included with this package.

You can download this release here:
http://prdownloads.sourceforge.net/vbdrupal/vbDrupal-4.7.3.1.zip?download

This download is suitable for both a clean installation and as update for any previous version.

Changes since vbDrupal 4.7.3.0

fixed broken mysqli patch in 4.7.3.0


Changes since vbDrupal 4.7.3.0 RC 4

hardend to utf8 conversion a bit more
added a safe guard for user creation with an empty username
fixed thread creation user when an other username has been entered as the node's auther.
small fix in the update code for mysqli to get properly past update 169


Note: Concerning version 4.7.3.0 and mysqli
Something went wrong while commiting a patch for mysqli in 4.7.3.0 and therefor users of mysqli (instead of mysql) were unable to correctly install 4.7.3.0. Version 4.7.3.1 fixes this problem. If you are not using mysqli you do not need to install 4.7.3.1 per se.
If you previously installed 4.7.3.0 and received the table updating errors you can either restore a backup of the database you made before installting the upgrade or run the update script again and start the system module update from 148. You will get a lot of sql errors (because a lot of these transformation have already been performed), but as far as I can see this should all work out. Ofcourse it's best to take the database restore method.

[elmuerte]

I would like to thank everybody that took the risk of installing the pre-final releases in order to catch and fix more bugs. This release wouldn't be possible in it's current state without your effort.

About bug reporting
Do not report bugs in this thread!
Please report bugs and issues in the support forums. This thread will not be monitored for bug reports.
Also follow the bug reporting guidelines posted in this announcement (http://www.vbdrupal.org/forum/announcement.php?f=5)
Please note that I no longer will be chasing bugs for older vbDrupal NG releases. Please upgrade to the stable version first.

About documentation
Most of the information can be found in the README.html file included with the package. An online version is available here (http://vbdrupal.cvs.sourceforge.net/*checkout*/vbdrupal/vbdrupal-ng/README.html). Content from this README, and more, will be created on this site in the future. If you think certain documentation is missing or incorrect you can post about it in the Suggestions (http://www.vbdrupal.org/forum/forumdisplay.php?f=12) forum.

Known bugs

[comment_vb module] SQL errors when a comment contains a attachment and comments are shown below the associated node. Workaround: disable comments to be shown below the node.

[sifuhall]

vbDrupal.org has been updated.

Update went smooth and with no issues.

[Tom-E]

it appears as if I, and possibly others have a problem with a non-moving status bar.

in another thread it is mentioned that if you run the upgrade script, and nothing goes, turn off javascript on your browser,

--hopefully this info will save you some time

[Gman]

Downloaded and I hope to install later today. I have been putting off the final configuration of a new site until the final release came out.

Thank you so much for your efforts. -Gman

[tamarian]

Congrats ElMuerte, and thank you, you've put a lot of hard work into this release.

How about releasing it on vb.org as well, under a separate thread in the 3.6 section? I know many members are still unaware of this place or sourceforge :)

[myetalk]

Thanks, looking good, will install when I upgrade to 3.6 :)

[elmuerte]

Congrats ElMuerte, and thank you, you've put a lot of hard work into this release.

How about releasing it on vb.org as well, under a separate thread in the 3.6 section? I know many members are still unaware of this place or sourceforge :)

Was going to do that. Buy first were going to wait a little while just in case.

[elmuerte]

Well, figures. I always manage to sneak in a stupid bug for a final release. That's why I always wait a while before big announcements to the world.

The 4.7.3.1 release is only for people using the MySQLi interface. If you are using the plain MySQL interface this install doesn't do much useful for you.

[Alexandros Roussos]

what about multi-site support?

Is it as good as on the legacy Drupal?

Although I could use vBDrupal in muti-site mode with 4.6.x releases, I have encountered several authentication problems when I tried it.

I used the method that elmuerte had provided on these forums since a while. And I tried all the cookies settings possible. These problems have to do with the multi-domain limits of vBulletin licence I guess.

Additionally, it took me much manual adapting of the upgrading script on every single upgrade (modifications on the xml file that is imported to vbulletin plug-ins so as to make it compatible with my prefixed tables).

Any hope that multi-site support on vBDrupal will be as good as with Drupal?

Do we still need to use that plug-in importer and if yes, does it still make database changes?

Thanks.

Alexandros
________
Cl100 (http://www.cyclechaos.com/wiki/Honda_CL100)

[Gman]

It is impossible to have multi-domain support for vbdrupal. Sessions can not maintained across the domains.

This can only be done on subdomains or subfolders, when using the multisite abilities on drupal/vbdrupal. But with the cookies in vBulletin set to '.example.com' everything works perfectly.

[Alexandros Roussos]

Thanks for your answer. This is exactly the way I managed to work around the issue.

I created a sub-domain for each site and I use it for user log-ins and I created an alternative log-in block for full domains that redirects to the corresponding sub-domain.

Now what about the upgrade with shared/prefixed database? Do we still have to re-edit manually and import that xml script in the plug-ins page, each time an upgrade is released?

It's not so hard to do but one day I'll make a mistake and I might lose data so I'm required to do that in three phases (development server --> testing --> production).

Adding the fact that vBulletin is very known by spammers which is another issue totally independant of vbdrupal. Although vBulletin has a cool feature set and is rock-solid stable, that choice costs me a lot of additionnal maintenance and I'm quite hesitant about keeping it or going classic drupal. If the site was single-domain and no prefixed table structure I would not hesitate of course.

If the prefixed multi-site database based sites get easier to upgrade then I think I'll stick with it though.
________
Vaporizers (http://twitter.com/vaporizer)

[spacefreak]

I am currently using vbDrupal 4.7.0 RC2 updated to RC3 (w/ vBulletin 3.6.0). I went through the changelog, but I couldn't determine how I might mess up my setup...

Is the proper way to update my vbDrupal to just upload the newproduct_drupal.xml into vBulletin and overwrite/merge the files? Or are there issues that could backfire as I perform the upgrade?

Any help would be appreciated.

[elmuerte]

simply follow the instructions given in the README.html (http://vbdrupal.cvs.sourceforge.net/*checkout*/vbdrupal/vbdrupal-ng/README.html#update) file.