The problem comes from the custom text custom field. There was a bug in a previous build of the 1.5.1 version. If you redownload it from our website and reinstall it that should solve the problem. In the mean time, I've unpublished that field and it's working properly.
