On Tue, Oct 21, 2008 at 05:44:05PM -0300, Elder Souza wrote: > It has been fixed after what version? Do you know? Don't have the time to check the release notes right now, but it's definately fixed in 3.0.32 and 3.2.4. Jeremy.