You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after upgrading to the latest Version (9.2.1) we realized that editing the ticket description of an existing ticket (a ticket that was created in an earlier glpi version) leads to non existent line breaks: the line breaks are replaced by 'rn'.
After saving the ticket, instead of showing
This is a
Test
the description shows
This is arnTest
When I look into the database, it's a similar behaviour: the 'rn's are also inserted in the 'content' field of an old ticket, whereas a new ticket entry shows real linebreaks.
id=1 -> old ticket (9.1)
id=2 -> new ticket (9.2.1)
mysql> select id, content from glpi_tickets;
+----+-----------------------------------+
| id | content |
+----+-----------------------------------+
| 1 | TestrnErneuter TestrnDritter Test |
| 2 | Test
Test zwei
Test drei |
+----+-----------------------------------+
2 rows in set (0.00 sec)
Seems not to be a real big deal, but perhaps you can check that.
Thanks in advance
The text was updated successfully, but these errors were encountered:
Dear GLPI team,
after upgrading to the latest Version (9.2.1) we realized that editing the ticket description of an existing ticket (a ticket that was created in an earlier glpi version) leads to non existent line breaks: the line breaks are replaced by 'rn'.
After saving the ticket, instead of showing
This is a
Test
the description shows
This is arnTest
When I look into the database, it's a similar behaviour: the 'rn's are also inserted in the 'content' field of an old ticket, whereas a new ticket entry shows real linebreaks.
id=1 -> old ticket (9.1)
id=2 -> new ticket (9.2.1)
mysql> select id, content from glpi_tickets;
+----+-----------------------------------+
| id | content |
+----+-----------------------------------+
| 1 | TestrnErneuter TestrnDritter Test |
| 2 | Test
Test zwei
Test drei |
+----+-----------------------------------+
2 rows in set (0.00 sec)
Seems not to be a real big deal, but perhaps you can check that.
Thanks in advance
The text was updated successfully, but these errors were encountered: