View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0024087||mantisbt||feature||public||2018-03-08 05:22||2018-03-31 19:58|
|Status||closed||Resolution||no change required|
|Target Version||Fixed in Version|
|Summary||0024087: $g_show_realname problem on 2.12.0|
I have set '$g_show_realname' to ON in my config file.
After the upgrade to v2.12.0 it doesn't work anymore (ie the assign bug .
In v2.11.1, it was working fine.
|Tags||No tags attached.|
Have you set
I tried to uncomment the $g_show_user_realname_threshold in my config file... and it didn't work.
I looked for some documentation into MBT Admin Guide, but I didn't find anything.
Surfing on the web, I found a page that suggest to set it as below:
<pre>$g_show_user_realname_threshold = ANYBODY;</pre>
This solved my problem.
I suppose that this new param should replace '$g_show_realname'.
Is there any documentation about this param?
It's not new, but used a little bit different in earlier versions.
Not in Admin Guide at the moment, but in config_defaults_inc.php
@vboctor again I am asking myself if it's not better to obsolete show_realname.
Same problem for me.
I have this configuration and doesn't work...
#$g_show_realname = ON;
Same problem to me. I just updated to 2.12.0. Real names not shown any longer.
The problem is actual to me too.
Isn't it fixed by setting the option?
No, It Isn't fixed.
my config_inc.php too:
On version 2.11.1 is no problem
Depends on what you mean with fixed.
Maybe this explains the confusion 0024069:0059091
Thank you. I understud
I commented in 0024069:0059161
@atrol We could deprecate
I suggest resolving this issue as
@vboctor, just to be sure that we are talking about the same thing.
When I asked for obsoleting
I didn't mean that we remove any existing functionality.
There are some aspects to consider
Visibility of the real name is driven by option
I am not sure why
You could argue, that
You could argue, that
Functionality / backward compatibility
Why does someone set real_names to ON?
So maybe displaying the real name and having the user name as the bubble is the better approach.
What about replacing
I wouldn't be if different pages had different behaviors there, since such decision was done in so many places in the code. One of the core changes I have done, is centralized this decision and formatting of username across all scenarios. I missed timeline scenario which was fixed in 2.12.1 that should go out soon.
The former is more powerful than the latter since it can allow showing realnames to DEVELOPER+ and only show username to users with lower access level. Hence, we could retire
That is easy to do now, since we do this functionality in one place. However, it doesn't handle the non-unique case in an obvious way, makes @ mentions harder, etc.
We could have a config options for preference to show realname vs. username. If user chooses realname, but logged in user doesn't have access to it, then fallback to username. That however causes complexity about sorting the list by usernames vs. realnames. So it is not just a display issue and requires more places in the code to understand this configuration option.
As for order of which ones display first in case of showing first, again we get into having the sort to take this into consideration, etc.
I think the current model is simpler and we should stick with it. I understand that some users get confused initially, but I suspect that once the behavior understood it makes sense. I think it may make sense to deprecate show_realname config option though.
Right, but let's see in 0024139 if we can deprecate or if we should replace by a format option.
|2018-03-08 05:22||sbordoni||New Issue|
|2018-03-08 05:36||atrol||Status||new => feedback|
|2018-03-08 05:36||atrol||Note Added: 0059117|
|2018-03-09 04:28||sbordoni||Note Added: 0059132|
|2018-03-09 04:28||sbordoni||Status||feedback => new|
|2018-03-09 04:45||atrol||Note Added: 0059133|
|2018-03-09 05:24||alopezserrano||Note Added: 0059134|
|2018-03-09 05:33||atrol||Note Added: 0059135|
|2018-03-09 05:42||alopezserrano||Note Added: 0059136|
|2018-03-09 08:49||oricgn||Note Added: 0059140|
|2018-03-09 10:27||atrol||Relationship added||related to 0024090|
|2018-03-10 12:21||Ruzhelovich Vladimir||Note Added: 0059151|
|2018-03-10 12:29||atrol||Note Added: 0059152|
|2018-03-10 12:45||atrol||Relationship added||related to 0024069|
|2018-03-10 13:26||Ruzhelovich Vladimir||Note Added: 0059153|
|2018-03-10 13:57||atrol||Note Added: 0059154|
|2018-03-10 21:57||Ruzhelovich Vladimir||Note Added: 0059162|
|2018-03-20 03:42||atrol||Relationship added||related to 0024139|
|2018-03-21 03:10||vboctor||Note Added: 0059254|
|2018-03-21 12:44||atrol||Note Added: 0059267|
|2018-03-21 12:44||atrol||Note Edited: 0059267||View Revisions|
|2018-03-21 12:45||atrol||Note Edited: 0059267||View Revisions|
|2018-03-23 20:04||vboctor||Note Added: 0059300|
|2018-03-27 17:42||atrol||Note Added: 0059328|
|2018-03-27 17:42||atrol||Assigned To||=> atrol|
|2018-03-27 17:42||atrol||Status||new => resolved|
|2018-03-27 17:42||atrol||Resolution||open => no change required|
|2018-03-31 19:58||vboctor||Status||resolved => closed|