This was fixed in 3.2.4/4.0.0
Please, can you guys stop reporting bugs on old versions. Try the latest version
to see whether it is fixed. That way you don't waste everybody's time with needless
This must be the difference between dealing with an open source company and a professional vendor. All you had to say was it's fixed in 3.2.4/4.0.0. We're busy dealing with our own software and don't always have the luxury of keeping up with your releases. We still have a customer on 3.0.4.
Thanks for the answer.