Support

October 27, 2016 at 11:36 pm

It may be completely unrelated, but I’ve also noticed that searching for the ticket name and filtering by “approved” in the backend produces an incorrect “x results found” string that seems to match the incorrect count in the database.

This is in spite of the number of actual results displayed being correct.

October 28, 2016 at 5:25 am

Here is a screenshot of the date times and ticket selectors for an event.

Here is a screenshot of the ticket sales numbers that have been counted using an sql query.

The default registration status is set to pending payment.

Apologies for obscuring the event name as I’m not sure performers would be too keen on us posting event data publicly.

The “holds” column in the first screenshot can be ignored, it simply stores a variable for our event report generator.

October 30, 2016 at 5:56 am

We have made a few small modifications to the core code.

– We have made a copy of the ticket_selector_chart.template.php, which is now hosted outside the core plugin folder. This should not affect ticket sale numbers, the customisations are entirely to do with the front end.

– We have made some modifications to <b>event-espresso-core-reg\caffeinated\admin\new\pricing\espresso_events_Pricing_Hooks_class.php</b> in order to give staff the ability to hide some events on the site’s front end. This involves the addition of two lines to _update_tkts:

$TKT_fronthide = isset( $tkt['TKT_fronthide'] ) ? $tkt['TKT_fronthide'] : 0;
$TKT->update_extra_meta( 'TKT_fronthide', $TKT_fronthide);

– We have added some customisations to store “holds” in the event meta for reports that we generate for clients. Our logged changes are:

in <b>caffeinated/admin/new/pricing/assets/ee-datetime-ticket-metabox.js</b>
under line <b>DTTeditform = $(DTTeditform).appendTo(DTT_row_container);</b>
added

DTTeditform.find('#event_holds-'+row).each( function() {
DTT_holds = $('#add-new-event-datetime-holds').val();
$(this).val(DTT_holds);
});


in <b>caffeinated/admin/new/pricing/templates/event_tickets_datetime_edit_row.template.php</b>
as a fifth column
added
<td class="event-datetime-column small-txt-column">
<input type="text" name="event_holds[]" id="event_holds-<?php echo $dtt_row; ?>" class="" value="<?php global $post; echo get_post_meta( $post->ID, 'event_holds_'.$dtt_row, true ); ?>" style="width: 40px;">
</td>

in <b>caffeinated/admin/new/pricing/templates/event_tickets_metabox_main.template.php</b>
as part of table <b>#add-new-event-datetime-table</b>
added
<td class="event-datetime-column holds-column" style="display: none;">
<label class="" for="add-new-event-datetime-holds"><?php _e('Holds', 'event_espresso'); ?></label>
<input type="text" name="add_new_datetime_holds" id="add-new-event-datetime-holds" class="ee-numeric ee-small-text-inp">
</td>

The rest of the code for that functionality is stored in a custom plugin and only touches the post_meta for the event, it doesn’t modify or interact with the EE tables in the database.

The SQL I’ve used to generate those numbers in the second screenshot is:
SELECT COUNT(REG_ID) FROM wp_esp_registration WHERE TKT_ID = " . $ticket->ID() . " AND STS_ID = 'RAP'

I realise the result from that query may not be entirely accurate, but it’s a stopgap measure which closer matches the ticket sales we’ve manually counted.