Forums
(@westcountymedia)
5 years, 3 months ago
Dealing with (what now appears likely to be) the same issue on a client site. Reverting to v 5.8.6 resolved this issue for me as well.