skip to Main Content

After you updated the plugin (Tues, 23 Jan ‘18): I’m still seeing this.