UpdateConfigBackend: use api4 to flush the cache #25913
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.