Broken child theme issue

[greuben]

If a child theme is broken, validate_current_theme() function updates the "current_theme" option to "Twenty Ten" but does not update "stylesheet" and "template" options, which results in displaying the default theme as current theme in backend but the front end still refers to the broken child theme's files.

To check this issue:

1) Create a child theme for twentyten theme( or anyother ) and activate it

2) Delete the child theme's style.css or the theme folder manually

3) Check the front end.

[nacin]

I think for 3.1 we can probably just revert to the default theme. Patch looks like it does way too much honestly. Also, we use tabs not spaces, so that might be messing up with the formatting a bit.

[greuben]

Replying to nacin:

I think for 3.1 we can probably just revert to the default theme. Patch looks like it does way too much honestly. Also, we use tabs not spaces, so that might be messing up with the formatting a bit.

Agreed, the first patch does way too much. Just thought reverting to parent theme would be nice. ​1670.diff just reverts back to default theme.

[greuben]

Its ​16760.diff not 1670. Typo days :(

[nacin]

Looks fine. Should be trivial to add parent theme support but I don't find that to be particularly necessary at this time.

[greuben]

relative to trunk and proper formatting

[nacin]

Looks good.

[nacin]

Forgot props the first time, sorry.

[16924], [16925]

[nacin]

(In [16924]) Revert to WP_DEFAULT_THEME if a child theme is in use and no style.css is present. fixes #15712.

[nacin]

(In [16925]) Revert to WP_DEFAULT_THEME if a child theme is in use and no style.css is present. fixes #15712, props greuben.