Support » Requests and Feedback » [WP 3.1.3] Upgrades shouldn't replace themes

  • Resolved svenjick


    Hi. I love WordPress. But what happenend with the 3.1.3 update pushes me to write. The automatic update get the blog to 3.1.3 and replaces the TwentyTen theme (as well).

    This is fine if people haven’t touched the original theme. But chances are that people had customised it (as was my case). Of course, I should have renamed it, but still. I think that updating the blog-system should not impose a theme change. These are two distinct elements, at least in my view.

    Sorry for the rant. Have a nice day.

Viewing 3 replies - 1 through 3 (of 3 total)
  • You should not have modified the original TwentyTen theme.

    You should have used a child theme of TwentyTen – well documented

    Moderator Ipstenu (Mika Epstein)


    Lead Plugin Wrangler

    This has always been the case (since WP 1) and invariably, the first time someone realizes it, they’re angry.

    WordPress MUST include a theme in the base build to work, however the idea of changing updates so they don’t overwrite themes is being looked at. That said, do use a child theme instead. Much safer all around.

    Thank you Ipstenu for your kind and helpful answer. I wasn’t really angry (as I had a backup) but just very surprised.

    I don’t pretend to be an expert WP developper, but I have built serveral WP website and had never come across child themes. By chance, I always created a new theme from scratch or used another theme as a starting point. For some reason, this time I used TwentyTen as a starting point, hence the surprise… I will look more closely at child themes. Thank you.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘[WP 3.1.3] Upgrades shouldn't replace themes’ is closed to new replies.