Allow LNbits admin to edit another user's event #22
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
The events extension admin index has an All Users' Events card (admin-only) that lists every event across every wallet. Today it's read-only — the admin can see proposed/rejected/canceled events from other organizers but can't act on them beyond the existing
approve/reject/cancelcontrols.A follow-up to PR #19, which made cross-tenant ownership visible by adding the
Ownercolumn.Ask
Let the LNbits admin edit another user's event from the admin UI:
allow_fiat,auto_approve, etc.)Today the
PUT /events/{event_id}endpoint is gated onrequire_admin_keyfor the event's wallet. An LNbits-level admin holding their own wallet's admin_key can't edit because the event belongs to a different wallet. Either:check_admin), orPUT /events/admin/{event_id}gated bycheck_admin) that bypasses the wallet check.The republish-to-Nostr side already handles "admin reaches into other users' events" — see
republish-all— so the precedent exists.Why
Today an organizer who needs to fix a typo, postpone, or cancel an event must do it themselves. If they're unreachable, the LNbits admin has no recourse besides approving/rejecting the existing record. This blocks normal moderation flows (typo fix, contested cancellation, etc.).
Notes
useActivityDetail"isMine" gate hides Edit from non-owners. An admin-level "isAdmin" override needs to be threaded through.last_edited_by_user_idon admin-edited rows so the event-owner can see "an admin edited this on YYYY-MM-DD" rather than silent override.