[Ben]

Apologies – I thought I was replying to another thread. Essentially this seems like a massive oversight.

– Once I delete a ticket from an event a record still exists somewhere for it and is displayed to a logged in user
– Once I delete an order in woocommerce for the ticket, a record still exists for the ticket and is displayed to the front end user
– The user with the non existent ticket can still scan their QR code on entry which returns an error
– All of the associated data with the an event (like how many people have responded, or purchased) is now incorrect by the number of deleted tickets in the back end
– Logged in users have no way of seeing their ticket history outside of an email
– Accounting tickets (sold versus tickets refunded) no longer match

I could go on and on but I am slightly afraid of what I’ll find. I was hoping to use this in a production environment for a major UK brand but I think this might have killed that idea.

/*edit*/

Actually – this is cached data. Clearing cookies solves the display issue (though not the data mis-match issue). Just an FYI.

• This reply was modified 9 years, 6 months ago by Ben.

[Ben]

I have been addressing these issues and there is a problem when the user navigates away to cart (in woocommerce) or another page if they hit the back button. The qty input field isn’t reset to zero so the jquery that reveals the form and the standard html5 error checking for whether the form is filled in never fires. The end result of that is that the add to basket button can be submitted without any data being collected. This could be handled in a session cookie but is currently not handled at all.

*edit*

I am also seeing this JS error when I navigate back to event page:

‘An invalid form control with name=’tribe-tickets-meta[85][1][first-name]’ is not focusable.’

• This reply was modified 9 years, 6 months ago by Ben. Reason: error report

[Author]

Posts