Hi,

after reading the warning:

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.

I'm unsure what exacly would happen, if I'd be using Imagefield in parallel with Image.module.

Image.module is running on my site for quite a while, so I won't be able to simply disable it, and I'm afraid to damage the existing image nodes by using Imagefield; could this happen, or does the compatibility issue only affect Imagefields? Would it be recommended, to use Imagefield not at all, or does the warning above only apply to image.module content types (meaning CCK fields attached to an image node?)?

Thanks for any clarification on this! -asb

Comments

dopry’s picture

dopry commented
Status: Active » Closed (fixed)

only applies to CCK imagefields attached to image nodes...

asb’s picture

asb commented

> only applies to CCK imagefields attached to image nodes...

I'm sorry to be bugging you even further, but what the heck is exactly an image node?

* The content type "Image" created by the "Image" module and nothing else, or
* any node type with something like "Image Attach" (Image assist module) or "Create attached images" (Image Attach module, Upload image module) enabled?

Also, already uploaded images can not be used by the CCK Imagefield, right? Is there any safe way to migrate nodes utilizing images from image module and the like to CCK Imagefield, or can this only be done when builiding a site from scratch?

Thanks & greetings, -asb

smoothify’s picture

smoothify commented

>I'm sorry to be bugging you even further, but what the heck is exactly an image node?

When you are using image module and you upload an image for a page, it creates a new separate node (of the image content type) that contains the information for the actual file.

Once uploaded it creates a link/reference from the page to that image node so that you can display it in the node view. If you look in your admin/content/list page you can filter to just image and you will see all the image nodes there.

So this warning means that you can run both modules along side, as long as you don't try to add the imagefield to the actual image content type. If you add an imagefield to your page or other node type it will be fine, just don't add it to the image type.

As for migration, this is something i'm interested in too - there is some discussion about it here, but i haven't tried it yet myself.

http://drupal.org/node/201983

asb’s picture

asb commented

Hi radiantflow,

thanks a lot for the clarifications, I'll now faithfully start experimenting with Imagefield and Image.module ;-)

Thank you, also, also for the pointer regarding migration of image.module to imagefield; Imagefield plus Imagecache seems to offer so much more flexibility and stability compared with image.module that it might be worth the effort.

Greetings- asb

socialnicheguru’s picture

socialnicheguru commented

subscribing- this is a great difference between the two.

I am having trouble with imagefield, imagecache, and upload of images and I think it might have to do with this.

Chris