VbAdvanced is flexible, robust & an outstanding product.

The only one worthy of being a CMPS ;)

Credit where its due to those guys :D

I'm sorry, but you are totally wrong in this statement. I use vBadvanced on my websites today and it is a flexible, robust, and outstanding product, but that doesn't make it a CMS. vBulletin is also a fleixble, robust, and outstanding product, but its not a CMS either. A CMS manages content... vBadvanced doesn't manage content at all. In fact, vBulletin is closer to being a CMS than vBadvanced. It at least manages posts, which are one form of content. A CMS has to be able to handle the input, management, and output of content. vBadvanced is more accurately described as a portal. It can organize blocks of information that is stored in vBulletin, or allow you to create custom blocks that have nothing to do with vBulletin. The other scripts being discussed... Drupal, Joomla, etc., are in the CMS category. Not everyone needs a CMS. You can have any of the CMS scripts behave as a portal like vBadvanced does, but you can't have vBadvanced operate like a CMS on its own. Together with GARS, and the GARS-vBadvanced connector, you can get some CMS like capabilities in that you can at least have it present other content types besides posts... but even that lacks much of the management capability and relies on some custom coding to make it work.

Found this as I am totally confused by the term 'Content Management System' which may not actually mean the same thing between different people. This wiki article smooths off some of the rough edges [LINK]

Thats a good overview, and it also links to a list of CMS systems... which gets further complicated by the fact that the list includes things like POSTNuke and wikis that aren't really comparible to the classic CMS. I think that a lot of people throw around the term "CMS" when they really don't mean CMS. The vast majority of forum owners are looking for a way to add a useful home page and some static non-forum pages. They want to be able to show news on the home page, being fed by a forum. This isn't really even the correct definition of a portal, but it probably fits that better than CMS. If you don't intend to add other types of content outside of forum threads, then you don't need a CMS. With vBulletin adding blogs, they start to blur the lines.

vBDrupal all the way.

http://audiosubculture.com <-- I just made this with vB Drupal. I can also add galleries, blogs, audio for users, the list goes on and on.


vB Drupal stays up on security updates and is already working on getting Drupal 6 to work.

Well thanks for the essay but that was a simple mistake "CMS" instead of "CMPS". Furthermore I didnt think it warranted such a response as that is off topic and irrelevant.

I may be wrong but this topic is named Vbadvanced VS other portal systems. It wasnt named Vbadvanced vs Vbulletin CMS? LOL

one word of advice

don't jump out of planes they are made for flying in

:D

--------------- Added [DATE]1197041154[/DATE] at [TIME]1197041154[/TIME] ---------------

you better sort the database out though ;)

Is that a word or a sentence? ;) LOL

Look I wasnt after a confrontation, I was stating a point but appreciated mccollin pointing out my typing error :)

Glad you think my reply was funny and off topic. :confused:

The title of the topic is actually "vbDrupal vs. vbAdvanced vs. vbPortal vs. Joomla ", not "vbAdvanced VS other portal systems". Since two of those products are in the CMS category (and the first one in particular), your use of the acronym CMS was taken for what it was. The six replies prior to yours were specifically talking about vbDrupal which is a CMS. Replacing "CMS" in your reply with "CMPS" doesn't even make any since because CMPS is a product name, not a category of software. Of course vBadvanced is the "Only one worthy of being a CMPS.", because its product name is CMPS. So I think its fair for me to have assumed originally that you intended CMS for its real definition. Your original statement was that vBadvanced was the "only" one in the list of four "worthy" of being called a CMS. In fact, Joomla and vbDrupal are the only ones in the list worthy of being called a CMS. The others are not. So that was the motivation for my reply, and explanation.

It amazes me that people come to forums to supposedly discuss things and learn, and when someone corrects a statement, they get accused of being "off topic" and laughed at. Based on the following replies to mine, there is confusion on the term CMS and so there was value in my reply. This is how people learn... by sharing their views on something. It would have been nice if you just replied back that you meant "CMPS", not "CMS", rather than attacking my post.

Now, if its OK, I'd like to add something to the vbDrupal discussion that was going before.

I've been testing vbDrupal for a few days now. Its interesting that the Drupal template files have been moved into the vBulletin template system. I'm not quite sure how they are doing it, but it seems to work pretty well. You can readily swap between this "defaultangy" template which uses the vBulletin template system, and the normal Drupal templates that have nothing to do with vBulletin. This gives a lot of flexibility. I would like to understand better how this works exactly because it may introduce some limitations. I know one thing is that I've struggled with my forum templates for some time with incompatibilities between Firefox and IE, and now I'm right back into that with defaultangy. I was hoping to have a clean fresh start. Does anyone know if its possible to pull the defaultangy template information out of defaultangy and put it in a separate Drupal skin, once its generated? Then I could severe the connection in the templates, but have them starting in the same place. My problem now is some of the classes that are used in this I can't easily change because the change may not work right in all the places the class is used in vBulletin. Not sure if that makes sense or not. Anyone tried to do that?

Interesting discussion to say the least.

I don't care that much about CMS vs Portal, but something all seem to lack is a "bypass flow valve" in case of huge traffic.

I run a webbsite with 225,000 members and they will flow on occasion to the site by the 1000s, bottlenecking and bringing the site to a crawl.

I'd need a portal/cms front end, that shuts down and redirects to the forums main page when SERVER loads defined are exceeded, then resumes itself without redirection once things calm down again.

Do any of these products do this?