Removed plugins

  • Resolved David Artiss

    (@dartiss)


    8 years, 6 months ago

    Hi Mika,

    Not an issue but a question. What does the “old plugins” feature cope with removed plugins? If it doesn’t already, could there be a specific warning if any of the installed plugins aren’t in the repository? I’m guessing this may be an issue for manually uploaded plugins, for example from third party sources). Is there therefore a way to highlight is it was in the repository and then goes?

    https://www.ads-software.com/plugins/ui-labs/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    Removed from the repo? It doesn’t track that since there really isn’t a way to do so. Until the unmanaged feature shows up (see https://core.trac.www.ads-software.com/ticket/32101 ), the best I could do is say “yeah, not in the repo.” It wouldn’t tell you if it had never been in or if it can been removed or what.

    Since the information isn’t useful without more context, it’s not something I’ll add soon.

    Thread Starter David Artiss

    (@dartiss)

    I understand what you’re saying Mika.

    You do cache the plugin data, though, don’t you? Wouldn’t it be possible – and I understand this would only work in some circumstances – that when you retrieve the cache data and need to refresh it, if it’s no longer in the repo to then display a message to say it’s been removed?

    Also, if you retrieve data from the repo at one point, cache it, and it’s then no longer available, retain the data and use that to report the plugin when it comes out of date (otherwise I assume once it disappears from the repo you clear the cache and don’t report on it anymore?).

    Plugin Author Ipstenu (Mika Epstein)

    (@ipstenu)

    ?????? Advisor and Activist

    You do cache the plugin data, though, don’t you?

    Sure, for whatever the default is for plugin checks (so I think that’s 48 hours maybe?). There’s too much margin for error then.

    Also … speaking as the one who closes the majority of plugins right now, I’m keenly aware of the FUD doing that would bring. Unless we have a way to mark a plugin as closed and here’s why, I know it would do little more than increase the risk for some people. I mean, we already have plugins who manually track what’s removed, and if you saw a plugin removed and then added back in within 3 days (and that’s normal), vs 3 weeks, vs 3 years, you’d have a lot of incomplete information :/

    I think, right now, it would be too dangerous.

    (otherwise I assume once it disappears from the repo you clear the cache and don’t report on it anymore?)

    No, it caches the ‘not in the repo’ for the time period and doesn’t check again until that expires.

    Once we have the ‘unmanaged’ filter, I’ll add in a check for that.

    Thread Starter David Artiss

    (@dartiss)

    That all makes perfect sense to me. Thanks for the responses ??

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘Removed plugins’ is closed to new replies.