-
Notifications
You must be signed in to change notification settings - Fork 488
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature Request - print ticket and ..! #1153
Comments
Hi @ZEROF, we're working on this feature as part of this year Google Summer of Code Also see these PR: which we plan to merge the next few days. For more information, you should contact @rishabhs95 (our GSoC student) or @lagartoflojo (mentor). Stay tuned :) |
@lagartoflojo @rishabhs95 did we cover sth of this in your GSoC project? If yes please update and close! |
@ChrisBr no, we didn't do anything about printing tickets. That's definitely something we can improve upon. Right now, you pay for a ticket and you still get the same email message we always had. |
Yes, so you can pay for the tickets via stripe and after a successful payment, Stripe will send you an email confirming the received payment. |
This is now implemented in OSEM as part of @siddhantbajaj GSoC 2017 project #1600 |
Hi,
I don't know if some payment system can be used with OSEM; but it will be nice (for now) if user can print ticket and that ticket can have few information in conf logo/conf name/ticket type/date/user name/ and qr code (ticket can be scanned) and in the end admin can set date when user(s) can download ticket(s), this option is good if user will send bank transfer or something like that, that give them week or two to do that, and orga team to check if payment is made. Setting ticket download date can be made as global option, for all users, not user by user. I say this, because if you have 1000 people on your event, it will be real mess for admin to keep trace.
I used this options with other ticket system (c4sh, not public anymore), and for orga team is very good to have this feature(s).
Thanks for GJ!
The text was updated successfully, but these errors were encountered: