https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #12 from David Cook ---
(In reply to Kyle M Hall from comment #11)
> It's starting to feel like we need a koha-plugin tool to go along with all
> the other "koha-" tools. Something that could take a kpz as an argument ( o
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #11 from Kyle M Hall ---
(In reply to David Cook from comment #9)
> (In reply to Kyle M Hall from comment #8)
> > Perhaps a "--read-only" switch that would add an additional "_ReadOnly" key
> > to the plugin_data table? T
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #10 from David Cook ---
I did have another thought...
What about adding a method to Koha::Plugins::Base, and then invoking it on a
per-plugin basis using bug 34335?
--
You are receiving this mail because:
You are the a
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #9 from David Cook ---
(In reply to Kyle M Hall from comment #8)
> Perhaps a "--read-only" switch that would add an additional "_ReadOnly" key
> to the plugin_data table? That would be easy enough to code a check for.
I
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #8 from Kyle M Hall ---
(In reply to David Cook from comment #7)
> (In reply to David Cook from comment #6)
> > Actually, I think it would need to be a flag, because you might want to
> > distribute a third-party plugin v
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #7 from David Cook ---
(In reply to David Cook from comment #6)
> Actually, I think it would need to be a flag, because you might want to
> distribute a third-party plugin via a shared directory to many Koha
> instances a
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #6 from David Cook ---
(In reply to Tomás Cohen Arazi from comment #3)
> (In reply to David Cook from comment #2)
> > Would the plugin itself denote itself as non-accessible to users, or would
> > it be a flag used when i
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
David Cook changed:
What|Removed |Added
See Also||https://bugs.koha-community
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #5 from David Cook ---
Bug 34335 could be used for interacting with the plugin.
We'd still need something to prevent the plugin from being affected by web
users though.
--
You are receiving this mail because:
You are
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #4 from David Cook ---
(In reply to Tomás Cohen Arazi from comment #3)
> (In reply to David Cook from comment #2)
> > One question:
> >
> > Would the plugin itself denote itself as non-accessible to users, or would
> > i
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #3 from Tomás Cohen Arazi ---
(In reply to David Cook from comment #2)
> One question:
>
> Would the plugin itself denote itself as non-accessible to users, or would
> it be a flag used when installing via the CLI?
I th
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #2 from David Cook ---
One question:
Would the plugin itself denote itself as non-accessible to users, or would it
be a flag used when installing via the CLI?
--
You are receiving this mail because:
You are the assigne
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
David Cook changed:
What|Removed |Added
See Also||https://bugs.koha-community
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
--- Comment #1 from David Cook ---
Oooh I like the sound of this.
Ideally, I'd like to not allow libraries to install their own plugins (similar
to Bug 25672), but I would like to be able to install plugins on their system
from the
https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28499
Nick Clemens changed:
What|Removed |Added
CC||dc...@prosentient.com.au,
15 matches
Mail list logo
