Support

May 30, 2024 at 1:36 am

The two ticket you shared seems expired, can you shoot video for us using loom?
https://loom.com/

Were you able to add this in your wp-config?

// Enable WP_DEBUG mode
define( 'WP_DEBUG', true );
if ( WP_DEBUG ) {
        @ini_set( 'display_errors', 0 );
        define( 'WP_DEBUG_LOG', true );
        define( 'WP_DEBUG_DISPLAY', false );
}

If yes, then do the following.
1. upgrade first your plugin to our latest version
2. then, go to your debug log (domain/wp-content/debug.log) and make sure it is cleared.
3. Shoot a video for us, showing the bug you experience.
4. Grab the log generated and paste it here. You can find that in your domain/wp-content/debug.log

If debug log is not enable, please enable it and skip #2

After these step, you can also check if there’s plugin conflict.
You can use https://wordpress.org/plugins/health-check/ or any similar plugin.

You can do the above using Troubleshooting mode:

Tools -> Site Health -> Troubleshooting -> Enabled Troubleshooting mode.

That will disable all plugins and switch to a default theme and then allow you to enable specific plugins troubleshooting mode. Once disabled you will revert back to the current state.

Let us know what happen afterward.

thanks

June 6, 2024 at 7:54 am

Hi there,

Firstly, my apologies for not updating your previous thread. I have no idea why there’s no update in that thread but I remember discussing your site at length with our developers and I’m fairly sure I wrote a reply…. regardless, it’s not there so I guess I didn’t hit post and threads will automatically close with no recent replies.

—

So the problem here is that some of your events have tickets assigned to them that don’t have a valid price object in the database.

I’ll give you an example for an event that is more it in the future so that it stays active. Event ID – 14423 on your site.

When editing that event I notice it has multiple datetimes and straight out the gate can see that ticket has only been assigned to 1 of those, that shouldn’t be possible through the UI as every DateTime should be assigned to at least 1 ticket. That isn’t directly related to this issue but shows that ‘something’ is up here.

See how the ticket has no price? EE would normally show a free ticket with a value of 0.00 but here its blank, that again shows me something is wrong here.

So from there I check the Ticket ID and it’s 710 (click the cog icon and you’ll see it in the advance menu or the ticket). The next steps need to be check in the database… so that’s where we go next.

Tickets are assigned prices and we save the Ticket and Price ID in a table called esp_ticket_price, it lets EE pull in all related price objects related to a specific ticket (for your setup thats 1 object, but there can be many price objects on a ticket depending on the pricing structure, hence the table).

Thats here: https://monosnap.com/file/n1fvrbxqHUGh5wQoAs928Sj08NpW0H

So here we can see TKT_ID relates to a PRC_ID (Price ID) of 681

Here we go to another table called esp_price to find the specific price object for the ticket, that’s here: https://monosnap.com/file/XDkko6oqUG3jhhISMHVEyNRxVSvw3e

This is where things get strange. Prices have types, they can be a base price, a percentage, tax etc but they always have a ‘type’ and those types apply in specific ways. For your setup your price type should be a base price and that would be indicated by a PRT_ID (Price Type ID) of 1… but notice how it’s 0? Thats a price with no price type at all. The other clue is no PRC_name, I included a few other rows in that pic to show you ‘correct’ prices, so PRC_ID 678 and 677 would be ‘valid’ prices and give an example of an event where the notice would work.

Whats happening is the Add to cart function is being passed the ticket and its trying to build out the ‘line items’ that apply to the transaction from that, one of those steps is to pull in the Price assigned to the ticket, pull in its price_type and use the name from the price type as part of the line item. As mentioned above with a PRT_ID of 0 there is now price type (not expect) and it throws a fatal error, thats why you get a blank notice.

So the error being thrown is:

PHP Fatal error:  Uncaught Error: Call to a member function name() on null in /wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Line_Item.helper.php:391
Stack trace:
#0 /wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Line_Item.helper.php(178): EEH_Line_Item::create_ticket_line_item(Object(EE_Line_Item), Object(EE_Ticket), 1)
#1 /wp-content/plugins/event-espresso-core-reg/core/EE_Cart.core.php(265): EEH_Line_Item::add_ticket_purchase(Object(EE_Line_Item), Object(EE_Ticket), 1, false)
#2 /wp-content/plugins/event-espresso-core-reg/modules/ticket_selector/ProcessTicketSelector.php(370): EE_Cart->add_ticket_to_cart(Object(EE_Ticket), 1)
#3 /wp-content/plugins/event-espresso-core-reg/modules/ticket_selector/ProcessTicketSelector.php( in /wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Line_Item.helper.php on line 391

The code in question is $price_desc = $price->desc() ? $price->desc() : $price->type_obj()->name();

But that code is a symptom of the cause rather than the problem in itself.

—-

How were these events created? There’s a few discrepancies in the database ID’s that I wouldn’t expect for ‘normal’ events, for example in esp_ticket_price, Ticket ID’s are higher than the TKP_ID rows…

TKT_ID 710 has row 707
TKT_ID 711 has row 679

So ticket 711 was create BEFORE 710?

This is going to be tricky to fix, not impossible but I’m trying to figure out how it got to this point so a proper fix is made rather than just updating the rows and then it’s still happening moving forward and we go through this again in X months.