Just a note that this was issue was discussed further with Ryan via PM. The upshot was:
-
The issue most likely is derived from an aspect of the environment common to @Ryan_Collins1 and @gizadev. Other plugins were seeing a similar issue on Ryan’s site.
-
The relevant log call was removed in WP Discourse
2.4.2which was released on 11 May.
If anyone sees this issue again, please let me know.