For integrating two system, it is better to provide a live demonstration or screenshot, since this kind of integration is much more complicated than installing a common module.

Could you please provide a live demo? Thanks.

-Derek

Comments

nhdriver4’s picture

nhdriver4 commented

I'd also like to see the same. I don't care to be messing with my vb forums untill I know exactly what I can expect.

vm’s picture

vm commented

just a guess here, but isnt the demo found http://www.vbdrupal.org/ ?

pshadow’s picture

pshadow commented

I believe 'drupal vB' and 'vbdrupal' are 2 different modules.

JStarcher’s picture

JStarcher commented

yeah, they are two completely different projects. I thought the name thing was pretty confusing too, thus I named mine Drupaltin :P

You can see a live demo of Drupaltin at http://www.TheOverclocked.com

User: Test User
Pass: tocf

Please don't make any posts with the test account though.

Thanks!

JStarcher’s picture

JStarcher commented

Scratch that username and password.

Here is the working one:

Username: Demo
Password: demo

Have fun!

huayen’s picture

huayen commented

Drupal and VBulletin use completely different theme. For a bridge code between tow php code, I think theme compatible is as same important as user account and post sharing. Anyway, this module is really a good start toward right direction...Thanks.

Roi Danton’s picture

Roi Danton commented

It's not too hard to make your own theme for both software packages, so you can create a similar look by yourself. I do not like if e.g. Drupal uses header template of vb or if the Drupal theme needs an additional tpl file for a header and it's wrapped around vb. To leave both systems as they are means the most freedom and most compatibility (e.g. for existing themes).

The main purpose of Drupaltin is to bring Drupal and vb together at the back of the stage, so the webmaster hasn't to worry about login and profile synching. The look is always the task of the particular webmaster and not the task of Drupaltin.

dnewkerk’s picture

dnewkerk commented

It's not a perfect solution (yet), but the way I get both to use the same theme is to use PHP includes to insert a header.php and footer.php file to generate the same "static" part of the site around both systems. No dynamic portions are included (e.g. PHP Template code)... those files can be included in both Drupal and vB, and each system's respective dynamic portions of their templates are added between these includes. One shortcoming I haven't had time to think through of this approach is that if the main menu system (or other elements) are generated by Drupal, getting these into vB might be an issue.

rastarr’s picture

rastarr commented

This is a little confusing.

Isn't there now Drupal VB, Drupaltin and vbDrupal?
This is DrupalVB - is there a live site demo for that or has DrupalVB turned into Drupaltin - confusing.

JStarcher’s picture

JStarcher commented

We are in a transition stage right now. Yes, all three do co-exist at this moment, but when Drupaltin 2 is released it will replace DrupalvB. Consider DrupalvB as EOL.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Component: Miscellaneous » Documentation
Category: support » task
Status: Active » Closed (won't fix)

A demonstration site requires extra $$$, since vB is a proprietary product. If anyone wants to donate a license, I would be willing to setup a demo. Until then, this is a won't fix. Feel free to re-open this issue.