GaryCameron

In my opinion, requiring Network Activation and having the settings page on the Network dashboard is the correct method for a backup plugin that is multi-site compatible.

When I see the settings appear in the Network dashboard I know that the author has considered multi-site and that these settings won’t be available to mortals.

The only thing I would add is a blurb in the installation instructions that specify Network Activate for multi-site and specify where the settings panel is.

Multi-site isn’t as niche or as scary as some people may think. There seem to be a fair number of people using it. I am testing this plugin on two multi-site installs and have done the following:

Network Activate and configure the backup through the main blog. (Need to be Super Admin to do this.)

I see only two things that need to happen in order for this plugin to function correctly with multi-site. Both of which the plugin SHOULD be doing already.

1 – Grab ALL database tables.

2 – Make sure ALL of wp-content is backed up minus any cache folders. (Multi-site adds two folders: blogs.dir; mu-plugins)

Am I missing anything?

Just finished upgrading and got the follwing error.

The plugin simple-image-widget/simpleimage.php has been deactivated due to an error: Plugin file does not exist.

Re-activated the plugin and all seems well.

This was after updating on a multi-site install where the plugin is Network Activated.

That was quick. Thank-you. ??

Yep. Same thing is happening with one of my sites. For what it is worth, I also have multi-site enabled.

Also, WordPress continues to show I have 1 plugin that needs updating even after the update.

I am happy to see someone has picked up the task of supporting this plugin.

I have been using this plugin for some time on a series of blogs. So far I haven’t noticed any issues with regard to WP 3.5.

Since this plugin is no longer supported, I am actively looking for a replacement.

It would appear that this plugin is not multi-site compatible. At least not if you have multi-site set for sub-domains (as opposed to sub-directories).

The WordPress handler for sub-domains is kicking in before the plugin can intercept the mobile sub-domain.