K
Karthikeyan Bhaskaran
Guest
While investigating this issue, it was found to be reproducible in 4.2.0.0, but not in 4.2.0.2. An upgrade to 4.2.0.2 or 4.3.1 (coming soon) should help resolve the problem.
Continue reading...
Continue reading...