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
After upgrading to 0.59.1 the Avatar settings were merged into Profile settings. To allow avatar updates I have to allow profile changes now which I am not intend to do. I want users to be able to update their avatars while maintaining the display name given by CAS or LDAP.
Server Setup Information:
Version of Rocket.Chat Server: 0.59.1
Operating System: Debian 8.9
Deployment Method(snap/docker/tar/etc): tar
Number of Running Instances: 12
DB Replicaset Oplog: Enabled
Node Version: v4.8.4
Steps to Reproduce:
Set Allow User Profile Change to false
Set Allow User Avatar Change to true
Try to update avatar
Expected behavior:
My Account should list Avatar.
OR
Administration -> Accounts should give me the option to set Allow User (Display) Name Change to false.
Actual behavior:
Avatar settings are in My Account -> Profile now, which cannot be accessed with above settings anymore. Thus, you cannot forbid changing the display name while allowing avarar updates.
Relevant logs:
None.
The text was updated successfully, but these errors were encountered:
Description:
After upgrading to 0.59.1 the Avatar settings were merged into Profile settings. To allow avatar updates I have to allow profile changes now which I am not intend to do. I want users to be able to update their avatars while maintaining the display name given by CAS or LDAP.
Server Setup Information:
Steps to Reproduce:
Expected behavior:
My Account should list Avatar.
OR
Administration -> Accounts should give me the option to set Allow User (Display) Name Change to false.
Actual behavior:
Avatar settings are in My Account -> Profile now, which cannot be accessed with above settings anymore. Thus, you cannot forbid changing the display name while allowing avarar updates.
Relevant logs:
None.
The text was updated successfully, but these errors were encountered: