2 Sep 21, 2005 22:02
From the user point of view, I don't want to know. The user I am likes the automatic (or semi-automatic, it's user defined!) [url=http://www.windowsupdate.com]Windows Update[/url] upgrade when security holes are fixed. The user I am also likes the way this system makes possible to install new additional software from the [url=http://www.windowsupdate.com]Windows Update[/url] site.
Now, in the blogging world, [url=http://www.dotclear.net]Dotclear[/url] has a very intuitive plug-in installation interface: you copy and paste the URL of a new plug-in to install and... a few seconds after, it's installed and ready to work!
In fact, it would be very interesting each plug-in would have its own folder with all the files it wants to have. Then, a _install.plugin.php file would contain all the needed code to perform an installation of that plug-in and _register.plugin.php would have all the plug-in needs to register itself. That would be interesting when complex plug-ins are developed.
But all this does not answer to your questions...
First, after installing the basic plug-in files where [url=http://b2evolution.net]b2evolution[/url] expects to find them (and those files should include all the plug-in-specific dependencies), all the additional files should be put in a separate, plug-in-specific folder. It should be straightforward to remove a plugin even if the user doesn't remeber the list of files to be removed.
Second, as [url=http://forums.b2evolution.net/viewtopic.php?p=26170#26170]EdB[/url] noticed, there is a Settings database table you can use to save some settings. I don't know about any OnInstall event or so. But I haven't installed the development version of Phoenix yet.
To save configuration and/or data, you can either use a database table -- that's slower than loading a .PHP configuration file --, either use a .PHP configuration file -- there may be issues with read/write access rights on some servers. I believe it's better to avoid to modify the core [url=http://b2evolution.net]b2evolution[/url] tables. I believe it's better to create new ones, so the plug-in can be uninstalled easily and the blogging system might be upgraded without any trouble.