Forums
(@ebonneteau)
4 years, 5 months ago
Problem fixed Many thanks for your quick actions 🙂
For information – Rolling back to V3.3.0 solved the problem. So I will wait for this issue to be solved in the next update, before updating this plugin.