Plugin autoactivation - Revision history

DenisChenu: Category:Plugin Development

2016-07-27T12:25:29Z

← Older revision		Revision as of 14:25, 27 July 2016
Line 15:		Line 15:
	* Put a file for enabled plugin in a specific directory : https://github.com/LimeSurvey/LimeSurvey/tree/develop/protected/config/plugins for develop version : BUT (for git/gitignore) : we need to allow adding a new file in it, but allow user to remove a file .......		* Put a file for enabled plugin in a specific directory : https://github.com/LimeSurvey/LimeSurvey/tree/develop/protected/config/plugins for develop version : BUT (for git/gitignore) : we need to allow adding a new file in it, but allow user to remove a file .......
	* Put a file in the plugin directory : when search for plugin, if plugin is new AND have this file : activate plugin. BUT see comment https://github.com/LimeSurvey/LimeSurvey/blob/master/application/libraries/PluginManager/PluginManager.php#L202 . Directory scanning is a bad idea.		* Put a file in the plugin directory : when search for plugin, if plugin is new AND have this file : activate plugin. BUT see comment https://github.com/LimeSurvey/LimeSurvey/blob/master/application/libraries/PluginManager/PluginManager.php#L202 . Directory scanning is a bad idea.

			[[Category:Plugin Development]]

DenisChenu: /* Solution idea */ directory (dev version)

2016-07-27T10:03:01Z

Solution idea: directory (dev version)

← Older revision		Revision as of 12:03, 27 July 2016
Line 13:		Line 13:
	== Solution idea ==		== Solution idea ==
	* Provide a config file (XML/JSON/anything ...) where we put an 'activated=>true' or something else . See for example https://github.com/LimeSurvey/LimeSurvey/blob/develop/protected/core/plugins/Authdb/limesurvey.json		* Provide a config file (XML/JSON/anything ...) where we put an 'activated=>true' or something else . See for example https://github.com/LimeSurvey/LimeSurvey/blob/develop/protected/core/plugins/Authdb/limesurvey.json
	* Put a file for enabled plugin in a specific directory : https://github.com/LimeSurvey/LimeSurvey/tree/develop/protected/config/plugins for develop version		* Put a file for enabled plugin in a specific directory : https://github.com/LimeSurvey/LimeSurvey/tree/develop/protected/config/plugins for develop version : BUT (for git/gitignore) : we need to allow adding a new file in it, but allow user to remove a file .......
	* Put a file in the plugin directory : when search for plugin, if plugin is new AND have this file : activate plugin. BUT see comment https://github.com/LimeSurvey/LimeSurvey/blob/master/application/libraries/PluginManager/PluginManager.php#L202 . Directory scanning is a bad idea.		* Put a file in the plugin directory : when search for plugin, if plugin is new AND have this file : activate plugin. BUT see comment https://github.com/LimeSurvey/LimeSurvey/blob/master/application/libraries/PluginManager/PluginManager.php#L202 . Directory scanning is a bad idea.

DenisChenu: Some idea

2016-07-27T09:59:58Z

Some idea

New page

Discussion about plugin activation / deactivation.

= Why open this page =
Some plugin must be activated by default : the first is AuthDB : https://github.com/LimeSurvey/LimeSurvey/tree/master/application/core/plugins/Authdb

But AuthDB contains all core export plugin : have a way to activate a plugin by default allow us to move the core export plugin to own plugin (core plugin) For example https://github.com/LimeSurvey/LimeSurvey/tree/master/application/core/plugins/exportDoc can really be moved to a sibgle deactivated allowed plugin.

= Solutions =

== Actual solution ==
Add a DB upgrade to activate the plugin by default. OK for core plugin, but can not be done in other system (limeservice can have some activated plugin too for example)

== Solution idea ==
* Provide a config file (XML/JSON/anything ...) where we put an 'activated=>true' or something else . See for example https://github.com/LimeSurvey/LimeSurvey/blob/develop/protected/core/plugins/Authdb/limesurvey.json
* Put a file for enabled plugin in a specific directory : https://github.com/LimeSurvey/LimeSurvey/tree/develop/protected/config/plugins for develop version
* Put a file in the plugin directory : when search for plugin, if plugin is new AND have this file : activate plugin. BUT see comment https://github.com/LimeSurvey/LimeSurvey/blob/master/application/libraries/PluginManager/PluginManager.php#L202 . Directory scanning is a bad idea.