Forums
(@ltymchenko)
8 years ago
Exact same error here. Started appearing after we have updated the plugin to 2.0.10 version. Still no fix?
