Forums
(@amauryneto)
10 years, 11 months ago
this happens after updating WP to 4.2 – having the same issue here. Had the latest plugin version installed on the previous WP version – no issues. Updated WP – got the error message.
