fix(BuildSocialSearchIndexBackgroundJob): ensure that special characters are handled correctly

[szaimen]

Fix is done as suggested by customer

[szaimen]

/backport to stable31

[szaimen]

/backport to stable30

[kesselb]

Hi, I find that, without additional context, a rather weird change. What problem did the customer run into? Also this pr changes only one write operation. If there's a problem, that non-utf-8-card-data must be sanitized, then it should happen in updateCard and createCard, no?

[ChristophWurst]

I agree. This doesn't seem right.

The job is a one-time migration, no? What about non-UTF-8 data that was already processed by the job? It won't be fixed.

How did non-UTF-8 end up in the cards table if PUTing cards validates for UTF-8 too? Manual inserts?

[gaudryc]

Hello,

I'm the customer who originally requested this fix.
I created this fix on Nextcloud 29.0.8 to address the issue #46100.
I tried to reproduce the original issue today without this fix, but without success.
I can confirm that you can ignore this fix since the issue #46100 has been resolved.

Best regards,
Chris

[szaimen]

Hello,

I'm the customer who originally requested this fix. I created this fix on Nextcloud 29.0.8 to address the issue #46100. I tried to reproduce the original issue today without this fix, but without success. I can confirm that you can ignore this fix since the issue #46100 has been resolved.

Best regards, Chris

Great, thank you for the feedback! Closing then :)