|
cstuckey
|
March 30, 2016 at 4:21 am
Hello,
I am setup on the EE3 Version 3.1.37.7.P, and WordPress 4.4.2. I had not been running events in awhile, and as such hadn’t used EE again until more recently. I set up some new events, and later discovered I wasn’t getting my registration confirmation as admin, and the end user wasn’t getting their registration confirmation either.
So I have gone ahead and tested the event by adding myself as a new user, and can confirm no e-mail is being received. I even went back to an older event, which I knew worked, and still the same thing happens, after confirming adding the user, I am brought to a new page with Add New User at the top, and the rest of the page doesn’t load. No error message or anything. Running Chrome inspection after the page load, would seem to indicate an Internal 500 Server error. I have gone to EE Status, and every page is green or loading fine.
I have ensured I am on the latest plugins for everything EE3-related, and disabled all non-critical plugins to see if it fixed the issue, it has not.
After reading the support forums here, I went ahead and add Check E-mail. Check e-mail sends e-mails correctly, and just to be safe I later installed Postmark, and also confirmed that Postmark can send e-mails correctly.
As far as I can tell this is an EE related problem, though I can’t track down the source. Testing events I knew worked before would also indicate this is a newly introduced error, but I don’t know from what specifically because I haven’t been adding new plugins at all. Which means it is something that happened when updating EE3 to the latest version, or when I updated WordPress.
Any idea what may be wrong, and how I can fix it?
|
|
Tony
|
March 30, 2016 at 5:00 am
Hi there,
I even went back to an older event, which I knew worked, and still the same thing happens, after confirming adding the user, I am brought to a new page with Add New User at the top, and the rest of the page doesn’t load. No error message or anything.
Is this within the Admin or on the front end?
Can you post a shttps://eventespresso.com/wiki/troubleshooting-checklist/#screenshots
so we can see this?
Also if you enable WP_DEBUG when testing it should show you any error messages on the page.
|
|
cstuckey
|
March 31, 2016 at 5:25 pm
Here is the error message from WP_DEBUG:
Fatal error: Call to undefined function espresso_qr_code() in /nas/content/live/momocon/wp-content/plugins/event-espresso/includes/functions/email.php on line 245
Going back through support it looks like the solution was to go from the old ticketing method, to the new Ticketing addon. Only problem is I am using the new ticketing addon. But I went ahead and tried deleting it and uploading it again, but sadly no effect.
It is also worth noting I have tried this with both events with, and without tickets, but all of them had confirmation e-mails. People are successfully registered, they are just never confirmed with that via e-mail.
Here is the screenshot you requested.
|
|
Josh
|
March 31, 2016 at 8:40 pm
Hi there,
Can you make sure that the Ticketing Add-on v2.2.0.p is the version that’s activated on your site?
|
|
cstuckey
|
March 31, 2016 at 8:44 pm
Josh, thanks for replying. As I had mentioned, I did redownload and install the Ticketing Addon. If you are implying there is a way another version could be active (but not installed as a plugin) let me know how to see what one is active.
|
|
Josh
|
March 31, 2016 at 8:51 pm
Hi there,
You go to the WordPress plugins page and check the version number of the Ticketing add-on that’s activated. It should be version # 2.2.0.p and it will have its version number printed there. If it’s not that version, you’ll need to download version 2.2.0.p from your account page and install that one.
|
|
cstuckey
|
March 31, 2016 at 9:03 pm
Yes, it is v 2.2.0.p as I mentioned before.
|
|
Tony
|
April 1, 2016 at 2:52 am
The reason Josh is double checking the latest ticketing system is being used is because espresso_qr_code() is a function from the old ticketing system. It doesn’t exist in the new version of the ticketing add-on (which is why your getting the error).
Can you check if you are using a custom template for the tickets please.
You’ll need to check within /wp-content/uploads/espresso/
Do you have a ‘ticketing’ directory there containing multiple files?
If so rename the ticketing directory to something different ‘ticketing-temp’ for example, then retest the above. Does it then work?
|
|
cstuckey
|
April 1, 2016 at 3:03 am
Tony,
That makes sense. I apologize for the curt reply earlier. And it turns out that is the error. I renamed the folder and it works again. I appreciate both of your help in problem solving this issue. Thanks!
|
|
Tony
|
April 1, 2016 at 3:19 am
You’re most welcome, I’m glad its now working.
Note that when templates have been moved to the uploads folder it is generally because you are using a custom template for the tickets that you don’t want to lose when EE updates.
Now that you have renamed that directory you won’t be using a custom template anymore so I would recommend checking the ticket looks how you are expecting it to.
|
