AJAX 500 error on content migration

Is it a dev site -- can you attach a db dump (with all unrelated modules disabled)?

+ What is the order of the migration plugins you execute?

+ What is the order of the migration plugins you execute?

Group Content -- Failed.

Add group audience field from node-picture to reference node-channel (i.e. mark node-picture as "Group content".

I've committed a few fixes, please get latest dev and re-try.

I'd prefer not to attach a full DB dump if I could.

If you want, you can send me on private.

I too got ajax http error on og migrate. Here is the info:

An AJAX HTTP error occurred. HTTP Result Code: 200 Debugging information follows. Path: /batch?id=2772&op=do StatusText: OK ResponseText: Fatal error: Class name must be a valid object or a string in /home/***/public_html/includes/common.inc on line 7656

On migrate page,

Remove global roles - 7.2 ,
Upgrade user roles - 7.2 ,
Upgrade OG roles - 7.2
All the above got executed successfully
Error occured during the following
Upgrade OG membership - 7.2 Re-populate group ID and group entity, deprecating the OG group entity.

Marked http://drupal.org/node/1497324 as duplicate of this.

Making this as Major as most of the sites cannot shift to OG 7.x-2.x from 7.x-1.x since migrate is not working.

nikkubhai, I'll need more info/ debug or better a patch...

@Amitai: I implemented it directly on production site. On production site, there are different group content types ( departments, clubs, etc.) and different group content content types ( article, project, etc.) . As I said earlier, Error occured during the following migration : Upgrade OG membership - 7.2 Re-populate group ID and group entity, deprecating the OG group entity.

One thing I noticed, on any group content (articles) , only admin could see the post. For others, there was WSOD.

As it was on production site, php errors were turned off. So , I will test this now on dev environment and report/resolve the errors.

On a fresh dev site , I installed og 7.x-1.x first, enabled og example, created a group and group content and then updated to og 7.x.2.x . Again, during migration,

Upgrade OG membership - 7.2 - execution failed.

But this time the debugging information is different. Maybe it will help.

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /d7/?q=batch&id=13&op=do StatusText: Service unavailable (with message)
ResponseText: PDOException: SQLSTATE[42S22]: Column not found: 1054
Unknown column 'base.language' in 'field list':
SELECT base.id AS id, base.type AS type, base.etid AS etid, base.entity_type AS entity_type, base.gid AS gid, base.group_type AS group_type, base.state AS state, base.created AS created, base.field_name AS field_name, base.language AS language FROM {og_membership} base WHERE (base.id IN (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2)) ; Array ( [:db_condition_placeholder_0] => 1 [:db_condition_placeholder_1] => 2 [:db_condition_placeholder_2] => 3 ) in EntityAPIController->query() (line 152 of /var/www/d7/sites/all/modules/entity/includes/entity.controller.inc).

This time I can provide any information you want Amitai. I also want to help with patch, but I have no idea where to begin.

nikkubhai, is it a dev site -- can you attach a db dump?

I have attached the database.

@nikkubhai,
With latest -dev version, and after executing update.php -- I was able to migrate with no problem.

I tested on dev site again and as you said, there was no problem in migration.

But , migration on production site still failed. with the following error:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows.

Path: /batch?id=2817&op=do
StatusText: Service unavailable (with message)
ResponseText: DatabaseSchemaObjectExistsException: Table field_data_og_group_ref already exists. in DatabaseSchema->createTable() (line 657 of /***/includes/database/schema.inc).

I'm also experiencing an EntityMalformedException: Missing bundle property on entity of type node when attempting to migrate group content nodes. All other migration tasks completed successfully. I am running 7.x-2.x-dev. Any assistance in resolving is appreciated - this is my last step for a successful d6-d7 migration.

Seems almost every member has a different error, so better read carefully the error messages, and open a different issue, but please *only if needed*.

But before that, please help test #1635366: Make og-migrate plugins less strict

I'll need a response...

I did install the patch, but continued to see the exact same error. No change. Thanks!

Hi. A few months ago I had a migration problem... upgrading the version of OG to a dev release had fixed that after some back-and-forth.

Now I'm migrating a similar but different site from D6 to D7. This time, everything in Content Migrate executed successfully except for "Group content nodes", with a message that looks almost identical to the original message in this issue:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /new/batch?id=1680&op=do StatusText: Service unavailable (with message) ResponseText: OgException: There are no OG fields in entity <em class="placeholder">node</em> and bundle <em class="placeholder">blog</em> referencing <em class="placeholder">node</em> - <em class="placeholder">group</em>. in og_group() (line 1751 of /var/www/new/sites/all/modules/og/og.module).

Should I create a new issue or keep it here? I'm running 7.x-2.0-beta1+11-dev

Today updated OG to 7.x-2.0-beta1+14-dev, entity API and entityreference to 7.x-1.0-rc3+2-dev and ran update. No change to above.

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /new/batch?id=1688&op=do StatusText: Service unavailable (with message) ResponseText: OgException: There are no OG fields in entity <em class="placeholder">node</em> and bundle <em class="placeholder">blog</em> referencing <em class="placeholder">node</em> - <em class="placeholder">group</em>. in og_group() (line 1765 of /var/www/new/sites/all/modules/og/og.module).

I can send a db dump if you wish.

Looks like there are multiple people with similar problems.
You said to open a new issue if necessary, but my errors seem to be the same as friendswoodtech's
If you want to open mine as a separate issue or need more info or a DB dump, let me know.

There's no movement on the issue, but it still exists for multiple people. If maintainers need more data, please let me know.

Solved the problem.

Did a fresh dump and reload, and just ensured that the blog and image content types were edited and saved as OG group content.

Part of the problem was that there was no "image" content type. One had been created and deleted from the system before the migration. Recreating the image content type allowed the migration to proceed, after which I could safely re-delete the type.

I was snooping around in that direction after reading a similar issue, "Setting per-instance target bundles changes global group audience field target bundle settings", especially posts #36 and #41 in it.

Thanks to all -- especially Amitaibu -- and I'm sorry if I was getting pushy. It was just that this one issue was holding up my D7 migration, everything else moved over fine. But now I have seen, for the first time, the message that I can now disable OG migrate.

We seem to have all of these errors. We have done something more complicated than the thread suggests. We went from og 6 to og 7.1 and then to of 7.2 and all the problems seem to be going from 7.1 to 7.2. Perhaps og 6 direct to og 7.2 will work better. Has anyone gone from 6 to 7.2 bypassing 7.1? We are on beta1 not dev. Should we be on dev?

It's 2013 and I'm still getting the same error.
Keen for an upgrade path from 7.1.x to 7.2.x !

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=59&op=do StatusText: Service unavailable (with message) ResponseText: PDOException: SQLSTATE[22P02]: Invalid text representation: 7 ERROR: invalid input syntax for integer: "1.36034716126E+12" LINE 1: ...ialHighwater) VALUES ('OgMigrateMembership', '1', '1.3603471... ^: INSERT INTO migrate_log (machine_name, process_type, starttime, initialHighwater) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2, :db_insert_placeholder_3); Array ( ) in MigrationBase->beginProcess()

I got here by searching for "OgException There are no OG fields in entity node and bundle video referencing node group" If you are searching for something like that, my problem was that there were no og fields on my content type that I was importing to.

I was getting a similar error but when using SimpleTest.

This page kept coming up in Google searches during my debugging session...so...

I solved my issue with this solution from DrMiaow.