Forums
(@dejaa)
11 years, 5 months ago
It looks like this fix was rolled into version 1.5 of the plugin, but unfortunately I’m still seeing the error on WP 4.0
