[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:
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  WordPress.org
Component:  Themes          |     Version:
 Severity:  normal          |  Resolution:
 Keywords:                  |     Focuses:
----------------------------+----------------------------

Comment (by earnjam):

 Your 2nd option is closer what I was going to suggest. I think what gets
 used to compute the hash could be debated.

 To save processing resources on the api.wordpress.org side, the best
 option would be to compute that hash on the end-user/requestee side before
 making the request and then pass that along as part of the API call. That
 would require an update to `wp_update_themes()` in Core.

 I'm not sure the mindset of whether it's ok to add that to previous
 branches or not, but in theory it could be added to all the branches
 getting security patches, so all the way back to 3.7. It's not a security
 patch though, so not sure it's something the lead devs would want to do,
 but that would essentially cover about 95% of installs based on the stats
 from https://wordpress.org/about/stats/. At for least those who allow
 automatic updates or install them themselves.

 At the very least, making that update in the latest version would cover a
 big chunk of installs.

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