Either disable "random image block" before saying "right, D6 is A-OK now, let's upgrade to D7
or have image legacy disregard any data from random image block in D6.

If random image block is enabled during the move, any images on various nodes with that block enabled get associated with said nodes. There's no random image block in D7, so the association is pure baggage.

Comments

joachim’s picture

> If random image block is enabled during the move, any images on various nodes with that block enabled get associated with said nodes

I honestly don't know how that can possibly happen.

Are you saying that if, say, node/1 is set to display the random image block, and it is showing image node/2, then the image at node/2 gets associated with node/1? There's no connection of that sort in the database.

Hetta’s picture

Status: Active » Postponed (maintainer needs more info)

Almost all of my images have at least two associations, one of them utterly random, the other the right one.
Random image block is the only explanation I have been able to think of.

Alas, you're correct, I'll have to do some checking (ie., disable random image in D6, re-upgrade to D7, check associations). I'll report back, probably late next week.

joachim’s picture

I don't understand what you mean by 'an association'. You're going to have to be more specific.

Hetta’s picture

On this page:
/admin/content/file
click on "usage" right next to one or the other legacy image. You get
/file/11195/usage?destination=admin/content/file
where associations are listed:
"This table lists all of the places where kings-inula.jpg is used.
Type Title Count
node Inula (U. S. P.)—Inula. 1
node Photo: Hibiscus schizopetalus 5. 1"

(And so on for all images I've checked, so far).

I've no idea why the inula drawing would get associated with the hibiscus photo. The only suspect is random image block. I'll revert to my D6 backup files+database and reupgrade with random image block disabled, to see if it fixes this, sometimes next week.

Hetta’s picture

Title: Disable random image block before moving from D6 to D7 » Random file usage added by image_legacy in D6-D7 upgrade
Priority: Normal » Minor
Status: Postponed (maintainer needs more info) » Active

image_legacy will add irrelevant file usage to a lot of files, and I can't see why.
(This time, I disabled random image block before upgrading from D6 to D7).

Upgrade the usual way: back up everything, upgrade from D6 to D7, add modules image_legacy and field_convert (with all they require), go to /admin/content/field_convert, select images and run field_convert:

file 9075
usage node 13761 - false
usage node 23965 - correct

file 9047
usage node 23937 - correct

file 11187
usage node 13291 - false
usage node 26083 - correct

It's not a major bug, as images actually do get upgraded to D7, but the file usage data is probably used somewhere in D7?

(For those who get inexplicable errors when trying to upgrade D6 to D7: download schema and correct all it deviations first, then upgrade.)

Hetta’s picture

Status: Active » Fixed

OK, file_usage table:
delete all uses added by module 'image' and the random usages are gone:

delete FROM `file_usage` where `module` ='image'

sorry, I don't know where the extra usage entries came from.

file_usage entries before: 28,548
file_usage entries after: 14,324

joachim’s picture

If this is a problem with the upgrade process, it shouldn't be marked as fixed.

Status: Fixed » Closed (fixed)

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