Closed deleted users still show in resource message body

That is expected - post content is not edited and saved when changes are made to member accounts.
 
Thats technically logical. Yet, the law requires website admins to remove such PII data if it exists.
 
Brogan said:
Neither is 0815.
Click to expand...
In this case the username is probably not PII, but in many cases it is considered PII by GDPR legislation. it would be nice if upon account deletion there would be a way to know that the username exists in post content and possibly an automatic way to clean it up.
 
It's easy enough to do if you need to do it...

add the username to ACP>Options>Censoring
then add: 'Deleted member <number>' to the Replacement field
 
Yes, I know, and if you add the original username to the censor and add 'Deleted member <number>' to the Replacement field it will replace the original username throughout the forum where ever it shows.
 
Automated triage: As designed

Thank you for reporting this issue. The opening post of a resource discussion thread is written once, with the author's name as it was then. Deleting or renaming an account updates the author shown on content but does not edit the text of existing posts, so names already written into a message stay as they were.

This is an automated assessment. A member of staff may review and update it.
 
XF Bug Bot said:
Automated triage: As designed

Thank you for reporting this issue. The opening post of a resource discussion thread is written once, with the author's name as it was then. Deleting or renaming an account updates the author shown on content but does not edit the text of existing posts, so names already written into a message stay as they were.

This is an automated assessment. A member of staff may review and update it.
Click to expand...
Its a weird explanation. Is this an LLM formulating an answer and classifying the bug report? I ask because the rejection reason the bot gives is the issue to fix.
 
I mean it's classifying it correctly. There's not a bug here, it's behaving as designed. In the same way as quotes aren't updated with names and so on. Sometimes a bug that is as designed will be rejected with a simple restatement of what the current behaviour is, because that's the designed behaviour.

On this occasion this is better posted as a suggestion.

As a bit of advice, you can essentially avoid this entirely for future resources if you modify the xfrm_resource_thread_create phrase which, by default is:

Code: 
{username} submitted a new resource:

[url={resource_link}][plain]{title}[/plain][/url] - [plain]{tag_line}[/plain]

[quote]{snippet}[/quote]

[url={resource_link}]Read more about this resource...[/url]

But changing it to the following (or similar) would remove the username entirely.

Code: 
A user submitted a new resource:

[url={resource_link}][plain]{title}[/plain][/url] - [plain]{tag_line}[/plain]

[quote]{snippet}[/quote]

[url={resource_link}]Read more about this resource...[/url]

You could probably regex out the current usernames in existing content if it matters enough.
 
A comment system would be the optimal fix IMHO. :p Then no duplication in a thread would be needed.
 
Back
Top Bottom