[MODDB] Ban Hammer

[Lord Le Brand]

Nice MOD. It would be nice to have an option of moving all posts to a forum (trash can) for archiving purposes instead of deleting.

I really wanted to do this (and I might be doing this for the version running on my own site) but phpBB does not have a standard trash can yet. It is more then likely I will rewrite this mod when phpBB decides on a soft delete system.

Why don't you add a settable field so the admin can designate a forum ID as being the trash can? plus an option to enable/disable trash canning?

[SamT]

Nice MOD. It would be nice to have an option of moving all posts to a forum (trash can) for archiving purposes instead of deleting.

I really wanted to do this (and I might be doing this for the version running on my own site) but phpBB does not have a standard trash can yet. It is more then likely I will rewrite this mod when phpBB decides on a soft delete system.

Why don't you add a settable field so the admin can designate a forum ID as being the trash can? plus an option to enable/disable trash canning?

I could

While I'm at it, I can allow an admin to set the rank they receive as well as a banned member.

[igorw]

In fact, acp_users has an option of moving all a users posts. You could copy that code over. You could have a dropdown where you can select the forum to move the posts to. That's easy to implement and doesn't require any new config keys.

[SamT]

In fact, acp_users has an option of moving all a users posts. You could copy that code over. You could have a dropdown where you can select the forum to move the posts to. That's easy to implement and doesn't require any new config keys.

I was also planning to automate the rank assignment process as well, in an ACP module they will be able to configure the ban hammer, they can choose the forum in which posts are moved to and choose the rank banned users will be assigned.

2 config keys shouldn't be a big deal, I have an automatic module installer anyway (which I need to improve upon).

EDIT: added Planned Features section in first post.

[SamT]

I have some more info on 1.1, this is the final feature list of features that are being implemented:

• Ban Hammer accessible via ACP
• Ban Hammer accessible via MCP
• ACP Configuration
  • Assign Trash Can Forum, instead of deletion
  • Assign rank to give hammered members
  • Set predefined Ban reasons
• Three new Permissions
  • a_hammer_ban - If an admin can use the Ban Hammer
  • a_hammer_settings - If an admin can configure the settings
  • m_hammer_ban - if a moderator can use the Ban Hammer
• Stop Forum Spam integration - A more last minute feature, but it will have the abilty to automatically report Hammered Users.
• Error Handling - The current version really has nothing aside from "You can't ban the founder" in terms of error handling, but this new version will be more user friendly in that department.
• Ability to define a usernote - to give to everyone as the Hammering is taking place
• Archive spammer's PMs - to posts in the "trash forum"

Screen shots will be available in the next few days.

[Obsidian]

Archive spammer's PMs

You mean spammer's posts?

[SamT]

Archive spammer's PMs

You mean spammer's posts?

And PMs.

[bonelifer]

You should also add to the FEEDBACK(usernotes) section the same way activating a user does. This would be totally seperate of the definable usernotes.

[Obsidian]

bonelifer, do you mean like the "User account activated" log? As in, have a user notes entry automatically added stating "User ban hammered"?

[bonelifer]

Yes, that's what shows up in the FEEDBACK section when you activate them.

[SamT]

Sounds simple enough.

[onehundredandtwo]

I've noticed Ban Hammer will sometimes give a MySQL Error when the user hasn't been activated.

Code: Select all

UPDATE phpbb_users SET user_birthday = ' 0- 0- 0', user_rank = '52', user_avatar = '', user_avatar_type = 0, user_avatar_width = 0, user_avatar_height = 0, user_sig = '', user_from = '', user_icq = '', user_aim = '', user_yim = '', user_msnm = '', user_jabber = '', user_website = '', user_occ = '', user_interests = '', user_gender = 0 WHERE user_id = 

[bonelifer]

It's a known bug. I believe Sam-T has it fixed in the next version. And it's not just sometimes. If they aren't activated and you ban hammer them, you'll always get that error.

[Obsidian]

We've never figured out why, either.

[RMcGirr83]

I think it may be due to this within includes/mcp/mcp_ban_hammer, using quote for colorizingness

// Grab the user id
$sql = 'SELECT *
FROM ' . USERS_TABLE . '
WHERE user_type = ' . USER_NORMAL . ' AND username_clean = "' . $username . '"';

inactive users are not USER_NORMAL, they are USER_INACTIVE

Haven't tested it though.