You are not logged in.
We just upgraded from 9.5 to 10. Using the rich text editor "insert image" option in a ticket follow up, the image then displays it in base64, something like this:
<img src="data:image/jpeg;base64,/9j/4QMsRXhpZgAATU0AKgAAAAgADQEAAAMAAAABD8AAAAEBAAMAAAABC9AAAAEPAAIAAAAIAAAAqgEQAAIAAAAJAAAAsg....(goes on for awhile)
At this stage there does not seem to be any way to delete it in Chrome. If you use the edit option to get into the follow up the browser will just freeze in Chrome. I was able to delete in Firefox so that at least got us out of the issue.
Not sure if this a bug or something with our upgrade, any ideas?
Offline
I can confirm that GLPI 10.0.2 has the same issue on our side. It is something that rarely happened before, in GLPI 9.5.5, but now happens much more often.
There seems to be a sweet spot in resolution/size of an image before becoming textual base64. Some images work, while others become an extremely long block of characters.
For now, using Firefox is the only way to edit or delete a corrupted post. Waiting for updates.
Offline