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

Front End Report With Stripe #117

Open
elanasparkle opened this issue Jul 20, 2021 · 8 comments
Open

Front End Report With Stripe #117

elanasparkle opened this issue Jul 20, 2021 · 8 comments
Labels
bug Something isn't working
Projects

Comments

@elanasparkle
Copy link
Collaborator

Can use Frontend report if payment is processed first

Name | Front End Stripe
Reporter | Elana D.
Submit Date | 7/20/2021
Summary | When the frontend report is enabled then stripe payment processed the form doesn't display and produces the below error.

image

@elanasparkle elanasparkle added the bug Something isn't working label Jul 20, 2021
@avonville avonville added this to Info / Awaiting Triage in BACKLOG Jul 29, 2021
@avonville avonville moved this from Info / Awaiting Triage to Prioritized Backlog in BACKLOG Oct 19, 2021
@avonville avonville moved this from Prioritized Backlog to In Progress in BACKLOG Oct 19, 2021
@avonville avonville added this to the 1.6.10 milestone Oct 19, 2021
@avonville
Copy link
Collaborator

@elanasparkle We don't really want to show frontend reports for payments? Is this something that a customer is asking for? what would be the use case where we would want to show payment data to anyone that submits the form?

A possible feature would be to make a donation report that said how much has been donated if that is something customers would use.

@elanasparkle
Copy link
Collaborator Author

@avonville This isn't a front-end report for payments. This is the front-end report option in the settings.

image

To reproduce: Enable front-end reports in the settings then add a payment method on the form. Payments successful or failed it doesn't redirect to the frontend report afterward.

@avonville
Copy link
Collaborator

Yes I know what the frontend report does, it shows the entry data for that form. So for instance if it did work...

image

It would show a report of all the entries with this data. What I am asking is what is the use case for them having a frontend report when using that form for payment.

@avonville
Copy link
Collaborator

We should loop harry and tony in on this and get their thought to see how we want to move forward.

@harryjackson1221
Copy link
Contributor

Your screenshot shows a payment and amounts, and that front end report should show the information you have in your screenshot. The current issue is that if stripe is used, said report is not working. Can you elaborate on what you are saying please? @avonville

@avonville
Copy link
Collaborator

avonville commented Nov 17, 2021

So the payment is the last piece that happens in the submission process. So the front-end report is running before the payment redirect is done. Furthermore, stripe checkout redirects and dies to a specific URL that is set. So if we were to have the frontend report run it would have go within the payments addon when a payment is enabled.

I still don't see a use case that has been brought up to where a customer is going to want people to see the payment information of all individuals that have submitted the form.
@harryjackson1221

@avonville
Copy link
Collaborator

In addition to what I said in the previous comment, I believe that the frontend report option should be disabled when a payment processor is enabled.

@harryjackson1221
Copy link
Contributor

It should redirect to the report after payment is made. If we want to add the payment info, we can do that later but for right now the error should not show when payment info is enabled. @avonville

@avonville avonville removed this from the 1.6.10 milestone Nov 19, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
BACKLOG
  
In Progress
Development

No branches or pull requests

3 participants