"Column 'offset' cannot be null"?

Still having the issue with 4.4.1.

Also having this issue with 4.4.1

This is driving me nuts so I decided to look deeper.

The issue is file wordpress-backup-to-dropbox/Classes/Processed/Files.php

Toward the bottom of the program change from

$this->upsert(array(
‘file’ => $file,
‘uploadid’ => null,
‘offset’ => null,
));

to

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

so change the offset default from null to 0 and the issue goes away

It should not be a problem but it seems some versions of MySQL are not handling defaults right. Hopefully if this is the solution Michael will update and release as 4.4.2

Thanks for that fix RichHelms – now I can stop my web server disk space from being eaten up with error logs!

Yes, just deleted a 189.9 MB error log file 2 minutes ago. RichHelms, just to clarify, the last 5 lines of your code are the corrected version?

Thank you for this, I have used this plugin on many of my clients sites and this has been a nightmare.

The issue is file wordpress-backup-to-dropbox/Classes/Processed/Files.php
The only problem line is ‘offset’ => null,

By changing it to
‘offset’ => 0,

the problem goes away. I have done this on all of my sites at a particular host and it has solved the issue.

I was hoping that Michael would come out with a new version but so far no luck. In my case the problem host is using MariaDB instead of MySQL. MariaDB does not allow the insert with null like MySQL does.

Still not fixed in 4.5

I updated to 4.5 on my host which uses MariaDB rather than MySQL

It is still giving error

[21-Apr-2016 00:04:27] WordPress database error Column ‘offset’ cannot be null for query INSERT INTO wp_wpb2d_processed_files (file, uploadid, offset) VALUES (‘/home/richard/public_html/abc.com/wp-content/wflogs/.htaccess’, 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

The key is inserting null into offset. The field is configured to not accept null and put in a default of 0.

On MySQL this works fine. On MariaDB it throws an insert null error.

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,
)); // fix MariaDB null insert error
}

Problem resolved. As 0 is what the DB is storing, no idea why the plugin insists on inserting null vs a 0

Thank you once again for this post, Rich. I found it about six weeks ago and resolved the same problem on my sites then had to make the same fix today after the updated plugin was installed. I appreciate the fix.

I wish Michael would just make the fix in the plugin. The modified program works fine in MySQL and MariaDB. I have installed in both. I have about 50 sites and run this plugin in all of them. About 10 of them are on MariaDB and throw the error

I just discovered this error, although mine is a MySQL server and not MariaDB.

The my solution listed above fix the error for you?

Running into this issue with plugin version 4.5, and MySQL 5.5.49.

RichHelms patch fixes my issue.
Thanks!

@RichardHelms,
I just wanted to say thanks for taking the time to share your fix. it worked. You rule!

Now if Michael will just put the fix in the next version

So annoying … it’s still broken!