Posted: January 22, 2024 at 6:17 am
I upgraded to EE Version 5.0.15.p and now there is no option to add to cart. Additionally I see quantity: expired. Any ideas on how to fix this? |
|
Hi there, Can you link me to the event so I can take a look?
That usually means your ‘sell until’ date on your ticket has passed. |
|
Does each event need a unique time limited to the event ‘ticket’ setup for it? It looks like the existing ones were expired. |
|
This reply has been marked as private. | |
Do I need to create a single default ticket or a single ticket per event? |
|
I’m not sure I understand what you are asking. The tickets within each individual event have their own start and end dates: https://monosnap.com/file/RuTsUInZT09pDPcujg00kIbADQyp6J If you are ask if those need to be set on each ticket within each event, then yes, otherwise EE doesn’t know what to set the values to or the event/ticket.
Why a default ticket? Whats the use case you are trying to use this for, I’ll advise how you can set that up within EE. |
|
Hi Tony, O.K. I see that I need to create tickets but EE 5.0.15.p isn’t documented. The documentation is OLD and reference EE 4.x here: https://eventespresso.com/support/documentation/versioned-docs/?doc_ver=ee4#getting-started The new process in 5.0.15.p is 3 steps. Ticket Details >> Set Prices >> Assign dates Is this documented anywhere with detailed explanations? If so, I can’t find it. Thanks for your help! |
|
The last step in the GUI needs some rethink. Not sure what is meant by the pull down dates by month? What would I choose here? I’m assuming I select the month in which this event takes place right? To assign a ticket date you click a big red button with a ‘-‘ in it. How does that make sense? Shouldn’t it be assign ticket or something more logical? Any help is appreciated. |
|
This reply has been marked as private. | |
This reply has been marked as private. | |
This reply has been marked as private. | |
You can change the price, but what Event Espresso will do, is archive the original ticket and create a new ‘copy’ of the ticket at the new price. The reason for this is the registrations are related to the ticket, if you change the price with existing registrations on a ticket, those registrations would show the new price, rendering any payments made previously now incomplete/overpaid.
You can move attendees to another ticket (be it on the same event or another) using the attendee mover add-on: https://eventespresso.com/product/eea-attendee-mover/ If you need to move a current registration to the new price, you can change the price on the event (creating the archive ticket and the new ticket), then use the attendee mover to move the registrations over to that new ticket. You don’t need to move them to another event.
Your ticket selectors are set to display expired tickets. You can set those not to display in: Event Espresso -> Events -> Templates. Look for the ‘Ticket Selector Template Settings’ heading and set ‘Show Expired Tickets?’ to No, then save. That should remove those from view on you events. |
|
This reply has been marked as private. | |
Can you post a screenshot of whatyour looking at, please? https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots |
|
This reply has been marked as private. | |
Oh! Sorry, that’s me having a moment. That was added to help if you have a lot of datetimes, that dropdown is a way of filtering datetimes within the assignments. You only have 1 Datetime by the looks of it, and that’s displayed already. But here is an example on an event that has 3 datetimes: https://monosnap.com/file/ri87G4RqH8jRHFbNYocVMtkKDKEGsS That section is for you to assign the ticket to Datetimes within the event, if you have multiple datetimes spread across various dates/years the dropdown helps filter to the correct month/year rather than scrolling through them all. Right now, that Ticket is assigned to the Dec 20th 2024 datetime, is that correct? |
|
This reply has been marked as private. | |
Yes, but if this is just a single datetime why are you using the dropdown? If there’s only one datetime you don’t need to ‘filter’ datetimes, as there’s only one anyway. If it looks like this: https://monosnap.com/file/R7bTP4PdK7dfu0aHDwjEwsD7Vtce4u The datetime is not assigned to the ticket. If it looks like this: https://monosnap.com/file/zXi375X9McjcH0drRC7ymtBMfo5lPc Then the datetime with the green icon is assigned to the ticket. |
|
Then interface is very confusing and the pulldowns and options are not clearly detailed or logical. You may want to rework that part of this interface IMHO. Perhaps it is because the new version of the product isn’t documented. Additionally, the interface is confusing and if you documented it perhaps there would be less confusion. Thanks for your help! |
|
We have documentation here of the new advance editor, perhaps it could be helpful. Btw, do you have recommendation on how we can make the Interface better? is there something in your mind, we can suggest this to our tEEm for consideration. thanks |
|
The support post ‘No checkout, add to cart since Version 5.0.15.p’ is closed to new replies.
Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.