|
Jamie Jennings
|
March 3, 2020 at 7:20 am
Hi I had inquired about this before but we are just now getting to the date of requiring final payment. I tried adding another ticket to the event, but it doesn’t add it to existing registrants as a final balance payment. Here’s the original support topic for more info https://eventespresso.com/topic/multi-payment-options/
|
|
Jamie Jennings
|
March 3, 2020 at 10:35 am
So I was going to just purchase the attendee mover but realized you have it for EE4 and we have EE3. What’s our best option in this scenario?
|
|
Jamie Jennings
|
March 4, 2020 at 9:24 am
You guys must be busy or short-staffed. Just checking back in on my situation.
Thank you for your consideration.
|
|
Josh
|
March 4, 2020 at 11:04 am
I can’t say this is a best option (the better options involve using EE4 and its attendee mover add-on), but you could send a PayPal invoice requesting final payment.
|
|
Jamie Jennings
|
March 4, 2020 at 1:13 pm
Thanks for your reply. We want to give multiple options to pay, and we’re actually trying to get away from PayPal because of all the fees. Also, that makes it so the information in the actual system isn’t complete because it’s won’t be able to reflect final payment. Wouldn’t it be easier to just send a batch message through EE vs. through PayPal. Really…no other solutions? Want to give me a free upgrade to EE4 so I can use the attendee mover?
|
|
Josh
|
March 4, 2020 at 2:24 pm
You already have access to Event Espresso 4, it’s included with your EE3 Business license.
|
|
Jamie Jennings
|
March 5, 2020 at 5:20 am
So does that mean I can purchase the “Attendee Mover” and it will work?
|
|
Jamie Jennings
|
March 5, 2020 at 5:20 am
So does that mean I can purchase the “Attendee Mover” and it will work?
|
|
Josh
|
March 5, 2020 at 7:35 am
Before you can use the Attendee mover add-on you’ll need to upgrade to EE4 and migrate the data from EE3. We have a guide here:
https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#migrate-to-event-espresso-4
|
|
Jamie Jennings
|
March 5, 2020 at 8:12 am
I get to the following step, click “activate” and nothing happens. It just shows as activated in my list of plug-ins. I did not see any notice “to migrate”. Also, I downloaded Event Espresso 4 Core Regular v4.10.3.p, so hopefully that was correct.
Step 6 – Activate Event Espresso 4 and start the migration
Click on Activate and Event Espresso 4 will run through a few tasks internally and then switch itself into maintenance mode. At this point, you’ll see a notice to migrate. Click to go to the maintenance screen for Event Espresso 4. Then click the button to begin migrating your information to Event Espresso 4.
|
|
Josh
|
March 5, 2020 at 8:25 am
Hi,
You’ll need to make sure the Event Espresso 3 plugin is deactivated before you can activate Event Espresso 4.
|
|
Jamie Jennings
|
March 5, 2020 at 8:47 am
I did deactivate EE3 before adding EE4. I’m obviously not doing something right though.
|
|
Josh
|
March 5, 2020 at 9:30 am
Hi,
It looks like somehow you’ve installed Event Espresso Version 4.9.22.rc.041. That wasn’t downloaded from your account page right?
You’ll need the current version of Event Espresso 4 that you can download from your account page.
Then, if you’re unable to migrate your current EE3 data, that’s an indication that EE4 has been previously installed on your site. T can delete its data from the Event Espresso > Maintenance > Reset page. This will allow for migrating the current EE3 data to EE4.
|
|
Jamie Jennings
|
March 5, 2020 at 9:57 am
It was downloaded from my account page. So basically I went to my account page, clicked on download latest software and went to the EE4 Downloads tab which is where I thought I had downloaded the correct EE4. What should I be downloading?
|
|
Josh
|
March 5, 2020 at 10:07 am
You’ll need to download the one that says “Event Espresso 4 Core Regular v4.10.3.p”
|
|
Josh
|
March 5, 2020 at 10:18 am
You might also have older copies of EE4 already installed on your site, in which case it would be best to delete those.
Along with that, is it possible that your site has been running EE4 this whole time? Maybe you haven’t had EE3 installed for a while, which would explain why you didn’t see a notification about migrating.
If your site has been running an older version of EE4, you’ll have a one-step database migration from EE4.9 to EE4.10. Then you’ll be able to install the Attendee Mover add-on .
|
|
Jamie Jennings
|
March 5, 2020 at 10:27 am
So the version I’ve been using is Version 4.9.22.rc.041, so is that EE4? How do you do a one-step database migration from EE4.9 to EE4.10.
|
|
Josh
|
March 5, 2020 at 10:32 am
So the version I’ve been using is Version 4.9.22.rc.041, so is that EE4?
That is EE4, it’s an older version of EE4.
How do you do a one-step database migration from EE4.9 to EE4.10.
You deactivate and delete the old version of EE4 from your WordPress > Plugins page. Then install and activate the version you download from your account page. After you activate the new version you’ll click the link to start the database update to 4.10.
|
|
Jamie Jennings
|
March 5, 2020 at 10:38 am
Ok, so not sure how it happened, but I now have this version 4.10.3.p. Is that correct?
|
|
Josh
|
March 5, 2020 at 11:27 am
Yes, that’s the current version of EE4.
|
|
Jamie Jennings
|
March 5, 2020 at 12:55 pm
Thanks so much I’m up and running. Now I’m just testing it out. Thanks for sticking with me. Who knew I had EE4!
|
|
Jamie Jennings
|
March 5, 2020 at 1:03 pm
So I thought I was all set. I clicked on the attendee mover icon and get the Change Event/Ticket selection and none of my events are showing in the “Select New Event Field”
|
|
Jamie Jennings
|
March 5, 2020 at 1:03 pm
Says “The results cannot be loaded”
|
|
Josh
|
March 5, 2020 at 1:37 pm
Hi,
The Attendee mover add-on uses the WordPress REST API to fetch the events list. It looks like any request to the REST API on your site returns this:
<b>Warning</b>: call_user_func_array() expects parameter 1 to be a valid callback, function '_return_false' not found or invalid function name in
The code that’s causing that error should probably be fixed, and to prevent further problems it would be best to turn off error_display and/or WP_DEBUG because a live website should not display errors.
If you can access your site’s wp-config.php file, you’ll want to make sure WP_DEBUG is false
You could also add the following to wp-config.php to help prevent errors from displaying:
@ini_set( 'display_errors', 0 );
|
