[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:  new
 Priority:  normal             |   Milestone:  Awaiting Review
Component:  Themes             |     Version:  6.7.1
 Severity:  normal             |  Resolution:
 Keywords:  reporter-feedback  |     Focuses:
-------------------------------+------------------------------

Comment (by siliconforks):

 Replying to [comment:5 mattk1980]:
 > Maybe it should be a choice to look at wordpress.org for themes and not
 be the default should the Update URI header not exist.

 Well, I think the reason it's the default behavior is that themes
 sometimes receive critical security updates from wordpress.org and users
 probably should receive those by default.  If it's not the default, then
 some users will inevitably forget to enable the option or simply be
 unaware that the option exists.

 > If you think the conditions for this are very unlikely then maybe i'm
 misunderstanding the logic of how this happened with my website. It was a
 brand new setup so perhaps I have created an unusual situation.

 It's not really an unusual situation: name collisions are not uncommon.
 But WordPress doesn't really have any way of detecting them (other than
 using the `Update URI` header).  WordPress doesn't know that your
 "starburst" theme is different from the "starburst" theme in the
 wordpress.org theme directory; it thinks that you're running an old
 version of the "starburst" theme from wordpress.org and there's an update
 available (which could be an important security update).

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