[m002.p]

Originally Posted by mccollin

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.

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