I do think it's a flaw since the intention of the block is to display all recent members and not all members. This also has a (minor, but nontheless...) performance impact.
Yeah, that's debatable. It's a matter of semantics, and in 20 years of software development I've never found a good answer to classifying those things that one person feels is a bug and another thinks is a feature request.
It's kind of irrelevant, though; it all goes in the same queue, and is prioritized as to level of urgency. What's your sense of priority - high, medium, low?
Comments
Moved this to..
.. Commons Feature Requests, since it appears to be more a requested change in functionality rather than an actual flaw in the existing functionality.
I do think it's a flaw since
I do think it's a flaw since the intention of the block is to display all recent members and not all members. This also has a (minor, but nontheless...) performance impact.
Semantics
Yeah, that's debatable. It's a matter of semantics, and in 20 years of software development I've never found a good answer to classifying those things that one person feels is a bug and another thinks is a feature request.
It's kind of irrelevant, though; it all goes in the same queue, and is prioritized as to level of urgency. What's your sense of priority - high, medium, low?
Definitely low. "CDO - it's
Definitely low.
"CDO - it's like OCD but alphabetical, like it should be."
Specify "recent"
I think a time-based option for this already exists, the "Recent joins time-frame" setting on admin/settings/commons.