vBulletin Mods

Yes, I'm complaining. Gonna do something about that? Didn't think so.
It's listed as a supported mod, if it isn't it should be listed as unsupported, so we know not to expect any support for issues like this that arise.

Vbresults may have a solution. Whether it works or not, it's a lot more productive then trial and error removal of other mods that I need. When/if I find the culprit using your "method", what then? Disable a mod I need? That makes no sense. Your post is a waste of bandwidth.

Welcome to my ignore list.

Nelson

I deleted several users using the mod with your replacement mod and the error no longer comes up!!

Looks like success! Thank you sir!!

Just for curiosity sake, what did you change in the new file that made the difference?

Should bring this mod to vb5 :)

will it work with vb5 too? i tried but show error

Fatal error: Call to a member function show_errors() on a non-object

I just did an instal and didn't notice what to do with vblang_glowhostspamomatic210_ro.xml

Unless you want the mod showing up in romanian, don't do anything.

Sounds like a good option to me!

It seems to have stopped posting problems dead! GREAT!
I am still having successful registrations though. Most registrations await email confirmation. Should this mod be combined with a country block mod? The registrations are virtually all from China and Viet Nam

How are others dealing with this.

I agree. Be sure to clear all cookies, history, and cache when testing.

Admincp > settings > user banning options

Mmmmm.....

I don't see "User Banning Options". I wonder if I screwed up the GlowHost instal!

On another look in the stats, GlowHost is missing there too!

The user banning is in vbulletin. In the Admincp usually the first option is settings. Mine is a couple down because of a couple of mods. Open Settings and select "Options" then scroll down the list to "User banning options"

You may ban e-mails and ip address. Be careful not to ban one that is legitimate. You may also ban an entire block by using a "*" (without quotes) as the last number.

That warning actually had a big underlying problem. It encased a large amount of code necessary for deletion to work, and when that warning line broke, all the code under/inside it broke too, which is why it didn't work for Nelson and the others reporting the issue.

Another product did not cause this conflict, and the reason you aren't experiencing this problem is because this problem was introduced in a recent release. You probably didn't upload the latest files to the correct directory and inadvertently averted this problem.

That foreach statement and it's closing brace -- there was no reason for it to be there, probably set in by accident.

Hey folks would appreciate help on this. Thank you

Those are "bad words" not "bad partial matches."

...or am I misunderstanding your question?

Isn't there a way to automatically block a post even using partial keywords from the list? That's my concern.