Please Backup MORE than db & wp-content

I don’t plan on it at this time, since I’m trying to minimize the load you’re asking WordPress to put on itself.

Also, no plugin should be storing content outside of wp-content (really outside of wp-content/uploads, but that’s a loosing battle).

Are these others apps that you’re using?

I’d second the motion to back up more, because if all the files aren’t backed up:
1) How are you going to know what plugins to install if you need to restore from the backup? Take notes?
2) Even if you did take notes, you’d have to install all the plugins again, and some might premium and not from the www.remarpro.com repository, so that will take some time.
3) What happens if you’ve got plugin settings in the DB but have no corresponding plugin installed and activated?

With all the files backed up, all I have to do is grab the .zip/tar.gz/etc. and unarchive it on the server. Then I’ve got all my files back. Import the DB and I’m back in business. Still not 1-click (unless you’re on WPengine :), but not too bad.

When you start managing 50+ sites, these little tasks start to really add up, so I’m always looking for better ways to make this stuff quicker.

Cheers!

Oops, never mind about the plugins; duh, I forgot they’re in wp-content until I unzipped what the plugin made and was reminded. I would have edited my previous post so I didn’t look like a bozo, but the edit time window expired and preserved my bozo-ness forever.

So then the restore process would be:
1) Install a fresh copy of WP
2) Delete wp-config.php and the contents of wp-content
3) Get the DreamObjects backup and unzip it
4) Move the restored contents of wp-content into place
5) Move the restored wp-config.php into place
6) Import the DB
7) Login and test the site
8) Enjoy a nice cup of Darjeeling (or your favorite beverage)

How does that look?

I now see why it’s unnecessary to back up anything more than wp-config.php and wp-content. What about a heavily modified .htaccess?

It backs up WP-config if it can find it. I’ve had hit and miss issues with .htaccsss, but I’ll give it one more pass with v 4. I’ve been working on a major overhaul to the interface, plus a better status system. ??

Thanks, I had no issues with wp-config.php, but it was in the standard location.

.htaccess is now in version 4.0 ??

Cool. Hmmm, .htaccess wasn’t backed up in 4.0. On this site I do have WP in a subdirectory (yeah, I know, but this is a legacy situation). There is a .htaccess in that subdir (along with wp-config.php, which was backed up fine) along with one in the root dir of the domain (one level up). Neither .htaccess showed up in the .zip.

The permissions of both .htaccess files are 644. This particular site is on DreamHost shared hosting.

It did back up the execution-prevention .htaccess located in wp-content/uploads.

I see this line in debug.txt:

wp-config.php added to backup list.

but no mention of .htaccess (and I see in dhdo.php that I should see it mentioned if it’s added).

That means it can’t find it :/ which is the problem I’d been having with the backup of htaccess all along. I’ll keep kicking at it.

Looks like you don’t need to escape the dot in the filename inside the quotes on lines 240 & 241 of dhdo.php. Currently they are:

if ( file_exists(ABSPATH .’\.htaccess’) ) {
$backups[] = ABSPATH .’\.htaccess’ ;

Eliminating the \ gives joy:

if ( file_exists(ABSPATH .’.htaccess’) ) {
$backups[] = ABSPATH .’.htaccess’ ;

Cheers

Okay I’ll patch this for .1

https://github.com/Ipstenu/dreamobjects/issues/9

I’m facepalming the hell out of this.

Sometimes it takes a village! ?? Or as Linus’s Law states, “Given enough eyeballs, all bugs are shallow.” I’m happy I was able to lend a couple of eyeballs.

Hi Mika, wanted to say thanks for rolling in the .htaccess fix in 4.0.1. Cheers!

Welcome ??