|
Gail Fireman
|
January 27, 2015 at 12:45 pm
When I deploy my website and copy over the database, none of the EE settings or events transfer over. All the other parts of the site transition easily. What are the steps for transferring locally to a live server? Where are the settings and events being stored?
|
|
Lorenzo Orlando Caum
|
January 27, 2015 at 1:07 pm
Hi Gail, Event Espresso stores it information in its own database tables along with native WP tables such as wp_options.
Try using a tool like WP Migrate DB Pro or Backup Buddy to move the information over to the new site.
—
Lorenzo
|
|
Gail Fireman
|
January 27, 2015 at 1:12 pm
I was able to transfer the events over but the settings are getting wiped out completely. Where are the settings stored?
|
|
Lorenzo Orlando Caum
|
January 27, 2015 at 1:17 pm
Hi,
They would be in wp_options. However, there are multiple rows with information there.
I would use WP Migrate Pro or Backup Buddy instead of transferring the information manually.
—
Lorenzo
|
|
Gail Fireman
|
January 27, 2015 at 1:26 pm
I’m not transferring any information manually. I’m copying the entire database and simply replacing the urls from the local to the live site. The settings should transfer fine with the database transfer, but they aren’t. This is bad.
|
|
Gail Fireman
|
January 27, 2015 at 1:52 pm
All of the settings are migrating correctly but the event espresso plugin is not reading them in. The settings are showing either blank or No.
|
|
Gail Fireman
|
January 27, 2015 at 2:32 pm
I upload a brand new copy of the database. I go in an see the events_organizations_settings option name in the options table. All of the data is option value field. All seems well. Then I go in to wordpress, navigate to the event espresso organizational settings page, and bam, all the fields are blank and it wipes out the values in the database. Something is terribly wrong with event espresso, why would it do this? How can any developer use ee when it has code set to wipe out the database?
|
|
Josh
|
January 27, 2015 at 3:24 pm
Hi Gail,
Event Espresso does not have code set to wipe out the database.
It turns out that some of the options in the wp_options table are stored as serialized arrays, and within those are file paths and URL’s that point to your development site. Some of that data is for Event Espresso, and some of it for WordPress in general.
The correct way to migrate data from one site to another is to use a plugin like WP Migrate DB or a script that does and automated search and replace like this one:
https://interconnectit.com/products/search-and-replace-for-wordpress-databases/
|
|
Gail Fireman
|
January 27, 2015 at 3:35 pm
When I migrate databases I simply pull the sql file in to sublime text and find and replace the the local url with the staging or live site url. I just have to find and replace the url string from the entire database, correct?
|
|
Josh
|
January 27, 2015 at 3:56 pm
Hi Gail,
It turns out simply doing a find and replace is not correct. This is because doing a find and replace in a text editor will not account for changes in the serialize data.
Here’s a quick example:
Let’s say your dev server is at “dev.website.com”. The URL in the serialized data will be s:15:"dev.website.com". Then when you change the string to the non dev site, it becomes s:15:"website.com". Do you see how the string length value stayed at 15? The data is now damaged.
Plugins like WP Migrate DB and WP Migrate DB Pro, or this script, will actually go through and ensure that the string length values are correct when the strings get changed. So in our example, s:15:"dev.website.com" becomes s:11:"website.com".
|
