I'm about to conclude a large upgrade of a production site. All of the 3rd party modules that we can upgrade have been, with the exception of imagefield. We currently have version 5.x-1.1 installed, and I'm trying to upgrade to 5.x-2.6. I found that when I ran the upgrade on a clone of the site, it broke a lot of our views (Views, CCK, etc are all at the latest 5.x release versions). The odd thing was that the nodes in those views didn't have any imagefields. In fact, there's only one content type that does have an imagefield, and it still displays just fine.

However, after quite a bit more testing, I've verified that updates 4 and 5 are breaking our views.

If I change updates 4 and 5 to simply return $ret; immediately, nothing breaks. Since I'm updating from 1.1, the whole thing about updating the default type (update 4) doesn't seem to be necessary, and update 5 looks like it's simply zeroing out file id numbers that correspond to files no longer in the {files} table.

My question, then, is this:

Am I safe to run the modified updates that don't do anything without fear of anything else not working properly? From what I can see, everything seems to be working as expected, but I just want to make sure.

Thanks,

Dave

Comments

davedelong’s picture

Status: Active » Closed (fixed)

Further testing has revealed that this is not directly an ImageField issue. I'll repost this once I figure out what's going on.