Matt Scheidler
Forum Replies Created
-
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] Errors with version 5.6.6Thank you for the reply.
Three others have commented to say “it’s happening to me too” but their posts are moderated before you can see them. (I do encourage others to open their own topic per the forum guidelines.)
I will send an email to Support to continue the conversation.
Forum: Plugins
In reply to: [BackWPup – WordPress Backup & Restore Plugin] Errors with version 5.6.6I have one site on Ionos hosting, which is not affected by the current issue.
The remainder of my 100+ sites, including all sites affected by the current issue, are in a cPanel environment.
Two other users have reported the same thing after also upgrading to 5.6.6, but the moderator removed their comments per the forum guidelines. As the OP, I’ll provide more info.
Five of my sites have encountered the issue since upgrading.
Of note, four of the five sites were at 256M. I increased them to 512M and all but one ran the next night.
One of the five was at 128M. I increased it to 256M but it failed again the next night. I’ve now just increased it to 512M like the others. I’m not sure what is different about this site, but backups were being performed with a 128M memory_limit prior to your update and now even 256 isn’t enough.Separately, I took one of the affected sites using your new UI, and changed Reduce Server Load to “minimum” (it was “disabled”) and lowered “maximum number script execution time” to 20. (it was 30) and then lowered its PHP limit back to 256M.
I cannot immediately identify any common factor in these 5 sites that might be contributing to the issue. I am happy to do this troubleshooting, as I have done with past issues, and will report back.
Thank you.
- This reply was modified 3 months ago by Matt Scheidler.
Rob, thank you! That is sound advice.
I think I found the IP that I need to allow, so we’ll give it a try.
Also, I’m glad that my question can help your knowledgebase!
Thanks for the prompt reply and the quality plugin.
- This reply was modified 4 months ago by Matt Scheidler.
Forum: Plugins
In reply to: [Download Manager] Version 3.3.38 breaking sitesYour most recent 5* review literally is from me, from earlier this month!
https://ww.wp.xz.cn/support/plugin/download-manager/reviews/
- This reply was modified 5 months, 2 weeks ago by Matt Scheidler.
Forum: Plugins
In reply to: [Download Manager] Version 3.3.38 breaking sitesI opened this topic at midnight and updated it at 1am locally. Glad to see the ongoing attention and fix, while I was asleep. I have now updated all sites to 3.3.39 and it looks like all is well.
Thanks again for the prompt response and for a quality plugin.
Forum: Plugins
In reply to: [Download Manager] Version 3.3.38 breaking sitesCuriously, after I manually restored the four sites, approximately one hour later they all broke again. I have now downgraded them to 3.3.7 and disabled auto-updates.
All my sites are now in the same status – 3.3.7, auto-updates disabled – and I’ll await a new update. Thank you for your prompt response.
Forum: Plugins
In reply to: [Download Manager] Version 3.3.38 breaking sitesBy the time I’d composed this message, two more sites had gone down for the same reason. I have disabled auto-updates on my remaining sites running your plugin. Thank you for your help.
- This reply was modified 5 months, 2 weeks ago by Matt Scheidler.
Thank you. I just sent an email to Support.
Thank you for the reply. Additional information:
On Friday 12/5 I took two of the sites where the legacy jobs stopped running, and created new jobs using the new UI. Upon creating these jobs, they each ran once. However, neither of them have run since. Both logs show a last-run date of 12/5.
I have just deleted and reinstalled BackWPUp on one of these two sites and re-created the job with the new UI, to see if that makes a difference.
- Site one – completely started over with new instance of 5.6. (Legacy Job no longer exists.)
- Site two – job created with new UI. (Legacy Job still exists, though it isn’t being triggered.)
I plan to report back tomorrow with the results.
- This reply was modified 6 months ago by Matt Scheidler.
Update: I downgraded one site to 5.5.2 on Friday, and the Legacy Job has run successfully the past 2 nights.
Thank you for the reply.
I performed the test you recommended, on one of the affected sites. The post published 10 minutes after I scheduled it, as expected.
The backup jobs stopped running on 101 sites, immediately after I updated those sites to 5.6.
Equivalent jobs are still running the same as always on the four sites that are running 4.1.7.
I can navigate to the legacy job, and click Run Now to start it manually, and the job runs. But the “Last Run” date still shows November 25, 2025 for all the sites that updated to 5.6 on that date.
Thank you for the reply.
Our most recent sites, where 5.x was installed in the first place and we’re using the new UI, are working fine.
A handful of sites still running 4.1.7, because I was able to turn off auto-updates before they updated to 5.0, are still working fine.
All the sites that updated to 5.0 before I realized what was happening, I’ve worked with you through all the issues and have kept them on your latest version, utilizing the Legacy UI with cronjobs that are set on the server.
- I have just tested on a site that is running 5.6.0.
- The small database only job did not generate a backup.
The Logs page shows no entries since November 25, from either the legacy job or the new job I just created.
Thank you.
Original poster here. After I took my request to Marcus’ website, he was able to help me resolve my issue. Thank you Marcus!
Marcus, thank you! I just sent you a message via the Contact page on your site.
Forum: Plugins
In reply to: [X3P0: Progress] Percentage displayWonderful. Thanks again for the replies.
I appreciate your work. I’ve still got a client site actively using your Whistles plugin from many years ago!