The plugin was updated yesterday.. and this has cost me $200 to upgrade plan.
I have deactivated the plugin for the time being
Hi there @possum66,
It’s likely that your Newsletter task scheduler option is set to MailPoet’s own script in MailPoet > Settings > Advanced. I’m afraid that our tasks scheduler is incompatible with SiteGround.
You will want to change this setting to Visitors to your website (recommended). That should sort it. You can see more details about this issue here:
https://kb.mailpoet.com/article/131-hosts-which-mailpoet-task-scheduler-wont-work
I hope this helps!
I’m experiencing a similar problem with the SiteGround. I’m experiencing MySQL database limit issues because of MailPoet. I’ve had the sever side cron (Linux cron) scheduler selected for months, but now all of a sudden I’m experiencing the MySQL database limit issues.
So I’m wondering if MailPoet is not a good plugin for SiteGround users?
If you are using Server side cron (Linux) and you are still experiencing issues, I’d give the following things a try:
– Reduce the frequency of which your cron job triggers MailPoet Task Scheduler
– If the issue persists, try switching your Newsletter task scheduler (cron) to Visitors to your website.
Hopefully, one of these things will do it. Let us know!
Hi, thank you for replying. I went to on SiteGround to see about editing the Cron Job. Right now it’s set to Once Per Hour (0****), so I switched it to Once Per Day (00***). Or should I switch it to Once Per Week? (by the way, in MailPoet Advance settings, it says “frequency running every minute: *1***” Not sure why it says something different in the settings than what I set in SiteGround.
I’m not sure why this is happening all of the sudden. I’ve had MailPoet for like two years now, and for the last few months I haven’t sent out emails using the system.
I’m wondering if I should try to moving my site to another server, like Plesk/Rootpal. I don’t want to use another email service. I like MailPoet.
-
This reply was modified 4 years, 7 months ago by
Bakari.
-
This reply was modified 4 years, 7 months ago by Bakari.
-
This reply was modified 4 years, 7 months ago by Bakari.
Hi there,
@bakari45 I see that we’re working with you via a ticket and your issue is not related to Cron.
@possum66 Can you please let me know if changing the Cron option helped?
@treibalen, it appears that the issue was caused by WPReset backing up data files were not being deleted. So I had a lot of MailPoet data files get backed up on my server. The tech person I hired to fix
This is what he wrote about MailPoet:
`The new database size was 182.2 MiB and I managed to reduce it to 167.1 MiB
The database size depends on your content and it is not critical anymore. Some
improvements can be made by removing unneeded tables.
I will say Mailpoet tables are the 3 biggest ones, but that can be easily solved by
removing the newsletters you do not need anymore.`
It seems that I can still use MailPoet, but I need to watch how it’s contributing to the database size. I’ll keep the cron settings in there to see if it helps.
Thanks for getting back with me.
Hi there @bakari45,
Some improvements can be made by removing unneeded tables.
If there are any MailPoet tables’ backups created by WPReset that are overloading your database, please remove them and disable this functionality for MailPoet tables.
Please reach out to your tech person or WPReset support to do that as it’s not something within the scope of our support.
In any case, I’m glad that you found a root cause.
Enjoy the rest of your day and stay safe!
