# Können defekte Plugins von Drittanbietern das Logging stören?

**URL:** <https://meta.discourse.org/t/broken-third-party-plugins-can-break-logging/94256>\
**Category:** Bug\
**Created:** [8. August 2018 um 23:13 UTC](https://meta.discourse.org/t/broken-third-party-plugins-can-break-logging/94256 "2018-08-08T23:13:16Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [8. August 2018 um 23:20 UTC](https://meta.discourse.org/t/broken-third-party-plugins-can-break-logging/94256/3 "2018-08-08T23:20:21Z")

</div>

> [@codinghorror](#):
>
> This is with all third party plugins disabled?

EDIT: Who’s online was enabled. I don’t know what made it happen, so I don’t know how to see if the problem is gone now.

### BUT

If 3rd party plugins can break logging, then I’m less excited about `lograge`. If an errant plugin can make it so that errors aren’t logged then. . . that seems worse than unreadable logs.

---

_[View the full topic](https://meta.discourse.org/t/broken-third-party-plugins-can-break-logging/94256)._
