Hi

I'm trying to upgrade my site to D7. Most of this has gone well, but there are some problems, including with the image module/gallery content conversion to D7 format.

I installed the D7 version & enabled the sub-modules, but the image gallery will not allow as it throws an error breaking the site:

Fatal error: Call to undefined function _image_check_settings() in /home/que1/public_html/abc/sites/default/modules/image/contrib/image_gallery/image_gallery.admin.inc on line 12

and yet I have a good number of images there to import.

Furthermore, when I go to /admin/content/field_convert to migrate data, it starts well, but then fails with this:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=327&op=do StatusText: Service unavailable (with message) ResponseText: EntityMalformedException: Missing bundle property on entity of type file. in entity_extract_ids() (line 7409 of /home/que1/public_html/abc/includes/common.inc).

So what am I doing wrong and how can this be corrected? I'm quite scared of the possibility of being forced to go through countless articles manually re-doing images or re-creating an image gallery.

Any help would be appreciated.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

asb’s picture

@lionheart8: The upgrade procedure is still incomplete. You can help with a donation: #1665912: Crowd funding for an upgrade to D7

Since the title "Upgrading to D7/migrating data fails" is pretty generic, I'd like to add that there are almost infinite reasons why the data migration might fail. A nasty example I just ran into are 'Image' nodes that are no "proper" image nodes. Those are created, for example, by the Upload image module. It claims to create 'Image' nodes, but they are not, not even on D6 (image derivates are not being generated, the 'files' table isn't handled properly, etc.).

joachim’s picture

I'm not sure how you've even managed to *enable* image_gallery on D7, as no part of the module has been upgraded yet, not even its core compatibility setting in the .info file!!

> A nasty example I just ran into are 'Image' nodes that are no "proper" image nodes. Those are created, for example, by the Upload image module. It claims to create 'Image' nodes, but they are not

Euw! Sounds awful.

asb’s picture

Status: Active » Postponed (maintainer needs more info)

Yes, it took some time until I remembered that I used the 'Upload image' module when I started with Drupal, either on D4.x or D5. The symptom I ran into were "inaccessible" files when transliterating those files with the 'Transliterate' module, which also converts the file name into lower case. Before, I never bothered about those images because I thought all Image nodes should be created equal ;) When digging into the database, I ran into s***loads of weird behaviours of those ~2,000 nodes. However, it's another issue for a de-facto abandoned module. I just wanted to add that we need some procedures to identify legacy stuff that wasn't even created to 'Image' module itself.

@lionheart8: As joachim said, please give some more details about your setup, if the issue from last December still persists for you.

joachim’s picture

So does upload_image create nodes that are of type 'image' but don't have the correct bits in them? If we need to contend with that, best file a new issue for it. (Though I see our ChipIn still stands at an impressive 0, so don't hold your breath....)

lionheart8’s picture

Hi

After several desperate attempts to get solutions enabling upgrading all aspects of the site in forums & module pages failing, at least in my time frame of several weeks, I gave up on that and as explained in this post => http://drupal.org/node/1390754 just re-did the site.
I'm not a programmer & so could not get custom solutions to issues I could not get from the forums or module folks (esp. image module, I was using the not continued node images module as well, nodewords, here upgrade created too many problems, etc) & though it involved a lot of work, I created a NEW CLEAN Drupal 7 site, with its much better & preferable modules & just copied & pasted content. That was quite a while back, though, I think in January!. ;). Site => here

Regards

Jaza’s picture

Status: Postponed (maintainer needs more info) » Needs review
FileSize
365 bytes

@lionheart8:

I've made a patch which resolves the error:

EntityMalformedException: Missing bundle property on entity of type file

Which you get when running the migrate task at admin/content/field_convert.

Apply the patch by executing (and also see help on applying patches):

cd /pathtosite/sites/pathtomodule/image
patch -p0 < /path/to/patchfile.patch

image_legacy and field_convert module maintainers: would be good to get this fixed, please review my patch.

Status: Needs review » Needs work

The last submitted patch, image_legacy_file_managed_type.patch, failed testing.

Jaza’s picture

Status: Needs work » Needs review
FileSize
452 bytes

My first time encountering the new requirement for -p1 style patches. New p1-style patch attached.

lionheart8’s picture

Hi Jaza

Good to hear about the good work. I am sure it will help someone.
At the time I critically needed a way, though there was none & so for the site I needed to upgrade at that time, I just re-did it, since it was not so big & though it involved a good bit of work, was able to copy & paste. For images, nodewords & so on, I had to use fresh D7 versions of modules, which are much better & I am quite satisfied with the site.

There are however still D6 sites and so I am sure this patch will help someone, so once gain - thank you :)

drzraf’s picture

Jaza, file_managed does not even contains a "type" column.
[edit]
...before media is installed