I upgraded from Organic Groups 7.x-1.5 to 7.x-2.0 on Drupal 7.20. All updates to database (using Drush updb) reported to complete successfully.
However, when I go to Migrate (7.x-2.5) to complete the process, I click all the checkboxes, select Import from the popup list, and click the Execute button -- and all migrations report as failing. I rolled them back and tried again and they always fail. For every row numbered (e.g. 25 rows of ogmigrategroupgroup), I get one message. When I view the messages for any of them, they all basically say the same thing...
There are no OG fields in entity <em class="placeholder">user</em> and bundle <em class="placeholder">user</em> referencing <em class="placeholder">node</em> - <em class="placeholder">group</em>. (/path-to-drupal/sites/all/modules/og/og.module:1930)
I can certainly paste in all messages if necessary, but I think they all say the same thing. Does anyone know why this is happening or what to do about it?
My site relies on OG and I can't really start from scratch! I can't seem to find this problem in my searching of issues.
Comments
Comment #1
jastraat CreditAttribution: jastraat commentedI was having quite a bit of trouble with the migration from 7.x-1.5 to 7.x-2.0 as well. I know a number of bug fixes have been added to the dev version of the 2nd branch to specifically address migration. I'd suggest trying the latest dev of OG.
Comment #2
chris.hunter CreditAttribution: chris.hunter commentedI'm having issues upgrading from OG 1.4 to 2.0. I was able to upgrade and run the migrations successfully but once I tried to edit content types that are groups I would get 500 server requests or white screens. When I removed the group feature from the content type I was able to edit and create items of that content type.
Per jastraat, I tried the latest dev version but the same issues as above were encountered.
I'm using 7.12 so I may test this after upgrading to the latest version of D7. Like somatics, I can't really start over and I rely heavily on OG.
Comment #3
somatics CreditAttribution: somatics commentedThank you for the suggestion, jastraat, but OG migration is still failing with the same error as before.
I have attached the entire transcript of the error messages. Please note too -- in case this is some symptom that is helpful for diagnosing the root problem here -- that at the bottom of the transcript below I included the entire set of pending migrations. The list of migrations is a A LOT longer than the one in the documentation for doing this upgrade (that doc I think shows only 3 migrations needed). Most of them say zero records need importing, and I only checked the boxes for the 5 that say there are records needing importing. However, is this many pending migrations a sign something is wrong in the first place?
Comment #4
darrick CreditAttribution: darrick commentedI had this same issue. I upgraded from D6 to D7 via the old og_migrate 7.x-1.x module a long time ago. After looking at the code realized I had to drop the d6_og table in the database. The above error is because you're running a D6 to D7 migration and not a 7.x-1.x to 7.x-2.x upgrade.
Comment #5
Emmanuel_S CreditAttribution: Emmanuel_S commentedDarrick, could you tell us how to select the correct migration to run ?
When I'm installing a new module version, I can't really select any script to run. Is it with drush ?
Thanks