Support

October 14, 2022 at 5:25 am

My apologies for the delayed reply.

So the issue here is not actually a conflict, its from some custom code in your child theme:

//* Set custom Event Espresso ticket selector template
add_filter ('FHEE__EE_Ticket_Selector__display_ticket_selector__template_path', 'ee_custom_ticket_selector_template_location');
function ee_custom_ticket_selector_template_location(){
    return WP_CONTENT_DIR . '/themes/Avada-Child-Theme/ticket_selector_chart.template_show_remaining_tickets.php';
}

That’s code to replace the template used by the ticket selector for a custom version but your theme does not have a ticket_selector_chart.template_show_remaining_tickets.php template file.

Remove the above custom code and the ticket selector will display as expected 🙂

October 18, 2022 at 2:08 am

We don’t currently have a list of hooks within EE4, partially because we have a huge number of hooks available within EE4.

We have roughly 1500 Filters and 1000 Actions hooks within core so that’s not including WP core hooks or add-ons, We also have dynamic hooks for use within a section of code that can be used for various stages. So at this point the list would basically end up being the same as searching through the codebase.

We use the prefix FHEE__ for filters and AHEE__ for actions so if your developers search for those they’ll find a bunch of hooks.

Here some details on the naming convention we now use:

https://github.com/eventespresso/event-espresso-core/blob/master/docs/A–Best-Practices/ee-actions-and-filters.md

Does that help?

October 25, 2022 at 12:53 pm

> We use this hook to create wp user, send welcome email, send data to sharpspring automation tool (https://app-3QNFZKDCN6.marketingautomation.services/webforms/receivePostback/MzawMDE3MDG0BAA/)

But when?

Have you run through EE4 registrations to see how they work, it works very differently to EE3 so at what point during an EE4 registration would you want to do the above?

The EE4 WP user integration add-on hooks into AHEE__EE_Single_Page_Checkout__process_attendee_information__end to create a WP User account so you could look into using that. You could then even use the WP User integration add-on to do some of your processing and hook into that if preferred, it depends when you want your code to run.

We use above hooks to update custom event meta data. What is the post_type name?

For EE Events… espresso_events

There’s also an EE hook:

FHEE__Events_Admin_Page___insert_update_cpt_item__event_update_callbacks

Which again allows you to hook into the CPT insert/update.

EE event doesn’t look like standard custom post type.

You’ll need to explain this further, Event Espresso does indeed use ‘standard’ custom post types to some degree, however we also use custom tables to store a LOT of out data.

The best thing you can do when working with EE4 is learn how our model system works:

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

> that’s correct + I want to update store data (custom table) at https://functionalanatomyseminars.com/find-a-provider/

So in EE4 that would not be solely based on payment but rather registration status, so when the registration status is set to Approved.

So maybe AHEE__EE_Registration__set_status__to_approved?

November 9, 2022 at 4:35 am

1 – Can you ask EE support if they know the EE 4 version of the below EE 3 query?

EE4 works differently with WP Users so this query doesn’t work the same way as aboe and this is really where they need to start digging into the EE4 Models system:

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

The above EE3 query is pulling attendee from the wp_events_attendee based on a relationship table (wp_events_member_rel). EE4 registrations don’t work that way, you would pull registrations based on the EE_Contact linked to the user account.

The simplest example of this in use is within the EE4 User integration add-on.

\eea-wpuser-integration\EES_Espresso_My_Events.shortcode.php

Take a look at the _get_template_objects() method to se how the add-on pulls in registrations based on the current users att_id.

2 – I can’t find EE4 tables for wp_events_member_rel, wp_events_detail, wp_events_category_detail.

wp_events_member_rel – there isn’t one, the integration works differently here.

wp_events_detail – EE4 events are a custom post type, so the post itself if within wp_posts and joined to our custom tables using the post_id. The model system takes care of those joins for you so again, I recommend learning how the model system works.

wp_events_category_detail – EE4 categories are a custom taxonomy within WordPress, so categories are terms within the espresso_event_categories taxonomy.

3 – Does EE4 still use some of EE3 tables?

No, not at all.

4 – Also, is there a difference between EE4 event and payment status from EE3?

I need more specific details to be able to this, do they have an example?

November 15, 2022 at 6:19 am

Apologies for the delay, I’ve been doing a little digging into the migrations.

I did get the login details and some of your events are set to draft which is likely why they show as inactive, I’m not making changes to the site, so can you check what the status of one of those events was EE3?

Or, does the migration script copy EE3 event IDs somewhere, so we can do post migration update ourself?

The migration scrips do indeed save a map of the Primary Keys from the old tables to the new ones, take a look at the developer documentation on this here:

https://github.com/eventespresso/event-espresso-core/blob/master/docs/H–Data-Migration-System/data-migration-scripts.md#ee_data_migration_script_base-only

get_mapping_new_pk() sounds like the method you need here.

I’d recommend opening up a github issue on the above repo for this and outline what it is you are trying to do, one of our developers may be able to provide some details (although I can’t guarantee that).

November 28, 2022 at 5:55 am

Where do you save the map, what table?
Maybe it would be faster if we just query directly to db?

Without meaning for this to come across the wrong way, if you are asking where it is saved (the function to save the map is in the same file as the function I mentioned) then it’s likely not going to be quicker trying to call it directly.

Did you open up an issue for this on the Repo?

One of our developers should be able to point you in the right direction here.

There is also the option of adding a hook in the migration script (even if you do it yourselves) on each loop over the migration for events passing the old and new event ID’s into the hook to allow you to do this yourself via said hook.

As it’s a migration and only happening once it’s less of an issue than the usually one of ‘hacking up core’, although still generally not recommended.

—

To actually answer your question it’s saved within an option within the database and uses the migration 'ee_dms_map_' prefix although with other details from the tables the specific map is for.

December 7, 2022 at 1:56 pm

They work differently in EE4.

EE4 registrations create an EE_Contact to store the ‘registrant’ details, the registration is linked to the contact using the ATT_ID for the contact.

The WP user integration add-on links a specific EE_Contact to a WP User using a user option (aka usermeta):

get_user_option('EE_Attendee_ID', $user->ID)

All registrations made by a specific user are not tied to that user, only registration where the First Name, Last Name and Email address matched the EE_Contact.

December 15, 2022 at 3:38 am

Hmm, good question and not currently, no.

You could run a script looping over every registration, pulling the contact for the registration and then comparing the first name, last name and email address to your WP_users and if finds one, create the user meta value.

The above will happen for each individual user as they register onto the next event as it stands. The WP User integration add-on will hook into the checkout process, search for a WP user account with details that match the first name, last name and email address provided within the personal information and link to contact to the user but we don’t have a batch process to do this for all current registrations/WP users as it stands.

December 22, 2022 at 3:18 pm

Hi Andreo,

Most of those ‘errors’ aren’t really errors, they are advisories from the migration saying ‘We didn’t expect X, but we did Y anyway’.

I’ll happily provide feedback on those errors, but what are they looking for here?

Could not find new registrations for old attendee 45409 when creating answer

Is saying EE4 could not find a related EE4 attendee for an answer in the EE3 data.

Could not find primary attendee’s new transaction. Current attendee is

The EE3 registration_id didn’t relate to an EE3 attendee and TXN_ID was null, so couldn’t relate to a txn.

EE4 creates an attendee for those individual registrations anyway.

Both of the above ‘errors’ could be related to registrations having been removed from EE3 previously.

Could not find 4.1 question group id for 3.1 question group #0.

I’m not why a question group in EE3 would have an ID of 0. A non-existent question group?

Could not get-or-create state because no state name was provided for venue

No state name was provided fro a venue so EE4 couldn’t set one for the venue passed to it.

Same with country.

Could not find 4.1 event id for 3.1 event X

Likely events that have been removed from the EE3 database but have registrations related to it, EE4 can’t link a registration to an event if it didn’t create an event during the event migrations.

Could not find payment method with PMD_type = ‘paid by phone ‘
Could not find payment method with PMD_type = ‘Added by Admin’

Those a custom values entered into EE3 for payments, EE4 can’t find related payment methods for them (expected in this case) and will have just set them to unknown.

January 13, 2023 at 4:54 am

My apologies for the delayed reply, for some reason the above didn’t show in my queue.

I can’t tell you why those are different from the info available to me. If the EE3 individual events are part of a recurring series it will create individual date times and tickets within an event, but I can’t tell if that’s part of the issue with your setup here.

Can I take another look in the admin? I know you sent credentials over previously but we try not to keep them for any long than needed for the specific issue we are looking into so I no longer have those.

You can resend using this form: https://eventespresso.com/send-login-details/

February 1, 2023 at 2:25 pm

Hi there,

Yes, I received your DB tables, support doesn’t work over the weekend so the first time I looked at them was Monday evening.

Migrations take a fair bit of troubleshooting and I’m confused with a couple of steps on this so asked for some feedback.

I’ll let you know as soon as I have any details on this.

February 17, 2023 at 7:56 am

Ok, so this is an issue that is fairly obvious now that it’s been found and I’m surprised this hasn’t come up before.

The issue with those missing events is due to some of your events not having a start/end time set. The migration script is expecting a start/end for each individual event passed to it, when a value isn’t passed it breaks the datetime creation.

The bigger picture for this is we can’t really assume start/end times for an events either as migrations could then create (many) events with start times that simply aren’t correct which are then available to the public which means the best way to fix this is to go through your EE3 events and confirm a start/end time is on them all, then re-run migrations.

I’ll create a ticket to discuss this further but knowing the above in terms of making assumptions on start/end times I can’t see a fix for this being release ‘soon’.

February 22, 2023 at 7:10 am

Yes, both the start and end times must be set otherwise EE4 has no idea when the end starts or end.

February 22, 2023 at 1:39 pm

SELECT e.id 
FROM wp_events_detail e 
LEFT JOIN wp_events_start_end start_end ON e.id = start_end.event_id 
WHERE start_end.id IS NULL;

Gives you a list of all of the events where there is no row within wp_events_start_end (where the start and end times are stored for each event), and you have 255 of them.

Loop over each ID and add a start and end time within wp_events_start_end for each of those event ID’s, for example:

INSERT INTO wp_events_start_end (id,event_id,start_time,end_time,reg_limit) VALUES (NULL, '{event_id}', '08:00', '17:00', '0');

That should the fairly easy to mock up within PHP 🙂

Just make sure you have a backup of the database, or at least wp_events_start_end first.

Note the above is doing this in the EE3 tables so that you can re-run the migrations again and EE4 sets up the datetimes correctly.