On 17/07/2012 01:40, Chris Travers wrote:
If I read this error right, this error has been around since 1.3.0. We can delay fixing it until after 1.3.20 is released.
No problem. Sorry I only just got around to testing this pathway. It isn't one that I use very frequently.