Miserable Users

This modification is no longer available or supported.

Here is a 3.5 version of the ever popular "miserable users" hack. Basically a way to really annoy anyone you don't want visiting your forum. Based on the original idea & hack for vb2 by Zzed, and the vb3 port by KuraFire.

When classed as miserable, a member suffers ;

1. Slow response (time delay) on every page (20 to 60 seconds default).
2. A chance they will get the "server busy" message (50% by default).
3. A chance that no search facilities will be available (75% by default).
4. A chance they will get redirected to another preset page (25% & homepage by default).
5. A chance they will simply get a blank page (25% by default).
6. Post flood limit increased by a defined factor (10 times by default).
7. If they get past all this okay, then they will be served up their proper page.

Note: All the above options are set in the vBulletin Options.

To install this hack simply download the xml file to your pc and then import it into vbulletin as a product - then create your 'miserable users' usergroup and set the value of this group, and your preferred other settings, in the hacks settings area (vBulletin Oprions > Miserable Users). To make a member suffer just edit their profile to add them to the miserable users group (it will work as either the primary group or as a secondary group).



History:

v2.01 - Released as a product - all settings are in the vB options.
v2.02 - Added option for multiple usergroups to be defined as miserable.
v2.03 - Added option for IP addresses to be defined as miserable.
v2.04 - Updated multiple usergroups code.
v2.05 : Minor changes, no update necessary.

[Rick Grunwald]

I also have to say THANKS for this. It is at the very least hilarious. I don't have any issues that require it but I set up a test account and let some folks try it after a normal login to verify that everything was running ok

The usual reply is a disgusted "Oh my GOD":devious: :banana:

[Stanley Steamer]

This is the first time I ever uploaded a plugin, so I am probably doing it wrong.
This is what I am doing.
Admin control panel>plug in system>download/upload plugins>browse to the file on my PC,select it> import.
then I get this messege.

XML Error: not well-formed (invalid token) at Line 1

[YLP1]

Sorry for butting on ... but since I have upgraded to ver 3_5_4, I am having similar issues with adding plugins. I have requested help from the member support area.

Right now the only way I can add plugins is to : manually add them or upload the xml file to the includes/xml folder and import from there.

In regards to the upgrade to new version... I did a complete upgrade to my live board and clean new install on my test board and both are having problems with the import of plugins.

When I find out anything knew I will post.

[Stanley Steamer]

I upgraded to 3.5.4 last week, but like I said, this is the first time I ever tried to upload a plugin so I am not sure how to do it.
I can try uploading it to my xml file and see if that works.

[Paul M]

Originally Posted by Stanley Steamer

This is the first time I ever uploaded a plugin, so I am probably doing it wrong.
This is what I am doing.
Admin control panel>plug in system>download/upload plugins>browse to the file on my PC,select it> import.
then I get this messege.

XML Error: not well-formed (invalid token) at Line 1

It's a product, not plugin - import it via the 'manage' products area

[Stanley Steamer]

I just tried that.
Manage products>add/import product>browse and selected the files from my PC> Import.
I got the same messege.

XML Error: not well-formed (invalid token) at Line 1

Should I up load the files to my xml files on my server?

[Stanley Steamer]

I up loaded the files to my server and imported them, but I am still getting the same message.

[Paul M]

Originally Posted by Stanley Steamer

I just tried that.
Manage products>add/import product>browse and selected the files from my PC> Import.
I got the same messege.

XML Error: not well-formed (invalid token) at Line 1

I suggest you re-download and unzip the XML file because it looks like you have corrupted it somehow.

[Stanley Steamer]

Thanks, I'll give that a try.

[Stanley Steamer]

That did the trick, Thanks paul!