Support

Home Forums Event Espresso Premium Change Event Status

Change Event Status

Posted: July 6, 2020 at 8:51 am


SteveMBragg

July 6, 2020 at 8:51 am

Hi

I have a “sold out” event that I would like to add extra tickets too as we now have increased space.

However I cannot find a way to change the sold out status.

How do I do that please?

Steve


Tony

  • Support Staff

July 6, 2020 at 2:27 pm

Hi Steve,

When you add additional places onto the event and update it should automatically switch out of sold out.

On the first update it may switch from sold out to draft and the button will show ‘Publish’ rather than update, click that to make sure the event is published.

Do you have the waitlist add-on active?

If so it changes the default behaviour as waitlist registrations are also taken into account.


SteveMBragg

July 6, 2020 at 2:36 pm

I tried three or four times to add new times to the event which seemed to work for a minute or two then the event dropped back to Sold Out and the new tickets I created dissapeared.

The Waitlist add on is not installed.

Because of this I have had to create a new event just to accomodate the extra bookings, which is not really convenient.

Any other ideas?

Regards

Steve B


Tony

  • Support Staff

July 6, 2020 at 2:46 pm

I tried three or four times to add new times to the event which seemed to work for a minute or two then the event dropped back to Sold Out and the new tickets I created dissapeared.

Is that new ticket types or did you increase the limit on the datetime/tickets within the event?

What did you do within the event itself? I’ll see if I can reproduce with the same steps.

Because of this I have had to create a new event just to accomodate the extra bookings, which is not really convenient.

It’s not expected that you would need to re-create another event to add additional spaces.


SteveMBragg

July 6, 2020 at 3:03 pm

Hi Tony

What I did was change the main event date range from it’s original period (14:30 to 17:30) to (10:30 to 17:30).

Then I added tickets between 10:30am to 12:30 pm. Then I Published.

Basically the tickets for this period just dissappeared and reverted back to the original tickets and the event flagged up Sold out again.

Did I do this wrong?

Kind regards

Steve B


Tony

  • Support Staff

July 6, 2020 at 3:26 pm

No that’s not wrong, but that’s not the expected behaviour.

How many dateimtes and tickets are on the event in question?


SteveMBragg

July 7, 2020 at 6:53 am

Hi Tony

When I tried to add the extra times there should have been 8 “slots”/tickets per 15 minutes between 10:30 and 12:30 – a total of 64 extra. So I added the extra 64 to the total available for the whole event. But it would not take the event off “Sold Out”.

We really would like to get this sorted out a.s.a.p. as there are a lot of events to come.

Regards

Steve


Tony

  • Support Staff

July 7, 2020 at 7:47 am

How many separate datetimes and ticket types are on the event currently?

Not the total available tickets, but the different tickets types themselves, like this screenshot has 4 datetimes and 6 tickets:

https://monosnap.com/file/sWs3nBA3wdvWipF2g6unBei5qGwUq7

The reason I ask is if you’re creating tickets for 15 minute intervals and have multiple datetimes then you’ll likely have more datetimes/tickets than your server will currently allow with its max_input_vars setting.

Without knowing the answer to the above I don’t know if thats the cuase yet, but its the most common issue for that causes ‘disappearing’ tickets when you update as your server will simply ignore them. You can increase that limit on your server, if your host doesn’t provide a section within your control that allows you to change this you’ll need to create a ticket with them to increase the limit. By default it is usually 1000, if your hitting that limit you may want to bump it up to say 3000.


SteveMBragg

July 7, 2020 at 9:12 am

Hi Tony

There is one date time, which was originally 13:30 – 16:30hrs, I then changed that to 10:30 – 16:30hrs, in an attempt to add the tickets I wanted between 10:30am and 12:30pm.

I am not getting a warning about max_input_vars, the new booking times are just not saving. Normally in WP you get a warning about max_input_vars.

However for your information the max_input_vars was changed to 4,000 about 2 weeks ago as we were getting warnings then.

As you mention multiple date times what it the point of these if an event is covering a full day?

Kind regards

Steve


Tony

  • Support Staff

July 7, 2020 at 10:11 am

There is one date time, which was originally 13:30 – 16:30hrs, I then changed that to 10:30 – 16:30hrs, in an attempt to add the tickets I wanted between 10:30am and 12:30pm.

1 datetime with how many different ticket types?

I am not getting a warning about max_input_vars, the new booking times are just not saving. Normally in WP you get a warning about max_input_vars.

WP does not normally warn you about max_input_vars, EE does but the notice depends on WP Heartbeat working and no Javascript errors so can easily be ‘broken’ by other plugins.

However for your information the max_input_vars was changed to 4,000 about 2 weeks ago as we were getting warnings then.

You’re already hitting 4k inputs, so either you have a lot of individual ticket types on that event, or something on your site is adding a whole bunch of inputs to our Event Editor (we’ve seen some themes load 14k inputs everywhere on the site)

Tickets just disappearing from the editor means 1 of 2 things.

1. Your server simply isn’t receiving the data from the page when POST’d (max_input_vars is one limit but there are others).

2. Your server is receiving the data but there is a database error and the details aren’t saved to the database, you would normally see an error message if this is the case.

As you mention multiple date times what it the point of these if an event is covering a full day?

Datetimes are essentially instances of events and tickets grant access to datetimes.

So if you have an event with multiple ‘sessions’ within a day, you can either set up individual ticket types for those sessions on a single datetime (which sounds like you are doing) or set up individual datetimes and then individual tickets for each of those datetimes. It depends on how much control you want over the numbers and if your offer different ticket types for different sessions etc.


SteveMBragg

July 7, 2020 at 10:42 am

Hi Tony

I don’t really undersand your first question properly. So here is my best shot at an answer:

The event has one date time – originally 13:30 to 16:30 on one day. The “tickets” are every 15 minutes, with 8 available per “slot”. So between 13:30 and 16:30 there are 13 tickets.

Is that what you meant?

I did’nt say we were getting 4,000 inputs. What I DID say was that we increased it to 4K as we were getting warnings, I guess from what you say from Event Espresso. The warning told us we were hitting 1K + and that we should increase, so we did and chose 4K arbitarily.

Re multiple date times. We used a single datetime and tickets as we were advised by Garth that this wold be a good way to set up our tickets.

When I try to add extra tickets to the Sold out event, by changing the datetime and increasing the ticket qty I get this warning at the top of the page:

“Please note that the Event Status has automatically been changed to Sold Out because there are no more spaces available for this event. However, this change is not permanent until you update the event. You can change the status back to something else before updating if you wish.”

We don’t seem much further forward….

If I set up an event to run from 10:30am to 5:30pm, can I leave time shots (or tickets) not done and just do tickets between 1:30pm and 5:30pm, then come back later and add the earlier in the day tickets if the afternoon tickets sell out?

At the moment we are struggling with the inflexibility, after having spent quite a bit on the plugin and suite.

Cheers

Steve


SteveMBragg

July 7, 2020 at 10:43 am

P.S. Do you need a back end login to take a look yourself?

Steve


Tony

  • Support Staff

July 7, 2020 at 11:07 am

Sure, you can send the login details using this form:

https://eventespresso.com/send-login-details/


Tony

  • Support Staff

July 8, 2020 at 4:30 am

Hi Steve,

We recieved your credentials a couple of hours ago so I’ve just logged into the site to take a look.

I quickly added an additional temp ticket to the event, set the ticket limit to 8 on that temp ticket and increased the datetime limit by 8 to allow for sales of that ticket then updated the event, the ticket saved and the event switched without any issue.

(Note I then removed the ticket and the event switched back to sold out as expected).

I’ve just gone through and added what I think are you trying to do into the editor (I have NOT pushed the changes live) to see if I understand what you are trying to do and will post a screenshot in a private reply.

If that is the same as what you did previously I’d like to try pushing those changes so I can check the request as it sends if that is ok?


Tony

  • Support Staff

July 8, 2020 at 4:32 am

This reply has been marked as private.


SteveMBragg

July 8, 2020 at 7:27 am

Hi

I have just this minute gone to the site and edited event ID 266. I changed the datetime to 4:35pm to add an extra 5 minutes.

I then increased the ticket qty total to 105, to add an extra 1 availability. I then went to create a new ticket, gave it a title of 16:35 then added a price then added a qty of 1.

I then clicked on UPDATE.

THe ticket I created dissappeared, the event shows SOld Out still and I have this message at the top of the page:

!!!

So I must be doing somethign wrong compared to you.

Please advise

Thanks


Tony

  • Support Staff

July 8, 2020 at 8:27 am

This reply has been marked as private.


SteveMBragg

July 8, 2020 at 8:29 am

Hi Tony

I am using Firefox.

I am quite happy for you to have a remote session on my laptop if you wish, I can log into the dashboard on the site and you can watch me try to make an extra ticket?

Steve


Tony

  • Support Staff

July 8, 2020 at 2:36 pm

Tested your site again with Firefox and same result, all working.

We generally don’t provide remote sessions and to so would require a support token but you could use a screen recorder to record the screen when updating and post a link to the video here for me to view.

You could also try login into the account you gave me and try updating with that to confirm it’s not an account-specific issue (I can’t think of a reason it would be, but it working for me and not you is odd).


SteveMBragg

July 8, 2020 at 3:08 pm

TOny OK.

But can you confirm the steps I am taking are correct. Am I doing something different to you?

Do you have a suggestion of a screen recorder. Frankly I have never had an issue with a plugin to this extent. So it’s a first for me.

Steve


Tony

  • Support Staff

July 8, 2020 at 3:44 pm

They sound correct but then it sounds like exactly what I’m doing, yet it’s not working for you.

For Chrome I’ve used https://www.screencastify.com/

Never used one for Firefox but heard of Nimbus: https://addons.mozilla.org/en-GB/firefox/addon/nimbus-screenshot/


SteveMBragg

July 8, 2020 at 3:50 pm

Thanks

I’ll have to look tomorrow.

Chrome is banned with us…..

Cheers

Steve

You must be logged in to reply to this support post. Sign In or Register for an Account

Support forum for Event Espresso 3 and Event Espresso 4.
Documentation for EE3 and EE4
Documentation for Event Espresso 3 Documentation for Event Espresso 4

Status: publish

Updated by  SteveMBragg 3 months, 2 weeks ago ago

Topic Tags

Notifications

This topic is:
pending
Do NOT follow this link or you will be banned from the site!
[gravityform id=80 title=false description=false ajax=false]
<div class='gf_browser_unknown gform_wrapper' id='gform_wrapper_80' ><form method='post' enctype='multipart/form-data' id='gform_80' action='/topic/change-event-status/'> <div class='gform_body'><ul id='gform_fields_80' class='gform_fields top_label form_sublabel_below description_below'><li id='field_80_1' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_1' >First name<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_text'><input name='input_1' id='input_80_1' type='text' value='' class='medium' aria-required="true" aria-invalid="false" /></div></li><li id='field_80_2' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_2' >Email address<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_email'> <input name='input_2' id='input_80_2' type='email' value='' class='medium' aria-required="true" aria-invalid="false" /> </div></li><li id='field_80_3' class='gfield gfield_contains_required field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' >GDPR Agreement<span class='gfield_required'>*</span></label><div class='ginput_container ginput_container_checkbox'><ul class='gfield_checkbox' id='input_80_3'><li class='gchoice_80_3_1'> <input name='input_3.1' type='checkbox' value='I consent to have this website store my submitted information so they can respond to my inquiry.' id='choice_80_3_1' /> <label for='choice_80_3_1' id='label_80_3_1'>I consent to have this website store my submitted information so they can respond to my inquiry.</label> </li></ul></div></li><li id='field_80_4' class='gfield gform_validation_container field_sublabel_below field_description_below gfield_visibility_visible' ><label class='gfield_label' for='input_80_4' >Phone</label><div class='ginput_container'><input name='input_4' id='input_80_4' type='text' value='' autocomplete='off'/></div><div class='gfield_description' id='gfield_description_80_4'>This field is for validation purposes and should be left unchanged.</div></li> </ul></div> <div class='gform_footer top_label'> <input type='submit' id='gform_submit_button_80' class='gform_button button' value='Download Now' onclick='if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} ' onkeypress='if( event.keyCode == 13 ){ if(window["gf_submitting_80"]){return false;} if( !jQuery("#gform_80")[0].checkValidity || jQuery("#gform_80")[0].checkValidity()){window["gf_submitting_80"]=true;} jQuery("#gform_80").trigger("submit",[true]); }' /> <input type='hidden' class='gform_hidden' name='is_submit_80' value='1' /> <input type='hidden' class='gform_hidden' name='gform_submit' value='80' /> <input type='hidden' class='gform_hidden' name='gform_unique_id' value='' /> <input type='hidden' class='gform_hidden' name='state_80' value='WyJbXSIsIjBiNjdjZjkyMDUzOWUxOWY5Y2NiZjIwMzM4YjA1Mjk4Il0=' /> <input type='hidden' class='gform_hidden' name='gform_target_page_number_80' id='gform_target_page_number_80' value='0' /> <input type='hidden' class='gform_hidden' name='gform_source_page_number_80' id='gform_source_page_number_80' value='1' /> <input type='hidden' name='gform_field_values' value='' /> </div> </form> </div><script type='text/javascript'> jQuery(document).bind('gform_post_render', function(event, formId, currentPage){if(formId == 80) {} } );jQuery(document).bind('gform_post_conditional_logic', function(event, formId, fields, isInit){} );</script><script type='text/javascript'> jQuery(document).ready(function(){jQuery(document).trigger('gform_post_render', [80, 1]) } ); </script>
[i]
[i]