Support » Themes and Templates » Update without losing design-changes

  • Hi, I have looked around and even tried it and I am kind of shocked. Is it seriously no way to update WordPress without losing theme changes?

    I designed my site on the twentyten theme and I would like to not have to sit 20 hours recreating my design every time I want to update WordPress.

    The update-guide is just confusing, other tips I have found on the forum doesn’t work and, yeah.

Viewing 15 replies - 1 through 15 (of 17 total)
  • If you are basing your design off of Twenty Ten, you should look at creating a child theme: http://codex.wordpress.org/Child_Themes

    A child theme will allow you to make a customized version of Twenty Ten (or any other theme) and not lose your changes when you update.

    Thread Starter tkse

    (@tkse)

    Only CSS. I would still have to update header, footer, etc. and therefor lose all changes.

    No it’s not only css.. that is just the beginning.
    You should always use a child theme to prevent this from happening.

    Since you all ready have altered twentyten, and it will be overwritten if you upgrade to 3.2.. my suggestion would be to:

    1-download your version of twentyten which is currently on your server
    2-using the method described above to make a child theme,
    rename your twentyten css file to something else:

    ‘/*
    Theme Name: Twenty Ten Child
    Theme URI: http: //example.com/
    Description: Child theme for the Twenty Ten theme
    Author: Your name here
    Author URI: http: //example.com/about/
    Template: twentyten
    Version: 0.1.0
    */

    3- name your current downloaded theme folder to mytwentyten (or whatever works for you)

    4- Download the current 3.2 WP to your hard drive, go to wp-content/themes/twentyten
    5 – grab that folder and upload to your server in /themes

    6 – NOW upload your child (mytwentyten) to your server in /themes

    7- go to the dashboard / themes and then click on ‘mytwentyten’

    This should give you clean version of 2010 and your altered version of 2010. Although this isn’t a perfect work around it should work.

    The other option would be to make a child theme of Twentyten as described above with only the css file..
    but then copy all your changes into the css file and if you changed header.php copy it to your child theme, if you changed functions.php copy it to your child theme.. etc..

    Thread Starter tkse

    (@tkse)

    So let’s say I have style.css, functions.php, header.php, footer.php, sidebar.php and the files for the different index-pages. I could just go to WP-Admin, chose automatic update and everything would be just fine, with my design? If I make it as a child-theme of course.

    If you make a correct child theme, yes no update would overwrite it.

    I would test it out for sure before you click the 3.2 upgrade button.

    Make your child theme, upload, check it out.. does it do everything it was doing before? Remember if you leave the version of twentyten that you altered on the server.. it will look the same, the changes are in there as well.

    That was why I said to download it first and upload a fresh twentyten.

    Thread Starter tkse

    (@tkse)

    What? I should leave it online, because the design will remain the same, but I should upload a fresh one?

    Another thing, I really just want the WP-Admin changes. Can I just replace that directory without anything going wrong? Or does it link in some way to another place so thats not possible.

    And if I just replace that directory, will everything work correctly?

    Did you make a child theme and upload it?
    Is it working?
    Did you copy the 2010 directory (the original one you made changes to– as a back up)

    The way a child theme works is that the parent theme (in this case 2010) has to be on the server, for the child theme to work.

    The only things you add to your child theme are your customizations, and the rest of the theme is displayed by the parent.

    So in your case, you need to switch the 2010 parent out with one not customized. That’s what I meant.

    Sorry I am not so good at explaining.

    Excuse me are you asking to just replace wp-admin ?
    I would think not. What version of wp are you running?
    3.2 was a major upgrade, just switching that directory could bring your site down. Many people doing a standard upgrade are having admin panel problems.

    Thread Starter tkse

    (@tkse)

    No, don’t have the time at the moment. Will maybe try later today.

    Now, I understand, but that means that I HAVE to recreate the design in the new twentyten-theme? Putting my, now, customized files in a child will not be able to work with the 3.2 version twntyten I guess? But then, wouldn’t that be a problem anytime there is an update?

    I am using version 3.0.5 I think.

    So, just to be clear, I have to recreate my design, but if I do it with a child-theme I will never have to recreate it again?

    Putting my, now, customized files in a child will not be able to work with the 3.2 version twentyten I guess?

    Yes it should work with twentyten in the 3.2 upgrade.

    And really you just need to copy your files into the child theme.
    You don’t need to ‘recreate’ them.
    And then upload a clean version of twentyten to be the parent.

    So, just to be clear, I have to recreate my design, but if I do it with a child-theme I will never have to recreate it again?

    Never is a very long time in the WP world.
    The theme should work for quite awhile, or until the code depreciates.

    Thread Starter tkse

    (@tkse)

    dragonsjaw: So when I decide to test it I would go like this:

    – Make a child-theme, paste all custom CSS into the child-themes CSS-file.
    – Put the rest of the files I have customized into that folder.
    – Backup twenty-ten with customization.
    – Replace the one online (still have the backup on my computer) with a clean 3.2 version twentyten.
    – Back up all SQL database data.
    – Go to WP-Admin, and update automaticly

    And hopefully that will work?

    Oh, one more thing, I am leaving EVERYTHING in the clean twentyten online right? I am not going to remove any of those files?


    Make a child-theme, paste all custom CSS into the child-themes CSS-file.
    – Put the rest of the files I have customized into that folder.
    – Backup twenty-ten with customization.
    – Replace the one online (still have the backup on my computer) with a clean 3.2 version twentyten.

    Correct.

    – Back up all SQL database data.

    Always a good idea, you could also get the WP xml export file.

    At this point I would upload your child theme and activate it and see how things are working.

    Then you will know if you have a theme issue if something isn’t working before you do the auto update.

    Oh, one more thing, I am leaving EVERYTHING in the clean twentyten online right? I am not going to remove any of those files?

    Correct.

    Good luck.

    Thread Starter tkse

    (@tkse)

    Thank you for all the help! 😀

    Just two more questions, where do I get the XML-file you mentioned?

    Me, running a Norwegian version will not effect this in a wrong way?
    As long as I wait until a Norwegian version is available.

    Just two more questions, where do I get the XML-file you mentioned?

    dashboard — tools—export– choose all

    this will be a file downloaded to your computer.

    Sorry I do not know about language packs // 3.2 ..

    Perhaps start another topic addressing that issue?

    you welcome

    Thread Starter tkse

    (@tkse)

    Okey, so it looks like I have to do this and update wordpress just to make sure all code are updated and optimised. I have read trough it and got one more question:

    When doing this, is it possible to rename index.php to something else and make a custom index.php to still let me se the website with the renamed file and let normal viewers se a note that the site are down for maintenance?

Viewing 15 replies - 1 through 15 (of 17 total)
  • The topic ‘Update without losing design-changes’ is closed to new replies.