|
Chris Stambaugh
|
April 8, 2014 at 9:07 pm
Not sure which of these upgrades caused the issue. But the site was borked until I replaced the EED_Ticket_Selector.module.php with an older version of code (from 4.1.9 I think is what I had lying around). The error I get is:
Fatal error: Call to undefined function espresso_event_link_url() in /home/bsopca/public_html/wp-content/plugins/event-espresso-core-reg/modules/ticket_selector/EED_Ticket_Selector.module.php on line 184
So, the error isn’t there right now, because, as I said, to get the site up and running I had to replace the code with some older code.
HELP!
Thanks,
Paul
|
|
Chris Stambaugh
|
April 8, 2014 at 9:16 pm
The error is caused by this line in the ticket_selector_form_open function:
$checkout_url = espresso_event_link_url( $ID, FALSE );
And obviously, that function (espresso_event_link_url) doesn’t seem to exist.
Paul
|
|
Dean
|
April 9, 2014 at 1:05 am
Hi,
Where about on the site is the error occurring? The admin, the /events/ list or the single registration?
What version of EE and WP did you upgrade from?
I’m not seeing the error on my test site. The function in question should be in core\helpers\EEH_Event_View.helper.php
Did you try reinstalling Event Espresso? It may have been an incorrect update.
|
|
Chris Stambaugh
|
April 9, 2014 at 6:04 am
Hi,
Upgraded from previous versions of both.
This is a single registration as from thus URL: https://www.bsop.ca/off-camera-flash-class-june-15-june-22-2014/
The file you reference exists and the function is in it.
I did immediately try reinstalling with no joy.
Please help.
Paul
|
|
Seth Shoultes
|
April 9, 2014 at 7:11 am
Did you get it fixed? The page you linked to above is working for me.
|
|
Josh
|
April 9, 2014 at 7:35 am
The fix for the Fatal error when using the ticket selector has been released in 4.1.12.reg.
|
|
Chris Stambaugh
|
April 9, 2014 at 8:05 am
Josh,
Sounds good but I’m not currently seeing 4.1.2.reg available as an upgrade?
Paul
|
|
Dean
|
April 9, 2014 at 10:03 am
Hi Paul,
It’s been released now. If you’re not seeing in the plugin screen it is available in your account page.
|
|
Tony
|
April 9, 2014 at 10:19 am
You can also force an auto update check by re-saving the General Settings page within Event Espresso -> General Settings.
|
|
Chris Stambaugh
|
April 9, 2014 at 12:59 pm
Thanks Josh.
I need you guys to do better than this. Having a feature like this borked by an upgrade is completely unacceptable. A modicum of testing would have saved me a lot of grief and money.
I also find it frustrating that any other support staff then Josh seem to have issues duplicating problems I’m seeing. If you read this thread you’ll see that Dean couldn’t see the issue and couldn’t look beyond the way he was testing it. You’ll see that Seth obviously didn’t read my original post because I explained I had got it working and how I had got it working.
I’m just a bit frustrated. The tag line for Event Espresso is: “Manage your events from your WordPress dashboard. Reduce your admin, reduce your costs, make your life easier! ” That hasn’t been my experience thus far.
I would implore the ownership to do what needs to be done to make things improve a bit.
Thanks for listening.
Paul
|
|
Josh
|
April 9, 2014 at 5:26 pm
Mr Burwell,
We really thank you for your valuable feedback. One of the important reasons why we decided to rollout the initial versions of Event Espresso 4 as a “beta” product was so that we not only learn about what our customers like and don’t like about the product, but so that we can also learn about our internal processes for testing and preparing the product for release. Event Espresso 4 is a completely different product than Event Espresso 3, and we are learning that what was sufficient testing-wise for Event Espresso 3 doesn’t exactly match what we need to prepare Event Espresso 4 for release.
It’s helpful feedback from people such as yourself that give us the information we need to make necessary changes to help things get better for our customers. An example of a recent change we’ve implemented is earlier access to the next major version (4.2 is in the pre-release channel), so this can be tested not only internally, but externally on a wider array of WordPress installations. Along with that, we have a very thorough testing checklist that is completed before release. It’s far from perfect and we are learning from mistakes like the one that led to what you’ve reported.
|
|
Chris Stambaugh
|
April 10, 2014 at 10:46 am
I truly appreciate what you’re say Josh.
I know from personal experience how difficult software development can be. But, I also know that there are methodologies that can be employed to reduce the liklihood of “show-stopping” errors from happening. That’s what I’m hoping for.
I’m with you guys for the long haul and truly appreciate the efforts everyone is making.
Paul
|
