[QGIS-Developer] Revert Previous Plugin, disable "Upgrade All" and "Upgrade Plugin" buttons

Wed Jan 11 18:20:55 PST 2023

It would probably be more the other way around for my case. I will have to modify the calls from my front end UI for my tool to work properly with their plugin and that is how I kind of expect it as I am making calls to their code.  We plan to have quarterly releases cycles of our code with new features/bug fixes unless there is some major issue found in the 3rd party plugin that requires a hotfix.

I was hoping to avoid forking and have to maintain 3rd party plugin.  We may be looking to transition to a version of Visibility Analysis in GRASS that is a core plugin that was developed inhouse almost 40 years ago, but in the mean time I tried another method as a test. I copied the VisibilityAnalysis plugin to another directory, VA_Test, so I can mess with privileges on a copy of the plugin directory.

Looks like if I deny write privileges to the VA_Test the Upgrade Plugin button just displays as Reinstall Plugin since it does not allow an upgrade and it is actually greyed out so that is good. The user can still run the Upgrade All plugin and that will upgrade all other plugins.  When I ran that it upgraded the original  VisibilityAnalysis plugin directory and all other plugins that had upgrades available.  So this seems like this will be a quick fix.  I will just need to make those permission restrictions in the my installer MSI file and test it out.  This in general could be a good solution to prevent user’s from upgrading plugins that we provide with our install, so that users don’t just continue to upgrade before we test to make sure they work so we can avoid unnecessary tech support called.

-----Original Message-----
From: Nyall Dawson <nyall.dawson at gmail.com>
Sent: Wednesday, January 11, 2023 7:14 PM
To: Catania, Luke A ERDC-RDE-GRL-VA CIV <Luke.A.Catania at erdc.dren.mil>
Cc: qgis-developer <qgis-developer at lists.osgeo.org>
Subject: Re: [QGIS-Developer] Revert Previous Plugin, disable "Upgrade All" and "Upgrade Plugin" buttons

On Wed, 11 Jan 2023 at 12:49, Catania, Luke A ERDC-RDE-GRL-VA CIV via QGIS-Developer <qgis-developer at lists.osgeo.org<mailto:qgis-developer at lists.osgeo.org>> wrote:

>

> I had a user that may have hit the "Upgrade All" button in the plugins window. Does that automatically upgrade all installed plugins to the newest version? If so is there a way to revert back to the previous versions. He may have just hit the Upgrade Plugin button for the specific plugin.  Not sure and I did not want to test it and mess up my configuration.

>

> We have created our own QGIS plugin that relies on the VisibilityAnalysis plugin and upgrading VisibilityAnalysis from 1.7 to 1.8 breaks our tool as I created a my own Visibility Analysis UI to run the VisibilityAnalysis tool.  I basically want to prevent a user from upgrading any plugin that we access so that this does not happen.  Is there a way to disable "Upgrade All" and "Upgrade Plugin" buttons in the plugin window through settings, interface customization, or programmatically through python on QGIS using startup.py?

I'd suggest in this situation that you should instead be either working with the VisibilityAnalysis maintainers to get the latest version compatible with your needs, or alternatively fork parts of the

1.7 code into your plugin so that you aren't dependent on another maintainer's work.

Trying to workaround this by blocking plugin updates is going to be a fragile path, likely taking much longer than either of the above suggestions.

Nyall

>

> Thanks,

> Luke

> _______________________________________________

> QGIS-Developer mailing list

> QGIS-Developer at lists.osgeo.org<mailto:QGIS-Developer at lists.osgeo.org>

> List info:

> Blockedhttps://lists.osgeo.org/mailman/listinfo/qgis-developerBlocked

> Unsubscribe:

> Blockedhttps://lists.osgeo.org/mailman/listinfo/qgis-developerBlocked

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/qgis-developer/attachments/20230112/0a140656/attachment-0001.htm>