Daryl C. W. O'Shea wrote:


I believe this was fixed in 3.0.4.  Bug 4080 if I remember correctly.


Upgraded from 3.0.3 to 3.0.4  and problem gone.

Thanks!



--

--beast

Reply via email to