Add Extractor page display issue #1686
Comments
Unfortunately (or rather fortunately) I can't reproduce this on Graylog 1.2.2. @henrikjohansen Is the |
@joschi the full_message field is present and can also be selected as a field to run extractors against - it's merely a display issue. |
@henrikjohansen Ah, ok. It seems only to happen on the Extractor page. I've tried to reproduce the bug on the search page and on the streams page. Should've read the issue title in the first place. 😉 |
The full_message formatted field is already escaped on the server, so we avoid escaping it again in the Javascript code. Refs #1686
The JSON serialization of the formatted `full_message` field is not working properly, returning an empty object. As we render those fields in Javascript, we can safely return the string representation of that Html. Refs #1686
Fix Html serialization in `FieldMapper#convertNewlinesToBr()` Refs graylog-labs/graylog2-web-interface#1686
Fix Html serialization in `FieldMapper#convertNewlinesToBr()` Refs graylog-labs/graylog2-web-interface#1686 (cherry picked from commit 5c3a713)
Fix Html serialization in `FieldMapper#convertNewlinesToBr()` Refs graylog-labs/graylog2-web-interface#1686 (cherry picked from commit 5c3a713)
This was fixed in the linked PRs, and also on master. |
After upgrading to v1.2.2 the full_message field is no longer displayed correctly - instead the page only shows "full_message [object Object]"
The text was updated successfully, but these errors were encountered: