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