|
Steve Dertien
|
August 29, 2016 at 7:53 pm
We are in the process of upgrading from EE3 to EE4. When we test creating events after the upgrade we are unable to set a ticket price in the event. Doing so continues to add additional 0 value price modifiers to the ticket. The base ticket price is never set. Note, the $175 that was set in this screenshot became 175%. We’ve tried creating new events, etc. and the field does not set a value. The only thing that results in setting any value is to use price modifiers only. We have not used price modifiers previously.
https://www.dropbox.com/s/u1xcqis5w14c42e/Screenshot%202016-08-29%2021.21.33.png?dl=0
Thanks in advance.
|
|
Steve Dertien
|
August 29, 2016 at 8:00 pm
Also note, I just verified all of the migrated events now have a $0 price as well and it’s not possible to select their respective tickets for registration.
|
|
Tony
|
August 30, 2016 at 4:28 am
Hi Steve,
So it looks like something from EE3 messed up the migration script and has setup the prices incorrectly.
If you go to Event Espresso -> Pricing, do you see ‘Range Fee’ price types there?
Within EE3 did you use surcharges on your tickets?
Which version number of EE3 did you migrate from? Did you have any customizations made to that version?
Is this on a live site or development?
|
|
Steve Dertien
|
August 30, 2016 at 8:18 pm
Hi Tony. We ultimately added a price type and found that it was the only way to get a price to come through. Without any price types we simply can’t set a ticket price at all. In EE3 we generally did not apply a surcharge but it likely has been used. More often we had a standard price and a member price. We have zero customizations to EE, just to the WordPress theme as you’d expect. We migrated from 3.1.37.6. At first we did it on the production site just treating it as an update but quickly found a bad template bug that caused EE to not work. We migrated a copy of production over to a dev instance, reran the migration and here we are so far. We are going to do another complete copy of production and rerun the process just to make sure we have everything covered. There were so many small tweaks in shortcodes and other things that we have to meticulously walk through the update. So far the only bug we have is on pricing and even on migrated tickets the prices are blank. Unfortunately we need to get through that challenge before we can go live with things. Let me know if you want any more in depth info. I may pursue setting up another dev instance copy and going through all the motions just to see if there are any obvious failures in the migration process.
|
|
Steve Dertien
|
August 30, 2016 at 8:30 pm
Just realized the above may be confusing. Under any situation we cannot set the ticket price. When a price type is present the ticket price will reflect a price type other than a discount. When you attempt to set a ticket price it will add an additional price type to the ticket and arbitrarily set the value to what was the ticket price. However the price type often defaults to percent and 175% of $0 makes things interesting. Ideally we would likely not leverage a price type. Generally the prices are the same for everyone and use a coupon code instead.
|
|
Steve Dertien
|
September 1, 2016 at 7:10 pm
I just performed a clone and reran the upgrade from EE3 to EE4 and I’ve captured the warning messages. Please advise how I can send the file. It has content I’d rather not post openly but am happy to share for review.
|
|
Josh
|
September 2, 2016 at 8:37 am
Did the migration fail? If so, there’s a button that will automatically send the crash report to support staff.
|
|
Steve Dertien
|
September 5, 2016 at 8:19 pm
Hi Josh. The migration at the end appears successful despite failures in several of the steps. I didn’t see what I would have expected to have been a button to send a crash report. When I visit the EE Maintenance > System Info the errors and configuration are all captured there nicely. Is there a way to trigger that crash report to send it?
|
|
Tony
|
September 8, 2016 at 5:54 am
The easiest way is to go to Event Espresso -> Maintenance -> System Information.
Copy all od the ‘Raw System Data’ into a text file and send that to support[at]eventespresso.com
If you prefer to send temporary login details for the site so I can view that same section you can use:
https://eventespresso.com/send-login-details/
|
|
Steve Dertien
|
September 8, 2016 at 10:05 pm
I’ve sent you temporary login credentials. Thanks in advance!
|
