Sorry for the long delay regarding this, but if you submit a support ticket, we have a patch available to correct this.