I think all that is needed for the problem to go away is to rename the _image_filename() function to something else, such as _imagefieldimport_filename()

I'll gladly make a patch soonish, but in the meantime this could be useful to know.

CommentFileSizeAuthor
#2 imagefield_import_272979.patch892 bytesvordude

Comments

boobaa’s picture

boobaa
he/him
commented

This one causes headaches for me, too.

vordude’s picture

vordude commented
Version: 5.x-1.1-beta » 5.x-1.2-beta
Assigned: Unassigned » vordude
Status: Active » Needs review
StatusFileSize
new imagefield_import_272979.patch892 bytes

I'd prefer someone else tests this one first.

(perhaps someone who has the issue with the image.module incompatibilities)

pixelpreview@gmail.com’s picture

pixelpreview@gmail.com commented

this patch has corrected the bug in my install.
I have effectively a fatal error with module image too on install
thanks

vordude’s picture

vordude commented
Status: Needs review » Closed (won't fix)

The patch is above, and should at least help, I think there may be one other function that needs tweeking...

But Imagefield as a project doesn't claim to be able to play nice with the image module:

Image.module - Imagefield is not compatible with image.module content
types. If you add an imagefield CCK field to the image type provided by image
module, image module will delete all the imagefield images on every node update.

So I'm not going to add this to the project at this time.