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
Currently, avatar sync in user triggers setup of the filesystem too early which leads to problems when encryption is enabled. The logic should be implemented in core.
GitMate.io thinks the contributor most likely able to help you is @PVince81.
Possibly related issues are #16808 (Sync problem), #26585 (Avatar Performance ), #30638 (Core controlled user metadata sync), #19938 (Move core apps to separate repositories), and #10100 (bug when moving folder while it syncs).
Looks like there is no official way for the backends to provide the avatar, nor to modify it from the backend. As far as the backend goes, it just provides the uids of the user and some information based on that uid, the avatar isn't included.
The avatar is supposed to be provided by the IUser, which is returned by the user manager but not by the backend. Basically, the backends shouldn't worry about avatars as they should be provided by ???? , so the user_ldap app has been doing forbidden things since the beginning 🤦♂️
Looks like there are more changes required to do this properly...
Currently, avatar sync in user triggers setup of the filesystem too early which leads to problems when encryption is enabled. The logic should be implemented in core.
cc @tomneedham @jvillafanez
The text was updated successfully, but these errors were encountered: