Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

refresh cache on demand #1169

Merged
merged 1 commit into from
Oct 3, 2022
Merged

Conversation

ArtificialOwl
Copy link
Member

might not be the best solution

Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
@max-nextcloud
Copy link
Contributor

I think this would do the trick for collectives. However the better solution might be to expire the cache when a new circle is created.

We are using the createCircle function of the circleManager from collectives:

$federatedUser = $this->getFederatedUser($userId);
$this->circlesManager->startSession($federatedUser);
$circle = $this->circlesManager->createCircle($name, null, false, false);

This should expire the cache for the federatedUser in question, right? Or should we use another method?

@mejo-
Copy link
Member

mejo- commented Oct 3, 2022

/backport to stable25

@max-nextcloud max-nextcloud merged commit c029fa4 into master Oct 3, 2022
@delete-merged-branch delete-merged-branch bot deleted the fix/noid/refresh-cache-on-demand branch October 3, 2022 13:13
@max-nextcloud
Copy link
Contributor

Okay... let's go with this for a start.

@mejo-
Copy link
Member

mejo- commented Nov 17, 2022

/backport to stable24

@mejo-
Copy link
Member

mejo- commented Nov 17, 2022

/backport to stable23

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants