My Blog: Upgrades and Patches

07 January 2018

It took me longer than I though it would, and I had to call on friends for help, but I've finally managed to upgrade my website's C1 Content Management System to version 6.2.

I'm not on a paid support contact, and so don't get the easy to use fixes and upgrades that Orckestra helpfully provide corporate customers. However, the C1 community often provides resources for developers like me. In this case, Pauli Østerø (a.k.a. burningice2866) published a handy guide for upgrading from v5.1 to v6.2:

Manual Upgrade Process

For upgrading v5.1 to v6.2, move to v5.4 as an intermediate step to prevent introducing too many datatype changes at once. It takes about 20 minutes.

  • It’s perfectly fine to do an in-place upgrade.
  • For each version, copy and overwrite all the files and folders from the release downloaded from except the following:
    • \App_Data\Composite\Composite.config
    • \Web.config
  • Manually apply changes to web.config and composite.config. GitHub Compare can be a good help here to visualize changes to a file across multiple versions Or simply look through the file in v5.4 and v6.2 side-by-side with the one being upgraded to see what the result should look like.
  • You may need to remove all C1 add-ons beforehand, except those in Packages > Installed Packages > Local Packages and Composite.Updates.

First to v5.4

  1. Stop the website;
  2. Copy and overwrite existing files with v5.4;
  3. Merge in the changes to web.config:
    • set framework version to 4.6.1
    • change SiteMapProvider to CmsPageSiteMapProvider
  4. Start the website.

Then to v6.2

  1. Stop the website;
  2. Copy and overwrite existing files with v6.2;
  3. Merge in the changes to web.config and composite.config:
    • web.config:
      • add fcnMode="Single" to httpRuntime
      • set the c# compiler to Orckestra.AspNet.Roslyn.CSharpCodeProvider
      • add necessary runtime bindings
    • composite.config:
      • add ComponentProvider Configuration
      • add new inheritGlobalReadPermissionOnHiddenPerspectives setting
      • remove obsolete DataLogTraceListener
  4. Start the website.

Going Secure with SSL Support

In addition to upgrading my CMS, I have also sprung for SSL support from my hosting provider. The main website is now delivered over HTTPS, as are my C1 add-in packages. If you've previously added my server as a package source, you might like to update the connection to point to instead.

comments powered by Disqus