My site's heavily dependent on Image module, but for node-specific images (that don't need to be managed separately as node) I'm looking at using Imagefield. I've authoritatively confirmed that there's no problem with using both together, as long as you don't try to add CCK imagefields to the non-CCK Image node type itself.

So now I'm trying to find ways to have imagefields reference files already in my site's filesystem, or if I can't, then at least batch importing groups of files into imagefields and creating duplicates would be (barely) acceptable.

The image.module, or image_import.module will likely cause conflicts. (check the issue queue)

I've looked through this (tiny) queue and didn't see any reference to a problem, so how about it, anyone know for sure? Couldn't the module be fixed to allow for assured co-existence? Little people, why can't we all just get along? :)

If not, anyone know of other ways to accomplish these goals?

Comments

HansBKK’s picture

HansBKK commented
Title: Why can't we all just get along? » Does this module actually conflict with Image or Image Import modules?

better title

vordude’s picture

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

Answer:

From Imagefield 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.
-------------------------------------------------------------------------------------------------

imagefield_import is dependent on imagefield.

HansBKK’s picture

HansBKK commented

Sorry, but I think this isn't a complete answer.

Imagefield is only "incompatible" with Image in the specific situation given in the second part of that quote. My original post's statement is actually a more clear statement of the same thing and has been verified by Darrel O'Pry (dopry), Imagefield's maintainer directly with me via email:

There's no problem with using both together, as long as you don't try to add CCK imagefields to the (non-CCK) Image node.

The two modules (Image and Imagecache) are completely compatible otherwise, in the sense of having them both active at the same time on a site (as long as. . .)

If this (somewhat misleading) information from Imagefield's description was the only basis for the warning in your module's description, then it is misleading and should be clarified with this more detailed information.

If there is another possible reason for Imagefield Import and Image being incompatible, then please let us know.

Thanks.

dman’s picture

dman commented
Component: Code » Documentation
Status: Closed (won't fix) » Postponed (maintainer needs more info)

This matches my understanding. It's a case of "Well Don't Do That Then".
imagefield and image.module are heading for a convergence, at which point both methods will be one and the same - both using the same method to attach files to nodes.
There may have historically been greater conflict (I can't quote them) but they know about each other enough now . I think.

vordude’s picture

vordude commented
Status: Postponed (maintainer needs more info) » Closed (fixed)

the project page has been changed, since this was first posted.

Well Don't do that then...