Richard Wesley wrote:

>
>> This issue is resolved in the v2.1.1 release which should be=20=20
>> released soon.
>
> Great! Is it in the latest snapshot/beta?

It should be there.

> And just to be sure, here are the comments from the developer who was
> investigating this issue and the references. Could you have a quick
> look to make sure we are all talking about the same things?

Yes, he's right.

Dmitry