<a href="http://www.overclockingwiki.org" target="_blank">www.overclockingwiki.org</a> is using both J, VB and MediaWiki. We're launching a new version in a few days that will better expose the Joomla install, but you can now see it at overclockingwiki.org/joomla. It will become root quite soon.

Deckard, where did you get the jaymediawiki for Joomla?

Custom development.

Any plans to release the component? It looks like a custom wrapper to parse Wiki URLs.

I'd be willing to release it but I'm not equipped to handle the development and security. So, the code would end up being transferred to someone who would be interested in the project.

<a href="http://www.thumped.com" target="_blank">http://www.thumped.com</a>

I'm not happy with any of the joomla / vBulletin bridges so just haven't bothered with user integration. I made the vB template look (sort of) like the Joomla one then just used a tiny bit of PHP to pull the latest headlines & events listings into the vB template.

After reading through all these problems, I came up with a solution. The solution is not to integrate it at all. The reason is that many CMS and other add-on scripts are not 100% flawless and they're new bugs everyday. If you don't mind fixing all new bugs, then it's fine. For me, it's painfree and not to worry much and easier to update your cms, etc if it's not integrated.

Not integrating is a great solution for you, but have you asked your users how they feel about maintaing 2 profiles for the same site? That will severely affect your traffic, signups, and retention rates.

<a href="http://www.infernalrc.com" target="_blank">http://www.infernalrc.com</a>

My site, that uses Joomla and Vbulletin, the databases are not integrated, there is no user database for the joomla end, as i really don't see the need for one on my site. All i had to worry about its the templeting for both to look alike, i think i have done it with success.

For most sites, integrating both databases is not really needed, going with the Forum database and only using one would be the wiser choice.

It all depends on how Joomla is used in your site. If you are using Joomla's polls, comments, ratings, or any other extension, then it would make sense to integrate the user logins/database.

If you are using Joomla just as a CMS and you and/or your staff are the only users adding/editing Joomla content, then you don't need the user login integration. Which in my experience is usually a pain.

We started with full integration, and eventually turned it off and now only the skin is integrated.

Recently we switched the home page to vbAdvanced (to provide member logins, threads, etc), and some of the content pages are in Joomla.