Thesis 2.0 Guide – Introducing the Thesis 2.0 Backup and Restore Manager

Thesis 2.0 has introduced an all new Backup and Restore Manager. This new skin manager system is just awesome!

When you select the Manage button at the top of Thesis 2.0’s user-interface you will be take to a one of the most important pages during your development phase.

Introducing the Thesis 2.0 Backup & Restore Manager

This new Backup & Restore manager let’s you do a number of things.

Backup your Skin

At the click of a button you can instantly backup your whole skin, so if you make a mistake, or delete something you didn’t mean too in the HTML editor you can restore it in seconds.

This thing is fast, and I mean fast.

I backed up my site by selecting the Create New Backup button .

I then went and trashed my test site. Placing all my confidence in this backup system.

Restore your Skin

Having placed all my confidence in this Backup manager, it was time to see if it delivers. So I selected the Restore Button for my backup.


Hit the restore button, it seemed like nothing happened, checked my site and she was as good as new. Back to where I wanted it. It seemed like nothing happened because it all happened so fast.

So to answer the question, did it deliver?

Of course it did 😉

But that’s not all

Not only can you backup your skin, you can export it to another site.

Just hit the Export button

and then a box like this will appear.

Here you can select exactly which parts of your skin you want to export. So perhaps you just want the template layout, or the packages and variables, boxes. You decide, once again Thesis 2.0 gives us a choice.

Select your options and hit the Export Skin, simple.

Once you have your Export, you can upload it to as many sites as you want, as long as their Thesis 2.0 of course.

To import the skin just hit the import button

a simple pop up will appear and you just located the file on your computer.

Once you have found your file just hit the Import Data and let Thesis 2.0 do the rest.

If that wasn’t enough for you, and you really wanted to start again.

Just hit the Restore Defaults Button.

This is just one more reason why I use Thesis 2.0 this feature will save me soo much time when developing sites. All I have to do is back them up as I’m bound to bump in to someone else who is looking for a similar layout that Ive likely built already.

Just think of the possibilities with this 😉
Don’t have Thesis check it out here

Meet the Author

Matthew Horne

Matthew Horne is web developer who specializes in optimized development. He also builds custom solutions instead of reverting to plugins. Matthew Has a strong understanding of PHP, JavaScript, jQuery.

12 comments… add one
  • KiwiBrian Oct 25, 2012, 4:25 pm

    Absolutely splendid!!!!
    And so prompt as well.
    Well done that man….

    • Matthew Horne Oct 25, 2012, 4:49 pm

      No problem, ive been looking forward to talking about this, its such an amazing feature and the implications of it are far reaching.

      • KiwiBrian Oct 25, 2012, 11:37 pm

        Comment from Rick re saving a skin limitation –
        “Right now the only “right” way to develop a skin is to do so from scratch and the only way to export the skin and redistribute it is to use a hidden export function that requires php to expose.”
        Would welcome your comment on this situation/limitation/frustration.

        • Matthew Horne Oct 26, 2012, 12:09 am

          It’s not necessarily a limitation, one of the intentions of thesis 2.0 is to build a micro market around it. Some skins will come with features specific to it, it would not be fair to the developers of those skins to allow free use of the features, also it prevents cross skins compatibility issues, skins are essentially themes and thesis is sort of like wordpress.

          In wordpress you cannot hotch botch 2 themes together in an efficient or usefull manner and the same applies to skins.

          For example, a skin might be designed as being responsive, this means it is fundementally built in a different way to a skin that isnt. That is assuming the skin is built correctly, the idea is to build skins specific to a purpose, to achieve certain goals and this is where skin specific features come in to it.

          Of course boxes and package can be loaded on to any skin, but you will soon begin to see specialist skins, such as kolakubes marketers delight, which will be transformed to thesis 2.0, the coding will be clean according to the features it will contain.

          A skin can be created from scratch similiar to how a normal theme is created, but there are certain parameters to follow to allow thesis 2.0 to recognise it. I will be looking in to this further as I have a few skins of my own to create, so once I have done that, I will have much better information for you in terms of getting started with creating skins.

          Hope this helps.

          • KiwiBrian Oct 26, 2012, 1:49 am

            Thanks Matthew for superb and comprehensive reply.
            You are certainly going the extra miles in your online support and tutorials.

  • Campbell Oct 27, 2012, 6:28 am

    Hey Matt,

    I have a strong interest in this topic as well in regards to creating skins, boxes, etc. It would be really nice if we could get some documentation on how to go about doing this in Thesis 2.


    • Matthew Horne Oct 27, 2012, 12:26 pm

      I will be looking in to writing some docs about that, but it will be at a later date.

  • Mike Smith Oct 29, 2012, 1:32 pm

    Hi Matthew,
    Very, very good tutorials. Thank you for taking the considerable time to do all these.

    One thing… you say above “I then went and trashed my test site. Placing all my confidence in this backup system.” Just wanted to confirm that the Thesis 2 Skin back/restore does not backup nor restore site data such as pages, posts and media. Thesis 2’s tools only backup/restore the theme customisations – CSS, HTML (templates), and boxes. If I’m wrong let me know.

    Mike Smith
    Brisbane, Australia

    • Matthew Horne Oct 29, 2012, 1:35 pm

      That is correct, the backup manager only backs up the skins, packages, boxes etc associated with the current skin.

      This allows you to duplicate the site on another domain to help build other sites but also for devs to build sites on there servers and quickly transfer the site.

      It makes development safer as well as more convenient.

      Also if you make a mistake you can quickly restore the site.

  • Les Dossey Oct 29, 2012, 7:00 pm

    Stupid Simple. Loving the 2.0.1

  • Darcy Nov 14, 2012, 4:22 am

    Hi Brian! I was only introduced to the Thesis theme a few months back now but it really has completely altered the way that I use WP and it has gotten me more into (see: addicted) to blogging than I thought I’d ever be. With some many people using the theme and pouring their time and effort into creating content, a backup and restore program is a must-have as far as I can see!

Leave a Comment