I recently upgraded in the following way:

CCK 2.1 to 2.2
filefield 3b1 to 3b3
imagefield 3b1 to 3b3

After running updates (CCK required a database change, I believe) and clearing the cache, I noticed that none of my images were appearing. I cleared all the caches and double-checked my permissions (774) and download method (public) but they still weren't appearing.

I verified that the images themselves still exist in /files, as do their thumbnails in /files/imagefield_thumbs.

I tried to edit a node type that contained an image, and got the following error:

Argument #1 is not an array ... [server path]/imagefield/imagefield_widget.inc on line 123

I went to look at the node type's content fields, and saw that the "type" listed was blank (see screenshot 1). Clicking on configure and editing the field's basic information showed a blank widget type, but the field type was still greyed out so I couldn't change it (see screenshot 2).

At this point I suspected that it had something to do with the shift from a "Image" field type to an "Image" widget type within field type "File." However I can't be sure as I've used imagefield on a few sites recently and on some I remember using Image, others File->Image, so I'm not sure which case this was.

Returning to look at the node, when I edited it again I didn't get the error I had gotten initially, but the field wasn't showing up at all (despite it still being there on the content-type fields page).

Even more strangely, when editing a different node type (portfolio) that used a different image field (screenshots), I saw that the field *was* there, but there were no images (see screenshot 3). When I tried to add a new one, I got the following dialogue box popup:

An error occurred.
/content/js_add_more/portfolio/field_portfolio_screenshots
Fatal error: Call to undefined function filefield_content_is_empty() in [server path]/sites/all/modules/cck/content.module on line 900

Given the preceding items, however, I'm pretty sure this is an imagefield thing and not a CCK thing.

For what it's worth, both imagefields are using an "unlimited" value for number of entries (thus the "add another item" button). I don't know if that might have something to do with it.

Has anyone else experienced similar issues in upgrading any of these?

CommentFileSizeAuthor
screenshot3.png7.33 KBrootwork
screenshot2.png40.8 KBrootwork
screenshot1.png13.14 KBrootwork

Comments

rootwork’s picture

rootwork
he/him
Primary language English
Location 🇺🇸 US-Pacific 🌎 Chinook (Multnomah, Clackamas) & Cowlitz lands 🌹 Portland, OR
commented
Priority: Critical » Normal

More weirdness, although better news for me.

When I visited my modules page, I saw that Filefield (but not Imagefield) was unselected, and additionally greyed out, as if there were some dependency that was missing (but its only dependency, CCK, was there and turned on).

Disabling all of the CCK-related modules through a few cycles and then re-enabling them along with Filefield worked. I then ran updates and Filefield had some database changes.

Visiting both my content types that used Imagefield, both had fields that were now correctly listed as using File, widget Image. Strangely, only one of the two content types -- the one I had created more recently -- was now displaying my images. (This was of course after clearing the caches.) When I edited the nodes of the older content type, there weren't any images being listed, even though once again I verified that they were still there on the server.

Since the second type didn't have many images, I didn't mind deleting the ones that were on the server and uploading new ones.

I'm still not sure what was going on, and I have no idea how Filefield disabled itself (or did so without disabling Imagefield) but now everything seems to be working OK.

I'll leave this up here in case anyone experiences something similar, but maybe it was just a fluke.

kappaluppa’s picture

kappaluppa commented

FYI...
Upgraded to 6.x-3.0-beta3 and image as an option was not present.
I reverted back to 6.x-3.0-alpha2 (the last copy I had) and it came back.

almaceria’s picture

almaceria commented

It seems to be missing an action in the {content_node_field_instance} table to convert the 'image-type' fields into 'filefield-type' fields.
quicksketch, please, consider it for further beta releases.

FYI: This action (launched from my DataBase console) worked fine to me:

update <em>db_prefix_</em>content_node_field d SET
 d.type = 'filefield',
 d.module = 'filefield'
 WHERE
 d.image = 'image',
 d.module = 'imagefield';

Hope it helps

quicksketch’s picture

quicksketch
he/him
commented

almaceria, I'm pretty sure we're already doing this exact thing. From update_6003:

  $ret[] = update_sql("UPDATE {" . content_field_tablename() . "} SET type = 'filefield', module = 'filefield', active = 1 WHERE module = 'imagefield' OR type = 'image'");
  $ret[] = update_sql("UPDATE {" . content_instance_tablename() . "} SET widget_type = 'imagefield_widget', widget_module = 'imagefield', widget_active = 1 WHERE widget_type = 'image' OR widget_type = 'imagefield_widget'");

kappaluppa's situation sounds a bit unusual, where the problem was that FileField module was somehow not enabled.

almaceria’s picture

almaceria commented

quicksketch you're right. My fault. :-(

I've experienced the same rootwork issue: images weren't being displayed.

I think my fault was to select the '6005' value in the versions combo box, when upgrading from 6001. I've just try again from a restaured db, selecting the '6003' value and it worked fine.
Thanks and sorry for my mistake.

quicksketch’s picture

quicksketch
he/him
commented

Oh dear. Yeah you should absolutely never change the version updates unless you have a very good reason to do so. In Drupal 7 they removed the ability to change the update numbers at all, since it was hurting a lot more people (users) than it helped (mostly just developers). Thanks for the followup.

quicksketch’s picture

quicksketch
he/him
commented
Category: bug » support
Status: Active » Fixed

I'm moving this to fixed, as in either situation I don't think there's anything ImageField could have provided to prevent such problems.

Pempi’s picture

Pempi commented
Status: Fixed » Active

Hello,

I am new to Drupal, so I do not know, what the problem is, but I have had the same problem. I turned on imagefield 6x-3.0 beta3 and there was no image type to choose from the drop down menu for my new field.

Some days before I was doing the same with an Alpha4 version and everything was all right.

Finally I deleted beta3 and put up alpha4 and it works now.
It seems to me that I have the same experience as KappaLuppa had, but i think my filefield is enabled and I can select filefield in the same dropdown menu.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Fixed

Pempi, the problem you're describing sounds like this problem: #403884: "Image" doesn't appear anymore in the field type list. Comment #10 has screenshots to help.

Pempi’s picture

Pempi commented

Thank you, and sorry... This is clear now!

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.