|
drumthwacketee
|
June 14, 2024 at 9:58 am
We offer free tickets for tours which take place three times (usually) throughout the day, and there are three or more days a month on which tours are held.
This adds up to making a lot of timeline and ticket entries, and takes a lot of time. To help speed up creating timelines and tickets, we duplicate entries and modify those duplicates.
It seems there are two bugs in Event Espresso which are caused by duplicating existing timelines and tickets.
1) When duplicating event timelines and then saving, the new entries are placed in mixed order together with the existing ones instead of keeping them in the location they were located. This means we have to then reorder the duplicated timelines.
This takes time to fix these when there are a lot of timelines to manage. Is this reordering a bug?
2) When duplicating new tickets, past event timelines become selected. This happens on a random basis, and it often happens several times when duplicating tickets.
The result is that existing tickets have unneeded timelines now assigned to them, which then takes time to unassign. Is this also a bug?
Thank you
|
|
Sam
|
June 14, 2024 at 12:38 pm
Hi there,
Can you please share a screenshot or screen recording of the issue?
Also, please share a direct link to the page with the issue so that we can help you better.
Looking forward to helping you.
|
|
drumthwacketee
|
June 14, 2024 at 7:10 pm
This reply has been marked as private.
|
|
Tony
|
June 18, 2024 at 8:55 am
This reply has been marked as private.
|
|
drumthwacketee
|
June 19, 2024 at 4:45 pm
Tony,
Thanks for the reply. We duplicated the live Website to a stage server, but can’t do a test update there to verify that updating is OK.
I think the major factors in delaying an update to the latest version were that the changelog was too out of the way to decide if we should update, and a warning message says only one license can be active for one domain, so that made it risky to just go ahead and update EE on the live Website without testing it first.
Making a ticket to address the legacy editor issues would be helpful, thank you. I understand that all efforts are on the advanced editor. But still, it would make life easier and result in less work for the user to have bugfixes in the legacy editor for those not ready to make the switch to the advanced editor.
Thank you.
|
|
Tony
|
June 19, 2024 at 5:23 pm
We duplicated the live Website to a stage server, but can’t do a test update there to verify that updating is OK.
You can update, just not through the one click updates, same file just a different process:
https://eventespresso.com/wiki/how-to-upgrade-event-espresso/#ee4-manual-update
In short, download the .zip file from your account then on the site go to Dashboard -> Plugins -> Add new -> Upload plugin.
Select the .zip file you just downloaded and upload.
WordPress should tell you there is a version already installed and ask if you want to replace it, do so.
You’ll now have the latest version running.
I think the major factors in delaying an update to the latest version were that the changelog was too out of the way to decide if we should update
Unless I misunderstand what you mean here the change log is always available HERE.
…and a warning message says only one license can be active for one domain, so that made it risky to just go ahead and update EE on the live Website without testing it first.
A method for the license system to allow updates on a staging server is something something we have discussed in the past, I’ll open the discussion on this again with the team.
Making a ticket to address the legacy editor issues would be helpful, thank you. I understand that all efforts are on the advanced editor. But still, it would make life easier and result in less work for the user to have bugfixes in the legacy editor for those not ready to make the switch to the advanced editor.
Yeah I understand, I’m not saying we won’t fix this but I also can’t guarantee we will do either. The problem is that at some point we have to draw a line and move forward with active features, otherwise, legacy becomes ‘the second’ editor that is never actually replaced with the new.
|
|
drumthwacketee
|
June 21, 2024 at 7:57 pm
Thank you for the plugin update instructions — we’ll give that a try.
For some reason github was down or having troubles when I tried to see the list of updates. It’s back now though.
Thank you again for your help!
|
|
Rio
|
June 23, 2024 at 6:55 pm
Awesome!, if you need anything, feel free to reach us again.
thanks
|
|
drumthwacketee
|
June 27, 2024 at 10:46 am
Hello,
We followed your instructions on our stage server, and the 5.0.20.p update installed without problems.
We’ll try out the advanced editor after we complete adding in tickets on the live server, which we are in the middle of.
Thank you again.
|
|
Tony
|
June 27, 2024 at 4:22 pm
You’re most welcome.
Please do let me know if you run into any issues or have any questions.
|
