You're right, sorry. The bug must have been introduced in 3.2.34. Is there
any way that I can help?

Reply via email to