Configuração `Log anonymizer details` não anonimiza completamente nomes de usuário

zogstrip · 21 Janeiro , 2026 16:21

@Moin percebi que estava sendo muito negligente ao fazer a atualização

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

Tópico		Respostas	Vistas
User anonymization and staff_action_logs Product Support	6	818	9 Agosto , 2021
User still able to log in after anonymization Bug anonymization	3	232	26 Novembro , 2025
Username change logging even if it failed Bug	2	685	13 Maio , 2019
Profile links not updated after anonymizing an user? Product Support anonymization	0	148	5 Julho , 2021
Admins changing user's name (not username) should be logged Bug	4	870	22 Novembro , 2018

Configuração `Log anonymizer details` não anonimiza completamente nomes de usuário

Related topics