Downloading vbulletin 3 stuff all at once?

[Michael_]

Originally Posted by Dr.CustUmz

you want it so bad be like the others who wanted it, and create a localhost backup of the org.

Yeah if nobody helps me this is what i have to do.

I learned my lesson when 3.5 got archived, since I have made sure to keep a vb3 section backed up.I have my backup

But why dont you share it with me?
So i would not have to unnecessarily go through the same pain as you did.

[Dr.CustUmz]

You have been a member here for over 10 years, in that time you have not made a single contribution to this community, I feel no desire to help those who serve their own greedy need. messaging me...

Did you got my message?

If you dont want to share your vbulletin 3.x stuff for free maybe you would do for it money?

If so for how much would you share your vbulletin 3.x collection with me?

Will not alter my decision. What I and many other members have done via their own methods have made local backups of things we deem a must save.

I will give you some tips for your journey, and then I'm done discussing this any further.

1. DONT BEG DEV'S AND LEGACY MEMBERS TO HAND YOU THINGS (you may just end yourself with a virus )
2. Create a local server with a fresh install and start creating new threads.
3. Google chrome has a handy (yet far from perfect) addon called copycat that will copy text from posts in bbcode format.
4. Theres no need to backup things that do the same thing (find the one YOU like best along with replies that are actually useful)
5. Have fun creating a local hosted board with THOUSANDS of posts / threads :up:

@Dave can we close this shit? lol

[In Omnibus]

I kept my mouth shut on this because I haven't run vBulletin 3.x in over a decade but there are reasons for that, like half of the 3.x mods having security flaws that make them unusable on public servers. These mods were coded for PHP versions that have been deprecated for a decade. They were coded using deprecated transitional HTML and XML. They don't meet minimum security standards and most of the developers have long since moved on so they can't even be contacted for permission to modify their work. I'm actually surprised how many are still available for download.

[Michael_]

Well many thanks to everyone on here. Big help.

And special thanks to @Dr.CustUmz: Screw you, man!

[Dr.CustUmz]

Originally Posted by In Omnibus

I kept my mouth shut on this because I haven't run vBulletin 3.x in over a decade but there are reasons for that, like half of the 3.x mods having security flaws that make them unusable on public servers. These mods were coded for PHP versions that have been deprecated for a decade. They were coded using deprecated transitional HTML and XML. They don't meet minimum security standards and most of the developers have long since moved on so they can't even be contacted for permission to modify their work. I'm actually surprised how many are still available for download.

veering off topic, lets do that since this post needs closed lol. I will always stick up for vb3 because its my baby lol. Half the mods have security flaws? unusable? deprecated?

There is NO reason vb3 can not be coded to todays standards, MOST mods that are deprecated are seriously just changing one character in the product file or PHP files. Yes the whole table every single bit in vb3 is just stupid (even back then they could have easily used divs), but with a little creativity you can get passed that.

I tend to find myself still using mods from 3.5, and even occasionally 3.0!

Yes SOME mods are completely F***ed due to php deprecations, but most of them are seriously easy as hell fixes IE removing &'s (wont go into detail on all that stuff though)

I GUARENTEE my 3x board is more "UP TO DATE" than any single vb4 / 5 vanilla board. If a dev has not been on here for years (which is almost everyone now days because everyone went to xF) It's up to other devs to continue their work. If an author has a problem with it at that point then they can do something. It's like with vB announcing EOL on vb3 (and I believe 4) it is now up to developers to keep it "Up to date" because the original developer is no longer supporting their product, for example I COULD begin to release updated versions of that product. vb3 was last updated to 3.8.11 where as my vb is more like 3.8.16. remove old shit here, add new shit there, etc.

I digress, my point is vb3 is 100% perfectly capible of staying with the standards of today, and if more people didnt give into the hype of bloat added to vb4, we wouldn't be stuck with the garbage vb5 (although it has improved some)

vB3 <3 Always

[Michael_]

Originally Posted by Dr.CustUmz

veering off topic, lets do that since this post needs closed lol. I will always stick up for vb3 because its my baby lol. Half the mods have security flaws? unusable? deprecated?

There is NO reason vb3 can not be coded to todays standards, MOST mods that are deprecated are seriously just changing one character in the product file or PHP files. Yes the whole table every single bit in vb3 is just stupid (even back then they could have easily used divs), but with a little creativity you can get passed that.

I tend to find myself still using mods from 3.5, and even occasionally 3.0!

Yes SOME mods are completely F***ed due to php deprecations, but most of them are seriously easy as hell fixes IE removing &'s (wont go into detail on all that stuff though)

I GUARENTEE my 3x board is more "UP TO DATE" than any single vb4 / 5 vanilla board. If a dev has not been on here for years (which is almost everyone now days because everyone went to xF) It's up to other devs to continue their work. If an author has a problem with it at that point then they can do something. It's like with vB announcing EOL on vb3 (and I believe 4) it is now up to developers to keep it "Up to date" because the original developer is no longer supporting their product, for example I COULD begin to release updated versions of that product. vb3 was last updated to 3.8.11 where as my vb is more like 3.8.16. remove old shit here, add new shit there, etc.

I digress, my point is vb3 is 100% perfectly capible of staying with the standards of today, and if more people didnt give into the hype of bloat added to vb4, we wouldn't be stuck with the garbage vb5 (although it has improved some)

vB3 <3 Always

Despite i dont like your attitude on sharing vbulletin mods i totally agree with this.
All that vb 3 is missing are responsive templates and php 7 compatibility out of the box.

Not a huge fan of bloated xf, ips etc. also.

[Dr.CustUmz]

https://i.imgur.com/Ha9Yzwe.png
https://i.imgur.com/OzZue4U.png

[lange]

Originally Posted by Michael_

All that vb 3 is missing are responsive templates and php 7 compatibility out of the box.

Out the box, yes ! But you can buy this responsive theme to do the job.

[Dr.CustUmz]

Originally Posted by lange

Out the box, yes ! But you can buy this responsive theme to do the job.

I've got better mobile themes coming soon look at my screenshot in the previous post (that one will not be released) just an example though.

[In Omnibus]

Originally Posted by Dr.CustUmz

veering off topic, lets do that since this post needs closed lol. I will always stick up for vb3 because its my baby lol. Half the mods have security flaws? unusable? deprecated?

There is NO reason vb3 can not be coded to todays standards, MOST mods that are deprecated are seriously just changing one character in the product file or PHP files. Yes the whole table every single bit in vb3 is just stupid (even back then they could have easily used divs), but with a little creativity you can get passed that.

I tend to find myself still using mods from 3.5, and even occasionally 3.0!

Yes SOME mods are completely F***ed due to php deprecations, but most of them are seriously easy as hell fixes IE removing &'s (wont go into detail on all that stuff though)

I GUARENTEE my 3x board is more "UP TO DATE" than any single vb4 / 5 vanilla board. If a dev has not been on here for years (which is almost everyone now days because everyone went to xF) It's up to other devs to continue their work. If an author has a problem with it at that point then they can do something. It's like with vB announcing EOL on vb3 (and I believe 4) it is now up to developers to keep it "Up to date" because the original developer is no longer supporting their product, for example I COULD begin to release updated versions of that product. vb3 was last updated to 3.8.11 where as my vb is more like 3.8.16. remove old shit here, add new shit there, etc.

I digress, my point is vb3 is 100% perfectly capible of staying with the standards of today, and if more people didnt give into the hype of bloat added to vb4, we wouldn't be stuck with the garbage vb5 (although it has improved some)

vB3 <3 Always

It's not legal to alter another developer's code unless they have given permission.

vBulletin would never go along with a public release of an altered version of software they have long since declared End Of Life.

Yes, you can make anything work if you have unlimited time and extensive knowledge of LAMP (Linux, Apache, MySQL, PHP) or their equivalents.

But this is specifically talking about the modifications as they exist for download.

If you were to pick any five 3.x modifications at random and install them the odds are high at least one of them would cause your site to stop functioning. Or open up a security vector.