|
FJMClinics
|
April 11, 2016 at 11:41 am
I inherited a WP site that primarily runs EE3 (3.1.37)… The client wanted to upgrade to EE4 (4.8 today’s latest). However, when i see the list of installed plugins, I see an old EE4.1 plugin listed. The issue is the data listed for migrating only lists 4.1 .. I can’t select the active 3.1.37 data to migrate. If i try to testing and activating the 4.1 module, there is no data to migrate.
Would be happy to send a support ticket in / provide access, but ultimately need to update this site to the latest version. Currently the EE3 is being used and not in a situation we can just re-create events / registrations.
|
|
Lorenzo Orlando Caum
|
April 11, 2016 at 12:55 pm
Hello,
There is a maintenance option available that can be used to clear the existing Event Espresso 4 information. First, backup your WordPress site (https://eventespresso.com/wiki/how-to-back-up-your-site/). Then go to Event Espresso –> Maintenance. Then look for the delete / reset tab and use the last option on the page.
From here, reactivate Event Espresso 3 and your data should still be there. Then you can deactivate Event Espresso 3 along with its add-ons. Once you reactivate Event Espresso 4, then it will prompt you to migrate.
I do recommend taking a look at the migration guide here:
https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#migrate-to-event-espresso-4
Please note that certain features like mobile apps and recurring events are available in Event Espresso 3 only at this time.
—
Lorenzo
|
|
FJMClinics
|
April 27, 2016 at 8:28 am
Hello again,
SO i did this on our staging site, and everything worked perfectly as you indicated. clearing the old data, seemed to be fine.
I try this again on our live site and i am getting an error right as a activate the plug, Nor do i get the data migration / conversion.
To recap what i do.
1. deactivate all of EE3 and modules.
2. activate EE4 (old 4.1), then go to maintenance > reset data and purge all of that.
3. deactivate EE4 and reactivate EE3 to make sure all my data is still there. It is, so that is good.
4. deactivate EE3, and then I delete EE4 plugin (if i don’t I can’t install 4.8.x)
5. Upload install 4.8. When i click activate, I get
The mysite.com page isn’t working
mysite.com is currently unable to handle this request.
500
I don’t see the same data migration tasks i did when i upgraded my staging site. It just looks like a new install. Please help here.
|
|
Lorenzo Orlando Caum
|
April 27, 2016 at 9:27 am
Hello,
Did that error message appear on a blank white screen?
If so there may be an error occurring. Could you temporarily turn on WordPress debugging by adding the macro in the following link to your wp-config.php file?
https://gist.github.com/lorenzocaum/848801a1173be464fbe7#file-gistfile1-php
The wp-config.php file can be found in the WordPress root which is where the wp-admin, wp-content, and other files and folders for WordPress resides.
Then please try to trigger the error and you should see something on the screen. Could you copy and paste that here into a reply?
If you do not see an error on your screen, then please browse to this location using your SFTP or FTP client (e.g. FileZilla, Cyberduck):
/wp-content/debug.log
You should see an error recorded within the file. Please copy and paste that here in a reply.
Then go ahead and deactivate WordPress debugging by removing the macro that was recently added or setting it to false and saving changes:
https://gist.github.com/lorenzocaum/848801a1173be464fbe7#gistcomment-1239850
—
Lorenzo
|
|
FJMClinics
|
April 27, 2016 at 1:02 pm
Notice: The called constructor method for WP_Widget is deprecated since version 4.3.0! Use
__construct()
instead. in /nas/content/live/fjmclinics/wp-includes/functions.php on line 3624
Warning: Illegal string offset ‘Core’ in /nas/content/live/fjmclinics/wp-content/plugins/event-espresso-core-reg/core/EE_Data_Migration_Manager.core.php on line 664
Fatal error: Uncaught exception ‘EE_Error’ with message ‘ The html messenger or the receipt message_type are not active. Are you sure they exist?’ in /nas/content/live/fjmclinics/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_messages.lib.php:557 Stack trace: #0 /nas/content/live/fjmclinics/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_messages.lib.php(581): EE_messages->_validate_setup(‘html’, ‘receipt’, true) #1 /nas/content/live/fjmclinics/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_MSG_Template.helper.php(82): EE_messages->create_new_templates(‘html’, ‘receipt’, 0, true) #2 /nas/content/live/fjmclinics/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(1380): EEH_MSG_Template::generate_new_templates(‘html’, Array, ”, true) #3 /nas/content/live/fjmclinics/wp-content/plugins/event-espresso-core-reg/core/helpers/EEH_Activation.helper.php(111): EEH_Activation::generate_default_message_templates() #4 /nas/content/live/fjmclinics/ in /nas/content/live/fjmclinics/wp-content/plugins/event-espresso-core-reg/core/libraries/messages/EE_messages.lib.php on line 557
|
|
Josh
|
April 28, 2016 at 9:17 am
Hi there,
I took some time to replicate this on another test site and what I found was if the following happens, the options for messages get corrupted with some 4.8 artifacts:
- Deactivate 3.x
- Activate 4.8
- Deactivate 4.8
- Activate 4.1, clear out EE data. At this point EE 4.1 clears out 4.1 data, but there are still artifacts from 4.8 because 4.1 doesn’t know to delete 4.8’s unique options (they didn’t exist in 4.1).
- Activate 4.8 and the fatal error that you reported is thrown.
The good thing is in Event Espresso 4.9, which is currently a release candidate, the messages went through a refactor and part of the refactor involved streamlining how the messages module loads up. The fatal error you reported will not happen when Event Espresso 4.9 is activated. I’ve verified this on the testing server that had the same error.
Before you try 4.9, if you have a database backup of the site **before** 4.8 was activated, you could restore to that backup, then install 4.1, reset data, then install 4.8. If you don’t have a database backup from that point, you can download a copy of 4.9 from our Github project page, it’s currently the Master branch of Event Espresso 4:
https://github.com/eventespresso/event-espresso-core/archive/master.zip
After you remove 4.8, and install 4.9, then activate, you’ll first need to run the reset data script on the maintenance page before you run the migration (it will try to migrate 4.8 data before you reset the data). Then after you reactivate 4.9, it will ask you if you’d like to migrate EE3 data.
|
|
FJMClinics
|
April 29, 2016 at 5:31 am
everything seemed to migrate fine.. I did get the following error.
based on what I am seeing, should we just do a drop table?
Database table wpclinics_esp_currency exists when it shouldn’t, and may contain erroneous data. If you have previously restored your database from a backup that didn’t remove the old tables, then we recommend adding
define( ‘EE_DROP_BAD_TABLES’, TRUE );
to your wp-config.php file then restore to that backup again. This will clear out the invalid data from wpclinics_esp_currency. Afterwards you should undo that change from your wp-config.php file.
If you cannot edit wp-config.php, you should remove the data from wpclinics_esp_currency manually then restore to the backup again.
|
|
FJMClinics
|
April 29, 2016 at 6:37 am
Well, after looking at it, it seems that the events didn’t migrate correctly, it is missing certain tickets available for purchase,
Is this something we can purchase a support token, and have you complete? Hopefully, today if possible. We are just spinning wheels here trying.
|
|
Josh
|
April 29, 2016 at 10:44 am
Hi there,
Generally speaking we do not offer a migration to EE4 service, partly because it can take a few hours or more, and one support token is for up to 30 minutes of priority support.
When you ran the migration on the staging server were there any missing tickets after the migration was run?
|
|
FJMClinics
|
April 29, 2016 at 12:45 pm
I have followed your step by step instructions, I have purchased a token, I just need to be able to replicate the upgrade again. I also have a web developer background, so I am trying to be very particular in the upgrade, but your “step by step” instructions are NOT working. The entire migration start to finish, based on your provided notes takes 20 minutes (i would know, as i’ve done it over a dozen times). I am confident that one of you could see where the error is from. We have already paid for the initial support token, I would like you to use that to provide insight, if it requires more, then ok.. but you website initially stated that you don’t do custom development, nothing of migration.
To answer you question, I believe there were few errors on the migration, but how am i to prevent that when it is an automated process. If you can please, utilize the support token to help otherwise, we are completely at a stand-still.
Thanks
|
|
Josh
|
April 29, 2016 at 12:56 pm
Can you answer this question please?
> When you ran the migration on the staging server were there any missing tickets after the migration was run?
While it’s true that a migration can be done in under 30 minutes, we are not familiar at all with your website, and it will take additional time to migrate data from backups to another site.
|
