Title: Basic upgrade question
Last modified: August 20, 2016

---

# Basic upgrade question

 *  [madaa](https://wordpress.org/support/users/madaa/)
 * (@madaa)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/)
 * Hi All,
 * I have a newbie question. I recently upgraded from ver 3.2.1 and I got an error
   message revolving around the new “add_help_tab” feature. Luckily, I solved it
   by coping the new code from twentyeleven theme-options.php.
 * My question is how does one suppose to upgrade the site smoothly when his theme
   is based of twentyeleven version x with bunch of modifications and the upgrade
   has version y with new features/changes required by the new core files. It looks
   to me like an impossible mission because you need to re-implement all your changes
   in the new theme. Please correct me if I’m wrong.
 * Thank you in advance,
    -A

Viewing 10 replies - 1 through 10 (of 10 total)

 *  [Pothi Kalimuthu](https://wordpress.org/support/users/pothi/)
 * (@pothi)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453863)
 * Hi,
 * You don’t have to re-implement those changes. My site is a modified version of
   twentyeleven too. But, I have made all the modifications only after [creating a child theme](http://codex.wordpress.org/Child_Themes).
 *  Thread Starter [madaa](https://wordpress.org/support/users/madaa/)
 * (@madaa)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453878)
 * thanks, but what if I have to modify theme files like content-aside.php, the 
   parent theme would not be accessible any more, right?
 *  [Pothi Kalimuthu](https://wordpress.org/support/users/pothi/)
 * (@pothi)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453882)
 * There are a few things that [override the parent theme](http://codex.wordpress.org/Child_Themes#Using_Post_Formats)
   and the [others are just added](http://codex.wordpress.org/Child_Themes#Template_files)
   to the parent theme. Either way, the parent theme would still be accessible.
 *  [Pioneer Web Design](https://wordpress.org/support/users/swansonphotos/)
 * (@swansonphotos)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453886)
 * It may also be worthy to note that the best manner of keeping _customized wp-
   contents folder files_, is to _manually update_ and only upload the _other folders_.
   First, deactivate your plugins, switch to default theme (or some other basic 
   theme that is known to work with the current version you are updating to), then
   do the uploads…activate your theme, test…activate plugins one at a time, test…
   one does not have to rely on the auto-update feature (and I suggest not to!).
 * Of course, and most importantly, always have a full backup done just before upgrading
   including your MySQL Database! – If something breaks, you can restore from backup
   right away and be back running.
 *  Thread Starter [madaa](https://wordpress.org/support/users/madaa/)
 * (@madaa)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453922)
 * Thanks guys, I appreciate you taking the time to answer my questions but I still
   don’t see the benefit of upgrading wp. I read about the child theme but still
   don’t understand how can you enjoy all new features of the upgrade. Let’s say
   your child theme was heavily customised and it relies on functions from the parent
   theme and wp core functions. Once you upgrade some of those functions will be
   gone/deprecated and it’ll screw up your child theme. Now you have to go figure
   the source of all your issues. Does this make sense? I understand that the parent
   theme stays intact but its a new version now where your child theme was overriding/
   adding to a previous version of that parent theme. The issue I see is that you
   will not enjoy any new features or even worse, bugs will appear cause your version
   of the theme is older. Do I have to manually go through every file I override
   in my child theme and Add/Change/Remove modules to make it work like the new 
   parent them?
 *  Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * (@jdembowski)
 * Forum Moderator and Brute Squad
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453928)
 * > I still don’t see the benefit of upgrading wp.
 * Do it to save yourself support problems down the road.
 * The WordPress software is continuing to evolve and finding support here is easier
   if you are running the current version.
 * As in other threads, you’ve just modified that one theme. That’s not too bad 
   and try the advice [here](http://wordpress.org/support/topic/how-to-update-my-modified-321-blog-to-33?replies=11#post-2505541)
   to get updated while preserving your theme changes.
 *  [Chip Bennett](https://wordpress.org/support/users/chipbennett/)
 * (@chipbennett)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453929)
 * Really, there are a few options:
 * 1) Use a Theme that someone else maintains, and rely on the developer to make
   Theme improvements. (This includes using core-bundled Themes, such as Twenty 
   Eleven.)
 * 2) Modify a Theme, via Child Theme, and maintain only your Child Theme, while
   relying on the Parent Theme developer to make Theme improvements.
 * 3) Fork a Theme, by modifying it directly, and then taking ownership of any future
   Theme improvements
 * 4) Creating your own Theme from scratch, and maintaining it.
 * Pick whichever option suits your needs – but understand the impact of each decision.
 * You chose to modify Twenty Eleven directly, and are now concerned with maintaining
   changes to the Theme yourself. Okay, well… that really doesn’t work.
 * If you’re not comfortable with maintaining Theme improvements, then you should
   limit yourself to options 1 and 2. Thus, if you need to make changes to the Theme,
   but are not comfortable maintaining the entire Theme, you are left with option
   2: use a Child Theme.
 * More often than not, a Child Theme is nothing more than CSS changes. Next most
   likely change is adding custom page templates, or customizing Theme template 
   files.
 * The least likely change involves modifications in the `functions.php` file. If
   you don’t have to make functional changes, your Child Theme doesn’t even need
   to _include_ `functions.php`. In such case, you have little to worry about when
   updating the Parent Theme.
 *  [xCalculator](https://wordpress.org/support/users/xcalculator/)
 * (@xcalculator)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453941)
 * Ok. Reposted that in a new thread. Ok, here’s a theme upgrade related Q. What’s
   the diff between twenty eleven v1.2 and v1.3? I can’t find documentation on “
   what’s new in twenty eleven”.
 *  Moderator [Jan Dembowski](https://wordpress.org/support/users/jdembowski/)
 * (@jdembowski)
 * Forum Moderator and Brute Squad
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453942)
 * xCalculator? You really should post a new thread, this one is a different topic.
 *  [xCalculator](https://wordpress.org/support/users/xcalculator/)
 * (@xcalculator)
 * [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453943)
 * Sorry bout that. Thought this was general twenty eleven theme feedback.

Viewing 10 replies - 1 through 10 (of 10 total)

The topic ‘Basic upgrade question’ is closed to new replies.

## Tags

 * [errors](https://wordpress.org/support/topic-tag/errors/)
 * [upgrade](https://wordpress.org/support/topic-tag/upgrade/)

 * In: [Installing WordPress](https://wordpress.org/support/forum/installation/)
 * 10 replies
 * 6 participants
 * Last reply from: [xCalculator](https://wordpress.org/support/users/xcalculator/)
 * Last activity: [14 years, 4 months ago](https://wordpress.org/support/topic/basic-upgrade-question/#post-2453943)
 * Status: not resolved

## Topics

### Topics with no replies

### Non-support topics

### Resolved topics

### Unresolved topics

### All topics
