PayPal payment processed but no ticket sale showing up

What that sounds like, in the Report by Event, is a case where you deleted an event that had sales; is that possible? Did you have a test event you were working with for set up, but then deleted?

Regarding the payment: is that payment listed in Payments? Does it have the status of ‘Completed’?

If not, in your PayPal account, can you see that PayPal has attempted to send an IPN notification to your server in the IPN History?

Hi Joe

It’s possible that I did delete an event early with sales early on in developing the site. Would it be better for me to make a fresh start in that case?

Also, I’m using the ‘All In One WordPress Security & Firewall’ plugin. Have you had any feedback about that plugin causing problems in the past?

The payment is showing as ‘active cart’ and ‘pending’. The Paypal IPN history shows that it did attempt to send the IPN.

Many thanks

Did you trash the event, or delete it completely? If it’s still in trash, then its meta data isn’t deleted yet, which could be the problem.

I’m not *aware* of any problems due to All in One WordPress Security, but that’s far from definitive information…

In the PayPal IPN history, there should be an http code for the response received from your server. What is that code?

I’ve been trying to set up a regular monthly event. The event is almost the same thing every time, so I’ve been cloning the event page (via a plugin) to generate a new page and event shortcode. I’m not sure that I did empty the bin to get rid of the old page the first time I did that, but I did empty the bin before I tried it with Paypal.

The HTTP response code is 200.

Sounds like there’s something odd wrong, but I’m not sure exactly what it is. Cloning posts can have strange results sometimes, however, depending on whether or not the tool you used to clone also copied all the meta data. What did you use to clone the page?

I used this – https://www.ads-software.com/plugins/duplicate-post/

Duplicate Post does copy over all post meta data by default, which would include any already sold tickets. This would definitely have potential to cause problems, as you’d end up with ticket IDs that would come up in reports but wouldn’t actually exist.

It’s not really possible to exclude all My Tickets post meta using Duplicate Posts, because the meta data is dynamic.

Hi,
I’m the developer of Duplicate Post.
Just dropping by to say that if you want to enforce compatibility with my plugin, it’s quite easy using the action hooks described here:
https://www.ads-software.com/plugins/duplicate-post/other_notes/
If you need any further detail, feel free to contact me!
Bye!

Thanks, @lopo – I’m aware of that, and I’ve used it with another plug-in. The system here is a bit more complicated, though – I have no way of knowing in advance what the custom fields are called to be able to filter them, even using your custom hooks. I can look at it, but…not sure it’s something I can do anything about short of re-building the ticketing system – which would have some significant back-compatibility problems.

Duplicate Post does give me the opportunity to generate a new event ID and shortcode, and I assumed that would be ok, but there is other metadata that is being duplicated and I need to create a new post every time. Is that correct?

That’s what I would recommend. If your events have the same general event parameters, then you can set those parameters in settings and it will be automatically pre-filled, and then you won’t have that confusion in the meta data.