Feature proposal #6024
open
Actually, wondering if we shouldn't change the term "banned" to it's opposite: "Profile Visible" or "Visible" ?
It's like Joomla that changed "blocked" to "enabled" for users, because using settings with a negative meaning is very confusing.
- Related to Bug #6025: In Users-list term is correctly "Enabled", but in User-edit, term and meaning is opposite: "Blocked" added
- Target version changed from CB 2.0.15 to CB 2.1
- % Done changed from 0 to 50
Partially improved with Blocked changed to Enabled.
- Status changed from Assigned to Resolved
- % Done changed from 50 to 100
Implemented in MR !1178
Banned changed to Visible. Also improved psuedo field objects to be more complete for userparams so APIs can better understand the field object.
- Status changed from Resolved to Feedback
- % Done changed from 100 to 70
I'm not sure we should change taxonomy in a minor release "banned" is used throughout CB, documentation, videos and website. Think we should discuss change or additional status "Visible", which is very different than banning (with the workflow to ask to be unbanned) first and for CB 3.0.
- Status changed from Feedback to New
- Target version changed from CB 2.1 to CB 3.0
- % Done changed from 70 to 0
MR changed to WIP and moved to CB 3.0. No time for this to make it into CB 2.1 and your proposal would be a major, possibly breaking, change to banning behavior (which agreeably needs improved significantly).
- Assignee deleted (
krileon)
- % Done changed from 0 to 50
MR !1178 has a WIP implementation (moving to 50% done) so we don't miss it.
Also available in: Atom
PDF