[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:  has-patch       |     Focuses:
----------------------------+----------------------------

Comment (by dd32):

 Replying to [comment:53 markparnell]:
 > 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.

 PR950 basically implements this for plugins as a proof-of-concept,
 although I'm not 100% on the naming of things, especially the filter
 `update_plugins_{$hostname}`.

 I decided to go with `Update URI` to be generic between Plugins/Themes,
 The PR description mentioned 'Update ID' but I changed it after creating
 it.

 A number of things in WordPress did need to be updated to reflect that not
 all updates would come from WordPress.org, such as expecting a `slug` to
 always be present.

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