Last Call, the Doors Are Closing

[vbresults]

Overview

https://vborg.vbsupport.ru/attachment.php?attachmentid=141191&stc=1&d=1347472912


Compatible with vBulletin 3 AND 4.
Prevents the number of active users in selected usergroups from increasing.
Adds a "Waiting List" while active membership is at capacity.
Demotes (with the option to delete) least active users.
Deletes users awaiting email confirmation after 7 days.

[deadlySniper]

Looks interesting. I may end up using this if I keep getting dud members

[ForceHSS]

in your install text file you dont talk about the product-extended_databases-1.4 xml telling you so you can update it

[vbresults]

in your install text file you dont talk about the product-extended_databases-1.4 xml telling you so you can update it

Added; thanks for the heads up. :)

[ForceHSS]

You need to really put all the xmls into just one also if removing the xmls if you don't disable plugins from the config and remove one of them it messes the board up u can't remove the rest to fix the problem. So putting it all into one plugin would also fix this problem

[vbresults]

You need to really put all the xmls into just one also if removing the xmls if you don't disable plugins from the config and remove one of them it messes the board up u can't remove the rest to fix the problem. So putting it all into one plugin would also fix this problem

I do not. These are all separate libraries and mixing them into one big Xml would make bug fixes and overall maintenance a nightmare. It does not mess up the board if you read the warning that clearly states other add-ons will not function if you remove the library in question. Remove the core add-on first and then the libraries (literally just remove the products in the opposite order of the installation instructions). If the library has another library that depends on it, exit, remove the other library, and come back -- no config hacking required.

On the other hand, if you ignore the warning and proceed anyway, you run into very predictable issues.

[ForceHSS]

I do not. These are all separate libraries and mixing them into one big Xml would make bug fixes and overall maintenance a nightmare. It does not mess up the board if you read the warning that clearly states other add-ons will not function if you remove the library in question. Remove the core add-on first and then the libraries (literally just remove the products in the opposite order of the installation instructions). If the library has another library that depends on it, exit, remove the other library, and come back -- no config hacking required.

On the other hand, if you ignore the warning and proceed anyway, you run into very predictable issues.

I have no problem with it and did read the how to but not everyone will and not everyone will remove it in the right order so you will get members posting about this problem in time

[vbresults]

It happens, but very rarely

[vbresults]

---

[vbresults]

This add-on is now private -- please graveyard.