Skip to:
Content

bbPress.org

Opened 11 years ago

Last modified 8 years ago

#960 new enhancement

Users list improvements

Reported by: wiseacre Owned by:
Milestone: Future Release (Legacy) Priority: high
Severity: major Version:
Component: General - Administration Keywords: needs-patch
Cc: kevinjohngallagher

Description

I think it is good idea to extend users list with

  • topics count
  • posts count
  • mass deleting function
  • sorting by one "field"

Attachments (1)

960-mass-delete-users.diff (9.3 KB) - added by Gautam Gupta 10 years ago.
Patch for deleting many users at a time

Download all attachments as: .zip

Change History (14)

#1 @(none)
10 years ago

  • Milestone 1.0-beta deleted

Milestone 1.0-beta deleted

#2 @sambauers
10 years ago

  • Milestone set to 1.0

#3 @sambauers
10 years ago

  • Milestone changed from 1.0 to 1.5

#4 @Gautam Gupta
10 years ago

  • Cc gautam.2011@… added
  • Version changed from 1.0-alpha-1 to 1.0.2

4) Sorting function can be taken from [WP12989]

#5 @Gautam Gupta
10 years ago

  • Cc gautam.2011@… removed
  • Keywords has-patch tested added
  • Milestone changed from 1.5 to 1.1
  • Priority changed from normal to high

Attaching patch for point 3

@Gautam Gupta
10 years ago

Patch for deleting many users at a time

#6 @chrishajer
10 years ago

I applied this patch, created 5 fake users, and logged in with 4 of those users, and made posts and created topics and added tags.

I deleted two users that had posted, and one who had not. Some observations.

  1. When deleting single users with the "delete" link, you get a javascript popup "are you sure you wanna delete that user." (I thought we changed WANNA to Want To with a previous patch, but now it's back?)

With something arguably more destructive (deleting multiple users by checking the boxes and then using the drop down to select "delete" and then clicking the button), you get no warning. I would suggest a warning "are you sure you wanna delete these $number users" where $number is the number of boxes checked. Should handle singular and plural as well "are you sure you want to delete this user" (or "that user", like the default warning) or "are you sure you want to delete these 4 users".

  1. When I deleted a user that had made the last post on a topic, the "last poster" name is missing in the column on the front page
  1. The user names for deleted users all appear "Anonymous" by their replies
  1. None of the posts got deleted (I don't think)
  1. None of the tags got deleted (I suppose because the posts were not deleted)

Should the delete function handle any of those things? Does deleting just one user at a time delete any of those things (their posts, their tags) so the mass delete function just works the same way?

Does a recount fix any of this? Are the statistics correct after doing this?

If there's something that should be done after deleting multiple users, we should tell users "now, go do a recount" (with a link to the admin page.)

If you should not delete a user who has added posts or tags, there should be a warning "do not delete users who have added replies or tags" or we should check to see if there are any posts or tags by the user you're deleting.

Just some thoughts on how this should work

#7 @GautamGupta
9 years ago

  • Keywords needs-patch added; has-patch tested removed

#8 @kevinjohngallagher
9 years ago

  • Cc kevinjohngallagher added
  • Milestone changed from 1.1 to 1.5
  • Severity changed from normal to major

There's no doubt that this feature would be great, and is definately needed, but the process of it all needs to be planned out slightly better.

Given that this wasn't a requirement for 1.1, and given that there is a working plugin that covers some of the functionality, lets move this to 1.5. If we're still waiting on BackPress after all the other bugs are done, we can come back to it.

#9 @kevinjohngallagher
9 years ago

  • Milestone changed from Future Release to 1.1

Officially hold up my hands as to making the wrong call here.
With no "future release" after this 1.1, lets bring this baby back into the fold.

#10 @GautamGupta
9 years ago

  • Milestone changed from 1.1 to Future Release

As chrishajer said, this still needs a lot of working.

#11 @johnjamesjacoby
8 years ago

  • Version changed from 1.0.2 to 1.1-alpha

#12 @johnjamesjacoby
8 years ago

  • Milestone changed from Future Release to 1.1
  • Version 1.1-alpha deleted

#13 @johnjamesjacoby
8 years ago

  • Milestone changed from 1.1 to 1.2
Note: See TracTickets for help on using tickets.