![]() |
Quote:
Make sure you've turned it on in ACP->Settings->Prevent Hostname or Useragent from Registering. And make sure you're entered the hostnames and useragents you want banned. |
|
rtrtr.com is neither a hostname or a useragent it is a TLD name.
If that is what is showing in the hostname or useragent in who's online, then just put rtrtr in the hostname or useragent box. |
Does this support wildcards? For example if I want to block any hosting ending with .ru, will this allow me to do it? Or will it wind up blocking things like 123.rummy.au ? Pretty important to know!
|
Quote:
I suggest using the full useragent or hostname minus any TLD extension such as .ru, .com, etc. |
I see, but I may *WANT* to ban something line .ru or .cn from registering.. That could be very effective for me. :) Seems to me it's just an issue of how the wildcards are set up (if the program accepts them, etc)..
|
Quote:
What you enter is automatically wildcarded. That is why you can't enter .ru and expect .rummy not to be banned. From the settings screen for the mod.. Quote:
EDIT: As an example, let's use googlebot. It has a hostname of.. Code:
crawl-66-249-72-133.googlebot.com |
Thanks for your responses... Is there anyway for me to easily modify the code so that it only looks at the last part of the hostname? I've ok with PHP editing.
Is there a log in vbulletin somewhere that shows the useragent (and not who's online because I'm not online all the time)? Or do we have to go digging through raw http log files? Thank you!! |
Quote:
All of the code is in the plugins for the mod. However, I will not assist in changing the code for what you want to do. That is not the purpose of this mod. You will need to look through your http logs. There's no log in vB of hostnames or useragents. |
Nice mod, thank you for releasing and your continuous work on it.
I have not downloaded/tested it yet, but I've got one little question; is it possible to like edit the message that will be shown once a username/hostagent has been blocked? Basically, like you mentioned, it wouldn't be too bad if an occasional human would be prevented from registering. But if it would happen often, for example if you choose to prevent people using proxies when registering (but fine when browsing), the message could show something along the lines of "If you are trying to register and feel you are wrongfully being blocked, feel free to message support[at]host[dot]com"? In the above case, you're not immediately allowing people to register anyway and can verify a 'legitimate' user by the correspondence with him/her. At least, that's what I'm thinking :). |
All times are GMT. The time now is 10:24 AM. |
Powered by vBulletin® Version 3.8.12 by vBS
Copyright ©2000 - 2025, vBulletin Solutions Inc.
X vBulletin 3.8.12 by vBS Debug Information | |
---|---|
|
|
![]() |
|
Template Usage:
Phrase Groups Available:
|
Included Files:
Hooks Called:
|