Skip to content

Conversation

@blizzz
Copy link
Member

@blizzz blizzz commented Jul 2, 2018

The general behaviour is that LDAP users can set their avatar within Nextcloud, as long as LDAP does not provide an image. What was not taken into account was when an unsupported (Avatar API accepts PNG and JPG only) or corrupt image was supplied. For instance a BMP. In that case, the generic placeholder was shown and the hint that the avatar was provided the by user backend. Expected was that users can set an avatar in that case.

(the first commit only cleans up unit tests without effective code changes, but makes the diff look big. don't be scared.)

@MorrisJobke
Copy link
Member

Copy link
Member

@skjnldsv skjnldsv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code looks good

Copy link
Member

@rullzer rullzer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🐘
Looks good

@skjnldsv skjnldsv added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Jul 4, 2018
@blizzz blizzz merged commit 42912a0 into master Jul 4, 2018
@blizzz blizzz deleted the fix/noid/ldap-unsupported-avatar-format branch July 4, 2018 12:37
@blizzz
Copy link
Member Author

blizzz commented Jul 4, 2018

would be awesome if the backport could get in, too 🍬 #10089

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4. to release Ready to be released and/or waiting for tests to finish bug feature: ldap

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants