Skip to:
Content

bbPress.org

#3305 closed enhancement (fixed)

Improvements to marking a user as a Spammer

Reported by: johnjamesjacoby Owned by: johnjamesjacoby
Milestone: 2.6.4 Priority: high
Severity: normal Version:
Component: Component - Users Keywords:
Cc:

Description

When marking a user account as a spammer, there are a few user metas that remain unchanged

  • topic count
  • reply count
  • last post time

There may be others, but the result is that their topics & replies all get marked as spam, but their counts and activity see no change.

I'm sure there are a number of other metas that should be cleaned up when this happens.

Change History (7)

#1 @johnjamesjacoby
23 months ago

In 7027:

Users: register the _bbp_last_posted meta key.

This commit ensures that the meta key used to check if a user needs to be slowed down is registered.

See #3305. For 2.6.4, branches/2.6.

#2 @johnjamesjacoby
23 months ago

In 7028:

Users: register the _bbp_last_posted meta key.

This commit ensures that the meta key used to check if a user needs to be slowed down is registered.

See #3305. For 2.7, trunk.

#3 @johnjamesjacoby
23 months ago

In 7029:

Users: ensure topic & reply counts and last posted time are updated when user is spammed & hammed.

This commit ensures that these user meta values are correct when a user is marked (or unmarked) as a spammer. In addition, the newer topic status function is used to ensure that Closed topics are included.

See #3305. For 2.7, trunk.

#4 @johnjamesjacoby
23 months ago

In 7030:

Users: ensure topic & reply counts and last posted time are updated when user is spammed & hammed.

This commit ensures that these user meta values are correct when a user is marked (or unmarked) as a spammer. In addition, the newer topic status function is used to ensure that Closed topics are included.

See #3305. For 2.6.4, branches/2.6.

#5 @johnjamesjacoby
21 months ago

  • Milestone changed from 2.6.4 to 2.6.5

Moving open issues from 2.6.4 to 2.6.5, for 2.6.4 release today.

#6 @johnjamesjacoby
17 months ago

  • Milestone changed from 2.6.5 to 2.6.6

#7 @johnjamesjacoby
17 months ago

  • Keywords commit removed
  • Milestone changed from 2.6.6 to 2.6.4
  • Resolution set to fixed
  • Status changed from assigned to closed

This appears to have been fixed since 2.6.4.

Note: See TracTickets for help on using tickets.