Forums
(@neenack)
12 years, 4 months ago
FYI a fix is here, though I’m sure @danielbachhuber will incorporate it soon.
Seeing the same problem. I know this worked correctly in 3.0 (not sure about 3.0.1)