Padreug
72b9c540f7
Some checks failed
lint.yml / feat: per-event organizer name + reply-to on ticket emails (pull_request) Failing after 0s
Each organizer is different, so the sender identity of ticket emails is now per event rather than per instance: - `extra.organizer_name` → From display name "Organizer via <site title>" (site title alone when unset). The From address stays the instance mailbox — that is what DKIM signs — so this costs nothing in mail auth. - `extra.reply_to_email` → Reply-To; blank falls back to the email on the LNbits account that owns the event wallet; no header when neither exists. When a reply-to exists the body says "Questions? Reply to this email and it reaches <organizer>", and "Organizer: <name>" is listed with the ticket details. Both fields sit next to the existing per-event subject/body in the admin dialog. The organizer's own wording (in whatever language) remains `notification_body`. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EYwoAkZZmXMMmaBp4WGUBo
5.9 KiB
5.9 KiB
Upstream PR candidates
Running log of fork features that are shaped so they could be offered to
lnbits/events (or lnbits/lnbits). Add a row whenever a change lands here
in an upstream-compatible form; strike it when the PR merges upstream.
| Feature | Where | Upstream target | Readiness |
|---|---|---|---|
frontend_url + origin allow-list + ?checkout= return contract |
views_api.py _resolve_frontend_root, api_ticket_create |
lnbits/events | after the #33 rebase, as a small PR |
Ticket ids minted before the invoice so success_url can carry them |
api_ticket_create |
lnbits/events | ships with the above |
extra.checkout (success/cancel URL, customer_email, line item, metadata) on fiat purchases |
api_ticket_create |
lnbits/events (needs lnbits StripeCheckoutOptions.cancel_url/customer_email, PR'd from aiolabs/lnbits) |
with the lnbits patch |
extra.payment_methods per event + tickets_payment_methods NIP-52 tag |
models.py, nostr_publisher.py |
lnbits/events (v2 PR #64 introduces the same field) | offer as review input on #64 |
asyncio.to_thread around the smtplib send |
services.py _send_ticket_email_notification |
lnbits/events | trivial, standalone |
QR logo overlay in make_qr_png (instance lnbits_qr_logo) |
views_api.py |
lnbits/events | standalone |
Multi-ticket purchase as N rows on one payment_hash |
api_ticket_create, crud.py |
lnbits/events | overlaps v2 baskets; review input on #64 |
| Free tickets without minting an invoice | _issue_free_tickets |
lnbits/events | small, standalone |
| NIP-52 publishing + approval workflow | nostr_*.py, views_api.py |
lnbits/events #46 | open; rebase onto v1.6.8 |
Date + Message-ID + From display name on the ticket email (build_ticket_email); event details in the body |
services.py |
lnbits/events (mailer) and lnbits/lnbits send_email (same omissions, hits password-reset/admin mails) |
trivial, standalone — measured: SpamAssassin MISSING_DATE 1.4 + MISSING_MID 0.14 |
Ticket card PNG (event/when/where/QR/name/id) attached to the ticket email instead of a remote <img> (qr.py, GET /api/v1/ticket-card/{id}) |
qr.py, services.py |
lnbits/events (their "ticket image" compositing could reuse the renderer) | standalone; mail-tester: removes HTML_IMAGE_ONLY (1.8) |
Per-event sender identity: extra.organizer_name (From display name "X via ") + extra.reply_to_email (Reply-To, falls back to owner account email) |
models.py, services.py, admin dialog |
lnbits/events | small, standalone |