• Does exactly what I need it to do. Had no issues so far. Permissions etc. may be something to keep in mind, since the files it creates will belong to the web server’s user (which may or may not be the same as the user doing the FTP uploads etc.)
    If you plan ahead and make your local test domain URL the byte-for-byte same length as the deployment site, it’s a great way to move things to and from with just a search and replace in the SQL dump.

Viewing 1 replies (of 1 total)
  • Thanks mark_al appreciate your comment follow up.

    I agree with the planning, etc. But this had nothing to do with permissions, FTPing, etc. The big issue was that there seemed to have been some integration of this code into another plugin (WPremote). 😉

    What was happening…

    The plugin BackUpWordPress was removed. Which means it should not function and there should be no scheduled backup.

    WPremote was installed (another plugin for a completely different thing); and appeared to pick up the scheduled backup settings from the removed BackUpWordPress plugin. But the (un)scheduled backup would not display in wp-admin; and it would run! (Remember, BackUpWordPress was removed so it should not have been running).

    What I was trying to say was that maybe the functionality of the two plugins should be kept separate, no? 🙂

    A bit off topic…
    WPremote is great, but alas, given the issues here, is not a feasible solution in my specific scenario – But I’d still recommend it to others.

Viewing 1 replies (of 1 total)

The topic ‘Does what I need’ is closed to new replies.