Support

Home Forums Event Espresso Premium Event Espresso 5 Beta Error

Event Espresso 5 Beta Error

Posted: January 11, 2023 at 12:39 pm


thinkbiglearnsmart

January 11, 2023 at 12:39 pm

Hi there!

I downloaded the EE5 beta, and we keep getting this error:
The incoming statuses argument must be an array with keys as the $status_id and values as the $status_code EEM_Status – localized_status – 270
/* */

Can you please assist with this?

Thanks!!


Garth

  • Support Staff

January 11, 2023 at 1:27 pm

Hi there,

Thank you. Can you provide more detail when this happens? What page are you using, what action are you doing? If you can give us more information we can test, or debug or try to replicate the issue so it can be addressed or so we can give you guidance.


thinkbiglearnsmart

January 12, 2023 at 5:27 am

Hi there!

We have both of these installed:
– event-espresso-core-pr
– eea-recurring-events-manager-pr

We have this on our staging site.

This is happening when we click on the menu items I’ve listed below, which are the only options available on the plugin:
– Maintenance
– Extras
– Help & Support
– Extensions & Services
– About

This error is also popping up on our staging site, which is not our error/database issue:

As part of the process for updating Event Espresso, your database also needs to be updated. Event Espresso is in COMPLETE MAINTENANCE MODE (both WordPress admin pages and front-end event registration pages are disabled) until you run the database update script. Visit the Maintenance Page to get started, it only takes a moment.

Please let me know if I can provide any additional information.

Thanks!


thinkbiglearnsmart

January 12, 2023 at 5:27 am

Hi there!

We have both of these installed:
– event-espresso-core-pr
– eea-recurring-events-manager-pr

We have this on our staging site.

This is happening when we click on the menu items I’ve listed below, which are the only options available on the plugin:
– Maintenance
– Extras
– Help & Support
– Extensions & Services
– About

This error is also popping up on our staging site, which is not our error/database issue:

As part of the process for updating Event Espresso, your database also needs to be updated. Event Espresso is in COMPLETE MAINTENANCE MODE (both WordPress admin pages and front-end event registration pages are disabled) until you run the database update script. Visit the Maintenance Page to get started, it only takes a moment.

Please let me know if I can provide any additional information.

Thanks!


Tony

  • Support Staff

January 12, 2023 at 8:55 am

Ok, so I assume you’ve installed EE5 in place of the latest version of EE4?

It’s gone into maintenance mode because there is a change in the database with EE5, so it triggers maintenance mode and asks you to run the migration scripts.

Is the error above the full error shown? No other details?

Is WP_DEBUG enabled on staging?


thinkbiglearnsmart

January 18, 2023 at 9:57 am

We are only using EE 5 beta on the dev site, there is no earlier version, so there is nothing to migrate. We may need to migrate data if we go into production with EE5. WP_DEBUG is not enabled.

When I try to go to the maintenance page, I get the following error:

The incoming statuses argument must be an array with keys as the $status_id and values as the $status_code EEM_Status – localized_status – 270

/* */

There does not seem to be a way to get to the settings to turn the mode off.


Tony

  • Support Staff

January 18, 2023 at 1:06 pm

Ohhh, interesting!

Can I take a look at staging at all? I’d like to add some debug code within the PR version to see what is happening if that’s ok?

If so I’ll need wp-admin credentials and FTP access which you can send over using this form:

https://eventespresso.com/send-login-details/

Is that a ‘clean’ install then?

The sections you mentioned above suggest that Event Espresso is in maintenance mode already but if no other version of EE was install previously that should be the case.


thinkbiglearnsmart

January 18, 2023 at 2:29 pm

The installation is clean.

Yes, it’s in maintenance mode. There is no way to turn it off, as the PHP error blocks access to the page.

I’m sending the info to you.


Tony

  • Support Staff

January 18, 2023 at 6:11 pm

Hi Amanda,

For some reason a migration had been triggered but as you mentioned there was nothing to migrate. So the fatal error that happened was because the database hadn’t been set up to include the statuses, but was then trying loads the statuses as part of the migration display.

I commented out the code which threw the error and allow EE to attempt to migrate, which then ‘fixed’ the migration and ended maintenance mode.

I’ll open up a ticket for our developers to investigate this further to see if we can find out why the migration was triggered in the first place.


thinkbiglearnsmart

January 19, 2023 at 12:58 pm

Hello,

We did not start a migration process. If I recall correctly, it did it automatically on the installation of the plugin.

If I upgrade the plugin to a newer beta version in the future, will it trigger the migration again?


Tony

  • Support Staff

January 19, 2023 at 2:16 pm

We did not start a migration process. If I recall correctly, it did it automatically on the installation of the plugin.

Yeah I understand, the migration process is not something you can trigger. You can work through it and either migrate the data or leave it, but you can’t manually ‘trigger’ a migration yourself.

So for some reason a migration was triggered with nothing to migrate.

If I upgrade the plugin to a newer beta version in the future, will it trigger the migration again?

As much as I’d love to answer this, without tracking down what caused this I can’t say yet. It shouldn’t do, but until we find out what the cause was I can’t say that for sure.


thinkbiglearnsmart

January 19, 2023 at 2:17 pm

OK, thank you. We should be able to do some testing now.


thinkbiglearnsmart

January 24, 2023 at 11:51 am

Hi there!

Is there a recurring events feature in EE5? I saw that there was supposed to be, but I’m not seeing it.

Thanks so much!


Tony

  • Support Staff

January 24, 2023 at 1:40 pm

Hi there,

First, make sure you are using the new editor and not the legacy version.

Go to Event Espresso -> Events -> Default Settings (tab)

Make sure ‘Activate Advanced Editor?’ is set to Advanced Editor.

That’s the new EE5 editor which is what the recurring events add-on hooks into.

Then create a new event and you should see the recurring events manage when you add a datetime.


thinkbiglearnsmart

January 25, 2023 at 10:59 am

Thank you! I’ve done this and gotten it to work.

However, this recurring event manager isn’t functioning how the EE3 previously did.

Basically in EE3, you could include whatever dates you wanted under the main event, so for example let’s say we have a Photoshop Intro training class running on the following dates:

April 1-2, 2023
June 3-4, 2023
September 5-6, 2023
December 8-9, 2023

Each of these would be created a events that students could uniquely register for.

Now with EE5, it doesn’t create each of these as different events to register for, it just creates these as having access to these specific dates.

Also, this doesn’t have the custom date picker option anymore, it either has to be daily, weekly, monthly, etc. when selecting the recurring date pattern.

Is there any other way I can try doing this that I’m not trying to get this same result?

Thanks so much!


Tony

  • Support Staff

January 25, 2023 at 11:13 am

EE3 and EE4+ are very different systems, the way the events work are vastly different so recurring events within EE4 wll not function in the same way they did within EE3.

Now with EE5, it doesn’t create each of these as different events to register for, it just creates these as having access to these specific dates.

That’s correct, you don’t ‘need’ a separate event like you did within EE3. A DateTime is an instance of an event and a ticket grants access to a Datetime. The event is the same for all of the above but is just held on different dates, so having completely separate events stored within the data for the ‘same’ event on X,Y,Z date isn’t necessary.

April 1-2, 2023
June 3-4, 2023
September 5-6, 2023
December 8-9, 2023

How would you previously generate those within EE3, manually entering the dates?

Also, this doesn’t have the custom date picker option anymore, it either has to be daily, weekly, monthly, etc. when selecting the recurring date pattern.

Sorry but I don’t follow, can you add more details on this?


thinkbiglearnsmart

January 25, 2023 at 12:51 pm

Hi Tony!

Thank you!

Can you walk me through this? I’m not clear on this part “That’s correct, you don’t ‘need’ a separate event like you did within EE3. A DateTime is an instance of an event and a ticket grants access to a Datetime. The event is the same for all of the above but is just held on different dates, so having completely separate events stored within the data for the ‘same’ event on X,Y,Z date isn’t necessary.”

Would you be willing to access my staging site and create an event on the scenario I shared above?

Or, are you able to record a quick video for this?

We can send you access to our staging site if that works!

Thanks so much!


Tony

  • Support Staff

January 25, 2023 at 3:01 pm

Sure, send over login details using this form:

https://eventespresso.com/send-login-details/


thinkbiglearnsmart

January 26, 2023 at 8:00 am

I’ve just submitted this! Thank you!!


Tony

  • Support Staff

January 26, 2023 at 11:55 am

Hi there,

The account provided doesn’t have access to Event Espresso, can you update it to be an admin account please?


thinkbiglearnsmart

January 26, 2023 at 12:27 pm

My apologies! I’ve updated this. Thank you!


Tony

  • Support Staff

January 26, 2023 at 3:01 pm

Ok, so your event in question doesn’t follow a specific pattern which makes the recurring event manage useful in helping create dates, so manually creating them works just as easily here.

I created a datetime, set the date to the correct date and gave it a name of Datetime 1, just for ease of example:

https://monosnap.com/file/gzq6Ko5ZGb5sEULNuwi6IqeZdmPTsM

I then click the stacked icon and chose copy datetime 3 times so I had 4 datetimes. I adjusted the other 3 dates and names to suit your event.

Now you have 4 ‘instances’ of when that event will happen, 4 ‘Datetimes’.

You need a ticket for each individual datetime, so same again, create a ticket as needed and duplicate it 3 times for 4 tickets (you can have multiple tickets per datetime if needed and tickets that grant access to multiple/all datetimes if needed, the tickets are really flexible).

Example of 1 Ticket per datetime: https://monosnap.com/file/2UEvns5R6IfiB47QrgSCMCz7ZUXt0f

Once you’ve create your tickets, you can click on the ‘Ticket Assignments’ button to show which tickets are assigned to which datetimes, I went through and selected each specific datetimes ticket to its own datetime, like so:

https://monosnap.com/file/2p1HVZKRBFaYeUZ7s1xMc9mapGhYVn

Now you have 1 event, which has 4 datetimes and each ticket allows you to register for a specific date within that event.

Is that what you are looking for?


thinkbiglearnsmart

January 30, 2023 at 7:15 am

Hi Tony!

Thank you so much for this! Yes, this is what we were looking for, however, there is one more thing.

For each datetime, there would be at least 3 different ticket amounts, one for commercial clients, one for education clients, and one for government clients. How would we best do this?

It seems that it would be super complicated to have 3 datetime tickets labeled as such, there would be way too many options.

Is there another way to think to do this?

Thank you!


Tony

  • Support Staff

January 30, 2023 at 7:45 am

For each datetime, there would be at least 3 different ticket amounts, one for commercial clients, one for education clients, and one for government clients. How would we best do this?

How do you determine those during the checkout? Do they have an account they log into or are they just selecting the relevant ticket?

It seems that it would be super complicated to have 3 datetime tickets labeled as such, there would be way too many options.

That is how you would do this, each DateTime would have 3 ticket types, one for commercial clients, one for education clients and one for government. There’s way around that if they have a different ticket type, your need a ticket within the event for them.


thinkbiglearnsmart

January 30, 2023 at 11:57 am

Hi there!

This is how we are currently doing it:
https://thinkbiglearnsmart.com/event-registration/?regevent_action=register&event_id=17304&name_of_event=Acrobat%20DC%20Intro

So if we did this same thing on the beta site, how would that show up? Could we get it to appear similar to the example I’ve shared above?

also, I have a couple other questions for you:

1. Can you use this recurring event manager in EE4?
2. Do you know when EE5 will be released?

Thank you!


Tony

  • Support Staff

January 30, 2023 at 3:01 pm

So if we did this same thing on the beta site, how would that show up? Could we get it to appear similar to the example I’ve shared above?

That’s EE3 with a recurring event and separate tickets within each single event, EE4 doesn’t work the same way, other than creating individual events yourself for those (maybe including the date within the slug/url) you can’t set up EE4 to create events in the same way.

1. Can you use this recurring event manager in EE4?

Which recurring event manager? The one for EE3? No.

The current version you are testing on the beta site? That IS the recurring events manager for EE4 (EE5 is essentially an update to EE4) but your events don’t follow a recurring pattern to follow.

2. Do you know when EE5 will be released?

We are working hard in the background to get EE5 released asap.

I can’t give yo a specific ETA but hopefully ‘soon’.


thinkbiglearnsmart

January 31, 2023 at 5:46 am

Okay, thank you!

Do you think there would be any way we could migrate our EE3 data to EE4?

Thanks!


Tony

  • Support Staff

January 31, 2023 at 6:07 am

Do you think there would be any way we could migrate our EE3 data to EE4?

When you first install EE4/5 is runs a check to see if there is any EE3 data within the database and will offer to migrate that data over to EE4 for you.

If you clone your live site onto a staging site and then install EE4 there you will see this in action.

The issue you had above with the migration error was because part of the migration was triggered for some reason on your site but then data was found and it threw an error.

Copy live to a new staging site, install EE4 there and run the migrations, EE4 will pull in all of the data it can from your EE3 events.


thinkbiglearnsmart

January 31, 2023 at 11:47 am

Have you seen EE3 to EE4 successful migrations, or do you think it’s better to start over from scratch?

Also, would it be seamless to migrate from EE4 to EE5?

Thanks!


Tony

  • Support Staff

January 31, 2023 at 12:10 pm

Have you seen EE3 to EE4 successful migrations, or do you think it’s better to start over from scratch?

Sure, I’ve seen many migrations. It really depends on the situation and if you need the previous data.

For example, if you already have a lot of registrations for future events, it’s likely worth running the migrations. If you don’t have any, personally I would start fresh and keep the EE3 data as my ‘archive’ on a dev site somewhere.

Also, would it be seamless to migrate from EE4 to EE5?

Yes, EE5 is an update to EE4, its not a completely new data schema like it was for EE3 -> EE4.


thinkbiglearnsmart

February 1, 2023 at 6:15 am

Thank you for this information!

If needed, do you have consulting services that could support us with our migration from EE3 to EE4? As we would like all of our data migrated to EE4 for historical data and many future registrations we already have in the system.


Tony

  • Support Staff

February 1, 2023 at 10:34 am

If needed, do you have consulting services that could support us with our migration from EE3 to EE4?

This is difficult to answer because it depends on what needs to be done, we can do some with support tokens but if it’s an issue with how the theme displays the events afterwards we generally don’t work on those issues.

To explain, EE3 had its own ‘template’ system within it, the events were basically completely separate from your posts and didn’t rely on your theme. EE4 events are custom post types, the output for those depends more heavily on your theme. Generally, they’ll work fine without any issues at all, but if the theme is doing something completely unexpected it can cause issues which then require fixes within the theme itself and not EE.

—-

We can help with issues from migration process itself however, the migration steps themselves are fairly self-explanatory, it will ask you to start the migration step and when complete, confirm and click to start the next one (repeat until all steps are complete). There isn’t much you (or we) can do during the migration other than site and wait for the progress bar to complete and click to move on to the next step so it’s generally recommended that you do that yourself as the time adds up and would be chargeable.

I highly recommend testing the migration process on a dev/staging copy of the site to see if you have any issues away from the live site and we can advise further on what needs to be done from there.

As mentioned, generally, migrations go smoothly and for the most part, just work but it’s recommend to test it due to the sheer number of theme and plugin combinations each site can have.

You must be logged in to reply to this support post. Sign In or Register for an Account

Event Espresso