@hnla
14 years, 3 months ago
It is a known issue and a patch has been committed and should be part of the 1.2.6 release, that will hopefully drop very soon.
