I am here to request the very first Hack for VB3

[romanticyao]

Mambo is a great Free Software released under the GNU/GPL License, It would be great if someone can make an Integration for VB(something like user&password, usergroup Integration), there isn't any integration yet.

Their website: http://www.mamboserver.com/
You can download from: http://www.mamboserver.com/content/Frontpage/Frontpage/Elvis_has_left_the_building%21/

This is the first hack request for vb3, thank you in advance to anyone who take your time reading it.

[The Keeper]

It's a bit of a simple answer, but the easiest way to integrate anything with vB is just to include global.php and require_once any special php files for certain functions.

[Nam]

The mambo version 4.5 stable has been release. It'd be a great, if not the best, hack for vb3, I'm really looking forward into this.

[wrongful]

I am a Mambo user and this would be wonderful.

[oly51]

Add me to that list!

[WebMasterAJ]

The only thing holding me back from going towards Mambo is the fact that there is no integration... so add me to this list as well :D

[oly51]

I run Mambo on 2 non-vbulletin sites that I run. Great CMS program. There's a lot of ongoing development and active support for it. I'd love to get my main site "Mambo'd".

[rrottman]

I run Mambo on 2 non-vbulletin sites that I run. Great CMS program. There's a lot of ongoing development and active support for it. I'd love to get my main site "Mambo'd".
If anybody could point me to a *downloadable* documentation manual, I'd definitely look into it.

[oly51]

Not sure how much is downloadable, but here is a link to the documentation project: http://mosdoc.mamboserver.com/wakka.php?wakka=Home_Page

[Troubadix]

Hi,

I´m not regulary looking around here...but I will join this request because
this is something I`m really looking for.

greets,

Troubadix

[rrottman]

Hmm... that is the only issue I have with mambo, it is miserably documented. (No offense ment...)

[oly51]

Yeah, I agree. It is a work in process.
I have not looked at the documentation too much. Just picked it up as I went

[Velocd]

What a pain it would be to integrate this CMS with vBulletin.

The CMS is meant to run on its own, not with another CMS (vBulletin), which is why it has its own classes and control panel.

Integrating it with vBulletin would get very dirty.

No offense, but this is likely why no coder has replied to this thread yet. You're best off just making your own simple CMS by require() the global.php of vBulletin on your main page.

[rrottman]

I have taken the liberty to take a deeper look into Mambo Server 4.5. I have not come across to use Mambo before I have been pointed to it by the posts in this forum.

Generally I like the clean administrator interface and the massive use of CSS in every area of the system. Installation was easy and everything worked perfectly well from minute 1.

I then tried to dive into templating and the Mambo code in order to get a feeling for what it would mean to possibly integrate parts of it (user registration, etc.) with vB. My final conclusion is: I don't try to integrate. Here are my main reasons, and again, no offense ment, I understand that Mambo is an Open Source initiative and possibly most of the developers invest their free time as opposed to being paid for it. So this is more or less my try to explain my main concerns with Mambo and obviously, it's only my personal opinion:

Key weaknesses:

1. Almost no documentation.
Mambo has a strong leck of documentation. Most of the documentation available on the projects site is either outdated, incomplete or 100% under construction. There are areas which are not covered at all. While a free templating system in PHP is a great tool, part of its value is driven by the ability to customize. Without a proper coverage of concepts and techniques, you're lost. Even if you have a strong background on CMS systems and PHP.

2. Inconsistency of the architecture.
I don't particularly understand the reasons why, but Mambo uses different concepts when it comes to dealing with templates. Chances are, I'm just spoiled by vB's consistency, but in Mambo there is a mixture between database driven content, file based templating, CSS (file) driven design and even other concepts (like PHP include techniques). For example: Most template parts are fetched by a "Mambo function" (mosLoadComponent) but the page footer has to be included by include_once("includes/footer.php"). [Yes, the includes path is not variable, it's hardcoded.]. While mainly three CSS classes allow you to control content presentation to a certain degree, other parts of the look and feel have to be hardcoded. A good example of this mixture is the pathway (breadcrumbs). The general idea is, that a simple include("pathway.php") does the trick and you can style the pathway via CSS. This is true for 99% of the pathway EXCEPT a little orange arrow in front of it. If you want to get rid of it or change it to the icons and buttons your website uses, the only way is to either rewrite the pathway.php script or exchange the image file.

I only had about an hour to look into all this, but my overall impression is, that Mambo needs some basic enhancement towards a consistent approach here. I believe that one of vB's key advantages is its concept of EVERYTHING IN THE DB.

3. Leck of free 3rd party resources.
Getting no docs on Mambo's homepage, I tried to find background information elsewhere. While there are some really nice templates out there (most of them you have to pay for) the overall quality of the tutorials I found has been weak. They all seem to have started as proud initiatives to stand in for the total leck of docs by the Mambo developers but ended up with way too much work.

All in all I have put Mambo on my internal "Watch List". I still think it's one of the Open Source projects which you should consider visiting now and again. If you plan to put a quick news portal type of website online, you can get it with Mambo within less than 10 minutes. If you want full consistent control and integration, it'll be a difficult road to go.

One last remark: Mambo has successfully been integrated with some forum systems. My remarks here do not say, that it is *not at all* possible. I am just pretty critical concerning some overall concepts of Mambo and the quality of accompanying material. Again, maybe it's the fault of the amazing team at vBulletin, that I'm way too ciritcal... your feedback is welcome.

[oly51]

rrottman - Thank you for the very detailed analysis and your explanation. I agree with your assessment.

I was hoping for a way to use Mambo for some of its features while still having a "one login" for vbulletin and PhotoPost. Guess I'll have to go in a different direction.

[rrottman]

@oly51:
Hmm... I spent a couple of additional hours on playing with Mambo. I tried to transfer one of my designs to Mambo. You might want to take a quick look: http://www.rottmann.net/mambo .

I found it pretty easy to migrate a static design (mainly html + images) into a Mambo template. The content of the above page (menu / news items) is driven by Mamboserver. Don't try any links, I published only a single page, yet.

And once you start managing content :-) it gets more and more fascinating. So it might be a fair to add a point to the "pro Mambo" side of the list: It's seems to be reasonable easy to migrate an existing page into a Mambo page. But then again, the missing documentation limits flexibility a lot. During my research I've seen quite some stunning Mambo templates, but you know, I don't want to run through Mambo's entire source code in order to understand and copy & waste my pages... .

In addition I found the tone of the Mamboserver forums annoying. Nothing compared to our neat vB community. (And I'm pretty new to it, as you can see from my post count. :-) ).

Well, I guess I'll start a new thread about PHP driven CMS and see what others use and how they think about it. I hope this is not too off-topic for the vB folks... .

Btw.: I'm not a native English speaker, am based in Germany, so please forgive my English.