|
John Fineberg
|
October 28, 2015 at 2:00 pm
Like a number of other folks on this forum, I am experiencing the “sold out” messages when my event is not even close to sold out. Only one out of 12 spaces is filled, and no one else can sign up until this is fixed. I’m on 4.8.18.p.
I haven’t seen a fix to this in the forums I’ve read, other than to downgrade to an earlier version or adding another event datetime. I now have two datetimes, and I can’t get rid of it, as the system thinks that there’s one person signed up for it, which isn’t true. So now I have an additional problem.
Has it been fixed yet? If not, what’s a quick fix, other than downgrading?
While I have you here, I’d also like to know how to change the wording that website visitors see from “We’re sorry, but all ticket sales have ended” to something else. I’ve tried doing that along with all of my other wording changes in my site-specific plugin, using the same format I’ve successfully used elsewhere with EE4 wording, like this:
‘We’re sorry, but all ticket sales have ended.’ => ‘Please choose a different date’,
But all attempts at making that or a similar change fail (though I haven’t tried with this particular version of EE). Is that the wrong place to make that change? What do you suggest?
|
|
John Fineberg
|
October 28, 2015 at 2:04 pm
I just figured out how to get rid of the second datetime. So that piece of the puzzle is already solved.
|
|
John Fineberg
|
October 28, 2015 at 2:15 pm
Not sure if you need these details, but here goes anyway.
Under Event Espresso -> Events, it says:
No Tickets have been setup for this Event
Under Edit Event, it says:
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.
And editing Status from “Sold Out” to “Published” simply doesn’t work.
|
|
Josh
|
October 28, 2015 at 3:18 pm
Hi John,
It sounds like the one ticket in the event was archived. A ticket will automatically get archived when its price is changed. When all the available tickets get archived, the event status will get switched to sold out. You can set up a new ticket to replace the archived ticket and when you update the event, it will switch from sold out to published.
|
|
John Fineberg
|
October 28, 2015 at 3:40 pm
Hi, Josh. Adding a new ticket did, indeed, solve the problem. Curious though, as I’ve changed prices many times before, yet never (to my knowledge) has this happened where I needed to go through this extra step. So I do believe that something has happened in the update to 4.8.18.p. (or earlier and I just didn’t notice it before). And, since it’s been reported by several other people recently, it sure looks like a common problem. Will this be addressed in an upcoming update?
Please let me know what to do about the wording I mentioned above. I get “syntax” errors, in case that helps you to understand the problem any better.
~ John
|
|
Josh
|
October 28, 2015 at 4:00 pm
The dev team needs to fix the ticket archive feature so when a price gets changed, it will automatically create a replacement ticket, like it did before. Until this is fixed, you’ll need to manually make a replacement ticket when you change a ticket’s price.
Your syntax errors might have something to do with trying to use an unescaped quote or ' in your code. Instead, you’ll need to escape the quote like this:
We\'re sorry, but all ticket sales have ended.
|
|
John Fineberg
|
October 28, 2015 at 4:15 pm
Good to know the dev team is on it, and that this is just a temporary fix. Will there be a note of some sort in the changelog when it’s permanently fixed?
Your forward slash and not-so-smart quotes worked.
Thanks again!
John
|
|
John Fineberg
|
October 28, 2015 at 4:27 pm
This is a little peculiar, and it’s hard for me to describe, so here’s a link for you to see what I mean:
http://www.cpr-twincities.com/upcoming/cpr/
On this page you’ll see “Click ‘Register Now’ to choose this class” on the older class, but a blank in that same spot on the class I just fixed (using your method). Any thoughts as to why it shows in the older listing, but not the newer?
|
|
Lorenzo Orlando Caum
|
October 29, 2015 at 9:28 am
Hi John,
If you set that ticket for the first event on the page to be required then the red help messaging should appear.
—
Lorenzo
|
|
John Fineberg
|
October 29, 2015 at 2:02 pm
Hi, Lorenzo. Thanks for your suggestion. I used the drag-and-drop function, reversing the order of the tickets, but it had no effect. Any other suggestions? ~ John
|
|
Josh
|
October 29, 2015 at 3:21 pm
Hi John,
The red text that says “Click “Register Now” to choose this class” only appears with the tickets that are set to be required. The one ticket where you have a blank space is not set to be required.
|
|
John Fineberg
|
October 29, 2015 at 3:57 pm
Thanks, again, Josh! That worked.
I’d close this topic, but I’d like to wait until the “sold out” issue is completely resolved. Are you able to post a note when it is?
~ John
|
|
Josh
|
October 29, 2015 at 4:42 pm
Yes we are able to do that.
|
|
John Fineberg
|
October 29, 2015 at 6:18 pm
Thank you.
|
|
Josh
|
October 29, 2015 at 7:11 pm
You’re welcome.
|
|
Josh
|
November 3, 2015 at 3:08 pm
The latest update of Event Espresso 4 includes a fix for the ticket archiving feature so the archived ticket gets copied, which will prevent the event from becoming sold out.
https://eventespresso.com/wiki/ee4-changelog/#4.8.20
|
|
John Fineberg
|
November 4, 2015 at 8:19 am
Thanks for seeing this through and keeping me in the loop, Josh. Glad it got resolved. ~ John
|
