My previous comment was incorrect, this bug has been present since 7.0.3.1 and should finally be fixed in the up-coming 7.0.5 release.
My previous comment was incorrect, this bug has been present since 7.0.3.1 and should finally be fixed in the up-coming 7.0.5 release.