restoring Updraft backup results in WordPress fatal error
- This topic is empty.
-
AuthorPosts
-
Kenneth
Guestwhy did this happen on my SlickStack server
did SlickStack support UpdraftPlus
Margaret
Guestsomeone 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
Brenda
GuestSlickStack supports Updraft 100%, actually it’s recommended:
Christine
GuestMU 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
Kathleen
Guestmore info about Must Use plugins
Raymond
GuestYou 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.Steven
Guestall I know is it’s not Updraft’s fault 😬
Ronald
GuestIdeally you should only backup your database and these folders:
– /wp-content/plugins/
– /wp-content/themes/
– /wp-content/uploads/That would be ideal. But too many WP products are creating folders all over the place these days which has become a mess.
-
AuthorPosts