2.9.19 -> Problem using "Escalade History Button"

[andrepetinga]

Code of Conduct

• I agree to follow this project's Code of Conduct

Is there an existing issue for this?

• I have searched the existing issues

GLPI Version

10.0.18

Plugin version

2.9.19

Bug description

If I send a simple email like this one:

The ticket is created correctly.
The problem occurs, if I escalate the ticket to other groups using the "escalade history button".
So I first escalate to one or two groups, using the escalate button -> Everything works fine.

Then, if I press the "escalade history button", it will change the original email content, adding several "n" chars...

Relevant log output

No errors on logs.

Page URL

No response

Steps To reproduce

1. Send an email to GLPI;
2. Escalate to one or two groups, using the escalate button or searching for the group name;
3. Escalate using the "escalade history button"
4. Check ticket original content

Your GLPI setup information

No response

Anything else?

No response

[github-actions]

There has been no activity on this issue for some time and therefore it is considered stale and will be closed automatically in 10 days.

If this issue is related to a bug, please try to reproduce on latest release. If the problem persist, feel free to add a comment to revive this issue.
If it is related to a new feature, please open a topic to discuss with community about this enhancement on suggestion website.

You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly.

[andrepetinga]

Problem still exists

[andrepetinga]

Hello.
Just tested the 2.9.18 version again and when I try to use the history button, it shows the error "Mandatory fields are not filled. Please correct: Technician group" like I reported since 2.9.17 version (#381)

So, then I applied the correction for this error: #392

And it stopped the previous error, and changes to the selected group, but it adds the "n" char and several line changes:

Original message:

After applying 392, it changes to the selected group, but:

So it seems the problem started with 392 patch.

[stonebuzz]

Can you try this -> #443

[andrepetinga]

Can you try this -> #443

Hello @stonebuzz.

I can't test it, because the code I have is different...
I have installed 2.9.19 and looking at #443, it says it's an alternative to #442.
So I looked at the #442 code, but even there the code is different from the one I have, from the original instalation of 2.9.19

Can you guide me on what I should install/apply, in order to test the #443?

Thanks!

PS: I'm using GLPI 10.0.23. I tried to download the main version, but it's for GLPI 11.

[stonebuzz]

After reading, this pull request will not fix your problem.

[github-actions]

There has been no activity on this issue for some time and therefore it is considered stale and will be closed automatically in 10 days.

If this issue is related to a bug, please try to reproduce on latest release. If the problem persist, feel free to add a comment to revive this issue.
If it is related to a new feature, please open a topic to discuss with community about this enhancement on suggestion website.

You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly.

[andrepetinga]

...

[Herafia]

@andrepetinga GLPI 10 will no longer be maintained. It is strongly recommended to upgrade to GLPI so you can benefit from the latest fixes and improvements.

You can find the documentation here:

https://help.glpi-project.org/tutorials/fr/procedures/updating-glpi
https://help.glpi-project.org/tutorials/fr/procedures/migrate-of-specific-plugins-from-glpi-10-to-glpi-11

Thx ;)