Meet my Bud, Butterfinger
Geez, ANOTHER Candy Code to remember??? Thankfully, no. Butterfinger is a site on my development server that I use to test and work out the kinks in upgrades. It's just a candy bar with the url of http://butterfinger, not a new Sueetie Product. I'm thinking that creating a Butterfinger Step-by-Step Guide for future upgrades might prove to be useful, so we'd have a common point of reference by giving Butterfinger the ball.
We're going to step through updating Butterfinger from Sueetie 3.0 to 3.1. Feel free to do it differently.
Copy the Upgrade Package
First thing we're going to do is copy the 3.0.0_3.1.0 folder. Not necessary, but it's a habit. This is the area we're going to update. We'll update the web.config here, as well as other files. That way we can copy everything from here to the http://butterfinger and know we've got the latest updates.
Replace "GummyBear" with "Butterfinger"
Next I fire up Notepad++ and do a search-replace, changing GummyBear to Butterfinger. You'll notice that we're updating connection strings as well as the web.config WCF addresses. My database is ButterfingerDB and site http://butterfinger. Typically we'd need two search-replaces for connection strings and a second for the WCF addressing.
Sueetie.config
I mentioned in the
3.0 to 3.1 Upgrade Guide that there was some tweaking involved with this upgrade. That tweaking starts with the sueetie.config in /util/config. We're removing several Core properties and adding a new "MarketplaceFolderName" property. We're also adding several new Providers.
Other .config tweaking
The remaining modified .config files are listed above: nolog.config, urls.config and tasks.config. Typically the only admins who need to concern themselves with these are CMS sites with custom CMS groups with support addresses in urls.config. Those with custom calendar pages as well.
Some Quality WinMerge Time
I like WinMerge, though I know others have different file comparison app favorites. Here we're comparing sueetie.config. I was able to go with the 3.1 sueetie.config entirely and change only a single SiteUniqueName property, and even that wasn't necessary. The default "MyGummyBearSite" would have worked just fine. The SiteUniqueName property is only used for caching purposes anyway.
Sueetie.xml
Sueetie 3.1 adds more localization support. Still not 100%, but getting there. Doing a WinMerge of Sueetie.xml.
No Addons Admin folder
There is no longer a
/admin/addons folder. Delete it.
SQL Script Time
Don't forget to run the Sueetie_3.0.0_3.1.0_Upgrade.sql Script in /sql. This is what it should look like after being executed in SQL Manager. No red fonts in the message window. No drips or errors.
Drag, Drop and Go!¶
We are now at the point where we can drag-and-drop our 3.1.0 update /web contents onto http://butterfinger, which concludes the procedure.
Top