The next thing to take a look at is the new skin manager in Thesis 2. This new skin manager has this ability to back up or store, export and import and that sort of thing so that’s what we’re going to take a look at next.
Manage Skins One at a Time
Notice the very first thing you see here is the name, Manage Skin Thesis Classic. We’re not managing all skins, we’re only managing this one skin. If we want to manage another skin, then we have to switch to that skin first.
Create a New Backup
The very first thing you can do is create a new backup and I’m going to say, Yellow Background for this backup. You can see now that it has been created, it gives us the date, it gives the notes, it allows you to restore this. It allows you to export it then it also allows you to delete this backup.
Now that we’ve made a backup and we can come back over to our CSS editor, go to the body and let’s change that background color to something a little greener. Let’s save that CSS.
Restoring from a Backup
Now, we really have a different looking skin because we’ve made this change. But in our skin manager here, if we don’t like that change, we can always just choose come back and restore this. When we restore this, notice this message here, “Are you sure you want to do this? If you restore from a backup, you will lose the current state of your Skin”.
That means that this backup will completely replace the skin that we have here. Let’s just go ahead and say, Yes to that . Now we’re back to our yellow and if refresh this, what do you think is going to happen? Well, restoring it automatically restores that CSS file so we didn’t have to go back in and save. So that’s how to restore.
Understanding Backup Skin Data
It’s important to understand that when it says, Backup Skin Data, it’s not backing up the entire skin, it’s just backing up the data. The data is the template configurations. So everything you do over here whether it’s moving around, changing class names or adding new templates or any of that sort of thing, that’s all parts of the skin data including any new boxes you might create and everything else.
In fact, let’s go ahead and create a test box so we can see that in action. We’ll create a container, we’ll call it, Rick’s Test. We’ll add the box and save the template. Let’s come back over here to our manager and we’ll create a new backup, we’ll just call this backup, Test. It’ll do the template configurations, it’ll do those new boxes you create. It’ll also do all of these packages and all of the custom CSS that’s in there and it’ll copy any custom CSS you might have written here so that is all of the skin data.
What’s Not Part of the Skin Data?
Now, what’s notably not skin data is for example, images. Images are not part of the skin data so when you backup your skin data or export your skin data or restore your skin data, you are not doing anything to these images.
The same thing is also true with the skin files. Any files that may be associated with the skin are not being backed up or restored or exported. The only thing that’s being backed up is the skin data when you use this and the only thing that’s being exported is that skin data.
We’re going to go ahead and export that skin data and when we say export, now it’s asking us how much of this do you really want to export? We’re going to export everything, click Export Skin and see down here, it says, thesis-classic-2012? That is the export file.
With this export file, you could import it back into here so you could yourself make copies of your backups on your hard drive then come back and import them later but you can also take this to other sites.