[wp-trac] [WordPress Trac] #28645: WP_DEFAULT_THEME falls back to twentyfourteen even if it doesn't exist

[WordPress Trac]

#28645: WP_DEFAULT_THEME falls back to twentyfourteen even if it doesn't exist
----------------------------+----------------------
 Reporter:  atimmer         |       Owner:
     Type:  enhancement     |      Status:  closed
 Priority:  normal          |   Milestone:
Component:  Bootstrap/Load  |     Version:  3.0
 Severity:  normal          |  Resolution:  invalid
 Keywords:  has-patch       |     Focuses:
----------------------------+----------------------
Changes (by DrewAPicture):

 * keywords:  has-patch close 2nd-opinion => has-patch
 * status:  new => closed
 * resolution:   => invalid
 * milestone:  4.0 =>


Comment:

 Replying to [comment:6 SergeyBiryukov]:
 > > WP_DEFAULT_THEME is by default set on the latest twenty* release, when
 you build a website for a client none of the twenty* themes are present
 and there is only one theme.
 >
 > Actually, I think removing default themes is a bad practice, since they
 are often an integral part of troubleshooting if something goes wrong with
 the current theme.
 >
 > This is merely a fallback, I don't think we should make it more complex.
 If you remove the default theme, you should define `WP_DEFAULT_THEME`
 yourself in `wp-config.php`.

 I agree with this sentiment, though we might promote a better user
 experience (in a separate ticket) by adding logic to try to grab and
 install the default if it isn't currently available. From a support
 perspective, it's important to keep the default as a default theme, as it
 were.

 It's the developer's responsibility to define a different default choice
 if the bundled themes are removed.

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