thanks for the reply Brian. I guess I'll stick with v2.6.38 (which I'm currently using and enjoying) and most probably switch to v3 once this bug is fixed.
thanks for the reply Brian.
I guess I'll stick with v2.6.38 (which I'm currently using and enjoying) and most probably switch to v3 once this bug is fixed.