Basically, this is a plugin issue, so this is something you’ll need to bring up on the relevant plugin’s forum. If you’re not sure which plugin is generating the error, it may be worth switching each off in turn until the error goes (and the last one turned off would therefore be the one generating the message).
]]>