in local plugin/theme listing e.g. if plugin/theme is removed from repository or external update-source is not reachable. Maybe dismissable for ‘a week, month, forever’ or similar.
Read-only archive : Issues · ClassicPress/ClassicPress · GitHub
Author : Dora D.
Vote count : 8
Status : open
Tags :
Comments
That is an awesome idea indeed. Having at least two plugins which have been closed down or are not available for download anymore, which are giving me major headaches on how to avoid the situation of accidential clicking “update now” out of habit - and then bang! boom! bang! installation broken and have maybe to do all changes this day again, because the latest backup is from the day before.
~ posted by Fabian Wolf
I like this idea on paper, but not so much in practice. I think this could lead to security issues. For example, say an ambitious hacker installed every last plugin in the repo across a network of “monitoring” sites. All they have to do is wait for notices to come up in the dashboard indicating that an update path is no longer available, which is sometimes an indicator that a plugin was removed for security reasons. These notices could direct hackers straight to vulnerable plugins.
~ posted by Mike
fwolf:
Having at least two plugins which have been closed down or are not available for download anymore, which are giving me major headaches on how to avoid the situation of accidential clicking “update now” out of habit - and then bang! boom! bang! installation broken and have maybe to do all changes this day again, because the latest backup is from the day before.
@fwolf , In that case, you can bump the plugin’s version number (in the main PHP file) to some high number and it will never again find an update.
3 Likes