[cellarius]

Well, all of this is only half the cake, really. Even if IB would add the plugin system back in, most addons on vb.org would not be updated. IB managed to drive a lot of formerly active coders away - not only by breaking the addon envoironment, but also by their business policy and poor management decisions over the past five years. The community here - compared to older days - has all but dried out, many have changed to other products. It would take a lot to gain that trust back, if that is at all possible.

[ozzy47]

I seriously doubt they will add them back. And if they did, it would probably be in a minimalist fashion, and not be no where as useful as it is in vB3 or vB4.

[Paul M]

Originally Posted by ozzy47

IIRC, they claim it is for security, so someone can't run code using the plugin system if they get a admin account.

Claimed by who ? where ?

[ozzy47]

If I remembered who where, I would have said so, or quoted, that is why I said IIRC.

[ozzy47]

Well here is one post alluding to such a claim, http://www.vbulletin.com/forum/forum...86#post3983686

And another, https://theadminzone.com/threads/vbu...-5#post-815223

[Paul M]

Hooks are not a security risk in themselves, but of course, people could misuse them, and create security issues with them.

It may well have been a factor in someones mind, but your post appears to suggest it was the main / only reason, which is not the case.

[Max Taxable]

Originally Posted by Paul M

Hooks are not a security risk in themselves, but of course, people could misuse them, and create security issues with them.

It may well have been a factor in someones mind, but your post appears to suggest it was the main / only reason, which is not the case.

Leaving us with the main reason being, to screw over the developers and distance the product from the volunteer community that once thrived, essentially deserting many dedicated and bright - and loyal - people.

[ozzy47]

No it don't, you just read it that way. So if you know it was not the reason, then why not answer the question?

Originally Posted by Brandon Sheley

What would be the benefit of not including that in vb5?

[kh99]

Well, I don't know anything about vb5 and I don't work for the company, so I can only speculate. But as others have pointed out there doesn't seem to be any advantage to intentionally screwing over developers who are adding value for free. And the security issue might have been a reason someone came up with, but it doesn't seem like something that would be the main reason. If I had to guess I'd go with the simplest and most obvious reason (to me, anyway): they just wanted to be able to develop vb5 without the constraint of keeping a plugin system working. I mean, if you started out with the idea that you were going to have hooks in the code, every time you changed or reorganized something you'd have to worry about whether the hooks still made sense, and how many mods you might be breaking.

The plugin system was a big hack anyway. I always thought what it needed was some kind of event-driven system, as in "call my function when someone writes a post", and I don't have to figure out where in the code that happens or what variables I need to use. Maybe vb5 currently works something like that, by extending classes, I don't know. But another possibility is that they just didn't think it was a good system for adding mods.