[wp-trac] [WordPress Trac] #50280: Enable auto-updates shows for plugins with no support

WordPress Trac noreply at wordpress.org
Mon Jul 27 03:34:03 UTC 2020


#50280: Enable auto-updates shows for plugins with no support
-------------------------------------------------+-------------------------
 Reporter:  elrae                                |       Owner:  audrasjb
     Type:  enhancement                          |      Status:  reopened
 Priority:  normal                               |   Milestone:  5.5
Component:  Upgrade/Install                      |     Version:  trunk
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch dev-feedback commit has-   |     Focuses:  docs,
  dev-note                                       |  administration
-------------------------------------------------+-------------------------
Changes (by dd32):

 * status:  closed => reopened
 * resolution:  fixed =>


Comment:

 I'm going to re-open this, as as @StephenCronin has pointed out this is a
 very confusing situation for plugins that simply will never update and can
 be quite a concerning where a plugin that should ever be updates shows as
 receiving updates.
 Themes are potentially far more likely to be in that situation, and may
 give some site owners the misunderstanding that whomever built a custom
 theme for them is still supporting it.

 The original purpose of the ticket still remains true, and the filter
 added in [48077] while beneficial, isn't actually super useful in these
 cases as the plugins in question are either:
  - Not going to include the filter, and will never update so never make
 use of it
  - Not going to be active, and as a result, not able to filter it
  - Be a custom plugin and there's really no reason a custom development
 agency should need to add an extra filter to disable this functionality,
 when we can do it automatically.

 At least in the case of Plugins, WordPress knows if a plugin supports
 automatic updates, the plugins update check API returns all known plugins
 (It's how the 'Visit plugin site' changes to 'View details'). I believe
 most 3rd party update scripts also do something to fill in the required
 `no_update` transient key.

 [https://github.com/WordPress/wordpress-develop/pull/431 PR431] implements
 a basic unavailable warning here, although the UI may want a bit more
 work.
 This can probably be punted to being worked on for 5.5.1, existing commits
 not withstanding.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/50280#comment:24>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list