On a fresh Drupal install with multiple modules installed, I created a node type "Picture". This node has a CCK FileField "Image" supporting only the jpeg file format.
I added multiple fields to this object, amongst them are the camera make and model, aperture settings, fnumber, etc. I also added the import of exif_datetimeoriginal into a CCK Datetime field.
Every time I save a node, I get the following error messages:
warning: date_offset_get() expects parameter 1 to be DateTime, null given in /homepages/41/d344310103/htdocs/site/sites/all/modules/exif/exif.module on line 178.
warning: date_timezone_set() expects parameter 1 to be DateTime, null given in /homepages/41/d344310103/htdocs/site/sites/all/modules/exif/exif.module on line 179.
I tried different configurations for the datetime field, setting default values, using different input formats (even the one described in Exif module documentation); I always get the same error.
I also tried changing this field to be a simple textfield, it was not filled with anything (left blank). My field syntax is correct and I double check that the file indeed has filled EXIF data.
I'm ready to work with you on solving this issue. You can contact me and I'll give you some access to reproduce the error.
Comments
Comment #1
lanouettea commentedSorry for that. I searched a lot about this problem and finally found the source in a recent issue posted a few days ago. Sorry to have opened a duplicate.
The solution is simple enough, and I guess it should be available in a next release, since it is set to fixed status.
ndm - September 16, 2010 - 08:27
For me every works fine but no value with date field. The reason was that the exif date format is in uppercase (automatically in my case). So the solutution i founded is here :
Comment #2
rapsli commentedcan you check out the latest dev version (probably available tomorrow) and see, if that fixes your issue
Comment #3
lanouettea commentedWill do. I'll keep you posted.
Comment #4
Romejoe commentedSame here. I did post in the other issue (742464) maybe we should continue there?
Please check Issue 742464.