Forums
(@asanti82)
11 years, 6 months ago
This same exact error has come up again when I upgraded to 3.6 and the latest version of the plugin