[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:9 mattk1980]:
 > I understand the solution, it seems ok but it seems that its quite a
 critical piece of text to have in the style.css.

 Yes, you should always have that `Update URI` header in your style.css
 (unless your theme is in the wordpress.org theme directory - meaning it's
 actually your theme in the directory, and not just another theme that
 happens to share the same name).

 > Would a child theme ever be a theme from wordpress.org e.g my parent
 theme is generatepress, my child theme has this in the css:
 >
 > {{{
 > Template: generatepress
 > }}}
 >
 > Would it still need to be overriden by a wordpress.org theme for an
 update? I can't imagine that scenario being common.

 That doesn't really make much difference - child themes are allowed in the
 wordpress.org theme directory too.

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