vBulletin 3.0 Modifications

[Hornstar]

Originally Posted by nighteyes

I don't really see why you have to block off access to downloads of these older modifications. Sometimes you need access to old code to properly path upgrades to newer products in forums that were badly managed or poorly maintained in the past. I would have thought closing the forums to new replies and making it clear they are read only, unsupported threads would have been enough.

But this site has a whole history of yanking code and making life difficult for some of us. So I'm not surprised.

I think this is a very valid point. It would be very easy to make it clear they are old, unsupported, arhcived modifications. Having it not possible to reply etc. makes this even more clear.

Personally I have no need to download them 3.0.x hacks. but I can only imagine that it could be beneficial keeping them downloadable to those that might need them down the track.

[Alfa1]

Will you move those modifications that work on vb 3.8 to the 3.8 forum?

[Dismounted]

We recommend that you post a new thread in the 3.8 forum - as those who search in the previous forums will not find your modification.

[Digital Jedi]

Originally Posted by hornstar1337

I think this is a very valid point. It would be very easy to make it clear they are old, unsupported, arhcived modifications. Having it not possible to reply etc. makes this even more clear.

Personally I have no need to download them 3.0.x hacks. but I can only imagine that it could be beneficial keeping them downloadable to those that might need them down the track.

At some point, it isn't worth taking up the space with modifications for a version of vB that only a handful are still using, for an even a smaller number people still using 3.0 modifications, with an even more nominal number of authors offering support for them. Sometimes it's best to do a little trimming if only a tiny few will be inconvenienced. Besides, it's in 3.0 user's best interests to have a reason to stay just a little current, as I can imagine 3.0 has all kinds of vulnerabilities at this point, much less their modifications.

[thefifthlord]

Originally Posted by Digital Jedi

At some point, it isn't worth taking up the space with modifications for a version of vB that only a handful are still using, for an even a smaller number people still using 3.0 modifications, with an even more nominal number of authors offering support for them. Sometimes it's best to do a little trimming if only a tiny few will be inconvenienced. Besides, it's in 3.0 user's best interests to have a reason to stay just a little current, as I can imagine 3.0 has all kinds of vulnerabilities at this point, much less their modifications.

Perhaps, however this seems like a way for jelsoft to force people to upgrade their vbulletin installations. If people want to use 3.0 and want to develop mods for it, why stop them? I doubt it consumes much bandwidth at all so theres really no reason to archive the forum.

[Digital Jedi]

Originally Posted by thefifthlord

Perhaps, however this seems like a way for jelsoft to force people to upgrade their vbulletin installations. If people want to use 3.0 and want to develop mods for it, why stop them? I doubt it consumes much bandwidth at all so theres really no reason to archive the forum.

Because at some point, it just doesn't make sense to keep selling parts for the Pintos, when your manufacturing Hybrids.

[SCRIPT3R]

Originally Posted by Digital Jedi

Because at some point, it just doesn't make sense to keep selling parts for the Pintos, when your manufacturing Hybrids.

So you're saying there is financial motivation behind this decision?

[Digital Jedi]

Are you asking me if there's a financial motive to running a business that sells updated software? Why not ask me if there's a financial motive for the grocery store to sell fresh vegetables?

[Paul M]

Originally Posted by thefifthlord

Perhaps, however this seems like a way for jelsoft to force people to upgrade their vbulletin installations.

Some people have very active imaginations.

In fact some people seem to seriously over estimate Jelsofts involvement in vbulletin.org. They provide the servers that we run on, the means for checking if a member is licenced, and a co-ordinator for any advice/issues we may have. Jelsoft do not make any day to day running decisions for vbulletin.org, they are made by the admins.

from a coder side of things -- which nobody seems to care about, supporting the old hacks that are used by 1% of the population is just harrassment. how much people still use a 3.0 vBulletin, and in that number, how much are using the hacks released here?!... compare to the number of coders who are still supporting their 3.0 hacks, and you will find a number close to zero... forcing these guys to continue supporting their old hacks is just slavery.

oh, btw Paul M, you are right about Jelsoft on vb.org, but i think they are mostly refering to supporting the older versions abroad the system... vbulletin.com is not supporting it anymore, so it's good to follow their support -- if you still have vb 3.0, you have to hire/call for specific support.