Ive never seen this error before, but you’ve actually found a bug. The Shashin database table is requiring a value for the takenTimestamp field, but it doesn’t have to be set in Picasa.
I’ll fix this in the next version. If you’re comfortable editing code, you can fix your copy now by going to line 98 in shashin/lib/ShashinPhoto.php and removing 'not_null' => true
Thanks a lot!
That helps.
However I had another problem with only one of my albums:
Database query failed. Error message: Out of range value for column ‘takenTimestamp’ at row 1
SQL statement: insert into wp_shashin_photo (sourceId,filename,description,linkUrl,contentUrl,contentType,width,height,takenTimestamp,uploadedTimestamp,fstop,make,model,exposure,focalLength,iso,albumId,albumType,sourceOrder,lastSync) values (5948380697314806578,’f2b50efa68cc1543c8e4346e7167439a.jpg’,”,’https://picasaweb.google.com/114241067492981536293/RgdJt?authkey=Gv1sRgCMn4iIrp2_We9wE#5948380697314806578′,’https://lh4.googleusercontent.com/-7H7k2_6tqoU/UozkunQ9SzI/AAAAAAAAA6Q/ivwQcbSOh14/f2b50efa68cc1543c8e4346e7167439a.jpg’,’image/jpeg’,383,512,-2147483648,1384965306,3.0,’NIKON’,’E4100′,0.017,6.6,187,55,’picasa’,19,1385446298) on duplicate key update sourceId = 5948380697314806578, filename = ‘f2b50efa68cc1543c8e4346e7167439a.jpg’, description = ”, linkUrl = ‘https://picasaweb.google.com/114241067492981536293/RgdJt?authkey=Gv1sRgCMn4iIrp2_We9wE#5948380697314806578’, contentUrl = ‘https://lh4.googleusercontent.com/-7H7k2_6tqoU/UozkunQ9SzI/AAAAAAAAA6Q/ivwQcbSOh14/f2b50efa68cc1543c8e4346e7167439a.jpg’, contentType = ‘image/jpeg’, width = 383, height = 512, takenTimestamp = -2147483648, uploadedTimestamp = 1384965306, fstop = 3.0, make = ‘NIKON’, model = ‘E4100’, exposure = 0.017, focalLength = 6.6, iso = 187, albumId = 55, albumType = ‘picasa’, sourceOrder = 19, lastSync = 1385446298;
Your photo’s takenTimstamp value is -2147483648, which converts to Fri, 13 Dec 1901. I’ve assigned takenTimestamp to be an “unsigned int” in the database, which means it’s not expecting negative numbers. This is also the first time I’ve heard of this problem, but it probably should handle negative values (in case someone scans a really old photo and sets the EXIF date, which may be what’s happening here).
..So to fix this in your code, change lines 96-98 in shashin/lib/ShashinPhoto.php from this:
'db' => array(
'type' => 'int unsigned',
'not_null' => true),
to this:
'db' => array(
'type' => 'bigint'),
Then deactivate and reactivate Shashin (I forgot to mention that step in my previous response). That should trigger an update to Shashin’s photo table in the database. Please let me know if it works for you.
I’ll make this same revision in the next version.
Yes, it works perfect, merci bien!
And I’ve reactivated plugin in both cases after making updates, thanks anyway for this note 🙂
For anyone keeping track, this is now fixed in Shashin 3.4.9
I had the same error Field ‘takenTimestamp’ doesn’t have a default value.
I read through this thread and saw your comment: I’ll fix this in the next version. If you’re comfortable editing code, you can fix your copy now by going to line 98 in shashin/lib/ShashinPhoto.php and removing ‘not_null’ => true
I have version 3.4.10 but when I looked at the code the line above was still present.
After removing this code and updating thinking this would resolve I can no longer log into WordPress. When I log in I get a White Screen : (
Please help I am now completely stuck, what should I do?
Thanks in advance!
I re-inserted the ‘not_null’ => true and wordpress is working again.
I still have the problem linking to Picasa album, here is the message;
Database query failed. Error message: Field ‘takenTimestamp’ doesn’t have a default value
SQL statement: insert into wp_shashin_photo (sourceId,filename,description,linkUrl,contentUrl,contentType,width,height,videoUrl,videoType,videoWidth,videoHeight,uploadedTimestamp,albumId,albumType,sourceOrder,lastSync) values (6021100674523673426,’Andrew Slow Mo.mpg’,”,’https://picasaweb.google.com/TrenthamCanoeClub/CruisingOnTrenthamLake?authkey=Gv1sRgCMim1JWG1pWALQ#6021100674523673426′,’https://lh6..googleusercontent.com/-08tmtfN2vLI/U48_KY3ZM1I/AAAAAAAAGgI/4JUhd0gjPsc/Andrew%252520Slow%252520Mo.gif’,’image/gif’,512,288,’http://redirector.googlevideo.com/videoplayback?id=9359cd6e9cb01038&itag=22&source=picasa&cmo=sensitive_content%3Dyes&ip=0.0.0.0&ipbits=0&expire=1404574218&sparams=id,itag,source,ip,ipbits,expire&signature=CE6F57FED928039ADF6D3F1547DB006C87ABB35.5FA95C6FF532C15CD0DA9FD5D709932AB9A4F018&key=lh1′,’video/mpeg4′,1280,720,1401896745,5727,’picasa’,1,1401982224) on duplicate key update sourceId = 6021100674523673426, filename = ‘Andrew Slow Mo.mpg’, description = ”, linkUrl = ‘https://picasaweb.google.com/TrenthamCanoeClub/CruisingOnTrenthamLake?authkey=Gv1sRgCMim1JWG1pWALQ#6021100674523673426’, contentUrl = ‘https://lh6.googleusercontent.com/-08tmtfN2vLI/U48_KY3ZM1I/AAAAAAAAGgI/4JUhd0gjPsc/Andrew%252520Slow%252520Mo.gif’, contentType = ‘image/gif’, width = 512, height = 288, videoUrl = ‘http://redirector.googlevideo.com/videoplayback?id=9359cd6e9cb01038&itag=22&source=picasa&cmo=sensitive_content%3Dyes&ip=0.0.0.0&ipbits=0&expire=1404574218&sparams=id,itag,source,ip,ipbits,expire&signature=CE6F57FED928039ADF6D3F1547DB006C87ABB35.5FA95C6FF532C15CD0DA9FD5D709932AB9A4F018&key=lh1’, videoType = ‘video/mpeg4’, videoWidth = 1280, videoHeight = 720, uploadedTimestamp = 1401896745, albumId = 5727, albumType = ‘picasa’, sourceOrder = 1, lastSync = 1401982224;
I looked back through this again and realised that you have changed the code in the latest version to resolve line 98 in shashin/lib/ShashinPhoto.php and removing ‘not_null’ => true
I was updating the Uploadedtime stamp and removing the above, that is why WordPress crashed.
I still get the same error as the above post however?