[wp-trac] [WordPress Trac] #49056: Can we stop bundling default themes?
WordPress Trac
noreply at wordpress.org
Fri Dec 20 17:48:31 UTC 2019
#49056: Can we stop bundling default themes?
-----------------------------+------------------------------
Reporter: crdunst | Owner: (none)
Type: defect (bug) | Status: new
Priority: normal | Milestone: Awaiting Review
Component: Upgrade/Install | Version:
Severity: minor | Resolution:
Keywords: close | Focuses:
-----------------------------+------------------------------
Changes (by knutsp):
* focuses: coding-standards =>
Comment:
I wonder:
1. What is the logic with this constant to defined and set to false, not
true (it contains SKIP)?
2. Could a new default theme replace the previous default theme if present
and inactive (not for multisite)?
3. Should this be a core user option with a UI, perhaps when/if there will
be a core UI user option to automatically update major versions?
After a major core update I always delete the previous default theme, on
all (single) sites not using this (being the active theme).
Site Health recommends removing unused themes, except (the last or any?)
default theme (and parent theme of active child theme). So updating core
creates issues in Site Health (new default themes and the bundeled
plugins). This is not ideal.
--
Ticket URL: <https://core.trac.wordpress.org/ticket/49056#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform
More information about the wp-trac
mailing list