Nope. This bug has been fixed ... a while ago, I think. At least a year. Get the latest version from GitHub to fix it.