Bug 25316 - Koha::Plugin::Base should automatically find plugin metadata and store it in the database for retreival
Summary: Koha::Plugin::Base should automatically find plugin metadata and store it in ...
Status: RESOLVED MOVED
Alias: None
Product: Koha
Classification: Unclassified
Component: Architecture, internals, and plumbing (show other bugs)
Version: master
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Kyle M Hall
QA Contact: Testopia
URL:
Keywords:
Depends on: 24631
Blocks:
  Show dependency treegraph
 
Reported: 2020-04-29 17:32 UTC by Kyle M Hall
Modified: 2020-04-29 19:29 UTC (History)
0 users

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments
Bug 25316: Koha::Plugin::Base should automatically find plugin metadata and store it in the database for retreival (7.83 KB, patch)
2020-04-29 19:28 UTC, Kyle M Hall
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Kyle M Hall 2020-04-29 17:32:25 UTC
We should store plugin metadata in the database for easy retrieval. 

Koha::Plugins::Base::get_metadata should check the database for its own metadata. If it doesn't find anything in the database, it should check itself for a $metadata global as it does now, but if one does not exist, it should then check for a companion PLUGIN.yml file ( from Bug 24631 ) in the bundle_path() and load the metadata from there.

In either case it should then be stored in the database.

InstallPlugins() should force the plugins metadata to be updated from source to the database, as the plugin metadata may ( and should ) have changed in the updated plugin.
Comment 1 Kyle M Hall 2020-04-29 19:28:44 UTC
Created attachment 103981 [details] [review]
Bug 25316: Koha::Plugin::Base should automatically find plugin metadata and store it in the database for retreival