id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc
12680	Update description on old default theme (Kubrick)	nacin		"It's going to be confusing for (new) users to see Twenty Ten and WordPress Default side by side. We should rename WordPress Default to WordPress Kubrick, and change its description to reflect that it used to be the default theme (much like the Classic theme's description).

We can rename it in style.css and be done with it, or we can take more complicated approaches.

Things to consider:

1. An active theme cannot be renamed without some problems. It used to be worse (see #12428), but the main issue now is that theme mods (header, background, etc.) are stored as mods_$theme, where $theme is the theme name (instead of the directory, for some reason).

2. Do we rename the directory as well? If we do, we would need to avoid doing this if the theme is active (even as a parent). And we would need to account for ""default"" as always being an alias to ""kubrick"" when referencing the parent theme from a child theme as well.

3. Renaming the directory in new installs makes sense, but how would we handle upgrades?

4. How can we do this without breaking anything?

There are potentially more angles to this. See [https://irclogs.wordpress.org/chanlog.php?channel=wordpress-dev&day=2010-03-237sort=asc#m94430 this IRC discussion] among me, Viper007Bond, and jorbin.

This might be a good time to bring up the fact that the automatic upgrader copies over wp-content. Maybe it's time to rely on the theme/plugin upgraders to handle updating wp-content, and have instructions in there to copy over themes only if the theme directory is nonexistent? We won't be bundling any more plugins in core, and as we bundle new themes, they can be copied over (and then updated via the theme upgrader)."	defect (bug)	closed	normal		Themes		normal	wontfix		aaron@…