#325 Pluginmanager - disable obselete plugins

closed-fixed
5
2012-07-01
2010-01-13
No

Hi,

I had the problem that jedit could no longer work properly, because an outdated plugin was installed.

It would be nice if jedit would recognize outdated plugins, much like in the "Find orphan" button. So that they can then be removed easily.

Best Regards
Lars

Discussion

  • Alan Ezust

    Alan Ezust - 2010-01-13

    basically, if the "max version" of a plugin is set in the plugin manager pluginlist.xml, then
    jedit should check if it is greater than that max version for each of the plugins that are installed, and
    disable the plugins that do not satisfy that requirement.

    But when should it be done? Ideally, before the plugin is activated. But jEdit doesn't load that information (the max version) until the plugin list is downloaded for the first time, in the update/install pane of pluginmanager.
    So where/when should the checking and disabling be done?

     
  • Alan Ezust

    Alan Ezust - 2010-01-13

    Since the pluginlist is cached, it can be done on startup provided the pluginlist was cached once before.

     
  • Lars Grundei

    Lars Grundei - 2010-01-13

    In my opinion, this do not need to happen automatically (although it would be perfect). A button in the plugin manager would be enough.

     
  • Alan Ezust

    Alan Ezust - 2012-07-01
    • assigned_to: nobody --> ezust
     
  • Alan Ezust

    Alan Ezust - 2012-07-01
    • summary: Pluginmanager - remove obselete plugins --> Pluginmanager - disable obselete plugins
    • milestone: 619623 -->
    • status: open --> closed-fixed
     
  • Alan Ezust

    Alan Ezust - 2012-07-01

    Patch#3539298 submitted.

     
  • Alan Ezust

    Alan Ezust - 2012-07-01
    • status: closed-fixed --> open-fixed
     
  • Alan Ezust

    Alan Ezust - 2012-07-01

    Leaving as "open" until the patch is committed.

     
  • Alan Ezust

    Alan Ezust - 2012-07-01

    Committed 21896. This will be in jEdit 5.1

     
  • Alan Ezust

    Alan Ezust - 2012-07-01
    • status: open-fixed --> closed-fixed
     
  • Alan Ezust

    Alan Ezust - 2012-07-01

    It disables obsolete plugins every time the plugin list is updated. You can temporarily enable it, but it will get disabled again next time you go to the install or update panel of Plugin Manager.

     
  • Alan Ezust

    Alan Ezust - 2012-07-02

    if you are working on a version that has not been released yet, there won't be an entry in the XML file and there won't be any conflict/disabling. You can try it yourself with the SVN version of Optional.

     
  • The Shady Watcher

    It might be better if a person were warned that plugins were obsolete, rather than just disabling them. It is not so bad, tho, to allow them to be renabled. I use an old version of Firefox so I can use the Speak It! plugin, since no modern version of FF allows for text to be sent to the M$ Speech API; and there are some pretty good voices that use it. The point is, it works for later versions of FF than advertised, and I can use Nightly Tester tools to get a slightly more recent version to work with the plugin. Likewise, I could imagine someone would want to use Clipper while transitioning to XInsert, even tho it break Undo and other stuff. Detecting the problem before an update, and then leaving things however the user wants them seems least Draconian to me. Likewise, I recently downloaded a version of a plugin on another machine that asked for a newer jEdit. It seems better to warn a person if an old version of jEdit doesn't work with a newer plugin version BEFORE it is installed; since how does someone go back, when an incompatible plugin is downloaded, and THEN the warning pops up? Remember, Linux users who install jEdit from repositories are often using antiquated versions of stuff; tho it is easy enough to e.g. just download the Java installer.

     
  • Alan Ezust

    Alan Ezust - 2012-07-03

    I can make it an option that one can switch off from the plugin manager option pane.
    But it will be on by default.
    There is no way you can download/update an a plugin via the jEdit plugin manager interface that doesn't work on your currently running version of jedit. if you did, that's a bug that should be reported.

     
  • Alan Ezust

    Alan Ezust - 2012-07-03

    Also, all jedit max versions are set in plugin manager for a reason - they really do break something in later versions of jEdit and should not be used.

     

Log in to post a comment.