Hello,
Thanks for reaching out. We’ve identified that the recent critical error you’re seeing is happening when both the free and Pro versions of BackWPup are active at the same time.
It’s not advisable to keep both active—if you’re using the Pro version, please deactivate the free one. This should resolve the issue right away.
Let us know how it goes!
Best regards,
It had something to do with MAINWP and BackWPUp. But since BackWPup has had so many issues in the last couple of upgrades, I’ve removed it from all my client sites and we’re implementing another solution.
We did NOT have the PRO version, for what it’s worth.
Hi,
Thanks for reporting this. The issue has been confirmed by the MainWP team — the MainWP BackWPup Child Extension is currently not compatible with the latest BackWPup version.
They’ve acknowledged this on their site (link) and have temporarily removed the extension from their package while they work on restoring compatibility.
In the meantime, we recommend deactivating the MainWP BackWPup Extension to avoid any issues.
We’ll keep you posted as soon as compatibility is restored. Thanks for your patience!
Hi,
Good news! MainWP has released an update for their Child plugin that restores compatibility with the latest BackWPup version.
Please update the MainWP Child plugin to the latest version from your WordPress dashboard or download it from here:
👉 https://wordpress.org/plugins/mainwp-child/#developers
Thanks again for your patience while this was being resolved!
