Support

May 13, 2015 at 1:59 am

Hi Eric,

On your dev site install Event Espresso and leave the license key blank.

When you are ready to switch over to the new site be sure to remove your license key from the original site, you can then request a license key reset within your account page input the key in your new site and Event Espresso will assign that domain to your key.

Which version are you upgrading to?

May 13, 2015 at 9:12 am

Hi Eric, we do not store any information for your events or registrations. That information would reside in your WP database on your web server.

We recommend using a tool like BackupBuddy or WP Migrate DB Pro to migrate the site. This is because information is stored in Event Espresso tables (wp_events_) along with native tables such as wp_options.

—
Lorenzo

May 13, 2015 at 2:03 pm

Hi Eric,

Yes. Any changes that were made to core will be overwritten during an update. You will need a developer to copy those changes over. We can’t provide support for any changes that are made to core files.

May 13, 2015 at 5:07 pm

Hi Eric,

I’m not sure I follow what you mean here.

If a developer added customizations to your EE3.1.36.4.P and you download a copy of that from ourselves you won’t have the customizations made within your version any more, you’ll have our standard version again.

It depends on how and what the developer added as to how you would update.

For example have they hooked into EE to add the functionality using another plugin? It sounds unlikely due to the changes they have made, meaning they have likely modified Event Espresso core files to make the changes. If that’s the case the developer will need to re-apply the changes to the latest version in order to keep the customizations.

May 15, 2015 at 8:56 am

Yes, I do understand they will need to modify the core files again. We do want to keep all the promo codes we have entered and old event registrations, etc. Someone mentioned BackupBuddy or WP Migrate DB Pro to move everything. Can we move the promo codes over, etc.

Your event data, including the events themselves, attendees, promo codes etc is all stored within the database and is not removed when you update or remove Event Espresso itself. If you are moving to a completely new site you will need to copy over at least the Event Espresso tables ($prefix_events_* from within your database) to keep all of the data.

Both BackUpBuddy and WP Migrate can do this.

Does it matter which version we do now 3 or 4?

Event Espresso 4 is a vastly different system to EE3. None of the modifications made to EE3 will be compatible with EE4.

However EE4 supports multiple ticket types allowing for male/female tickets (with individual limits on each and as a whole for the event) we have recently released promo codes for EE4 (beta testing), depending on if any issues are found during testing we should shortly officially support promo codes within EE4 so it may suit your needs, I would recommend installing it on a development copy of the site if you would like to try it.

Or does it more involved where I need to move certain core files over to my desktop then re-load them once a fresh version is installed, like a promo code file?

When modifications have been made to the core plugin it is unfortunately not as simple as copying the modified file and adding that file to the latest version.

We may have made changes to that file between the version numbers meaning you would then not have those fixes. It depends on which file and what was modified, we would usually recommend porting the changes over to the latest version (comparing the two an applying your custom changes to the new copy). To do this we recommed comparing the files using something like DiffMerge to compare the changes.

Before moving forward with ANY updates besure you have a full site back (including all files and the database.