Implement logging of disabled registration
Open, Needs TriagePublic
Actions

Assigned To

None

Authored By

	ifried
	Sep 20 2022, 1:49 PM

Description

NOTE: Can we log both enabling AND disabling? This would give more useful information to users.

As a wiki user or admin, I want to be able to access logs of disabled registration, so that I can monitor for bad actors or unexpected activity that may require further investigation.

Acceptance Criteria:

We would be logging to Special:Log
Ideally, we would want a list of disabled registrations, which can be filtered by the user who disabled the registration
Note that logging is per-wiki and not global in terms of what users can see in Special:Log, and that's okay because that is the current experience. However, what happens if user disables registration via MyEvents on one wiki but the event is on another wiki? Ideally, the behavior should be that the disabling is logged on the wiki where the event page lives --> let's explore options for this

Related Objects
Search...

Status	Assigned	Task
Open	None	T321018 Implement logging of registration enabled
Open	None	T321833 [EPIC] Logging of event registration activity
Open	None	T318412 [EPIC] Restore disabled registration
Open	None	T318160 Implement logging of disabled registration

Event Timeline

ifried created this task.Sep 20 2022, 1:49 PM

Restricted Application added a subscriber: Aklapper. · View Herald TranscriptSep 20 2022, 1:49 PM

ifried mentioned this in T315080: Investigation: Allow deleted registration to be restored.Sep 20 2022, 1:51 PM

ifried moved this task from Backlog to To be Estimated/Discussed on the Campaign-Tools board.Sep 21 2022, 3:44 PM

ifried updated the task description. (Show Details)Sep 21 2022, 5:41 PM

ifried updated the task description. (Show Details)

ifried updated the task description. (Show Details)Sep 21 2022, 5:45 PM

ifried added a parent task: T318412: [EPIC] Restore disabled registration.Sep 23 2022, 1:05 PM

Adding the link to the manual of how to implement Logging to Special:Log on an extension:
https://www.mediawiki.org/wiki/Manual:Logging_to_Special:Log

We would need answers to the following questions to determine the complexity of this task, or in general to actually implement it:

Name of the log (first selector on Special:Log)
- I would suggest using a generic name here, and then having subtypes, see T321018#8334107.
Who should be able to view this log? Should be public unless there are good reasons against it.

However, what happens if user disables registration via MyEvents on one wiki but the event is on another wiki? Ideally, the behavior should be that the disabling is logged on the wiki where the event page lives

It's logged on the "other" wiki. We can add this to the list of cons of a central DB...

ifried moved this task from V1 (MVP) to Jan-June 2023 on the Campaign-Registration board.Oct 27 2022, 3:57 PM

ifried added a parent task: T321833: [EPIC] Logging of event registration activity.

Yes, I think the log should be public.

I'm trying to learn more about how logs are structured/named. Would the expected hierarchy be that we have a general category (like event registration) with actions to monitor (such as enable, disable, restore, participant registers, etc)? For example, I see the deletion log lets you filter by type of deletion.

Do we need approval from anyone to add a new log type to Special:Log?

ifried mentioned this in T322657: Investigation: Can we display event registration actions in event page history?.Nov 9 2022, 1:33 PM

DerHexer subscribed.Nov 13 2022, 5:08 PM

ifried moved this task from To be Estimated/Discussed to Backlog on the Campaign-Tools board.Nov 30 2022, 8:23 PM

Daimona moved this task from Backlog to New functionality on the CampaignEvents board.Nov 10 2023, 6:25 PM

Daimona mentioned this in T362365: Event registration should not be disabled when a translation page is deleted.Apr 11 2024, 9:55 PM