Archived mods : how bad VB considers is clients ?

[imported_Fabz]

You must not care of my arguments as you don't need to access those archived mods.

Archived mods are not read only, they are empty.
What arguments except "support" do you have ?

[Lynne]

Originally Posted by mikey1991

I disgree on that point, Developers and coders shouldn't have to make their mods futureproof.

(unless you emant that was what people expected?)

I was saying what I have read people expect - perfectly working mods with immediate support at all hours.

Originally Posted by imported_Fabz

You must not care of my arguments as you don't need to access those archived mods.

What arguments except "support" do you have ?

fact 1: when i was using vB 1.0, i stored all the possible *(32) hacks available. same with vb 2.x, and each time we have a generation, i backup all the mods that i can think of a use...

what you complain about is that you have no chance to download the hacks you want to access, because when it was time you did not have the ability to do so...

but it would be the same if you go to vb.com and try to update your forum or request support for your 2.x version... Jelsoft would say they are not supporting that version anymore... if the official company is not supporting it anymore, why would they do it on the official mods site?

vb 2.x is 4 years old... one generation of softwares... no more webserver is using the prerequisite PHP/MySQL version that would make them run perfect...same for performances...

beside "support" ?... efficiency, quality of work, obsoletitude of your site -- which would require that you pay a coder just to update it professionally...

[imported_Fabz]

Originally Posted by nexialys

what you complain about is that you have no chance to download the hacks you want to access, because when it was time you did not have the ability to do so...

Yes, exactly. I thought I just needed to store URLS to get back when needed... I was wrong.

Originally Posted by nexialys

vb 2.x is 4 years old... one generation of softwares... no more webserver is using the prerequisite PHP/MySQL version that would make them run perfect...same for performances...
beside "support" ?... efficiency, quality of work, obsoletitude of your site -- which would require that you pay a coder just to update it professionally...

That is not my way of thinking about a community board... And it's not a question of paying a coder. I already pay for such things, I'm not a robber.
I wish you will have time - all your life - to follow and upgrade any software you use. When you manage an only board it's so easy. I keep an old version because I don't need other functionalities, and because everything else on the website is linked and modified, much harder than just playing with a forum.

Anyway, I don't force anyone to have the same opinion, but I do not agree with such a decision, that's what I wanted to say. I have no choice, you said it, but I feel misled.

Why don't paying to get access to those things you reject ?

[Carnage]

Its amusing; I still use a mod intended for vb 2 on my 3.8 board. Its gone through so many changes since then to get it to work on 3, 3.5, 3.6 and 3.7 It would be slightly useful to me to be able to get the original code so that i could re-modify it from scratch at some point.

I don't see any harm in leaving old mods on the site so long as people realize that they come with ZERO support.

[imported_Fabz]

Thank you.
There are many reasons to get access to "read only archived mods", code is always usefull, independently to the VB version we use.

Originally Posted by Carnage-

Its amusing; I still use a mod intended for vb 2 on my 3.8 board. Its gone through so many changes since then to get it to work on 3, 3.5, 3.6 and 3.7 It would be slightly useful to me to be able to get the original code so that i could re-modify it from scratch at some point.

I don't see any harm in leaving old mods on the site so long as people realize that they come with ZERO support.

Hah, I'm pretty sure my /me hack is from the oldschool vb2 release as well.

I don't recall a "vote" per se (or being asked) if I wanted my old mods archived, and I don't see the harm in letting people have access to them. Just stick a no-support announcement in those forums and be done with it.

.2c

Edit:

A good example is this one:

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

This does work on at least 3.7.x, because it still works on the last forum that I ran. I'd love to put it on my new venture, but alas, the file is unavailable.

[lasto]

Originally Posted by imported_Fabz

It looks like you throw away those millions of books in a library only because they are too old, and take too much place.

He does have a point there

anyway if people want the attachments from old versions of hacks then why not let them have them.Just set the forums so they cant reply to the threads but allow downloads.
And put a disclaimer on that all these hacks are old and use at your own peril.

[BlueNinjaGo]

I agree that everyone should be able to download archived mods. Perhaps a pop-up message when they do so to remind them this is out-dated and will have 0 support and even warn it can damage their board.

My two suggestions:
1) Allow users to download old attachments. A clear warning for those new users who might have stumbled upon it through a search and not realize how old it actually is. (I suggest this because sometimes users would like to simply see how something was done, and then modify it or just have that knowledge)

2) Delete the thread all together. Why tease people with "this is how to do THIS" but not let them see how it was done.

I completely understand why old mods are archived, but why save the thread if no one can see the code?

[Biker_GA]

First of all, attempting to compare old library books to obsolete code is just wrong. There's absolutely no similarity between the two, other than they're old. Talk about a flawed premise.

Speaking from an administrative standpoint, tossing old code out there for the clueless to download is nothing more than a recipe for disaster. You only have to read the support threads to see that there are those with a bare minimum of knowledge attempting to run vBulletin. To make obsolete code available to those individuals would exponentially create more complaints, broken boards, and unhappy customers.

Leaving the old threads in place via the archives serves a twofold purpose. One, it gives a historical timeline of how vBulletin has grown through the years. Second, it provides a minimal support thread for those that may be running the code on older versions.

As for wanting the code, you should have saved the instructions to your local machine. To expect vBulletin.org to be your off site backup source is unrealistic.