3.0.3 broken

  • Resolved Pieter Hartsook

    (@hartsook)


    12 years ago

    The “upgrade” to 3.x caught me by surprise while I was on vacation. Several of my clients upgraded and have lost all the job settings and schedules I had created for them and the backups are no longer working.

    PLEASE. PLEASE, PLEASE… in the future if you’re going to fork the code and make a major changes, offer a beta version for us to experiment with before putting the code out for the general updates!!!

    Also, if you’re going to blow away all the user job configurations, give us a method to save the job settings (xml file?) and a way to restore the jobs in both the current version (in case we need to revert) and import into the new version. I have over the years strongly recommended this plugin, but the way you have released this 3.x upgrade was very unprofessional and unnecessarily raises credibility issues with users. The stats show over half-a-million downloads of the plugin, consider the work you are causing by making every user who upgrades recreate jobs, schedules, passwords, authentication, etc.

    Here’s one error log from a simple database backup that used to work in the previous version for your consideration:

    [INFO] BackWPup version 3.0.3; WordPress version 3.5.1; A project of Inpsyde GmbH developed by Daniel Hüsken
    [INFO] This program comes with ABSOLUTELY NO WARRANTY. This is free software, and you are welcome to redistribute it under certain conditions.
    [INFO] BackWPup job: Basic backup; DBDUMP
    [INFO] BackWPup cron: 0 3 * * 6; Sat, 9 Mar 2013 @ 03:00
    [INFO] BackWPup job started manually
    [INFO] PHP ver.: 5.2.17; cgi-fcgi; Linux
    [INFO] Maximum script execution time is 0 seconds
    [INFO] MySQL ver.: 5.5.30-log
    [INFO] curl ver.: 7.24.0; OpenSSL/1.0.0
    [INFO] Temp folder is: /home5/venturev/public_html/wp-content/uploads/backwpup-8ff58-temp/
    [INFO] Logfile folder is: /home5/venturev/public_html/wp-content/backwpup-c61f0-logs/
    [INFO] Backup type is: archive
    [INFO] Backup file is: /home5/venturev/public_html/wp-content/backwpup-c61f0/backwpup_database_2013-03-03_22-13-40.zip
    [03-Mar-2013 22:13:40] 1. Try for database dump …
    [03-Mar-2013 22:13:40] Connected to database venturev_wrd1 on localhost
    [03-Mar-2013 22:13:40] Dump database table “wp_StatSurfer”
    [03-Mar-2013 22:15:49] Dump database table “wp_StatSurfer_countries”
    [03-Mar-2013 22:15:49] WARNING: Database error MySQL server has gone away for query SHOW CREATE TABLE wp_StatSurfer_countries
    [04-Mar-2013 06:15:49] PHP Fatal error: Call to a member function fetch_assoc() on a non-object in /home5/venturev/public_html/wp-content/plugins/backwpup/inc/class-mysqldump.php on line 311
    [03-Mar-2013 22:15:49] ERROR: Call to a member function fetch_assoc() on a non-object
    [03-Mar-2013 22:15:49] 1. Script stopped! Will start again.
    [03-Mar-2013 22:15:59] 2. Try for database dump …
    [03-Mar-2013 22:15:59] Connected to database venturev_wrd1 on localhost
    [03-Mar-2013 22:15:59] Dump database table “wp_StatSurfer”
    [03-Mar-2013 22:17:49] Dump database table “wp_StatSurfer_countries”
    [03-Mar-2013 22:17:49] WARNING: Database error MySQL server has gone away for query SHOW CREATE TABLE wp_StatSurfer_countries
    [04-Mar-2013 06:17:49] PHP Fatal error: Call to a member function fetch_assoc() on a non-object in /home5/venturev/public_html/wp-content/plugins/backwpup/inc/class-mysqldump.php on line 311
    [03-Mar-2013 22:17:49] ERROR: Call to a member function fetch_assoc() on a non-object
    [03-Mar-2013 22:17:49] 2. Script stopped! Will start again.
    [03-Mar-2013 22:17:51] 3. Try for database dump …
    [03-Mar-2013 22:17:51] Connected to database venturev_wrd1 on localhost
    [03-Mar-2013 22:17:51] Dump database table “wp_StatSurfer”
    [03-Mar-2013 22:18:06] ERROR: Aborted by user!

    https://www.ads-software.com/extend/plugins/backwpup/

Viewing 4 replies - 1 through 4 (of 4 total)
  • Thread Starter Pieter Hartsook

    (@hartsook)

    By the way, this lack of wide beta testing before a major revision is a repeat of the problems you caused back in July 2011 with the “upgrade” to version 2.0. that broke the previously working code (see: “WordPress BackWPup backup plugin is broken” article in case you’ve forgotten).

    You have some sophisticated users and real fans for your plugin. We would be happy to help you test your code and get the bugs out BEFORE you release it to the public. All you have to do is ask..

    I get the fetch_assoc() error as well, and this post is now 8 months old. What’s the solution?

    Hello JoshKay,

    the fetch_assoc error is a error of the previous error. That is why the fetch_assoc error can’t fixed. You can only look why the Database has gone away and that is hoster specific. Theat means i must have more details to can help you.

    Hi Daniel,

    Thanks for the reply. When I see the error again I’ll post more details.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘3.0.3 broken’ is closed to new replies.