Thanks for the hint. We fixed this in version 2.1.0.0. Please update your plugin instance.
↧
Thanks for the hint. We fixed this in version 2.1.0.0. Please update your plugin instance.