https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39466 --- Comment #8 from David Cook <dcook@prosentient.com.au> --- (In reply to Marcel de Rooy from comment #7)
Ok, didnt think about the static_routes here. But it might still be easier and faster to serve directly from this plugins/js folder.
That's true.
When installing copy js files to that folder, and when uninstalling remove the same files again there.
Maybe but that would be a big shift in how plugins work I think. It would be interesting to see what heavy plugin users thing of that. Actually, I like the idea of changing how plugin deployments work. Honestly, I think I might prefer a system where plugin code got copied/moved at install/uninstall time. (Not just the JS but all of it.) Food for tought...
For common js libraries, we could define a dedicated plugin that only serves to install those common js files?
Or even call it plugins/static and copy whatever you have in [your_plugin]/static to the common folder?
I'm not sure that I understand what you're saying here. If we did standardize the location of plugins, and install them under a plugin name (after all we already define namespaces in up-to-date plugins), we could use "AliasMatch" to serve static files out of /var/lib/<koha>/pluginsv2/<koha_plugin_namespace>/static or /var/lib/<koha>/pluginsv2/<koha_plugin_namespace>/public -- You are receiving this mail because: You are watching all bug changes.