Version: 1.0.0 RC2, by Michael Morris
Developer Last Online: Jun 2009
Category: Major Additions -
Version: 3.6.x
Rating:
Released: 04-25-2007
Last Update: Never
Installs: 68
DB Changes Uses Plugins Template Edits
Additional Files
No support by the author.
Warning!!! An potential exploit has been found in this modification. The server that hosts vjoomla.com has been attacked several times. It is known to already be severely comprimised so at this time it is unclear whether the vulnerability lies in vJoomla, Joomla itself or the server. Until this is resolved to my satisfaction I am removing this modification. My apologies.
The modification WILL be re-released once this issue is resolved!
vJoomla is an offshoot of Joomla 1.0 that is designed to run in tandem with vbulletin. Unlike the main release it will not run without vbulletin - if you desire a CMS without a forum then use Joomla! instead. vJoomla is identical in most all regards to Joomla!
What vJoomla Does
Provide a single session, single login interface to Joomla and vbulletin.
Allows Joomla pages to be skinned by vbulletin's template engine.
Maps Joomla usergroups to vbulletin usergroups.
What vJoomla Does Not Do
It does not rewrite your templates for you - so you will need to go in currently and change relative links to images and pages to absolute links. This is most important in the style sheets and in the navbar template. This is something you need to do yourself rather than programmatically since no two sites are likely to be using the same style sheet and the same setup for these links.
Install Instructions
Log into your admincp
Close your forum
If your forums are at the root of your site move them elsewhere - the best location is probably /forum
Upload the files from the zip packages to their respective locations. There should be no overwrites.
Navigate to the root of your site and run the Joomla installer.
Go back to the admincp and install the Joomla product file
Now either copy the ./cpstyles, ./clientscript and ./images directory of the forum into the Joomla directory OR create symbolic links to those directories. The contents of the ./images directory of Joomla and vbulletin will need to be merged.
I hope to have my demo site up within the next week or so. But don't expect to see it until I release the first Release Candidate. The beta is an advanced preview if you will.
Rather than continuing bickering with them I'm branching off Joomla to allow templates to drive the content pages -- the vbulletin template engine in the case of vJoomla and the patTemplate engine in the case of my contract work (The only difference between these two is the line that calls the template).
Fine piece of work. I've been doing a fair amount of vB/Joomla integration and mod writing recently (for other people), and I'm even considering re-adopting Joomla for myself when vJoomla stablizes. I had exactly the same frustrations you did with the two template systems (and lack of support from BBpixel), only I didn't have the patience to do what you are doing!
My only concern is, as you say above, "I'm branching off Joomla". Are you literally working on core Joomla files, or is it plugin based? How likely are you to implement this in 1.5? Much as I like the look of what you are doing, i don't want to paint myself into a corner with an "old" version of Joomla I then can't upgrade. 1.5 seems to address a lot of the XSS vulnerabilities in Joomla, which were another large part of why I abandoned it in the first place.
This might be a simple question and more related to the Joomla admin side of things, but on my Joomla pages that are using the VB templates, my right hand column is empty [i have unpublished all the modules] but it's still showing, how can I remove it?
Fine piece of work. I've been doing a fair amount of vB/Joomla integration and mod writing recently (for other people), and I'm even considering re-adopting Joomla for myself when vJoomla stablizes. I had exactly the same frustrations you did with the two template systems (and lack of support from BBpixel), only I didn't have the patience to do what you are doing!
My only concern is, as you say above, "I'm branching off Joomla". Are you literally working on core Joomla files, or is it plugin based? How likely are you to implement this in 1.5? Much as I like the look of what you are doing, i don't want to paint myself into a corner with an "old" version of Joomla I then can't upgrade. 1.5 seems to address a lot of the XSS vulnerabilities in Joomla, which were another large part of why I abandoned it in the first place.
-- hugh
Joomla 1.5 can be bridged in quite a different manner since it is able to directly authenticate off foreign user tables and more fully implements it's native template engine. I've been watching it too - the one thing that has me worried about it is their 'php 5 emulation under php 4' -- this seems to be a severely unnecessary complication to the product.
vJoomla modifies core joomla files - it has to in order to accomplish what it does. I'm trying to keep the changes to a minimum, but they are significant. So far they have not proven significant enough to stop any module I've tried to run on it from working.
BTW, for a XSS attack to work against vJoomla it would first need to defeat vbulletin's xss precautions in addition to Joomla's native ones.
Hi Michael - am watching this thread and eagerly await the release of your version.
Qn if I may: skinning and templates... does your bridge do anything with these and make it easier to use a Joomla template on vB or a vB template on Joomla...? I appreciate matching the two is way out of scope of a Joomla/vB bridge, but are there any presentation layers considered?
Joomla for vBulletin (IMPORTANT UPDATE) - Bridge to the World's Most Popular CMS Details »»
About Developer
Visit Web Site
DB Changes 
No support by the author.
05-01-2007, 03:05 PM
