[wp-trac] [WordPress Trac] #14179: Theme asking to update (theme with same name on WordPress.org)

[WordPress Trac]

#14179: Theme asking to update (theme with same name on WordPress.org)
----------------------------+----------------------------
 Reporter:  design_dolphin  |       Owner:  (none)
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  WordPress.org
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+----------------------------

Comment (by markparnell):

 This was raised in dev chat last week, and the point made that with the
 auto-update functionality added in 5.5 this really needs to be addressed.

 After some discussion a solution was suggested which seems to address the
 underlying issue without adding significant additional complexity.

 In short, the proposal was to add support for a single additional header
 to theme and plugin files, `Update API`.

 This header would be optional, with a default value of `wordpress.org`.
 Any other value would mean that the theme/plugin should not be updated
 from the WP repo.

 At a very high level the changes would look something like this:

 * Update wordpress.org to reject themes/plugins which have this header
 containing a value other than `wordpress.org`
 * Leave core as-is - it can ignore this header and still pass everything
 through to the update APIs, which will be responsible for responding
 appropriately
 * Add hooks to the core update processes to allow filtering the update
 responses, so that custom update logic can be applied when updates are to
 be served by something other than wordpress.org.

 For reference, the discussion started here:
 https://wordpress.slack.com/archives/C02RQBWTW/p1598506703279700

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