Images not displaying because of sanitize in FaqHelper.php

[lagasss]

Describe the bug
Images not displaying because of sanitize in FaqHelper.php if I comment, it works again.

Screenshots

phpMyFAQ (please complete the following information):

• phpMyFAQ version : 3.1.14
• PHP version : 7.4

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[SilentDude80]

Wow, that's the fix for my issue #2484 - thanks a lot, @lagasss !

[thorsten]

Removing this line of code opens potential security risks.

[lagasss]

Removing this line of code opens potential security risks.

ok but I guess the sanitize function has to be reviewed because keeping it there breaks the display of html whenever they are images.

[thorsten]

Yes, will work on it after my holiday

[SilentDude80]

The sanitize problem is also present in 3.2.0-RC, although it behaves a little different: Images are partially displayed, but then suddenly rest of the image and rest of the articles content is cut off... commenting it out makes everything work...

[thorsten]

@lagasss @SilentDude80 could you please test this fix: 0a904c1

[SilentDude80]

Cannot test in 3.1.14 at the moment, since I have it at my company and now I'm on holidays too and have no access ;-)
But I did a quick test for 3.2.0-RC which I host at home and here it throws an error, although I replaced "Sanitizer" with "HtmlSanitizer" which should be the correct variable name in 3.2.0-RC:

phpMyFAQ Fatal `error`
Uncaught exception: 'Error'

Message: 'Call to undefined method Symfony\Component\HtmlSanitizer\HtmlSanitizer::create()'

Stack trace:

#0 /var/www/html/phpmyfaq/faq.php(110): phpMyFAQ\Helper\FaqHelper->cleanUpContent()
#1 /var/www/html/phpmyfaq/index.php(793): require('...')
#2 {main}

[thorsten]

You can't use that fix for 3.2 as we switched libraries for 3.2