Closed (won't fix)
Project:
Ignore User
Version:
5.x-1.3
Component:
Miscellaneous
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
11 Mar 2009 at 13:24 UTC
Updated:
30 Aug 2011 at 22:15 UTC
Jump to comment: Most recent file
Comments
Comment #1
Gabriel R. commentedI've modified the module, to make it also ignore blocked user content. It's a quick fix, base don v 1.1.
It works for me, use it at your own risks, there's no guarantee.
PS: Don't ask for a patch, I don't roll like that.
Comment #2
jaydub commentedyou don't roll like that? Not sure what that means but patches are an essential part of implementing fixes and/or features. Can I ask why you don't like patching?
Comment #3
Gabriel R. commented1. I don't like using the CLI unless I really have to. Diff-ing with a visual tool like WinDiff or FileMerge is more useful to me.
2. This particular fix is kind of messy. I works for me, but I would recommend integrating it in a more elegant way, and making it an optional.
Comment #4
minesota commentedDoes this added code blocks pm from the user and hides that name from who's online display?
Comment #5
Gabriel R. commentedNo. It only hides content from users blocked at the Drupal level for everyone.
Comment #6
jaydub commentedAs far as use cases, I am wondering why you would want to block a user site wide using ignore user over just blocking the user from within core Drupal?
Comment #7
minesota commentedNot very sure what points we are discussing here. So pardon me if I am wrong.
"Ignore user" allows any member of a site to ... well ... 'ignore' another member.
Core drupal allows the site admin to "block" an user for example a spammer.
However, "Ignore user" is somewhat far from "blocking" an user - almost all social network have this "block this user" feature which is almost similar to one another
"ignore user" is rather dissimilar to the standard "block this user" feature available in social nets. It also probably does not block PMs from the ignored user, thus not making it a true "ignore".
Comment #8
Gabriel R. commentedRemember, Drupal keeps published the content from blocked users. What my change does is that it hides the content from users blocked at the Drupal level using the Ingore User system.
You are right, it may not make sense for many. I find it very useful and logical though.
It's your module, you decide if it'll make sense to have the extra feature or not.
Comment #9
danielb commentedI have written a module that does something similar to what is being discussed here
http://drupal.org/project/cave
I am not entirely happy with what i've done, and part of what I'd like to reconsider one day is whether to integrate with this module.
Comment #10
jaydub commentedOut of scope