DOMDocumentFragment::appendXML(): Entity: line 1: parser error : EntityRef: expecting ';' in Drupal\glossify\GlossifyBase->parseTooltipMatch()

I created a patch to convert special characters to HTML entities.

Patch #2 has security implications, so this should be checked with care.
Thank you for the patch so far! :)

It seems like this can be reproduced by creating a Glossify term containing an ampersand ("&"). And then running the replacement.

Could someone please try to reproduce this and then write a test?
Maybe also for other special characters?

Okay I at least found a way to fix the errors, but I think the replacement may not work propely in all cases now, but that's less important.

Hotfix attached in MR. For further implementation, this should first have tests.

Okay I at least found a way to fix the errors, but I think the replacement may not work propely in all cases now, but that's less important.

Hotfix attached in MR. For further implementation, this should first have tests.

Green tests are not enough here due to missing test coverage, but I think if the hotfix from MR!27 works, we should merge it already to improve the risk for people running into this.

We should keep this major and add tests next to reproduce it.

In my case it happened on taxonomy terms with the title "Lorem & ipsum". It resulted in user session being discarded due to the errors.

Merged the hotfix! See #9 for further steps.

I started with https://git.drupalcode.org/issue/glossify-3351345/-/tree/3351345-test-only

that needs to be completed, but even then it's not yet sure it will fail (but it's definitely a good test to add).
But for the test-only we'll need to revert the fix there!