Posted: April 14, 2020 at 4:59 am
Hello EE support team
No surprises here, we’ve had to cancel our annual beer festival and therefore to put a stop to the selling of tickets, I put the ‘event’ in to a draft state.
Would it be possible to change the date timeline to the new date in 2021 once it’s been decided or will that not be possible given that we had already been selling tickets?
Would appreciate any short cuts there might be to having to redefine a brand new event and all the configuration which goes with it, if possible?
Many thanks for your help.
Stay safe and well.
Event Espresso will allow you to change the dates on the datetime(s) within the event as it is expected that events will be ‘moved’ from time to time. It won’t let you remove tickets/datetimes with sales on them, but changing the dates on ticket/datetime is fine.
Meaning you don’t need a ‘new’ event, just alter the datetime Event Start and Event End date alone with the ticket ‘Sale Starts’ and ‘Sell until’ dates. Any registrations made onto those tickets will ‘update’ to show the new date.
You have another option for your event right now as well, rather than setting it to draft (meaning any public links to it are now invalid) you could publish it and set the ‘Display Ticket Selector’ option to No on the event. The event content will still display (which gives you a place to add an update on what is going on with that event) but no registrations can be made as the ticket selector wont display.
Does that work better for you?
Hi Tony, thanks very much for this info. It’s good to know that I can alter these times and that any registrations will ‘update’ to show the new date.
We’re making a number of refunds back to people who would rather have their money back rather than to rollover. How best would you recommend to remove their tickets so that they no longer appear as live active tickets in the system? The refund of the money itself will be made from within the Paypal account.
My other background concern is around updating the EE software between now and January 2021 (which ticket sales would go live again for next year’s event). I seem to remember that on the last couple of occasions when I’ve updated the EE software, the database is obliterated and all data lost. Would it be possible to do the EE software upgrades without losing the data of the tickets which have been rolled over to the new date?
Thank you for your help.
Assuming you want to keep a record of the refund, you’ll also need to apply the refund within EE.
Event Espresso -> Registrations.
Find the registration in question and click on TXN Date column for that registration to go directly to the transaction.
Click the ‘Apply Refund’ button and provide the requested details. The registration status will be updated to cancelled by default and that will release the tickets back for sale.
I can’t really give you an answer to that as normally EE doesn’t lose any data during updates and certainly doesn’t obliterate the DB.
What can happen, is if we’ve made changes to the database structure between the version you are currently running and the latest version, then when you install the latest version a ‘migration’ will be triggered and you are given the choice to migrate or not.
If you opt to migrate your data (and you should) it pulls the original data from your current database tables and updates it to use the latest DB schema. If you chose NOT to migrate your data, EE has to wipe the databases because your data will now be in a format that the latest version does not expect, in short always run through all EE database migrations.
I can’t think of any other way in which the database would change to cause you to lose any data when updating EE other than opting to NOT migrate your database to the latest version.
What you can do is backup your database before you run ANY updates on the site, not just EE but with any plugin/theme/wp updates it’s a good idea to backup your database just be safe, they all have the possibility of losing data so a backup is always a good idea. Generally, if something updates your database, whatever data it’s writing to the DB has the chance of being lost/incorrect so it’s possible to ‘lose’ but then usually not everything.
To lose EVERYTHING within a table/DB would worst-case scenario with all the planets aligning, standing on one foot with your finger in your left ear and pressing enter, it’s not actually hard to do, but you’d usually need some code that intentionally does something crazy. So for it to function as expected on for thousands of other sites and then drop all tables on your site only would be very much unexpected.
AND/OR you could create a staging copy of your site on a subdomain and run the updates there, why a subdomain? Because you want to match your live site as closely as possible. You’ll then see any issues on the staging site first and can post the details of what happened here so we can troubleshoot with you.