How can I simply enable cave for an anon user by IP (for example, 99.99.99.88) and a registered user by either IP or his username ?

Troll only allows to import huge blacklists but how do I add IP or IPs of those who access my site to blacklist or just enable cave ?

CommentFileSizeAuthor
#7 cave.gif13.86 KBkaakuu

Comments

danielb’s picture

danielb commented
Status: Fixed » Active

I believe troll can do what you're after regarding IP addresses. There is no alternative at the moment than using troll for ip banning. I understand there are some drawbacks to the troll module method, but it was the quickest way for me to give IP support to this module. I would eventually like to make an IP list module that can service this one, like troll, but more appropriate for use with a module like this.

danielb’s picture

danielb commented
Status: Active » Fixed
kaakuu’s picture

kaakuu commented

Fixed ?

I am unable to do this simple operation -

username : Robert. [] Enable cave for him

Neither Troll + Cave helps, nor any documentation to guide.
Things are not intuitive, and I do not how many hours have to be given to get the settings right and things work for me. I am willing though to learn and spend the time once I avail the time.
May be I can after that and reopen it if needed with greater details.

Thanks.

danielb’s picture

danielb commented

Alright I'm gonna look into making this more usable.

danielb’s picture

danielb commented

Here are some instructions for using it with Troll.
- Go to the admin/user/troll
- Search for the user you want, and get their IP addresses
- Add their IP to the list at admin/user/troll/ip_blacklist/import
- go to admin/user/troll/ip_blacklist/punishment
- Tick the Cave option.

kaakuu’s picture

kaakuu commented

OK, Thanks a lot, that should be helpful.

The MAIN problem with IP is that most users in our scenario or in many countries have dynamic IPs. Those doing net from cybercafe or institutes also have changing IPs. So "cave" via IP route becomes pretty unusable apart from the fact that there are so many steps one has to do. We need to "cave" an user directly by user name.

Each user has an easy [Active] [Block] option - making this [Active] [Block] [Cave] would make the things actually work as intended apart from the fact that things will become a simple administrative task.

kaakuu’s picture

kaakuu commented
StatusFileSize
new cave.gif13.86 KB

Diagram to explain above.

danielb’s picture

danielb commented

I would like to make a module that allows you to maintain several categorised list of user Ids or user IPs, easily see the user's different IP addresses, as well as seeing which users use the same IP address, suggesting possible IP ranges and masks to identify the user with, finding the user's unique IP addresses, and blocking future unique IPs they may try to log in with. Then you could add user control features to each category of list, such as banning, or the effects of the cave module.

kaakuu’s picture

kaakuu commented

Thanks. That sounds great and I hope that will be of great use.
In addition a simple operation like [block user] [enable cave] http://drupal.org/files/issues/cave.gif
would be a welcome urgent addition to this module as IPs horribly change as user changes ISP, has dynamic IPs and may even use various proxy services.

danielb’s picture

danielb commented
Category: support » feature

I have added the ability to activate a checkbox in the user's account page to cave them. The obvious flaw is they can log out and see that their posts are removed. This is why we need the ability to match IPs with users, and perhaps even tag their browser with a cookie, so we can attempt to identify them when they log out.

Also with some testing I have found that while nodes and comments are removed from listing, the node will still show if you go to the node page, and the comment count is wrong. This was probably true of the 'troll' method as well, I just didn't notice?

kaakuu’s picture

kaakuu commented

Thanks.

The obvious flaw is they can log out and see that their posts are removed.

The same applies to IP. Many ISPs have now wide dynamic range and using another IP or proxy service the user can very well find out that their posts have been removed :)

I have added the ability to activate a checkbox in the user's account page to cave them.

YAY!! Is that now available in the stable downloadable version?

danielb’s picture

danielb commented

The same applies to IP. Many ISPs have now wide dynamic range and using another IP or proxy service the user can very well find out that their posts have been removed :)

Yeah but it's not really a simple matter of accidentally seeing it when they're logging out. They would have to suspect they are being caved to evade detection - and for many users it is impossible to do this. The dynamic range is a bit annoying - I wonder if there is a way to detect a range of IPs and make suggestion to the admin whether to assume anything on that range belongs to that user - and at least to see what other users it might affect.

Do not assume this module is stable - please test it on your site!

kaakuu’s picture

kaakuu commented
Status: Closed (fixed) » Active

No, not a matter of accidental! Users from most ISPs or cybercafes or institutes can have such variety of ISPs and IPs so that they by 'chance' or by will can easily see so. We also have users who have mobile browsing while on the go and at home regular broadband. This is getting common. Anyway thanks.

Edited - To remove a question I asked.

danielb’s picture

danielb commented
Status: Active » Closed (fixed)

It is obvious you don't actually read anything I write, so I'm not going to respond any further.

kaakuu’s picture

kaakuu commented

Sorry if anything sounded like that. I may have failed in communicating to you.
I am trying my best to use this module and make it popular as far as I can.
I have spend hours testing and trying it. And will do so more asap.

It will be nice to know what made it obvious that I do not read what you write.
Anyway, I appreciate the help I got from you and am really grateful that you created this module which actually needs to be part and parcel of Drupal.

Thanks a lot.

Status: Active » Closed (fixed)

Correcting issue status, see #2125263: Issue status not taken from last comment during D7 migration.