Top

shop_thumbnails_DBCBackup2

DBC Backup 2 updated for WordPress 3.6

A new version of DBC Backup 2 my WordPress plugin to automatically backup your website has been released. This version has been tested to support WordPress 3.6 and is available to download now.

 

What’s new in DBC Backup 2 v2.2

DBC Backup v2.2 — WordPress

Minor changes to the Settings Page for the plugin, that should make it easier to use.

FIXED – a few bugs

TESTED – on WordPress 3.6

 

Where to get it …

Get from my DBC Backup 2 plugin page

 

 

or

Download via WordPress.org

,

2 Responses to DBC Backup 2 updated for WordPress 3.6

  1. Johannes June 15, 2013 at 6:44 pm #

    Hi Damien,

    I’m trying this plugin now to replace an older backup plugin. It looks nice and small. Unfortunately, it generates lots of PHP notices, which is one of the reasons I want to replace the older plugin. Could you please fix them? They might not matter to most users, but once you develop anything with WordPress, you will want to see PHP errors from your own work, and then it is annoying to see unnecessary notices from plugins with every page load.

    To see the notices, define WP_DEBUG as true in your wp_config.php and e.g. call your settings page. It’s some undefined indexes (use isset or array_key_exists before using an array index) and some undefined variables (you’ll only see this before you save the plugin’s options because dbsbackup-options.php misses an else in line 222).

    Now the backup actually ran and generated 20 MB of error notices (two of them, as far as I can see, all over again)!!! That leaves me actually a bit speechless…

    Greetings from Germany,
    Johannes

    • Damien Saunders June 18, 2013 at 10:51 pm #

      Hi Johannes

      Debug and getting rid of low priority error messages are on my list of things to do. In the latest version of DBC Backup 2 I killed off a few depreciated errors which were messing up the admin page.

      As I adopted the plugin, I’ve not touched the core functions of the php — ‘Don’t fix what ain’t broke’ I think is the saying.

      I had already tried to get rid of some of the other undeclared variable errors, but in ‘fixing them’, I made things worse and broke the plugin.

      If you’re interested, then I’ll give you access to the source on Bitbucket? Otherwise – yes they are on the list of things I’m trying to fix.

      Thanks for getting in contact!

      Cheers

      Damien

Leave a Reply

Read previous post:
Introducing empty – Apache Ant Build for WordPress

Welcome and say hello to empty. empty is a bunch of ANT Build Tasks for WordPress plugin developers that help...

Close