We demonstrate how to upgrade to Thesis 2.4 on our site, BYOBWebsite. There have been internal improvements that may cause problems on your site which we address as we go through the upgrade process.
There are three things in particular that can affect your site. One has to do with your CSS and another has to do with Thesis no longer supporting an obsolete hook system. The third is fixing scripts and html. We have a second video that you can watch for how to fix the scripts.
We also talk about choosing to wait to upgrade until your Theme has been brought up to Thesis 2.4 compliance.
We demonstrate the following steps in this video.
- Make a backup in the Data Manager
- Upgrade Thesis
- Upgrade Skins and Boxes
- Install and Run “Fix CSS”
- Dump all Caches
- Check Site Appearance
- Delete Fix CSS
- Check for Broken Scripts
Comments on this entry are closed.
Hi Rick
Something is fishy with “BYOB Footer Widgets” each time I switch Skin I kinda need to re-save the box, I always loose the CSS to kick in.
Pierre
That’s not I problem I’ve seen. I’ll look into it.
Pierre
That has always happened for me.
Keith
Hi Keith
I still have a sub-domain running T2.3.2, that’s not happening there.
I have gotten into the habit of saving these 4 sets of code prior to upgrading thesis version or skins and then copy/pasting the code back in after the upgrades.
Editor CSS
Skin Custom CSS
Site Tracking Scripts
Site Head scripts
Does that serve the same purpose as the fix CSS box?
No, the Fix CSS box removes extra slashes in CSS.css that arise from the change in escaping method in Thesis 2.4
Is it still a good precaution to do the steps of saving these 4 sets of code (Editor CSS, Skin Custom CSS, Site Tracking Scripts, and Site Head scripts) prior to upgrading thesis version or skins and then copy/pasting the code back in after the upgrades anyway, or does the Fix CSS box handle those concerns.
I have had to recode the CSS on my entire site in the past after upgrading thesis, which is why I am concerned.
No, I generally don’t recommend all of that now. I recommend using Skin Editor >> Data Manager to backup your current skin data prior to upgrading.
Hi Criss and Rick
Flex-direction interfering with proper functioning of Rick footer box.
Let’s say I switch Skins (Pearsonified – Flex). Me and others need to re-save the Footer box so it’s CSS kick in. Then, in Flex I also need to add in Custom CSS :
Code:
.footer-section .flex-row-to-col {
flex-direction: column;
}
Because this is interfering :
Code:
.flex-row-to-col {
flex-direction: row;
}
Kinda like the “Copyright & Attribution (Flex)” is added as a Column in the “footer-container”.
I hope both of you are working on this.
Please keep me appraise of developments.
Pierre
I noticed the skin editor for Agility 3.2 won’t save changes to the template. Likewise the custom CSS won’t save changes either. Is there an update coming or a fix for this?
Jake, something else is going on here. I don’t think it is related to Agility as I can’t make my copies of Agility fail in that way.
I guess it’s also worth mentioning that none of the Agility Easy Responsive columns have a clear:both after the columns. Not exactly sure of the best description for this but for some time now I’ve been manually inserting a div container and adding custom css to clear the html.
Again if the Agility ERCs don’t behave as if they are self clearing then something else is wrong. They don’t need clearing divs. Post a question to the forum with a link to a page where the self clearing isn’t happening.