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

UpdateConfigBackend: use api4 to flush the cache #25913

Merged
merged 1 commit into from
Mar 24, 2023

Conversation

mlutfy
Copy link
Member

@mlutfy mlutfy commented Mar 24, 2023

Overview

CiviCRM has a few places where it flushes the cache, and sometimes they work in slightly different ways.

This removes one of those slightly different ways.

Before

Flushing the cache would not refresh the list of installed reports provided by an extension.

(It's a custom extension where new mgd files are being added by devs)

Running system.flush via the API worked fine, but not when using this form/button.

After

Flushing the cache works as expected.

@civibot
Copy link

civibot bot commented Mar 24, 2023

(Standard links)

@civibot civibot bot added the master label Mar 24, 2023
@mattwire
Copy link
Contributor

test fail unrelated

@mattwire mattwire merged commit e1d7378 into civicrm:master Mar 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants