Protokollierungslücke für Gruppenverläufe

martin · 4. Februar 2026 um 06:21

Entschuldigung, dass dies eine Weile gedauert hat, es kamen andere Prioritäten dazwischen. Ich habe jetzt einen PR zur Überprüfung freigegeben, es sollte nicht mehr lange dauern:

github.com/discourse/discourse

FIX: Logging hole in group user histories and convert group create to service (#37054)

main ← issue/group-logging-hole-and-refactor

opened 03:57AM - 12 Jan 26 UTC

martin-brennan

+501 -25

When creating groups, we weren't logging the group owner as being the owner in …group histories, nor were we logging them being added to the group. So it was not clear in the user logs where this user ever came from. This PR fixes the issue, and also converts the admin group create endpoint to use a service. Now the logs look like this when a group is created: <img width="830" height="378" alt="image" src="https://github.com/user-attachments/assets/871e319a-5512-411e-8565-3b63803e688c" /> c.f. https://meta.discourse.org/t/logging-hole-for-group-histories/392942

Thema		Antworten	Aufrufe
New logging functionality: delete/add group Feature	0	403	6. August 2019
Logs for users added to groups Feature groups	0	36	11. Februar 2025
Add group owners to manage group membership Site Management groups , how-to	0	11757	2. Dezember 2015
Adding owners/members UX is inconsistent and misleading UX	26	3029	20. April 2018
"You cannot allow membership requests without any owners." UX	3	1116	5. April 2023

Protokollierungslücke für Gruppenverläufe

Verwandte Themen