its already fixed in v2.3.4-dev
Either you can update to the above development version (which is running very fine) or wait for stable release.
its already fixed in v2.3.4-dev
Either you can update to the above development version (which is running very fine) or wait for stable release.