|
OEPB
|
January 24, 2017 at 5:02 am
I help organize a local community event with a guest speaker and about 300 people in Melbourne Australia. It happens just once a year.
An IT guy who used to serve on our committee purchase Event Espresso and installed it on our WP site about 2 years ago as a ticketing plugin. However, when he resigned, it seems that I have been left managing the website which isn’t my training or forte.
Our support licence keys expired a month ago and I noticed last night that when I tried to book tickets via the website, it wasn’t working (at all). When I asked him via SMS, he said “upgrade or update all the WordPress plugins” which I attempted to do myself.
I saw there was a free lite version of Event Espresso 4 called deCaf. Because we are a NFP community event once a year, I thought it would be worth looking at so I downloaded.
When I tried to Activate it, it said I had to deactivate the other version of Event Espresso.
Because they were both EE I assumed that they would work or play together.
But when I went into Event Espresso decaf all my event data (and 200+ registrations) were lost… So I went back to the original version and my data wasn’t there either.
Is there any possible way of recovering the registrations and event data????
N.B. I am not an IT guy
|
|
Tony
|
January 24, 2017 at 5:23 am
Hi there,
Because they were both EE I assumed that they would work or play together.
You can’t have 2 of the same plugin activated (not just EE but any plugin) and as Event Espresso Decaf is basically a limited version of regular Event Espresso its basically the same plugin.
But when I went into Event Espresso decaf all my event data (and 200+ registrations) were lost… So I went back to the original version and my data wasn’t there either.
Before that did it show something about a migration? Like this – http://take.ms/OSjXm
Is there any possible way of recovering the registrations and event data????
Do you have any backup plugins active on the site? If the data has been remove from the database the only way to get that back is from a recent backup. If you don’t have a backup plugin your host may make daily backups they can restore you to (note you’ll lose any changes between the backup and now when that happens)
However first lets find out what happened with the data.
|
|
OEPB
|
January 24, 2017 at 3:36 pm
Thank you Tony. I have gone back to Godaddy, our host, and restored a previous backup. So I’ve got the data back.
The IT guy who set it up came back and said:
“I attempted an upgrade to all the plugins several times (doing full site restores after each failure). Unfortunately, OEPB did not keep up with the upgrade cycle and it looks like it may not be possible to upgrade from the real old version you had of EE to their new version. There was a major version upgrade required last year that changes the EE Database structure and it wasn’t done… you may be now too far behind.
The problem is that the core WordPress is automatically updated by the hosting provider and it is OEPBs responsibility to keep the plugins up to date so as to keep in step with the core system. If you don’t the site eventually breaks… that’s what has now happened.
You will need to contact EE and ask for their advice as to how you can migrate from 4.8.43.p to 4.9.26.p as it places the whole system into Maintenance mode (including the backend!) and the upgrade fails with this error message, “Update Failed: <!DOCTYPE HTML PUBLIC “-//IETF//DTD HTML 2.0//EN”> 500 Internal Server Error Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator and inform them of the time the error occurred, and the actions you performed just before this error. More information about this error may be available in the server error log.”
I’ve just renewed our licence support key.
Can you assist?
|
|
Josh
|
January 25, 2017 at 7:56 am
You can avoid the above error by deactivating all other plugins before running the migration. This will allow more memory to be used by the migration script.
Then, you can also set the migration to work in smaller “chunks” at a time, which will reduce the memory it uses, by adding the following to your wp-config.php file:
define( 'EE_MIGRATION_STEP_SIZE', 5);
|
