It's not 4.2.2 - rolled back to 4.1.4 and had exactly the same problem. @ojo1 was testing today, not yesterday when the problems were reported....
↧