Testing out embedding Pretix in AMY#2985
Draft
maneesha wants to merge 6 commits into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@pbanaszkiewicz As discussed, this PR begins to try to embed Pretix in AMY. I will share credentials with you tomorrow.
For now, you can run AMY locally with this PR and log in as an active user and go to
/dashboard. You will see the embedded widget at the top of the page with a list of dates. Select any date and use the voucherabcde. This now takes you to an external page to continue registration. The email and attendee name are automatically filled in from the AMY profile. This is the step we'd like to keep within AMY. This will help integrate the profile creation form questions with event registration questions and integrate event registration with AMY event tasks.You can see some cors headers settings I tried changing with @froggleston. I commented those back out because they weren't working but I wanted you to see them.