Support

May 5, 2015 at 5:20 am

No this is not due to using a new account, EE4 should detect if EE3 has previously been installed on your site and offer to migrate the data.

Which version of EE3 did you have installed on the site?

May 5, 2015 at 5:32 am

Hi,

3.1.20 is quite old. I think there was a minimum need of 3.1.36 required to then migrate to EE4 due to database differences.

If you reactivate EE 3.1.20 do your events reappear?

If they do, it would be advisable to upgrade your EE3 first then swap over to EE4.

Also, did you take a backup of your site before trying the upgrade?

May 5, 2015 at 6:56 am

You can updgrade the ee3 version by downloading the current version of EE3 lite and activating. You can download it here.

Then you deactivate ee3.1.20, then activate current ee3 lite. The database update script will run and will make the data migrate-able to EE4.

Then when you go to update to EE4, you’ll need to deactivate EE3 first.

May 7, 2015 at 9:05 am

A white screen of death means there’s a PHP error in your code somewhere.

You can check your error log or enable WP_DEBUG to find out what’s causing the white screen of death.

More tips here:

http://www.wpbeginner.com/wp-tutorials/how-to-fix-the-wordpress-white-screen-of-death/

May 7, 2015 at 10:25 am

I’m sorry for the trouble. Please try this code instead:

// stop redirect to about page after update
add_action( 'init', 'ee_remove_about_ee_redirect', 4 );
function ee_remove_about_ee_redirect() {
    global $pagenow;
    if (
        ! in_array(
            $pagenow,
            array( 'wp-login.php', 'wp-register.php' )
        )
        && class_exists( 'EE_System' )
    ) {
        remove_action(
            'AHEE__EE_System__initialize_last',
            array( EE_System::instance(), 'redirect_to_about_ee' ),
            9
        );
    }
}

The above will ensure the fatal error isn’t thrown.

When you go to activate EE4 with the above code in place, it may bring you to a white screen, because it’s not redirected to the about page. You can navigate away from the white screen by hitting the back button.

May 7, 2015 at 11:59 am

That’s likely because EE4 was activated previously (when EE3 hadn’t been updated)

You haven’t created any Events/Registrations/etc within EE4 yet correct?

If so you first want to create a database backup*, there are many plugins available to do this. Here is one I use – https://wordpress.org/plugins/backupwordpress/

Then go to Event Espresso -> Maintenance -> Reset/Delete Data tab.

Within there you will find the option ‘Permanently Delete All Event Espresso Data’

http://take.ms/E00XK

If you click that it will reset the EE4 tables as if EE4 had never been activated. Then when you re-activate EE4 again, the migrations should trigger.

*Note as that function deletes tables from the database, it is highly recommended to create a database backup before hand and not skipping this step, we’ve not had reports of issues with the feature but it is better to be safe.