Open-event-frontend: Tickets that are unpaid are showing up as placed. Expected: Should show up as "Pending" and Expire after 1 day

Created on 3 May 2019  ยท  20Comments  ยท  Source: fossasia/open-event-frontend

Tickets that are unpaid are showing up as placed. Expected: Should show up as "Pending" and Expire after 1 day.

This issue shows in

Screenshot from 2019-05-03 16-48-22

bug

Most helpful comment

Expected is:

  1. Ticket orders that use online payment methods (credit card, paypal) should be labeled as "pending" until they are paid and expire after 1 day.
  2. Ticket orders that use offline payment methods (bank, cheque) should be labeled as "Placed" once the user has hit the button "order". These user need to pay offline. This is only the case if the organizer has specified offline payment.

All 20 comments

@shreyanshdwivedi Can you take care of this as well in you PR regarding open orders?

@kushthedude this issue requires proper implementation as the unpaid tickets are required to expire after 1 days. So, I'll suggest that we should keep both the PRs separate.
I'm a bit busy this week so if you want you can take it up and open a separate PR for this issue.

@shreyanshdwivedi Cool i will look into it

Expected is:

  1. Ticket orders that use online payment methods (credit card, paypal) should be labeled as "pending" until they are paid and expire after 1 day.
  2. Ticket orders that use offline payment methods (bank, cheque) should be labeled as "Placed" once the user has hit the button "order". These user need to pay offline. This is only the case if the organizer has specified offline payment.

Noted @mariobehling , Will do as expected ๐Ÿ˜„

@kushthedude We can make this a scheduled task handled at server side. How about I take this up on server side?

@uds5501 not sure what @mariobehling and @CosmicCoder96 want, but if they agree. You may go on server side and i will take care here

@kushthedude can I take over?

@uds5501 did half work , will be pushing soon ,๐Ÿ˜…

Oh, can I take care of the state change part on the backend? @kushthedude

Oh, can I take care of the state change part on the backend? @kushthedude

Just a question, Is there really need to handle it on backend , Cant we do all on frontend ?

Just a question, Is there really need to handle it on backend , Cant we do all on frontend ?

@kushthedude How will you set the status to expired automatically after a day on the frontend?

Cool , ๐Ÿ‘ Go on

@kushthedude your PR is awaited

@kushthedude The PR will get merged, already approved. But it won't affect your PRs though, so you may push em whenever you feel like it :smile:

Cool ,

On Wed, 15 May 2019 at 11:00 PM, Uddeshya Singh notifications@github.com
wrote:

@kushthedude https://github.com/kushthedude The PR will get merged,
already approved. But it won't affect your PRs though, so you may push em
whenever you feel like it ๐Ÿ˜„

โ€”
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-frontend/issues/2852?email_source=notifications&email_token=AKQMTLQT6BACLMIGFTHZ6SLPVRCFBA5CNFSM4HKSGD42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVPMBCY#issuecomment-492748939,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKQMTLW2RQAN3CPQK33UATLPVRCFBANCNFSM4HKSGD4Q
.

@kushthedude The PR has been merged at the server side, please push your PR here

Half of work is done , but i wont be able to push the pr today .

On Fri, 17 May 2019 at 11:08 AM, Uddeshya Singh notifications@github.com
wrote:

@kushthedude https://github.com/kushthedude The PR has been merged at
the server side, please push your PR here

โ€”
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fossasia/open-event-frontend/issues/2852?email_source=notifications&email_token=AKQMTLQ3OZVUKUXBGMQN6LLPVZAGTA5CNFSM4HKSGD42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODVTZC3Y#issuecomment-493326703,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKQMTLQRVTZ4B7ATME7KAVLPVZAGTANCNFSM4HKSGD4Q
.

Irrelevant now, default status has been changed to pending.

Was this page helpful?
0 / 5 - 0 ratings