J4 Issue ? ?
avatar mbabker
mbabker
6 Jun 2017

After #16502 the standardized extension install path now makes available preflight, uninstall, and postflight tasks for scripts to hook. However, as noted in the pull request:

The current implementation triggers both preflight and uninstall immediately, this seems a bit illogical to trigger two hooks back-to-back when nothing else has happened in the middle. I think moving uninstall somewhere in the middle (after SQL and before files is where it is for plugins in 3.x) may make sense, but there may be other options as well.

IMO we should move the uninstall task somewhere later than it is now, otherwise either preflight or uninstall is redundant.

avatar mbabker mbabker - open - 6 Jun 2017
avatar joomla-cms-bot joomla-cms-bot - change - 6 Jun 2017
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 6 Jun 2017
avatar mbabker mbabker - change - 6 Jun 2017
Labels Added: ?
avatar mbabker mbabker - labeled - 6 Jun 2017
avatar franz-wohlkoenig franz-wohlkoenig - change - 7 Jun 2017
Category com_installer
avatar franz-wohlkoenig franz-wohlkoenig - change - 9 Nov 2017
Title
[4.0][RFC] Uninstall Extension Script Triggers
[4.0] [RFC] Uninstall Extension Script Triggers
Status New Discussion
avatar joomla-cms-bot joomla-cms-bot - edited - 9 Nov 2017
avatar brianteeman brianteeman - change - 25 Mar 2018
Labels Added: J4 Issue
avatar brianteeman brianteeman - labeled - 25 Mar 2018
avatar mbabker mbabker - change - 13 Sep 2018
Status Discussion Closed
Closed_Date 0000-00-00 00:00:00 2018-09-13 01:41:53
Closed_By mbabker
avatar mbabker mbabker - close - 13 Sep 2018
avatar zero-24 zero-24 - change - 16 Sep 2018
Labels Removed: ?
avatar zero-24 zero-24 - unlabeled - 16 Sep 2018
avatar joomla-cms-bot joomla-cms-bot - change - 16 Sep 2018
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 16 Sep 2018

Add a Comment

Login with GitHub to post a comment