Mike:
I am seeing this as well. Out of curiosity, which version of the plugin are/were you running? We saw the behavior when running 2.6.9. While observing the behavior, we disabled this plugin and confirmed that the calls to the loader.js script which pushes server info were no longer included in site content. Re-enabling then brought them back. We subsequently updated to version 2.7.0 and the calls to loader.js are no longer included.
The reason I am curious about your version, is that if you are already on 2.7.0, then I can potentially expect to see something reintroduce the issue over time. The big change in that release according to the release notes (and reviewing git history) is “Remove notification plugin. It was not a good idea btw.”. If this is the trigger, then “not a good idea” indeed.
-craig
I had the same problem, but then it started working. I did a few things along the way, including deactivating/reactivating the plugin, and editing and saving the settings. I’m guessing it was one of those things that did the trick.
