Reply to thread

Hello,

After upgrading from 1.5 to 1.6, the same problem happened to me. The fix proposed works like charm, thanks a lot.

I suppose it would be included in the 1.7.

What is strange is that I didn't had the problem during the previous upgrade (1.2 -> 1.3 -> 1.4 -> 1.5 -> 1.6) but this time I did a "clean install", maybe that's why the problem happened.