mirror of
https://github.com/glenndehaan/unifi-voucher-site.git
synced 2026-05-09 08:25:29 +02:00
[GH-ISSUE #91] Add additional information to the list of vouchers #48
Labels
No labels
bug
enhancement
pull-request
question
question
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/unifi-voucher-site#48
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?
Originally created by @koles142 on GitHub (Aug 27, 2025).
Original GitHub issue: https://github.com/glenndehaan/unifi-voucher-site/issues/91
Originally assigned to: @glenndehaan on GitHub.
The feature
Hi,
It's possibile to add information about sent voucher by mail to the list of vouchers near voucher code, notes etc? Example: "sent by email to: {email address}".
Problem to solve: two or more persons working with sending vouchers via email to the guest before they arrive. After generate voucher and sent by first person second have no information about that was sent and to which guest.
Thank you
@glenndehaan commented on GitHub (Aug 27, 2025):
Hi @koles142,
Unfortunately this is not possible in the current architecture of the app.
See I only have a direct connection to UniFi as a source of data, and yes there is a notes field that I have already mis-used to add additional metadata to a voucher. The problem here is in the update phase, a voucher once created within UniFi has no edit function, only a revoke function. So there is no way for me to update the notes field (metadata) to add data after creation. And since email sending happens after generation (since we first need a code before we can send an email, therefore a catch 22) there is no way for me to store the data somewhere.
So at this time it is just not possible, I am working on a High Availability feature that would utilize Redis as a global datastore but I don't expect this soon since it would also complicate the setup for others.
Kind regards,
Glenn de Haan