http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12805 Bug ID: 12805 Summary: Proposed changes to Koha plugins system (.KPZ) structure Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: In Discussion Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt@gmail.com Reporter: indradg@gmail.com QA Contact: testopia@bugs.koha-community.org In present scenario, the <pluginsdir> as per git install is located at /var/lib/plugins and per the Koha manual should be set up at /var/lib/koha/plugin. That makes it a shared directory, and a problem with multi-tenanted installations. Removable of the plugin by Client A, results in it being removed for everyone else. Same goes for installation of new plugins. These may not have been vetted or required by other clients / sites sharing the installation. Further, while the git based dev installation and the tarball installation have the <pluginsdir> defined in their respective 'skel' structures, this is missing the .deb packages. So, I propose the following changes: 1) move <pluginsdir> to a site-specific directory i.e. /var/lib/koha/<site>/plugins Rationale: (a) allow for security-vetted and need-based plugin upload and segregation; (b) "UseKohaPlugins" is classed under site-specific "Enhanced Content" sysprefs; (c) allow for easy resolution of AssignUserId apache directive in case of git installs (on a git install, .kpz uploads failed by default, citing apache doesn't own the directory); 2) add a 'koha-enable-plugins' shell script as part of the command-line tools. Since, the plugins module was primarily Kyle's baby, I would like to hear back from him and others on this, before proceeding. thanks -indra -- You are receiving this mail because: You are watching all bug changes.