-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The monitoring plugin removes carriage returns (\n) in text body #36
Comments
This is caused by https://issues.igniterealtime.org/browse/OF-1804 |
guusdk
added a commit
to guusdk/Openfire
that referenced
this issue
Jun 25, 2019
toString() applies a pretty print formatter, which mangles the formatting of message text. This introduces igniterealtime/openfire-monitoring-plugin#36
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Jun 25, 2019
guusdk
added a commit
that referenced
this issue
Jun 25, 2019
Fixed in 1.8.0. |
akrherz
pushed a commit
to igniterealtime/Openfire
that referenced
this issue
Jun 28, 2019
toString() applies a pretty print formatter, which mangles the formatting of message text. This introduces igniterealtime/openfire-monitoring-plugin#36
guusdk
added a commit
to guusdk/openfire-monitoring-plugin
that referenced
this issue
Nov 22, 2019
The fix for igniterealtime#36 replaces the text value of the body element with other text. The replacement text needs to be properly escaped for XML.
guusdk
added a commit
that referenced
this issue
Dec 2, 2019
The fix for #36 replaces the text value of the body element with other text. The replacement text needs to be properly escaped for XML.
akrherz
pushed a commit
to akrherz/openfire-monitoring-plugin
that referenced
this issue
Oct 30, 2020
akrherz
pushed a commit
to akrherz/openfire-monitoring-plugin
that referenced
this issue
Oct 30, 2020
The fix for igniterealtime#36 replaces the text value of the body element with other text. The replacement text needs to be properly escaped for XML.
akrherz
pushed a commit
to akrherz/openfire-monitoring-plugin
that referenced
this issue
Oct 30, 2020
…gniterealtime#36) As a side effect improve ClusteredCacheFactory
akrherz
pushed a commit
to akrherz/openfire-monitoring-plugin
that referenced
this issue
Oct 30, 2020
akrherz
pushed a commit
to akrherz/openfire-monitoring-plugin
that referenced
this issue
Oct 30, 2020
The fix for igniterealtime#36 replaces the text value of the body element with other text. The replacement text needs to be properly escaped for XML.
akrherz
pushed a commit
to akrherz/openfire-monitoring-plugin
that referenced
this issue
Dec 1, 2020
akrherz
pushed a commit
to akrherz/openfire-monitoring-plugin
that referenced
this issue
Dec 1, 2020
The fix for igniterealtime#36 replaces the text value of the body element with other text. The replacement text needs to be properly escaped for XML.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When a message is formatted as a multi-line string with carriage return "\n" characters, it is saved correctly in the DB, but monitoring plugin removes the "\u000a" in the body of the archived message stanza created.
This causes markdown text to be formatted incorrectly
The text was updated successfully, but these errors were encountered: