|
Aneleise Ruggles
|
May 19, 2014 at 11:57 am
Hello, we recently migrated our site from an older version of wordpress to a newer version which uses cPanel. We copied our database to the new site. We copied the wp-content folder. We copied all WordPress posts, pages, files, etc. to the new site. Everything is working fine except Event Espresso. None of our old site’s Event Espresso customizations, users, or event entries are coming up.
Example (these two pages are supposed to be identical):
OLD SITE: http://arsenalarts.org/browse-classes/
NEW TEMP SITE: http://new.arsenalarts.org/browse-classes/
Question 1: Where is this Event Espresso information saved? Did I move it correctly or am I missing something?
Question 2: If I did move it correctly, is there some sort of configuration component I’m missing? I can view Event Espresso on the WP dashboard, but none of the entries, customizations, etc. are there. It’s all reverted to the default/blank state.
What am I missing here?
New site is running
Event Espresso – 3.1.36.4.P
Wordpress 3.9.1
Thanks,
Matt
mattjatkola@arsenalarts.org
|
|
Lorenzo Orlando Caum
|
May 19, 2014 at 12:46 pm
Hi Matt,
Those steps sound correct. Copying the wp-content folder would ensure that both sites are using the same theme and version of Event Espresso.
The Event Espresso data is stored in the database so I would try migrating the database over one more time. BTW: are you manually moving the database or was this done using a tool like BackupBuddy or Duplicator?
—
Lorenzo
|
|
Aneleise Ruggles
|
May 21, 2014 at 9:15 am
Thanks for the reply Lorenzo. We have been moving it manually (with some help from our GoDaddy support rep). We tried using WordPress Duplicator to move everything, but it doesn’t seem to be working, which I think is due some timeout/server problems we’re having (hence, the reason we’re doing the migration)… any other suggestions or insights?
|
|
Lorenzo Orlando Caum
|
May 21, 2014 at 11:02 am
Could you try manually exporting the database?
http://codex.wordpress.org/Backing_Up_Your_Database
—
Lorenzo
|
|
Aneleise Ruggles
|
May 21, 2014 at 11:57 am
Yes, we’ve done that, and uploaded to the new site. The databases appear to be identical. GoDaddy has verified this on their end as well. Still none of our EE data, users, etc. are appearing in our dashboard.
|
|
Aneleise Ruggles
|
May 21, 2014 at 12:11 pm
Is there some sort of configuration thing we’re missing?
|
|
Lorenzo Orlando Caum
|
May 21, 2014 at 6:41 pm
No configuration is necessary. You do have to move the entire database and a copy of the files and folders (entire wp-content folder) from the old site to the new site.
If you partially move the database to a site with new versions of the Event Espresso software, then you’ll have information missing.
BTW: do you have any customizations in this location on the old site:
wp-content/uploads/espresso
Those would also need to be migrated as well.
—
Lorenzo
|
|
Aneleise Ruggles
|
May 22, 2014 at 11:47 am
Thanks for the info Lorenzo. We’ve recopied the wp-content folder and made sure the contents are the same on the old site and the new site. Same for the database (just did another full move). No change.
|
|
Tony
|
May 22, 2014 at 2:57 pm
Hi Kimberley,
Your domain name is changing (although temporary it is changing) which has implications when moving WordPress.
So can you explain all the steps taken when you migrate the site please?
How are you changing the domain within WordPress?
Just to confirm you are also exporting the EE tables when exporting the original sites database? They will all being with the name *wp-prefix*_events_
|
|
Aneleise Ruggles
|
May 23, 2014 at 11:21 am
Hi Tony, yes, “new.arsenalarts.org” is a test site we’ve set up to make sure our website would work on a new server. Everything is working fine except EE. Once we get that working on the new site, we’ll move everything back over to “arsenalarts.org” and that will be the permanent home.
For migration, we’ve done it a few different ways with the same results. The simplest way we’ve done it is:
– Copied the entire “wp-content” folder from arsenalarts.org to new.arsenalarts.org via FTP uploader (here is a screen shot, you’ll see the contents are the same: http://arsenalarts.org/filesfordownload/screenshot2-ftp.jpg)
– Copied the database manually (in accordance with wordpress codex database migration) You will see here, that the contents are the same: (http://arsenalarts.org/filesfordownload/screenshot1-database.jpg)
Do you need any other details about the migration to further evaluate? It appears all the *wp-prefix*_events_ you referenced are there.
There are 3 possibilities I see that *could* be the problem, but I’m not sure how to correct them (or if they are in fact the real problem).
1. EE not understanding the “new.arsenalarts.org” directory and is instead trying to pull from “arsenalarts.org” (?)
2. The wp-content folder (and all our wordpress stuff) has been placed in “new.arsenalarts.org/public_html” rather than the root directory. Since everything else seems to be working fine in this directory, it seems strange that EE isn’t working.
3. I also get this error on our “new.arsenalarts.org” Event Espresso page, but only when I’m not logged into my wordpress acct. http://arsenalarts.org/filesfordownload/screenshot3-error.jpg …a clue? or something unrelated…?
Let me know if you need any other details. Thanks,
Matt
|
|
Josh
|
May 23, 2014 at 6:30 pm
Hi Matt,
The first thing to check at this point is the new server’s error logs for clues. A few ideas: The new server is hitting a memory limit or even a query limit when it tries to load up the event list. If the server runs low on memory or throws a PHP error you may see some errors in the error log. If you can’t find an error log you can add one by defining error logging:
http://codex.wordpress.org/Debugging_in_WordPress#WP_DEBUG_LOG
The old site is reporting this on the event list page:
86 queries in 19.264 seconds, using 23.43MB memory
New site:
52 queries in 0.081 seconds, using 5.68MB memory
That’s pretty low, but if your new site is set to be really really low that could make a difference.
There is an important step in migrating a database that was missed here. There are file paths and urls stored in the database, and usually these are stored in settings in the wp-options table. Event Espresso uses a few of these and that may also be causing some problems. I can suggest running the wp migrate db plugin on the old site and input the new server paths when running the data migration as directed. Then you can import that data onto the new site.
The screenshot along with issue #3 is a PHP notice, which wouldn’t be a clue here as you’re running PHP 5.4 with error display turned on. That’s normal to see that on Event Espresso 3.1.36 or below.
|
