What do you think about Vbulletin vs Xenforo?

[JacquiiDesigns]

Originally Posted by BirdOPrey5

Actually Jacquii that list is great...

The actual bugs on that list are mostly related to foreign characters and that is because UTF-8 was never a fully supported feature of VB 4.x, there are functions that just don't work with it.

So if you are using VB 4 in a supported setup (say English) then none of those are problems for you.

Now you say these are all marked as bugs but just reading these I can see that is simply untrue- Look at the notices condition- script name- that "bug" is clearly marked as a "feature request" - http://tracker.vbulletin.com/browse/VBIV-6602 - Absolutely nothing is broken about it, someone is simply requesting we add more options to the notices manager. There are several others listed that seem to be feature requests or improvement requests whether they are listed as bugs are not I don't know (and honestly don't care- because it doesn't really matter) such as- Facebook Connect needs a User CP feature to Opt Out and Usergroup permissions to enable HTML in forums- this has been a long requested feature that was delivered as a feature in VB5. It's not a bug and not likely to come to VB4.

The bug reported by digital point about user merges is legit- http://tracker.vbulletin.com/browse/VBIV-6602 - but it only will hit really big sites with slave databases (I've never seen one in the real world) doing multiple user merges at once which is very few. A great example of a legit bug but it just doesn't affect many people.

Hidden CMS Forum Visible If URL is known - http://tracker.vbulletin.com/browse/VBIV-4785 - another "Improvement Request" - not a bug, not a problem, as designed really.

So in that entire screen shot perhaps there are one or two actual bugs but they don't really affect the vast majority of license holders and fewer still who use the software in a supported environment.

Originally Posted by Paul M

Jacquii, No one said vB4 doesnt have bugs, it does, just like every other forum software.

The general implication of calling something "bug ridden" is that it has so many bugs you will find it hard to use without issue.
Thats just not the case, the vast majority of users will never encounter a bug, and even then in many cases its just trivial (like a mis-spelt word).

Im not sure what your point is exactly, but to imply (as you seem to be trying to do) that vB4 is unstable or unusable is simply untrue.

Well - the initial purpose of my post:

I most certainly wish vBulletin (under the inept ownership of Internet Brands) would get its act together. vB has had some of its positives brought to light... That was called vB 3.8.7 --- From my and a great many other vB license holders' perspective though, vB 4 (with the exception of vB 4.2 perhaps) and now the vB 5 bomb is doing absolutely nothing to deserve similar praise.

Then Joe stated something about vB 4 code being stable for years. This seemed curious to me - so I, a bit distracted, wondered aloud how 'stable' a product can be when it has at least 3 pages of user-reported bugs in JIRA. Then the (unwinnable?) battle of semantics: stable, usable, buggy, bug-ridden, etc:

No, VB4 isn't bug ridden either. Bug Ridden products cannot be used in production environments. VB4 has been strong and stable now for years.

For me = bug ridden does not mean unusable, it simply means there are substantial amount of bugs. And from the look of it - vB 4 has quite a substantial amount of them. vB 5 Connect is just one huge roach.

I'll appreciate you guys' vB 4 bug (feature/improvement request) feedback and concede that it's safe to say vB 4 obviously is stable enough to use in production environments. That's a little difficult to do when you own a script that's much less than the perfection you'd rightfully expect it to be... But I'll do it.

In terms of what this thread is about though (vB vs. XF) --- my point was not at all to insinuate that vB 4 is unusable. These words never came out of my mouth -- and afterall - I have a vB 4 license that I'm planning on using sometime this year... My point is to show that XF is a cleaner script in terms of code bugs/errors when compared with both vB 4 and vB 5.

And don't get me wrong. I'm not 'hating' vBulletin. [s]I simply feel that I am in a position to demand better of a product that I've been a fan of since vB 3.5[/s] I simply feel that WE are in a special position and SHOULD demand better of the product that's struggling to remain #1. We're obligated to do so not only because we've purchased the script, but because we are still fans of it in some way or other. Also because - at the end of the day - these facts still remain: bugs are going unfixed, development has basically stopped as far as vB 4.x is concerned and vB 5 in its current condition seems mired in tar, with seemingly a 2+ year non-plan of a timeline to bring it to usable status.

J.

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

Originally Posted by TheLastSuperman

Well I'm sure you already knew from interacting w/ 4 after it first hit but styling 4.x is different than 3.x used to be. If you're tinkering anytime this week or weekend then check out my article here - it's older but 95% of it still holds true to the style so it can help!

https://vborg.vbsupport.ru/showthread.php?t=256370

Oh yes. I had been doing some styling for vB 3 and found the process enjoyable even.

I was completely floored to see the drastic changes made between vB 3's to vB 4's styling system. The vB 4 stylevars seem all over the place. It certainly wasn't intuitive the last time I actually seriously considered coding a vB 4 style anyway.

Thanks for the article link - I'll check it out a little later.

J.