You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This is a follow up of #454. Basically, users sending messages from Slack to Mattermost fall into one of the three following categories:
They use a default avatar from Slack, in which case this one is properly displayed on mattermost side.
Me, using a custom avatar on Slack which is properly displayed on Mattermost.
Anyone else using a custom avatar, which is replaced by the default bridge logo.
To Reproduce
Have anyone excepted myself post on the Slack side.
Expected behavior
Custom avatars should be displayed properly on Mattermost side, not only mine.
On a side note, thanks to you I’ve figured out why it worked for me and not the others, and this helped me fix another issue: under Mattermost my Slack username was shown, while other people have their normal name. But that’s because they have a DisplayName while I was only having a FullName. Added a display name for myself and now everything is OK.
Since you’ve also fixed #452 in that release, this is now looking very pretty.
#191 would make this awesome, #474 (and the reverse way) would be the cherry on the top!
Keep up the great work! :D
zeridon
pushed a commit
to zeridon/matterbridge
that referenced
this issue
Feb 12, 2020
Describe the bug
This is a follow up of #454. Basically, users sending messages from Slack to Mattermost fall into one of the three following categories:
To Reproduce
Have anyone excepted myself post on the Slack side.
Expected behavior
Custom avatars should be displayed properly on Mattermost side, not only mine.
Screenshots/debug logs
Logs: see #454 (comment), #454 (comment) and #454 (comment).
Environment (please complete the following information):
Additional context
Config: #454 (comment)
As well as a new addition to gateways:
Tests have been made in both the
samechannel
gateway and thegateway_test
.The text was updated successfully, but these errors were encountered: