@BlazZe.
Guys like you shouldn't be allowed to vote.
First of all, vBulletin doesn't have any major bugs. Second, neither there are any major security vulnerabilities.
Even though that vBulletin 3 won't be developed anymore, I'm 100% sure that there won't be any major vulnerabilities.
Biggest Internet Communities are using vBulletin 3.
It really doesn't spend that much resources like IPB does.
It can be lite without having to remove bunch of unnecessary things like on IPB.
You can make anything out of it with little HTML/CSS knowledge.
Everyone is familiar with it.
But the important thing is that no matter what they try to do with XenForo, IPB and vBulletin 4 they can never achieve the same thing like they achieved with vBulletin 3, it was and it remained the best commercial forum software.
^^Didn't you die typing Hyperz ?
If you actually know anything, you'd know that from all vBulletin security vulnerabilities, only 19 of them weren't mod related. And of all those 19 security vulnerabilities, only 2 of them were for the vB 3.8.x. And guess what, neither one of them is a major security vulnerability.Ignorance is bliss. History has proven vB to be one of the most insecure but also the most wide spread BB software. That's a dangerous combination. Anyone who paid a bit of attention during history lessons in school will know that by knowing the past you can make more accurate assumptions and decisions in the future. Point being, new vulnerabilities being found is a likelihood. Anyone who has worked with vB's code base and has some basic understanding of programming and security will tell you that vB is insecure by nature because of the way the underlying code and API was written. When it comes to its plugin system it doesn't enforce secure code trough its API. The code base is old, poorly optimized and not well thought out security-wise. The only fix is a total rewrite like Invision did with IPB 3.
That's because up until recently there was nothing around that was competing vB in terms of features and usability. Times change though. Nowadays vB is miles behind IPB 3, let alone IPB 3.1 (and we won't even mention the soon to be released 3.2). It is behind in virtually all aspects - performance, security, code-base, maintainability, useability, price and the list goes on. Lots of these big communities, especially those who are well maintained, are switching to better alternatives. Lots of new sites are now avoiding Jellysoft software. Anyone claiming otherwise is either as ignorant as they come, has a biased opinion or simply likes to think they know a few things about the technical side while in reality they are as green as they come.
It consumes a lot more resources than IPB 3. This not a biased opinion but a fact. And one that can easily be proven by setting up a test environment and simulating unique traffic. Everyone is able to do the test. While the performance difference will be nearly non-existend on small sites, under large stress IPB will run circles around vB. This goes back to the outdated code base, which by the way is used in vB 4 too, but with a bit of extra bloat to further slow it down. It's the Crysis of BB software, only difference is that Crysis looks good. vB does not. Perhaps take off your vBulletin T-shirt and give it a go, hmm? It's easy to make a claim and present it as being a fact because it makes your favorite software/brand/e-penis look good/big.
Same goes for most other BB's, including IPB. The difference being that IPB's ACP is actually usable and straight forward.
Familiar with what exactly? What does IPB have that is so radically different from vB from a users perspective? Nothing. From a webmasters perspective it doesn't matter because IPB's ACP is functional, well structured and very straight forward. This is in sharp contrast to vB ACP, which DOES take getting used to for new users.
What did vB 3 achieve? Or rather, what did it achieve that IPB 3 hasn't so far? And how, according to your oh so professional opinion, is it "the best" when everything you just claimed was based on a biased opinion that doesn't hold water?
I personally think that all premade scripts aren't meant to be liked by developers, as it's obvious they wouldn't like the backend, if it's not coded the way they like it.
Read that part of my reply again, and read it carefully this time. As I said, vB is insecure by nature. As a developer, if you make a plugin, you interact with an API (and I suggest you look up that term because I don't think you quite understand what it actually means). If you write a plugin that adds tags to threads then most of that will go trough the API/library, which of course is part of vBulletin. For example, inserting new tags would require handling input data and interaction with MySQL based on that input data. Thus API calls would need to be made. It is the API that is responsible for presenting that input data to said plugin and executing the queries. That means it is the API's responsibility to ensure that by the time the data reaches the plugin (and the DB after that) it is secure and filtered. So an SQL injection should be nullified way before the plugins code is run. In human language, if the API doesn't provide a secure environment for the plugin then the API is unsafe and poorly designed/thought out. And since the API is an interface to the core code base, an unsafe API means unsafe script or program. This is why IPB doesn't have this issue. Its API is safe and well thought-out. Based on the concept of a sandbox environment .If you actually know anything, you'd know that from all vBulletin security vulnerabilities, only 19 of them weren't mod related.
Sure. I guess reading the FAQ on a vB site and suddenly being presented with the MySQL database password, username, prefix and the whole shebang isn't major. Or registering under the same name as an admin account which caused vB treat both accounts as one in ceirten cases. Which amongst other things allowed the second account to receive and read all PM's from the admin account.And of all those 19 security vulnerabilities, only 2 of them were for the vB 3.8.x. And guess what, neither one of them is a major security vulnerability
What the "admin" wants doesn't matter. A site is there for its users and community. It depends all on what they want. Unless you're just as clueless as a lot of todays self-proclaimed webmasters are and are happy with a 0-activity site that relies on worthless DLL submissions and whatnot to generate some worthless numbers on a traffic stats page.All forum scripts have more features than they actually need, it all depends on what the site admin likes and what not.
Great software according to whose standards? Yours? Your forums, if you have any, must be very competitive.New sites can avoid vBulletin all they want, it still doesn't change the fact that vBulletin is a great forum software.
Again, wrong. A script is either optimized or it isn't. IPB does a fairly good job because it is optimized within reason. Further optimization must come from the http server, php config, db, etc. Not the case with vB.Every premade script needs to be optimized in order to work on a high traffic site.
Stop basing your opinion on prehistoric IPB version or phpBB and give IPB 3.1/2 a try. For an admin both work pretty much the same, though IPB uses different concepts for developers which make developing hooks a lot easier.Not true. For a Webmaster who just started, vBulletin's style system will be way easier than the IPB's one.
I guess only geeks and IPB fans register on Facebook then. Which seems odd since I'm not registered on Facebook.IPB is kinda like social network sites, with those sexy profile features, different reputation system, and some other stuff. User who was mostly on vBulletin forums would need time to get used to the IPB's features and everything.
I feel like I'm in a parallel universe replying to you. I already addressed the numbers thing in my post you just quoted.There are more big forums running vBulletin than IPB, and all of them have a normal speed, even though some of them have over 2,000 users online at the same time.
Reach 1000's of webmasters, hosts & affiliates. Banner & sponsored-thread slots available.
Contact us