someone in the SlickStack Discord was asking about this question and he discovered that MU plugins installed by SlickStack were causing the fatal error, after he tried to restore the backup and skipped the MU plugins the fatal error disappeared
MU plugins installed by SlickStack were causing the fatal error
This is not really a SlickStack issue, it’s a general WordPress concern. Anytime you backup your WordPress site to remote services, you shouldn’t include the MU plugins, those are usually meant for the hosting environment only and can be skipped
You can probably also skip the wp-config.php in your backups too, at least for SlickStack and other DevOps tools that generate that file for you automatically.
That would be ideal. But too many WP products are creating folders all over the place these days which has become a mess.
Author
Posts
Viewing 8 posts - 1 through 8 (of 8 total)
Please Donate
Friends, the time has come for us to ask for your financial support. After 5+ years of (growing) expenses, and taking time away from consulting and services, we must start generating donations in order to continue this level of rapid project development. Please consider donating, so that we can keep SlickStack free and open source. Thank you! 🙏 😍
