Adam D. Barratt wrote: > Have you had chance to test 2.10.16 or later and confirm whether you're > still seeing this problem? (2.10.18.1 is currently in testing.)
Just treid with 2.10.18.1 and the bug seemed to have been retitled.. -- To unsubscribe, send mail to [EMAIL PROTECTED]
