Skip to content
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

Mandatory fields do not let you buy a ticket #561

Closed
icougil opened this issue Dec 10, 2018 · 4 comments
Closed

Mandatory fields do not let you buy a ticket #561

icougil opened this issue Dec 10, 2018 · 4 comments
Labels

Comments

@icougil
Copy link

icougil commented Dec 10, 2018

Describe the bug
It is not possible buy a ticket if you added few mandatory fields to fill

To Reproduce
Steps to reproduce the behavior:

  1. Create mandatory fields
  2. Go to the main site and select a ticket
  3. Click on I don't know yet who will attend the event
  4. Scroll down to the payment process
  5. You won't be able to continue and pay your ticket :-(

Expected behavior
Continue the process if the user wants to pay and include the mandatory information later on

Screenshots
N/A

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
Alf.io v.1.17-SNAPSHOT

@syjer syjer added the bug label Dec 10, 2018
@syjer
Copy link
Member

syjer commented Dec 10, 2018

Hi @cougil , you are right, it's a bug that will be fixed .

As a work around you can enable the following option:

2018-12-10

@icougil
Copy link
Author

icougil commented Dec 11, 2018

Hi @syjer
Thank you for your suggestion. We will enable this option in order to make the data mandatory... but as you can imagine it is not the best way to solve this :-/
Do you have an idea about how difficult will be to fix it? I mean, I remember it was something already detected in previous versions, wasn't it?
Best,

@cbellone
Copy link
Member

@cougil should be fixed now. Can you please confirm that this solves the issue?
Thank you.

I mean, I remember it was something already detected in previous versions, wasn't it?

I checked with @syjer and we don't recall a similar problem. I also checked the file history and couldn't find anything related.
If you've a specific resolved issue in mind, can you please mention it so that we can keep track of the regression, if any?

Thanks,
Celestino

@icougil
Copy link
Author

icougil commented Dec 16, 2018

Hi @cbellone !
I've tested and it seems that it is working right now! Thank you very much! ;-)
About the issue I was thinking it was already shared. In fact, I thought I did raised it time ago, ... but I didn't ;-) I think it was this one the one I was referring, and it is not exactly the same thing that we are discussing here.
So thank you once again ;-)

cbellone added a commit that referenced this issue Dec 30, 2018
(cherry picked from commit 2cf0c24)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants