[wp-trac] [WordPress Trac] #62783: WordPress.org theme replacing custom theme of same name.

[WordPress Trac]

#62783: WordPress.org theme replacing custom theme of same name.
-------------------------------+----------------------
 Reporter:  mattk1980          |       Owner:  (none)
     Type:  defect (bug)       |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Themes             |     Version:
 Severity:  normal             |  Resolution:  wontfix
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+----------------------
Changes (by peterwilsoncc):

 * status:  new => closed
 * version:  6.7.1 =>
 * resolution:   => wontfix
 * milestone:  Awaiting Review =>


Comment:

 I know when WP Core merges a new bundled theme, there is a certain point
 that a theme slug will be blocked in a theme directory if it used by a
 certain number of websites. I have no idea what the number is, as it's
 managed by the WP.org meta team, but I think it's relatively low.

 That means that if a premium theme uses the slug `popular-premium-theme`,
 a theme with the same slug is unable to be submitted to the theme
 directory once it hits a certain number of installs.

 As @siliconforks says, for custom themes it's critical to use the
 `UpdateURI` header to prevent updates from WordPress.org.

 I see a suggestion of reversing the process so the update URI header needs
 to be set to call for updates from WOrdPress.org. Unfortunately this isn't
 a workable solution as once the switch was made, there would be no way to
 update legacy themes without the header.

 As such, I'm going to close this ticket as `wontfix` with regard to
 reversing the process.

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