I installed ImageAPI, ImageAPI GD2, ImageCache, ImageCache UI (all 6.x alpha), and Thickbox in order to use Fast Gallery. When I try to create a new action for my ImageCache such as scale I get this error :
user warning: Field 'module' doesn't have a default value query: INSERT INTO imagecache_action (presetid, weight, action, data) VALUES (1, 0, 'imagecache_scale', 'a:3:{s:5:\"width\";s:2:\"50\";s:6:\"height\";s:2:\"50\";s:7:\"upscale\";i:0;}') in C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\drupal6\includes\common.inc on line 3308.
or say for desaturate:
user warning: Field 'module' doesn't have a default value query: INSERT INTO imagecache_action (presetid, weight, action) VALUES (1, 0, 'imagecache_desaturate') in C:\Program Files\Apache Software Foundation\Apache2.2\htdocs\drupal6\includes\common.inc on line 3308.
Can anybody shed some light on this? Has anybody experienced this?
Comments
Comment #1
bmeier commentedComment #2
attiks commentedsame :/
work-around: remove the 'not null' from the 'module' column and then it's working
Comment #3
bmeier commentedAttiks - Where did you remove this from? I had gotten around this error by batch resizing all my pics into thumbnails but I'd like to have it working correctly.
Comment #4
attiks commentedi removed it from the database table, the column is defined as not null, so a value has to be provided. I removed this condition.
Comment #5
bmeier commentedComment #6
ugerhard commentedEven if there is a work around, this is not fixed yet in the code base, so this issue should not be closed. I've been bitten by this just now and was about to open a new bug before remembering to look for closed bugs, too...
As it does not seem to be possible to create a preset with imagecache_ui right now, this definitely should be changed in some way in
imagecache_schema(). Maybe the'not null' => TRUEfor the module column can be removed? Or maybe it should get a default value?Comment #7
drewish commentedi think the default should probably be set to 'imagecache'
Comment #8
dopry commentedI think the value should be populated when passed to drupal_write_record... anyways it's fixed in HEAD.
Comment #9
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.