How many modifications did vb4.1.4 break on your site?
 

I think it actually only broke one on my site, and it's one that's not even up here on vB.org (for vB4, anyways). That was the Live Topic, 'n I figured out how to fix it, so it's all good. The issue was that all line breaks were removed from a post while quick editing.

For a while, I wasn't able to use Custom BBCode buttons, which was a real blow. THey've got a fix posted on the bug tracker now, so that's cool.

I was getting reports of users not being able to to save/submit, cancel, or go advanced on the Quick Reply/Edit, but either that healed itself or I accidentally fixed it.

It does still look ugly, and is a pain in the arse to style, but so far as I know, there's only one thing left that I need fixed with it, and that's this issue users are having where is "breaks" their words while trying to wrap while typing. Can't figure that one out for the life of me, though.

Oh, I don't even use the Advanced WYSIWYG... I just used the Enhanced Source editor. Same with most of my members.

I suppose that forums who do use it might find some things more painful. XD

Aside from moaning, whats your point ?

Upgrades can break mods, that's a fact of life, 414 broke one of mine (not the editor either).

I fixed it, life goes on.

Well, I'd suppose this one was pretty big in breaking stuff. If the posts themselves are the heart of the forum, then the post editor is the circulatory system. Since so many modifications depend on that circulatory system, I don't begrudge anyone with clogged arteries moaning a bit. ;)


EDIT: Even if it is our fault for eating too many cheeseburgers.

I think they should have called the editor release "4.2.0" instead of "4.1.4"

Of course "4.1.4" should have been called "4.0.14" and then the new editor could have been "4.1.0" - It would make tracking which mods worked for which versions FAR more logical.

But vBulletin Solutions doesn't seem to care about mods to begin with... I hope that mindset will change with Paul on board. The mods MAKE vBulletin. Without mods they'd have less than half the sales they have now- probably a lot less. It doesn't take a market research study to see this.

Its pretty obvious that a new editor would break things and would introduce some new issues. 4.1.5 will hopefully resolve those. Mind that there were a lot of editor related issues that are now resolved. Who cares what version name they give it.

I do think that its time for vBS to start caring about mods. There are too many mods abandoned because coders no longer have a license and therefore no permissions on vb.org and no current vb installation to create updates for their mods. This hurts vb.org and therefore decreases the value of vbulletin itself.

Just a point of calcification- if someone ever had an owned vbulletin license they continue to have access to vbulletin.org. But expired licenses are a legitimate issue. For example though I am happy to make 4.x versions of my mods, I personally don't and never intend to use VB 4.x on a live forum. As a result I don't have access to the latest 4.x version.

Obviously vBulletin can't offer a free license to every "coder." Some people release 1 small mod and are considered coders. Debating who is worthy or not would be more trouble than it's worth.

But I do wish they offered a free version licensed only to develop on (must be password protected and not open to the public) that coders could download. We could register as a coder and get a development license number so it could still be tracked if it was ever found on a crack site or something.

I think that would help a lot of people without causing any lost sales. If a development version was ever found on a live site it would be treated like any other pirated version is now.

There could be a message in the footer saying "For development and testing only. Please report piracy here." with a link.

I can't speak for everyone... but in my case, this is 100% correct.

The reason I haven't gone with some other forum system is because of the ease of making modifications to vB, and the wealth of modifications already available. When vB was doing that license crap a while back with offering a deal "if you hurry up and buy it right away," you can bet I checked out other forum systems. In the end, I stuck with vB, solely because of the modification easiness and library.

It broke a mod I had released here, so I fixed it. I figured it was going to potentially break any mod that had anything to do with the editor. This is why you do upgrades on your test site first, fix the issues, then upgrade your live site.

In my case, the mod had no direct connection to the editor, so it was a surprise to find it broke it, turned out it was due to some minor changes in showthread, made as a result of the switch to CKE.

I just saw a post by Sorky who can no longer receive PMs.

It wouldnt hurt to offer a developer license or a discount to coders who have more than 100 mod downloads/installs. Most will not take up such offer, but those who do have the possibility to further develop their mods.

He changed his email or something because he is no longer associated with a Customer Account.

The update was so major it should've been called 4.2 series due to the extremely significant change.
I don't think many of us were as prepared for 4.1.4 as we should've been. That's my point.

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

Thanks for understanding but my site's arteries are more clogged than most forum owners.

I have almost 40 different forum skins.

I try to set them as child styles as much as I can to reduce the headache though.

Hey Paul are you reading that? That's why I'm complaining. So don't pay me any mind dude.

I have a lot of skins so when one thing breaks it's like times 3 cause of the amount of skins I have.

I love vbulletin. I work hard as hell on my site since I first started. I'm allowed a lil moaning.

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

Oh wow really? I thought the license was lifetime for the series you bought. :erm:

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

With that said, I'll keep you as an admin. You can experiment with the latest versions anytime you want.

My members LOVE your all topics mod. It's really relieved a problem I've had since I became a webmaster.

Oh okay. I'll figure out how to create a test site then. Thanks for the good advice.

If I understood it correctly his account was linked to his former employers license. When the employment ended, his account no longer was licensed.

- VaultWiki (now 4.1.4 ready)

- Photopost Gallery (works, but can only use plain text edit for comments, fix planned)

- vBA CMPS (works, but some loss of function (drag 'n drop), waiting for fix)

- Skins (4.1.4 versions now available)

- BBcode [TABLE] our modified version (4.1.3) support
** we are going to drop this and use the new 4.1.4 native TABLE markup

We are waiting for Photopost Gallery before going live production.

I don't know the specifics. But, if his email was still associated with a customer account, whether vB3 or vB4, then he would still be able to download here and get PMs.

Joe, the revised vB versioning system was debated for quite a bit, all for naught (may have been during your big sleep if you missed it). The current mentality that (paraphrasing) 'version numbers are meaningless' is one that a lot of people disagreed with it, with a lot of feedback from coders, but it did no good. Personally I suspect that even if some of the current IB team agrees that the versioning scheme should go back to the way it was that IB will just continue as-is for the forseeable future.

I was awake for the "why is this called 4.1.0?" questions and I know the official position is that the numbers are meaningless now... still doesn't mean I won't point out this was a bad decision that could have been fixed with calling this 4.2.0. Plus it would make the stoners happy.

At this point though throwing stones at their bad decisions won't make any difference since they aren't going to change the versioning system they currently have in place.