Search the Community

vBulletin Suite vs. vBulletin - vBulletin Community Forum In answer to some of the questions about this... Why will these components only be available as part of the Suite? There are two reasons for this change. The first is that with so many separate components, keeping them synchronized was unnecessarily inefficient from a coding standpoint. There's just too much engineering overhead to maintain them all on separate development tracks. And since we want to be able to develop quickly and get releases out to you more frequently, we made the decision to keep all components in sync as part of a single code base. The second reason is that it provides much greater opportunities for tighter integration between the products, such as the ability to convert blog posts (or forum posts) to articles, to have forum discussions attached to CMS content, etc. The whole idea is to make vBulletin better, faster, and these changes will help us develop new features more quickly. They will also help as we dive into the deeper round of rearchitecture with 4.1 and 4.2. Does that mean I'll be running lots of extra code? No. vBulletin runs only the code it needs for any given page load, so if you're not using a component, its code won't run and it won't impact the performance of the application. Can I turn off components I don't want to use? Yep, just turn them off from the Admin CP, and they'll be disabled. Once again vb is pissing me off. We spent the extra one time fee of $50 for the blog addon. But since they are changing their packages and price structures around, they are going to dick people over. They still have not announced their price structures or upgrade fees, but now we definitely know that upgrading to vb4 suite will cost us money. They will no longer sell their add-on products individually anymore, which means that we'll have to upgrade to the vBulletin suite to continue getting updates for the blog add-on we already have. This is retarded. I wouldn't mind getting the vbulletin cms, I was planning on it actually. But unless it was worth another $50 (or whatever the price they're changing it to now) I wouldn't buy it. But, now we'll have to buy the suite upgrade which includes the CMS, Blog and Project Tools just to continue getting updates for the blog! WTF!? We have absolutely no need for the Project Tools add-on. If we were still a hosting company we could have used it for a support desk, but we no longer have a need for anything like that now. So thanks alot vb. I hope to god the cost to upgrade to the suite is low because if the price is to high, I'll be willing to spend the little extra cash to switch over the IPB just to spite your fucking money hungry, non-supportive, no major scheduled updates company. And their CMS better be something fucking amazing and have a gallery built into it, because if its just a page maker or a rip-off of vb advanced (free) like the blog is a slightly better rip-off of wordpress (free), then I am going to be even more seriously pissed off.