#28645 closed enhancement (invalid)
WP_DEFAULT_THEME falls back to twentyfourteen even if it doesn't exist
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 3.0 |
Component: | Bootstrap/Load | Keywords: | has-patch |
Focuses: | Cc: |
Description
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. If there is only one theme present in the themes folder it would be better if WordPress fell back to that theme.
Attachments (4)
Change History (14)
This ticket was mentioned in IRC in #wordpress-dev by SergeyBiryukov. View the logs.
11 years ago
#6
follow-up:
↓ 7
@
11 years ago
- Keywords close 2nd-opinion added; commit removed
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
.
#7
in reply to:
↑ 6
@
11 years ago
- Keywords close 2nd-opinion removed
- Milestone 4.0 deleted
- Resolution set to invalid
- Status changed from new to closed
Replying to 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 inwp-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.
WP_DEFAULT_THEME has been introduced in 3.0.