Project

General

Profile

Actions

Feature proposal #6024

open

Banned icon needs to be more readable

Added by krileon over 8 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
13 June 2016
Due date:
% Done:

50%

Estimated time:

Description

If a user is not banned it shows as a red x, but it should be a green x. Checkmark should be red instead of green.

https://www.joomlapolis.com/forum/153-professional-member-support/233926-banned


Related issues 1 (0 open1 closed)

Related to CB - Bug #6025: In Users-list term is correctly "Enabled", but in User-edit, term and meaning is opposite: "Blocked"Closedkrileon13 June 2016

Actions
Actions #1

Updated by beat over 8 years ago

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.

Actions #2

Updated by beat over 8 years ago

  • Related to Bug #6025: In Users-list term is correctly "Enabled", but in User-edit, term and meaning is opposite: "Blocked" added
Actions #3

Updated by beat about 8 years ago

  • Target version changed from CB 2.0.15 to CB 2.1
Actions #4

Updated by krileon almost 8 years ago

  • % Done changed from 0 to 50

Partially improved with Blocked changed to Enabled.

Actions #5

Updated by krileon almost 8 years ago

  • 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.

Actions #6

Updated by beat almost 8 years ago

  • 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.

Actions #7

Updated by krileon almost 8 years ago

  • 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).

Actions #8

Updated by krileon almost 8 years ago

  • Assignee deleted (krileon)
Actions #9

Updated by beat over 7 years ago

  • % Done changed from 0 to 50

MR !1178 has a WIP implementation (moving to 50% done) so we don't miss it.

Actions

Also available in: Atom PDF