Impostazione `Log anonymizer details` non anonimizza completamente i nomi utente

zogstrip · 21 Gennaio 2026, 4:21pm

@Moin ho notato che ero troppo permissivo durante l’aggiornamento

github.com/discourse/discourse

FIX: Only anonymize staff log fields that contain the username

main ← fix/anonymizer-selective-field-replacement

opened 04:19PM - 21 Jan 26 UTC

ZogStriP

+19 -4

Follow-up to 1fd17242d1. The previous implementation replaced all four UserHi…story fields (context, details, previous_value, new_value) whenever any one of them contained the username. This caused confusing output in the staff action logs UI - for example, a "check email" action that only had the username in the context field would display: New: [removed due to user anonymization] Previous: [removed due to user anonymization] [removed due to user anonymization] ...even though those fields were originally empty. Now each field is updated independently using SQL CASE expressions, so only fields that actually contain the username get replaced. Fields with unrelated content or nil values are preserved. This keeps the anonymization effective while avoiding the cluttered display. Ref - https://meta.discourse.org/t/-/387500

Argomento		Risposte	Visualizzazioni
User anonymization and staff_action_logs Support	7	707	Settembre 8, 2021
User still able to log in after anonymization Bug anonymization	4	76	Novembre 30, 2025
Username change logging even if it failed Bug	3	589	Maggio 13, 2019
Admins changing user's name (not username) should be logged Bug	5	746	Novembre 22, 2018
Anonymizing user keeps email address and real name when "full name required" is on Bug	22	4202	Marzo 19, 2016

Impostazione `Log anonymizer details` non anonimizza completamente i nomi utente

Argomenti correlati