|
paintforfun
|
July 20, 2018 at 8:04 am
I am pretty sure my emails are failing due to changing to HTTPS. Before the change everything was working fine. Other emails are being sent from the website its just wont send when it is related to Event espresso. it shows in the table as failed. This is a message I get when clicking the i:
“Message was not executed successfully.
Messenger and Message Type were valid and active, but the messenger send method failed.”
email i use : WP mail smpt google.
when I try to send a test email I am being redirected to a page with this message:
http://www.paintforfun.com.au is currently unable to handle this request.
HTTP ERROR 500
Any thoughts? Thanks!
|
|
paintforfun
|
July 20, 2018 at 8:14 am
more info: i checked the wp-mail-log and I see the emails as sent it does not show any error.
|
|
Tony
|
July 20, 2018 at 9:41 am
Hi there,
http://www.paintforfun.com.au is currently unable to handle this request.
HTTP ERROR 500
Looks like the site is still loading over HTTP.
How did you enable HTTPS on the site? Are you still loading the site of HTTP and just redirecting everything over to HTTPS?
If you go to Dashboard -> Settings -> General
Do the ‘WordPress Address’ and ‘Site Address’ fields show as HTTP?
|
|
paintforfun
|
July 21, 2018 at 7:32 am
Hi its shows as HTTPS. I used the simple SSL plugin to go from HTTP to HTTPS
|
|
paintforfun
|
July 22, 2018 at 5:06 am
This reply has been marked as private.
|
|
paintforfun
|
July 23, 2018 at 4:24 am
This reply has been marked as private.
|
|
paintforfun
|
July 23, 2018 at 4:31 am
Event espresso-> messages->settings -> it is already set to on the same request
|
|
Tony
|
July 23, 2018 at 7:49 am
Hi its shows as HTTPS. I used the simple SSL plugin to go from HTTP to HTTPS
Hmm, ok.
If you run a test email again so you get the error 500 again, then check the error log above, what error does it show?
How exactly are you sending a test email?
Message: Incoming data for the Gateways data handler must have an EE_Transaction object as the value for the first array index.
This may be another symptom of the problem.
If you go to Event Espresso -> Messages -> Message activity, do you have a lot of messages waiting to generate and waiting to send?
|
|
paintforfun
|
July 23, 2018 at 10:22 pm
do you have a lot of messages waiting to generate and waiting to send? yes. it shows as failed.
I no longer think it is due to transferring to https it is something else. I cant figure out what but this problem puts a massive pressure on the business as things are being done manually or transferred to Eventbrite for checkout and I have to solve it ASAP.
Any leads?
|
|
Tony
|
July 24, 2018 at 2:16 am
Any leads?
Can you answer this question, please?
If you run a test email again so you get the error 500 again, then check the error log above, what error does it show?
How exactly are you sending a test email?
If there is an error being thrown during the request it may well point to the cause.
do you have a lot of messages waiting to generate and waiting to send? yes. it shows as failed.
So you don’t have any messages ‘waiting to generate’ they are all just failed?
When you say the emails need to be done manually, in what way? You already mentioned above that the emails are set to send ‘on the same request’, so manually resending them shouldn’t make any difference as its almost exactly the same as what EE is doing.
|
|
paintforfun
|
July 24, 2018 at 4:24 am
This reply has been marked as private.
|
|
Tony
|
July 24, 2018 at 4:45 am
And I understand that EE should handle the messaging part – its exactly why I paid for it but it is not working.. Thats why the business manager needs to manually send the emails..
No-one is saying EE is working as it should here (although the problem may not actually be with EE based on the above), nor that there isn’t a problem that needs to be fixed but what the problem is isn’t clear just yet.
EE is correctly triggering the functions to send the email, the above error indicates there’s an issue with the data used to build the email but theres multiple possible causes for that.
You mentioned the messages are sending manually, yet if you are using EE to manually resend the message there should be no difference between that manual resend and the request EE uses to generate and send the messages.
Hope my answers are clear and we will resolve this very soon.
Thanks!
You missed one:
When you say the emails need to be done manually, in what way? You already mentioned above that the emails are set to send ‘on the same request’, so manually resending them shouldn’t make any difference as its almost exactly the same as what EE is doing.
To rephrase, what exact steps are you taking to ‘do the emails manually’?
|
|
paintforfun
|
July 24, 2018 at 5:20 am
Manually->
created a template outside of WordPress and every time I have someone registered to an event I modify with details it and send it via gmail.(Not threw EE in any way)
-The most manual that you can get.
|
|
Tony
|
July 24, 2018 at 9:51 am
The error message above is showing there’s an issue with the data being pulled in to try and generate at least 1 message in the queue.
Can I take a quick look over the admin? If so you can sent temp login details using this form:
https://eventespresso.com/send-login-details/
|
|
Tony
|
July 25, 2018 at 10:28 am
Thank you, so the issue wasn’t with EE or even changing to HTTPS.
The problem was due to a conflict between Duplicator Pro and WP Mail SMTP, if you use oAuth in the WP Mail SMTP plugin Duplicator replaces the oAuth library with its own version which casues a fatal error each time WP Mail SMTP attempted to send an email.
I’ve de-activated Duplicator Pro on the site and now the emails send fine, you can’t use both those plugin at the same time.
|
|
Tony
|
July 25, 2018 at 10:31 am
This is the error that was being thrown:
Warning: json_decode() expects parameter 1 to be string, array given in /wp-content/plugins/duplicator-pro/lib/google/apiclient/Auth/OAuth2.php on line 184
Fatal error: Uncaught Google_Auth_Exception: Could not json decode the token
in /wp-content/plugins/duplicator-pro/lib/google/apiclient/Auth/OAuth2.php:186 Stack trace:
#0 /wp-content/plugins/duplicator-pro/lib/google/apiclient/Client.php(218): Google_Auth_OAuth2->setAccessToken(NULL)
#1 /wp-content/plugins/wp-mail-smtp/src/Providers/Gmail/Auth.php(121): Google_Client->setAccessToken(Array)
#2 /wp-content/plugins/wp-mail-smtp/src/Providers/Gmail/Auth.php(53): WPMailSMTP\Providers\Gmail\Auth->get_client()
#3 /wp-content/plugins/wp-mail-smtp/src/Providers/Gmail/Mailer.php(79): WPMailSMTP\Providers\Gmail\Auth->__construct()
#4 /wp-content/plugins/wp-mail-smtp/src/MailCatcher.php(80): WPMailSMTP\Providers\Gmail\Mailer->send()
#5 /wp-includes/pluggable.php(481): WPMailSMTP\MailCatcher->send()
#6 /wp-content/plugins/wp-mail in /wp-content/plugins/duplicator-pro/lib/google/apiclient/Auth/OAuth2.php on line 186
|
