Hi! We believe that this issue has been fixed upstream and the fix is shipped with the newest version of the package (4.7.0.1). Could you please confirm that it works for you, so that we can close this bug? -- Sincerely yours, Yury V. Zaytsev