Problem:
Joomla stores extension metadata such as the version number in the manifest_cache
column of the #__extensions
table during installation or update. However, if an extension is updated manually — for example via Git, FTP, or a CI deployment — the XML manifest file is updated on disk, but Joomla does not re-read this file automatically.
This leads to inconsistencies between the actual extension files and the metadata shown in the Joomla admin interface.
Most notably:
Currently, the only way to update the manifest_cache
is to reinstall the extension or use low-level CLI/SQL workarounds.
Proposed Solution:
Add native support for refreshing the manifest_cache
from the manifest XML, via both GUI and CLI:
manifest_cache
field with current data.php cli/joomla.php extension:refresh --name=plg_myplugin
--name
, or a combination of --type
, --element
, and --folder
.Why it’s important:
Security Considerations:
Optional Enhancements:
--all
CLI option to refresh all installed extensions.Labels |
Added:
No Code Attached Yet
|
Thanks for the clarification, and apologies for raising an unnecessary feature request.
I honestly never realized that the “Refresh Cache” button already performs a manifest refresh — I’ve always assumed it was related to internal or system caching, not extension metadata.
That’s exactly the problem though — the label is too vague to communicate its actual function. I’d suggest we really just need to:
Rename it to “Refresh Manifest Cache” (or similar),
And ideally show a success message once the action completes.
This small change would greatly improve clarity and help other developers like me avoid confusion.
Thanks again!
I honestly never realized that the “Refresh Cache” button already performs a manifest refresh — I’ve always assumed it was related to internal or system caching, not extension metadata.
As it exists on the Extension Updates page I thought it was obvious what it referred to. I get that obviously it wasnt obvious to you but I dont think adding the word manifest would help as that word is meaningless to regular users.
I honestly never realized that the “Refresh Cache” button already performs a manifest refresh — I’ve always assumed it was related to internal or system caching, not extension metadata.
As it exists on the Extension Updates page I thought it was obvious what it referred to. I get that obviously it wasnt obvious to you but I dont think adding the word manifest would help as that word is meaningless to regular users.
That's also reasonable I agree.
OK, so let's close this issue then.
Thank you very much!
Status | New | ⇒ | Closed |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-05-11 15:10:51 |
Closed_By | ⇒ | richard67 |
The feature is already supported. From extensions management screen, you can check on checkbox next to the extensions you want to refresh manifest cache, and press Actions -> Refresh Cache button to have manifest cache of the selected extensions updated. Maybe we could change label of the button to Refresh Manifest Cache to make it more clear and display a success message when the action completed.