Well I can confirm that upgrading did fix the problem. We were using version 1.1.6 and had the problem reported in this ticket and upgraded to 1.1.8 and the problem was fixed.