Skip to content
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

Closed
deleolajide opened this issue Apr 13, 2019 · 2 comments
Closed

Comments

@deleolajide
Copy link
Member

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.

<message from="test@conference.desktop-545pc5b/Dele Olajide" id="e0678c1b-fa3d-421b-a5b3-5b39d4a8b149" to="dele@desktop-545pc5b/pade-converse-v4.2.0-Chrome73Win10.64-26059867" type="groupchat">
  <body>Your heading goes here ======================</body>
  <active xmlns="http://jabber.org/protocol/chatstates"></active>
  <origin-id xmlns="urn:xmpp:sid:0" id="e0678c1b-fa3d-421b-a5b3-5b39d4a8b149"></origin-id>
  <stanza-id xmlns="urn:xmpp:sid:0" id="e0678c1b-fa3d-421b-a5b3-5b39d4a8b149" by="test@conference.desktop-545pc5b"/>
</message>

This causes markdown text to be formatted incorrectly

@guusdk
Copy link
Member

guusdk commented Jun 25, 2019

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
Copy link
Member

guusdk commented Jun 25, 2019

Fixed in 1.8.0.

@guusdk guusdk closed this as completed Jun 25, 2019
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
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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants