Posted: May 19, 2023 at 9:36 pm
Upgrade and migration to Event Espresso 4 failed. After that I deactivated version and reactivated version 3 and where the events are supposed to show, just see the following shortcode: [ESPRESSO_EVENTS order_by=start_date sort=ASC show_expired=false]
Thank you for contacting us.
Can you please let me know what error you see while upgrading?
Also, please share a direct link to the event page so that we can check the issue for you.
Looking forward to helping you.
EE4 converts your shortcodes to the ‘new’ format during the migration.
Do you have the fatal error that was thrown during the migration?
OK, so I assume you still looking to switch to ee4?
If so reactivate it and continue on with the migration, without the fatal I can’t say what will have gone wrong but EE4 will give you the option to continue the migration and try to pick up where it left off.
Yes, EE4 has had a new event editor add and a lot of the code updated for PHP8.
It’s a major version number bump but is still ‘Event Espresso 4’. We named EE4 the way we did in the beginning, to differentiate between EE3 and EE4, but eventually will likely just have ‘Event Espresso’ at whatever version number it may be at.
Those options are within Event Espresso -> Maintenance -> Reset/Delete Data, thats not the migration options.
Is that the only section you can see?
Can you add a screenshot of what is available?
Thank you, the migration report shows the ‘usual’ errors we expect (things like ‘Couldn’t find X so used Y’) and also a fatal error status, but it does not contain the fatal itself which likely means your server is set not to display errors.
Do you have FTP/File Manager access to the site?
What do you see on the maintenance tab (top left of that screenshot)
No, the min PHP requirement is PHP7.4
Ok, so that last screenshot will allow you to continue with the migration.
However, before proceeding, I recommend enabling WP_DBEUG_LOG so if another fatal is thrown it’s logged and we know where to look.
Edit the sits wp-config.php file and look for:
Replace that single line with the snippet here:
That tells your site to store errors within /wp-content/debug.log
Then on that screenshot above, click the ‘Next Step’ link, which should take you to a page that allows you to continue the migration. If unsure of how to proceed add a screenshot fo what you see and I’ll walk you through it.
I didn’t say click to Reset/Delete Data, why did you chose that option?
Sure I did, in the reply above HERE, clicking the ‘Next step’ link would allow you to continue the current migration.
This is your last screenshot with the ‘Next step’ link:
I understand and the option I gave you above would have done exactly that but now that the tables have been reset there isn’t migration to allow you to continue with.
Ok, before moving forward, do you have a Database backup from before the migration and do you have one from ‘now’?
If you don’t, create at least the one for now. It’s important not to skip creating a backup as you’ll be manipulating the database a fair amount from here dropping tables, if something goes wrong the only way to get that data back is with a backup.
Once you have a backup, you’ll need to restart your migration from scratch again by completely dropping EE4 tables, if you have a backup from before you ran the migrations you can revert the site to that would be best, but if not…
Go to Event Espresso -> Maintenance -> Reset/Delete Data.
Click the ‘Permanently Delete ALL Event Espresso Data’ button.
This drops all EE4 tables.
Once complete, reactivate Event Espresso 4+ and you should be offered to restart the migration over again. Follow the steps to migrate over again and as you have WP_DEBUG_LOG enabled if it throws a fatal again we should be able to track down that error.
Again, that’s why I said to let me know what you see in that same reply and I’d walk you through it, I guess I wasn’t clear.
The options you see depend on the migration step you are on so I needed to see the page to know what to click.
That’s correct, the EE3 tables have not been reset by the above.
EE3 tables use the
EE4 tables use the
EE4 entities are also a custom post type so data is also stored within the
None of your EE3 tables will have been lost, but the migration that was running pulling EE3 data into EE4 has now been lost because you’ve reset the tables. So the migration from EE3 -> EE4 needs to start again.
EE3 is no longer updated, it receives security updates only and now that EE4 supports the majority of use cases that EE3 does it will likely be phased out over the next 12 months.
So generally when the date/time output is different from whatever is set within EE its because something is calling
WordPress (and therefor Event Espresso) expect the server timezone to be set to UTC and then an offset is applied on display based on your sites settings. If something within the site changes that timezone it throws off the output.
Do you have any other plugins that work with dates?
First create a database backup, just to be safe.
Then what I would do is use the WP Health Check & Troubleshooting plugin to check the output with only Event Espresso running.
Install and activate the above, then go to Tools -> Site Health -> Troubleshooting -> Enable Troubleshooting Mode.
What that will do is disable all plugins and switch you back to a fault theme, but only for you, the logged in admin.
Then in the admin bar at the top go to Troubleshooting mode -> Manage Active Plugins.
Enable Event Espresso and check the output of the dates/times. Are they correct?
Try switching from the default theme to your sites normal theme (again within the troubleshooting menu bar items).
Check the output again.
Then work through your site’s active plugins, enabling them one by one in troubleshooting mode and refreshing the page with the event date on until it stops displaying correctly, you should then find which plugin is causing the timezone to shift.
Post that here.
When finished in Troubleshooting mode, click ‘Disable Troubleshooting Mode’ in the admin menu again to switch the site back to normal.
You must be logged in to reply to this support post. Sign In or Register for an Account