Skip to content

cache the displayname after an LDAP plugin set it - #15987

Merged
blizzz merged 1 commit into
masterfrom
fix/noid/cache-displayname-on-save
Jun 18, 2019
Merged

cache the displayname after an LDAP plugin set it#15987
blizzz merged 1 commit into
masterfrom
fix/noid/cache-displayname-on-save

Conversation

@blizzz

Copy link
Copy Markdown
Member

When you have an LDAP plugin that would write the displayname, in the current state the cache would not be updated. Thus, a refresh will still show the old name, this is confusing. That's solved now.

@blizzzblizzz added this to the Nextcloud 17 milestone Jun 17, 2019
@blizzzblizzz changed the title caches the displayname after an LDAP plugin set itcache the displayname after an LDAP plugin set itJun 17, 2019
@skjnldsv

This comment has been minimized.

Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
@blizzz
blizzzforce-pushed the fix/noid/cache-displayname-on-save branch from 0ef97fd to a1f2dbeCompareJune 18, 2019 10:42
@juliusknorrjuliusknorr added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Jun 18, 2019
@blizzz
blizzz merged commit 8951376 into masterJun 18, 2019
@blizzz
blizzz deleted the fix/noid/cache-displayname-on-save branch June 18, 2019 21:20
@blizzz

Copy link
Copy Markdown
MemberAuthor

/backport to stable16

@blizzz

Copy link
Copy Markdown
MemberAuthor

/backport to stable15

@backportbot-nextcloud

Copy link
Copy Markdown

backport to stable16 in #16000

@backportbot-nextcloud

Copy link
Copy Markdown

backport to stable15 in #16001

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

Labels

4. to releaseReady to be released and/or waiting for tests to finishbugfeature: ldap

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@blizzz@skjnldsv@juliusknorr