Summary: | Plugin link location needs extra documentation so indicate where it may be found | ||
---|---|---|---|
Product: | Koha | Reporter: | wajasu <matted-34813> |
Component: | Documentation | Assignee: | Bugs List <koha-bugs> |
Status: | Needs documenting --- | QA Contact: | Testopia <testopia> |
Severity: | minor | ||
Priority: | P5 - low | CC: | dcook |
Version: | Main | ||
Hardware: | All | ||
OS: | All | ||
GIT URL: | Change sponsored?: | --- | |
Patch complexity: | --- | Documentation contact: | |
Documentation submission: | Text to go in the release notes: | ||
Version(s) released in: | Circulation function: |
Description
wajasu
2022-08-15 21:42:51 UTC
The docs probably do need an update. Caroline's advice is overkill though, and your description of the plugin migrating to tools after a plugin is installed is inaccurate. Once a "tool plugin" is installed, it will appear in the Tools menu. Same for a "report plugin" in Reports I believe. Administration will still be the place to manage plugins regardless. As for workflows: When you update koha-conf.xml, you need to clear the memcached and typically restart the Starman server so that it clears its own local cached copy of koha-conf.xml too. (In future, that restart should be done using Bug 21366.) When you upload a plugin for the first time, you shouldn't need to do anything to get it to appear. However, if you upgrade a plugin, you will need to restart Starman so that it loads the latest version of the plugin. (I have speculated on a way for that restart to be done automatically and gracefully at Bug 30897.) |