There is an issue with image_fupload when a user has an image content type setup that didn't come from the image module. For example, i never use the image module and I usually create my own image content type with CCK imagefield. image_fupload CCK widget doesn't load up properly because of the settings of 'image_node_types'.

It gets set as a default "pre"-set during install. I'm working on a little patch where I'll move this behavior to hook_node_type and test the module property of the content type to make sure it matches "image".

JG

Comments

jose.guevara’s picture

jose.guevara commented
Category: bug » feature
Priority: Minor » Critical
Status: Active » Needs review

I reviewed the code... the image content type is hard coded in several places... I'm changing this to a feature request instead.... I'm sorry I'm not familiar enough with this module to recommend a course of action.

Sorry....

grandcat’s picture

grandcat commented
Category: feature » support
Priority: Critical » Normal
Status: Needs review » Closed (duplicate)

Of course, the image type is hard coded, because image.module's image is hard coded as well.

All in all, there's another topic with a patch which will be submitted after some testings.

tsmulugeta’s picture

tsmulugeta commented
Status: Closed (duplicate) » Active

I have the same issue. Was a solution ever found?

tsmulugeta’s picture

tsmulugeta commented
Priority: Normal » Critical

Can anyone please help me solve this problem or let me know of a possible patch?