Thread: Plugin Updater
View Single Post
Old 12-19-2017, 04:08 PM   #21
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,825
Karma: 30277270
Join Date: Mar 2012
Location: Sydney Australia
Device: none
@Kovid and Plugin developers

I would have thought the test ought be:

If the plugin was not already installed, i.e. configuration folder->plugins->this.zip was absent at the start of the current update process, then pop the 'which menu' question at the end of the current update process with default selections, otherwise do nothing.

But, the question is... could this be rectified within existing shared common code, or would it require changes within individual plugin code.

@Kovid - if the former is it worth my while lodging a 'bug' report?

If the latter then forget it. Firstly the defect is not critical; secondly, there are far too many plugins that have been effectively abandoned (e.g. User Category) or are on limited support (View Manager) to warrant a concerted campaign to rectify the defect.

BR
BetterRed is offline   Reply With Quote