ceguimaraes
Results
1
comments of
ceguimaraes
I can confirm the error was fixed on 2.0.3. We recently upgraded to 2.3.3 and we are experiencing the error again.