I got an error message because of a silly mistake of my own, but it revealed a bug in Resource Conflict. The error message was caused by the call to the watchdog function and said Data too long for column 'type' at row 1 query: INSERT INTO watchdog (uid, type, message, .... A look at the code and the database shows that the type variable can only be 16 characters long (64 in Drupal7, yay!), while "Resource conflict" is 17 characters. I'm not attaching a patch; I'll leave it to the maintainers to choose a suitable 16-character string to be used on line 432 of resource_conflict.module.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 518844_data_too_long_5.x.patch | 691 bytes | deviantintegral |
| #1 | 518844_data_too_long_6.x.patch | 666 bytes | deviantintegral |
Comments
Comment #1
deviantintegral commentedThanks for the report. I've attached patches for both Drupal 5 and Drupal 6 which change the type to 'rsrc conflict'. I'll be committing them shortly.
Comment #2
marcvangendThanks!
Comment #3
Vc Developer commentedAny news on when this patch will be available, because I can't use any of my Presets in Imagecache for my images?
Update:
Actually I'm having this problem with using ImagemagicAPI, I switched back to GD2 and it working fine. I assuming is because ImageMagic is using a longer string.
Comment #4
deviantintegral commented@Vc Developer: Looks like you posted in the wrong project. It sounds like you meant to comment about an issue in ImageAPI.
Comment #5
Vc Developer commentedWell, when I use ImageMagicAPI I get the same warning message and my Presets don't work. So could this still be a ImageMagic problem?
Comment #6
deviantintegral commentedDo you have Resource Conflict installed on your site? If not, then you need to use the issue queue over at http://drupal.org/project/imageapi.
Comment #7
Vc Developer commentedWas not aware of that feature, but will look into it now. Thanks!