>> >The patch below should fix this, or do >> >> It did. Thanks! > > Any plans for a 1.3.2 (Or 1.3.1.1) release yet? I think we might run > into the same bug. Released now // Rickard