Conductor v1.3.8 saw the update of the underlying framework. Considering the scope of the update, things went smoothly. There were, however, two underlying problems that have since been corrected.
Problem the First: Liquid templates
During our testing, liquid templates appeared to work just fine. However, upon deployment, we quickly discovered a situation that didn’t work as well.
The above code parsed in Conductor v1.3.6, but not v1.3.7. To fix this, we forked a copy of the liquid library, and applied a patch and now use our liquid library as the source for Conductor. The goal is for us to not use our own library, but until our fix is accepted by the original library owner, we have a working solution. This is all thanks to the distributed source control of git and Github. If you are curious about git, another great source is Pro Git, a free online book that provides a lot of useful, well formatted information.
Problem the Second (and perhaps last): Google Analytics
A lot of Conductor sites make use of Google Analytics. If the site is in development, or just launched, there usually isn’t any Google Analytics information. During our last deploy, we found a case where the Conductor Dashboard was throwing an error because of a lack of Analytics information. So a quick patch later, and we patched up that issue.
Opportunity the First: Automated Site Crawls
With this launch, we have created an API to get a list of live Conductor sites; With this list in hand, and a web-crawler, we are going to add an automated tool to help verify that links on newly deployed, and existing sites, are all working.
