Peter Bieringer

still existing with latest 3.1.x? If not, please close this issue.

still existing with latest 3.1.x? If not, please close this issue.

if reproducable with current version, please reopen

can this be reproduced with 3.1.8? If not, please close.

can this be replicated with latest version 3.1.x?

is this still an issue with latest 3.1.x?

still existing with latest 3.1.x? If not, please close this issue.

closing now, in case still reproducable with current version (which should also support #4 now) reopen

closed as really old version

is this still an issue with latest 3.1.x?