|
vrwaadmin
|
December 4, 2019 at 4:14 pm
I know it set it once, but I can’t locate the page to edit SMTP and accounts information for the outgoing messages sent from EE4.
|
|
Josh
|
December 4, 2019 at 7:36 pm
Hi,
The outgoing messages are actually sent through the wp_mail() function, so what ever you set up with SMTP was likely using a plugin. If you no longer have an SMTP plugin, this one is actively maintained and supported:
https://wordpress.org/plugins/wp-mail-smtp/
|
|
vrwaadmin
|
December 5, 2019 at 8:18 am
Thanks Josh. I should have added later after some digging but I went straight to bed so I could dig in again this morning. In the digging, I found EE recommendations for a mailing system and signed up for and setup Mailgun. It’s active and the test emails are going on.
Now, oddly, my message seems stuck in the Queued for sending.
Is there something I need to do to tell EE that Mailgun is in play?
Will Mailgun just take over for the wp_mail() function? I didn’t see anywhere to make it do so.
|
|
Josh
|
December 5, 2019 at 8:35 am
Is there something I need to do to tell EE that Mailgun is in play?
No.
If the messages stay in the queue after 5 minutes, after refreshing any page on the site, then that could mean there’s an issue related to scheduled tasks not working on your site.
A quick way to check scheduled tasks functionality is you go to your site’s Tools > Site Health page. After that page loads it will check scheduled tasks and give you a status message on how that went.
|
|
vrwaadmin
|
December 5, 2019 at 9:33 am
Everything says good in there, except PHP was at 7.2 so I upgraded that. (We’ll see what that broke. 😉
In the EE – Messages – Settings tab, should I disable “This messenger delivers messages via email using the built-in wp_mail function included with WordPress” option? Does the reference to wp_mail mean that wp_mail is still the active mail engine?
|
|
Tony
|
December 5, 2019 at 10:40 am
No, wp_mail() is a function and is used regardless as Mailgun (and others) hook into wp_mail to alter the settings to suit.
On the messages activity list, if you click the icon for one of the messages, does it send?
|
|
vrwaadmin
|
December 5, 2019 at 11:21 am
Yes, that is the only way I can get them to send. No luck in disabling some Plugins I thought might be the problem.
|
|
vrwaadmin
|
December 5, 2019 at 11:38 am
And it looks like the emails are still going out through my GSuite. I mistyped and outgoing address and got an undeliverable back to my email. So I still have to fight with Mailgun to get that working.
|
|
Tony
|
December 5, 2019 at 12:18 pm
Install WP Crontrol.
Go to Tools -> Cron events.
Do you have these 3 listed there?
AHEE__EE_Messages_Scheduler__generation
AHEE__EE_Messages_Scheduler__sending
AHEE__EE_Messages_Scheduler__cleanup
|
|
vrwaadmin
|
December 5, 2019 at 1:41 pm
I do not see “AHEE__EE_Messages_Scheduler__sending”
The first and last you listed are there.
|
|
Tony
|
December 5, 2019 at 2:03 pm
Ok, that’s why.
If you deactivate and reactivate EE does it show up again?
|
|
vrwaadmin
|
December 5, 2019 at 2:09 pm
It does not.
|
|
vrwaadmin
|
December 5, 2019 at 3:43 pm
Should I remove and reinstall the EE core?
|
|
vrwaadmin
|
December 6, 2019 at 1:14 am
I am not sure why, but after Deactivating and Reactivating, it’s now there! It’s working!
Thanks again!
|
|
Tony
|
December 6, 2019 at 1:45 am
My apologies for the delay, I see you’ve marked this as resolved now but I’ll answer the above for future readers.
Should I remove and reinstall the EE core?
You could, but it’s very unlikely to fix the problem unless the something was missing from the install (in which case I’d expect other errors not just the above).
I am not sure why, but after Deactivating and Reactivating, it’s now there! It’s working!
EE checks if AHEE__EE_Messages_Scheduler__generation has been set and if not, sets up all 3 of the above crons, if it has been set it skips setting them again (if AHEE__EE_Messages_Scheduler__generation it is expected that all of the crons are set).
So what may have happened is you de-activated EE at the right time for AHEE__EE_Messages_Scheduler__generation to run, it will try and run and not be rescheduled so then when you re-activate its missing, meaning EE reschedules all 3 tasks again.
—
I can’t think of a reason for that cron task to have gone missing, if it continues to happen please do let us know, we may need to add some debug code to see why it’s happening.
|
|
vrwaadmin
|
December 6, 2019 at 1:51 am
I see you’ve marked this as resolved now but I’ll answer the above for future readers.
That’s why you’re awesome, Tony! Thanks for the follow up. I really appreciate all the help you all have been able to provide when I run into problems.
|
|
Tony
|
December 6, 2019 at 3:19 am
You’re most welcome, we are here to help 🙂
If you have a minute it would be great if you could share your experience with Event Espresso or maybe provide a review on WP.org.
Although no pressure to do so if you prefer not to.
|
|
vrwaadmin
|
December 6, 2019 at 5:43 am
Done, and I stand by what I said. But I typed it out before I went back in the site this morning and found the __sending cron job missing.
De/reactivating brought it back again, but wonder what is happening to keep removing this entry.
|
|
Tony
|
December 6, 2019 at 5:57 am
If you use cron tools to run the cron, does it throw any errors?
You may need to check your servers error logs as they may not be set to display.
|
|
Tony
|
December 6, 2019 at 8:02 am
I just realised I made a couple of assumptions in my last post.
To run the cron: Tools -> Cron Events
Find the cron in the list and on the right of the screen (you’ll likely need to scroll) hit Run Now.
Any errors thrown during the request should be saved to your servers error logs, most hosts give you access to it in your control panel, if not check for an error_log file or similar in the root directory using FTP/File Manager.
Again if there’s none to be found, add this to your wp-config.php file:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
Add that above the line that has /* That's all, stop editing! Happy blogging. */ and repeat the test, any error will be logged to/wp-content/debug.log
(That last step makes your errors log in publicly available location, so don’t leave that code in place as first that file could end up huge if you forget about it and also you don’t want to leave your error log publicly accessible for various reasons)
|
|
vrwaadmin
|
December 11, 2019 at 4:30 am
Hi there. Sorry for the delay. This hasn’t occurred again, so I haven’t proceeded with the above. I will bookmark this in case the issue happens again. Thanks Tony!
|
