It's all hindsight at this point but maybe a few more third party coders would have stuck around had they understood the API documentation. I realize they're all experienced with and used to PHP hooks but it's an outdated coding method compared with API apps. The intention of vB5 was correct. The implementation left much to be desired.

A straight no, looking at your join date.. age old users should move ahead.. rather then making new accounts..

I would say not to email VB Support, nothing we can do about it. Perhaps post on the Licensed CUstomers Feedback Forum on vBulletin.com and say you want access to old mods on vb.org. No, it won't change, but I always thought losing access to the early 3.x mods (3.5, 3.6, 3.7) especially was arbitrary and unnecessary. Many still worked on 3.8.x at the time.

You can still access 3.6 & 3.7 mods, its only 3.5 or earlier that are not available.

Almost anythigng released for 3.5 was duplicated in 3.6 onwards as well, by the developers at the time.

It would appear someone has restored access to 3.6 and 3.7 mods, though they are still listed as being the "Archives." When they were first archived you could not download the mod files.

"So they all went to XenForo, where they can code like it's the year 2000. LOL."

Dont know Xenforo but back in 2000 coding was more fun than it is now on this bulk and complex systems.

Look at vb2 its so easy to use and modify.
Then look on vb4 or 5.

They have always been available, I specifically wrote the code to allow it when they were archived, and put out a slightly different message.


vB4 is easy to modify (easier than XF) and just the same as vB3 - however, vB5 is a whole different story.

People want to switch to XenForo because vBulletin won't support software written in 2001?

I sometimes can't quite comprehend the stuff I read sometimes.

Why vB2, and not vBulletin 4? vB4 is the best, in my opinion anyway.

Like others have said, its not just about the security issues in the latest PHP7. vB2 wont even install in PHP7. But thats just not the security issues, its the entire vB2 framework, its how vB2 is coded.

You would have to rewrite most, if not ALL of the vB2 PHP files, for it to even install in PHP7. Then if you get it to install in PHP7, im sure you will run into problem after problem after problem after install. PHP had so many changes over the years, its crazy.

Then after you rewrite most or ALL of vB2, at that point most of the code wouldn't even be vBulletin's code, it would be yours. lol.

If you want to go down that route, your better off Coding and Building your own Forum Software from the ground up, for PHP7.

Thats just my two sense, good luck. To be honest, vB4 would be a lot better, and a lot more stable, with a lot more features then vB2.