Support

November 19, 2024 at 5:39 am

Have you heard back about this question? We’d also like to modify the “Event Espresso” link in the admin toolbar… our client is very pick about ordering.

Currently you can’t filter those URLs, not the overview or admin toolbar menu (we’ll technically you can with the admin bar but you would need to use the admin_url WordPress hook and it’s applied everywhere.

Additionally, is there any way to adjust the query used on the overview page? We’d like to exclude a specific category unless it’s explicitly selected.

Yes, and actually you would be better using that to filter the default covering and leave the URL’s as they are.

The hook to filter the query is FHEE__Events_Admin_Page__get_events__query_params

To change the default ordering you can do something like this:

https://gist.github.com/Pebblo/833a66cc6a191b7df99a72b53727a01f

(Remove the snippet I get you above HERE)

If you change the default ordering that will apply to all locations when no additional filtering is set.

1. The filters on the “Overview” page don’t seem to be working correctly; for “Select a Month/Year” we only see “September 2025,” but there are many events in other months.

Hmm, strange.

Have those events been published?

Is this with no other filters applied?

2. Is there any way to sort by a date range? If you can point me to the hooks, I can implement this myself.

A filter to add an additional filter for a range to apply?

If so there’s a dynamic filter for this:

$filters   = apply_filters(
    "FHEE__{$classname}__filters",
    $this->_get_table_filters(),
    $this,
    $this->_screen
);

For the EE event list table the hook name would be FHEE__Extend_Events_Admin_List_Table__filters.

You can apply the values to the query using the same filter from above FHEE__Events_Admin_Page__get_events__query_params.

3. Is there any way to allow searching in the dashboard to include searching by venue?

Yes, you’d use with the same filter above or FHEE__Events_Admin_Page__get_events__where which is applies specific to the where conditions right before the other filter:

$where          = apply_filters('FHEE__Events_Admin_Page__get_events__where', $where, $request_params);
        $query_params   = apply_filters(
            'FHEE__Events_Admin_Page__get_events__query_params',
            [
                $where,
                'limit'    => $limit,
                'order_by' => $orderby,
                'order'    => $order,
                'group_by' => 'EVT_ID',
            ],
            $request_params
        );

Either of those can be used to add additional conditions when searching.

November 25, 2024 at 3:46 am

Sorry, I assumed you’d reviewed our model system previously so I didn’t provide details on using them.

For this…

In FHEE__Events_Admin_Page__get_events__where, how can I specify “NOT IN” or “!=”? I want to query for all events that are not in a specific category, but I can’t figure out how to do this.

You need to review this doc:

https://github.com/eventespresso/event-espresso-core/blob/master/docs/G–Model-System/model-query-params.md#different-operators

In short this:

"Term_Taxonomy.operator" => "NOT IN", // this leads to an error

.operator doesn’t exist on the EE models, you pass it as part of the term_id parameter itself:

"Term_Taxonomy.term_id" => ['NOT_IN', [869]],

(NOT_IN expects an array of values, even just 1)

Side note – your code is currently completely replacing ALL values of WHERE with the code to just exclude the category, meaning if anything else is set it’ll be replaced/ignored.

Similarly for the venue filtering, I just don’t understand how your hooks work. Can you provide me an example of how I’d filter the results using the FHEE__Events_Admin_Page__get_events__where hook?

I’ll need more details on what you doing with venues to give you an example. However, the best example I can give you here is to point you to how the current filters work.

If you search our codebase for FHEE__Events_Admin_Page__get_events__where you’ll find where that filter is applied, it’s in \event-espresso-core-reg\admin_pages\events\Events_Admin_Page.core.php.

Within that class you’ll see this code for filtering by Venue:

// filter events by venue.
$venue = $this->request->getRequestParam('venue', 0, DataType::INT);
if ($venue) {
    $where['Venue.VNU_ID'] = $venue;
}

If a venue (ID) is set pass that to the model for the related Venue.VNU_ID.

All of the model query params work in the same way so once you follow how those params work you can apply it to pretty much every model/query you want… without in-depth knowledge of the joins going on in the background.

Is there any way for me to just feed it a direct SQL query so I can cross-relate the data as I need to?

No, the models handle all of the various joins, converting the params to the correct DB columns, etc. Ultimately they use wpdb so if you really wanted to dig that deep you could but I don’t advise it, or support it.

The models make querying EE data much easier and you can do some really powerful querying with ver minimal code, I highly recommend browsing the above docs, the time taken will be a huge timesaver when working with EE data.

https://github.com/eventespresso/event-espresso-core/tree/master/docs/G–Model-System

December 10, 2024 at 1:26 pm

Just a couple of notes from the above:

add_filter("FHEE__Events_Admin_Page__get_events__where", function (array $where)...

The current Request Params are passed to the filter as a 2nd parameters, so against whilst there’s nothing technically wrong with using $_GET, why not use the values from $request_params?

So: add_filter("FHEE__Events_Admin_Page__get_events__where", function (array $where, $request_params)

Then:

/**
 * Ensure it's the Event Espresso dashboard
*/
if (! (isset($_GET["page"]) && $_GET["page"] === "espresso_events")) {
    return $where;
}

Nothing wrong with this per say, but that hook will only ever fire on that specific request, so this will work but is redundant.

Why check for OR:

/**
 * Ensure the "OR" key exists
*/
if (! array_key_exists("OR", $where)) {
    return $where;
}

If its a search request (which is what sets OR) you want to add your own search params. A search request will always have OR set unless something else has filtered the request to remove it… in which case you now don’t want to include Venue Name as a search param?

/**
* Exclude events in espresso_event_categories = 869 from the Event Espresso dashboard
*/

Again, I’d recommend using $request_params, and why not include this is the initial function? You can separate them out but if always altering that query I’d use one for them all. Personal preference more than anything though.

Next, I was able to figure out how to filter out events with a specific category, but it only works if the event is *only* in that category. That’s fine with me, but my client might complain; is there any way to adjust this to exclude these events even if they’re in other categories?

Do you mean when selecting another category to show in the table or just in general?

Any vent set in in more than one category will still display when excluding one of the categories with the above?

/**
* Sort Event Espresso dashboard by start date
*/

Nice.

I’ve also got event dates mostly showing up throughout the checkout process, but is there any way to add them to the invoices …

Can you link me to an invoice and highlight where you’d like to add them? I’ll check into this from there.