• I got a warning from my host with this quote:

    [12-Jan-2016 15:17:33 UTC] WordPress database error Column ‘offset’ cannot be null for query INSERT INTO wp_wpb2d_processed_files (file, uploadid, offset) VALUES (‘/home/themoon/public_html/wp-content/themes/atahualpa/footer.php’, NULL, NULL) made by do_action_ref_array, call_user_func_array, run_dropbox_backup, WPB2D_BackupController->execute, WPB2D_BackupController->backup_path, WPB2D_Processed_Files->add_files, WPB2D_Processed_Base->upsert

    My error log was huge. I deleted the error log and all is well. What causes this??

    https://www.ads-software.com/plugins/wordpress-backup-to-dropbox/

Viewing 9 replies - 1 through 9 (of 9 total)
  • Me too. Am having to abandon WP2DB because of this unfixed error.
    A pity because it was a great plugin and nothing else backs up my whole site.

    Thread Starter sharonejackson

    (@sharonejackson)

    Well, I am going to simply check once a month and delete the error logs. I don’t want to switch, as you said it is a great plugin except for this problem.

    And it took quite a while to build up that high as well.

    I wish a moderator would drop in here from time to time!!

    @sharonejackson

    But is the error harmless? You had better check the integrity of the backups it is making. Otherwise you may get a nasty surprise if you actually need them.

    Thread Starter sharonejackson

    (@sharonejackson)

    You have a point. What other backup plugin do you plan to use?

    I’ve started using DropBox Full Backup

    It is neat and has a restore function as well. But it only backs up the site it is installed in (presumably for multisite you only need to run it in the head site). It is free for manual backups – charged per run for automatic.

    It does not do the rest of the site outside the WP installation, such as files that may be above that point in the file system. WPB2D did the whole lot.

    Hi, I am using (free) WPB2D v.4.4.1 and am recently having this error:

    “WordPress database error Column ‘offset’ cannot be null for query INSERT INTO wp_wpb2d_processed_files (file, uploadid, offset) VALUES…”

    The error was so excessive that it filled the error_log to 200MB and almost crashed the website due to overuse of disk_usage_space.

    I have unlinked the account and linked it to another Dropbox account and the backups started but the error_log file continues to grow again with the above entries for every file.

    Can someone please help?
    J

    I have given up on WPB2D and have now used antipole’s suggestion of DropBox_Full_Backup and love it!. So easy to use!

    Thread Starter sharonejackson

    (@sharonejackson)

    I know, I have to go go in to the directory every few days and remove a GIGANTIC error log file. I will try your suggestion, thank you jenfre13.

    They told me they would be fixing this on the next upgrade but could not say when that will be. So, bye bye!

    All I do to fix the issue is change in

    wp-content/plugins/wordpress-backup-to-dropbox/Classes/Processed/Files.php

    Change lines 69 to 74 from

    $this->upsert(array(
    'file' => $file,
    'uploadid' => null,
    'offset' => null,
    ));
    }

    to

    $this->upsert(array(
    'file' => $file,
    'uploadid' => null,
    'offset' => 0,
    ));
    }

    Problem resolved.

    Original post: https://www.ads-software.com/support/topic/column-offset-cannot-be-null

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘Error log up to 45 MB’ is closed to new replies.