Rocket.chat: Proper names reverting to username in thread

Created on 24 Oct 2019  路  5Comments  路  Source: RocketChat/Rocket.Chat

Rocket.Chat 2.1.1 Docker (checked on two instances)

Just noticed this morning when I click on a thread the 'Real' names are getting changed to usernames.

The name of the thread creator stays the same, but any one else in the thread gets changed to username.

Bit of video to demonstrate - notice in the right pane when I click on Replies - you can see the name change (I hope)

Seems to have occurred after updating from 2.1.0 to 2.1.1

Once it has changed it will not revert back.

animation

threads / discussions uux bug

Most helpful comment

@MartinSchoeler @reetp I would like to take this up.
Thankyou :smile:

All 5 comments

(Can also be seen on React Native client as well)

@MartinSchoeler @reetp I would like to take this up.
Thankyou :smile:

Clearly a regression. Hopefully you can find it.

@reetp John, exactly the same problem I have here on my live server (version 2.2.0, bundle) too. The name of the creator of the thread is displayed (first message). For all further messages either the username is displayed directly or after a reload the name changes to the username. Strangely enough, my test system, which should be configured identically and runs on the same version, does not behave like this. On another live system with version 2.1.1 the problem does not occur either.

Strangely enough, the names are displayed correctly outside threads in a channel/room.

And also strange is: if you upload a photo in the thread, for example, the name is displayed again and in all following messages, you write. After a reload of the client the names change back to the usernames.

See 15734

I have a feeling someone has been messing about with defaults???

Was this page helpful?
0 / 5 - 0 ratings

Related issues

mattlin picture mattlin  路  3Comments

amayer5125 picture amayer5125  路  3Comments

tanc picture tanc  路  3Comments

ghost picture ghost  路  3Comments

karlprieb picture karlprieb  路  3Comments