[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[EP-tech] Re: Plugins: enabled by default?
> I would suggest disabling the plugin in its 'new' function
This isn?t a good option. When installing extensions from the Bazaar, people often forget to do this ? which means installing anything on a multiple-archive setup is *dangerous*...
I?ve tried to trace the ?disable? param through EPrints::PluginFactory ? but nothing looks out of place.
I?d suggest that this is a priority to get fixed in EPrints core.
From: eprints-tech-bounces at ecs.soton.ac.uk [mailto:eprints-tech-bounces at ecs.soton.ac.uk] On Behalf Of Adam Field
Sent: 02 November 2015 13:22
To: eprints-tech at ecs.soton.ac.uk
Subject: [EP-tech] Re: Plugins: enabled by default?
Yes, I've noticed this too, recently. It used to be the case but doesn't seem to be any more. I would suggest disabling the plugin in its 'new' function, and enabling it in the local configuration. See http://bazaar.eprints.org/393/1/plugins/EPrints/Plugin/Export/Hello.pm and http://bazaar.eprints.org/393/1/epm/hello_test/cfg/cfg.d/z_hello.pl (the bazaar package I wrote for a training video).
Business Relationship Manager and Community Lead
On 2 Nov 2015, at 12:39, John Salter <J.Salter at leeds.ac.uk<mailto:J.Salter at leeds.ac.uk>> wrote:
Just trying to verify (or otherwise) my understanding of plugins and disabling/enabling them.
"By default plugins installed in lib/plugins will be disabled and hence can be enabled on a per-repository basis."
On our test repository (3.3.10), we're not seeing this - things in ~/lib/plugins/... seem to be enabled for all archives.
This causes a problem when a plugin references a field that doesn't exist for a dataobj.
Can anyone verify that their install works as expected:
Is a plugin in ~/lib/plugins/... available without being specifically enabled in the archive's cfg.d?