Exactly what the title says.

This is the error that I get (on a blank page, not the theme or admin page) -

Fatal error: Cannot unset string offsets in /home/susheel02/3in.coloursalive.com/sites/default/modules/image/contrib/image_attach/image_attach.module on line 402

Would be great if someone can take a look at it.

Cheers!

Comments

susheel_c’s picture

susheel_c commented
Priority: Normal » Major

Upping to major because it hinders some functionality. Is nobody else seeing this issue?

belpix’s picture

belpix commented

I got the same error. I can only proceed with import if I set "Attach images:" to Off in Image Attach settings of imported content type.

alex72rm’s picture

alex72rm commented

@#2:

where is the trigger for setting Off "Attach images:"? I haven't found it on steps for node import.

belpix’s picture

belpix commented

@#3:

It's not on steps of import, it's on the page of the Content Type you want to import: /admin/content/types.
The workaround is: select there the content type you want to import, and before import in "Image Attach settings" of selected Content Type set "Attach images:" to "Disabled". After import you can set back to "Enabled".

susheel_c’s picture

susheel_c commented

Any progress here? Would be interested if this is fixed. Thanks.

dimitriseng’s picture

dimitriseng commented

I was also having this issue using Node Import and Ubercart. Have a look at issue [952732] of the Image module. The suggestion in #1 of that issue allows the import to complete, however I am not sure if that solution is acceptable, it has not been commited yet, I have asked this question there.

jonathan1055’s picture

jonathan1055 commented

After getting WSOD when trying to progress from step 6 to 7 I eventually found the error message in my php installation /logs/ folder.

#952732: Fatal error: Cannot unset string offsets in .../image/contrib/image_attach/image_attach/image_attach.module on line 397 is helpful. The suggestion is that Node Import "should be doing node_save(), not pretending to save forms" and that would correctly invoke the hook nodeapi functions and avoid the error.

However, I've only just started using Node Import, and to get my head around it and code what would seem to be a major patch ... well, I'm not going to start on that right now. Belpix's tip in #2 and #4 will do atm.