Opened 10 years ago
Last modified 3 years ago
#6130 new defect (bug)
Default (Last active) sorting doesn't show some members
Reported by: | sooskriszta | Owned by: | |
---|---|---|---|
Milestone: | Awaiting Contributions | Priority: | normal |
Severity: | normal | Version: | |
Component: | Core | Keywords: | needs-patch needs-unit-tests |
Cc: | vivek@… |
Description
Picking up from https://buddypress.trac.wordpress.org/ticket/5611#comment:6
It seems odd that some members would be shown for one sort and not for another.
Change History (8)
#2
@
10 years ago
- Keywords needs-patch needs-unit-tests added; dev-feedback removed
- Milestone changed from Awaiting Review to Future Release
In my opinion, we shouldn't filter by a member's last activity here. For comparison, the "Alphabetical" sort does not filter on a member's last activity.
This change is OK with me. We'll need to sort by u.ID DESC in this case.
#4
@
8 years ago
- Milestone changed from Future Release to 2.8
- Summary changed from Default sorting doesn't show some members to Default (Last active) sorting doesn't show some members
Check other components as well.
#6
@
4 years ago
Yup, just sort, don't filter. Or in other words, just run the sort, don't add a limit on the number of results or how long ago the activity was...
#7
@
4 years ago
- Milestone changed from Awaiting Contributions to 8.0.0
Let's try to work on this during 8.0.0. Who's volunteering to submit a patch, before I do 😉 ?
#8
@
3 years ago
- Milestone changed from 8.0.0 to Awaiting Contributions
I was very optimistic in my last comment 😱.
I've been looking into this more deeply, and it's not just a matter of sort Vs filter. The active
order is getting user IDs from the activity table as long as there were active once (the where clause is looking for the last_activity
activity type. It's pretty clever to do so as when a user is spammed their activities are deleted. It also filters out 'non-activated' users when on a non multisite configs (this is needed unless BP_SIGNUPS_SKIP_USER_CREATION
is defined to true). So I'm not sure we should change anything here.
Instead and to avoid having this confusing behavior (alphabetical
showing members active
is not), I believe we should filter out from alphabetical
the same users 😊.
I believe it's safer not to touch to this part so close to the 8.0.0-beta1 release. Let's try to have a look at it during next release.
"Last active" is the default sorting behavior. This sort depends on a user having some sort of activity, so it makes sense that we filter out members who have never logged in before.
However, I see your point about the "Newest registered" sort relying on the member's last activity. In my opinion, we shouldn't filter by a member's last activity here. For comparison, the "Alphabetical" sort does not filter on a member's last activity.