|
mhfacincy
|
May 20, 2016 at 10:04 am
On Tuesday morning we tried to do all plugin and WordPress updates. We followed the prompts for migration and it said it happened successfully. The site broke completely, likely due to customization a previous developer did within the Event Espresso plugin.
We (the host) tried to restore the site using the backup from the previous day. All files and the database were restored. Everything on the front of the site was fine, but going to Events under the Event Espresso menu caused a white screen.
Then, for no discernible reason, Event Espresso put the events section into Maintenance Mode and is requesting that data migration be done. This makes no sense as the plugin installed on the site is still Version 4.6.25.p.
We’ve tried restoring to an earlier point, creating a new database with the backup and connecting the site to that, and even running the migration (which failed).
Can you point us in the right direction to get this resolved?
|
|
Lorenzo Orlando Caum
|
May 20, 2016 at 11:12 am
Hello,
I understand what you have shared but something may have gone wrong with the DB restoration.
The maintenance mode for migration triggers when moving between major releases. For example, going from 4.4.x to 4.8.x would trigger a quick migration as there were some features introduced that were not previously available as as the promotions add-on.
Did you do a full restore of the database after you noticed some issues or was it a partial restore?
The reason I ask is that Event Espresso information is stored in native DB tables like wp_options along with custom esp_ tables so if it was a partial restore then there could be a mix of old and new data.
—
Lorenzo
|
|
mhfacincy
|
May 20, 2016 at 2:10 pm
It was a full restore. We actually thought maybe there was an error in the database after the first try and so we used an older backup and then tried to use the database from the staging copy of the site – all with the same results. The last time we used a new database with the backup.
|
|
Josh
|
May 20, 2016 at 2:38 pm
You can find the cause of the white screen (usually a PHP fatal error) by checking the PHP error logs or setting up WP_DEBUG.
https://codex.wordpress.org/Debugging_in_WordPress#Example_wp-config.php_for_Debugging
|
|
mhfacincy
|
May 20, 2016 at 4:07 pm
The error we were getting with the white screen was pointing to this file:
mod_fcgid: stderr: PHP Fatal error: Cannot redeclare class Venues_Admin_Page in /wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/venues/Venues_Admin_Page.core.php on line 1259, referer: /wp-admin/admin.php?page=espresso_registrations
But the white screen didn’t stay, because the plugin seemed to think we’d updated and the migration message appeared.
So, I guess the first thing is how do we signal to the plugin that we are using Version 4.6.25.p. We’ve tried multiple database copies, including a staging one that was working perfectly fine in the staging site, and they all have the same issues on the live site.
|
|
Tony
|
May 23, 2016 at 2:37 am
Hi there,
As soon as each version of Event Espresso runs it checks the last versions installed and then checks if a migration should be triggered based on that information. So you don’t signal that you are using a specific version, EE uses its current version and compares it to the previous versions installed and runs migrations if needed.
If this is a full database restore then the version of EE installed is not the same version that was installed previously or there is a problem with the database.
What version numbers does it shown for the migration when its triggered?
Can you check within:
Event Espresso -> Maintenance -> System Information.
There you will find both ‘ee_activation_history’ and ‘ee_config’
Within ee_activation_history what is the last version number shown in the history? Also note if the version numbers have jump from later to older version numbers within the list. IE:
4.8.40.p => 2016-04-14 09:51:38
4.8.37.p => 2016-04-27 08:11:28
4.8.42.p => 2016-05-03 08:05:36
4.8.43.p => 2016-05-12 07:19:24
Also what does it show for the ‘ee_version’ value on the same page?
Reg.
PHP Fatal error: Cannot redeclare class Venues_Admin_Page in /wp-content/plugins/event-espresso-core-reg/caffeinated/admin/new/venues/Venues_Admin_Page.core.php
It is expected that we declare the Venues_Admin_Page class within that file, again if this was a full restore then it sounds like something has either been modified within EE core files or something is wrong with the backup/restore.
|
|
mhfacincy
|
May 23, 2016 at 1:44 pm
Here’s what is says in the version info:
ee_version
4.6.25.p
ee_activation_history
4.4.0.decaf
2014-09-19 14:43:23
2014-10-07 16:04:54
4.4.3.p
2014-10-07 16:05:21
4.4.4.p
2014-11-06 23:47:15
4.4.8.p
2015-01-09 16:31:37
4.6.19.p
2015-04-10 11:49:13
4.6.25.p
2015-05-12 02:25:16
So here it looks like we’re using 4.6.25.p, but it’s still activating the migration message.
|
|
Josh
|
May 23, 2016 at 2:55 pm
You could try restoring the database to the point before the update was made, and restore the files to use the 4.6.31 release tag (instead of the customized version of 4.6.25) , which you can download from here:
https://github.com/eventespresso/event-espresso-core/releases/tag/4.6.31.p-sans-tests-tag
4.6.31 was the last stable release of 4.6.
|
