Open PMIBR opened 11 months ago
Hi, I had the same problem after upgrading to the latest version of formcreator. Did you get a solution?
Hi, I had the same problem after upgrading to the latest version of formcreator. Did you get a solution?
Sadly not, I'm not an experienced programmer, nor do I have a development environment to try and fix this. If I were to guess, it'll be either commit #6ce71f95 or #1b71d652 that re-introduced the bug, since they're the only commits related to escaping/sanitization post-2.13.5 afaik (the latter of which pertains to ticket title specifically).
However, do take this with a grain of salt, it's just a guess which I am unable to test.
Hello, I still have the same problem here, did you manage to solve it?
Today I updated my GLPI to 10.0.15 and formcreator version 2.13.9 and the error still persists =\ Any light to help us solve this? @btry
Hi
The issue seems simple to solve, but I could not find a reliable fix for that (those found so far broke something else in the plugin). As the plugin reached end of life, I'l much less available for this kind of time consuming (and hopefully low impacting) issues. Please be patient and wait for GLPI 10.1 which will implement native forms.
Thanks for the reply! Yes, it's a low impact issue, so no problem with it staying as it is. Waiting for GLPI 10.1 then!
Describe the bug ITIL Categories on ticket titles displaying
>
instead of >To Reproduce Steps to reproduce the behavior:
##answer_x##
(i.e. the answer to the ITIL Category question);Expected behavior Title being shown as "Category > Sub-category > Sub-category"... Instead, it is shown as "Category
>
Sub-category>
Sub-category".>
s inserted manually on the target ticket title still work, just##answer_x##
does not. Answers outside of the title (i.e. on the ticket body) work as intended.Screenshots
GLPI / Plugins (please complete the following information):
Full plugin list on bottom of issue
Desktop (please complete the following information):
However, it happens on other machines with other OSes and browsers as well.
Additional context This bug was not present on formcreator version 2.13.5, so it's probably a regression bug introduced in a version after that one. Please let me know if more information is needed, and I'll be glad to assist.
Full plugin list