I am trying to migrate from 7.x-1.5 to 7.x-2.x-dev (2012-Oct-03 release). I have executed the migration actions with the update option checked and got some messages I am not able to understand:
Processed 526 (0 created, 526 updated, 0 failed, 0 ignored) in 54.5 sec (579/min) - continuing with 'OgMigrateMembership'
Processed 14 (0 created, 14 updated, 0 failed, 0 ignored) in 1.6 sec (509/min) - done with 'OgMigrateMembership'
Skipped OgMigrateRoles due to unfulfilled dependencies: OgMigrateMembership
Processed 176 (0 created, 176 updated, 0 failed, 0 ignored) in 11.9 sec (891/min) - done with 'OgMigrateUserRoles'
This results in an overview attached, which states that several rows are unimported.
My questions are:
Please help.
| Comment | File | Size | Author |
|---|---|---|---|
| og_migrate.jpg | 39.75 KB | edvanleeuwen |
Comments
Comment #1
drupalshrek commentedThe answer to why there is a negative value is strictly that this, I guess, is the correct answer to how many are unimported: unimported rows is "Actual rows to import minus Actual rows imported". So, for example, if you had 200 rows to import, and only 175 were imported, then unimported would be 25. Since the number of rows actually imported is given as more than the number of rows you had (!), then this maths is correct.
The question is rather: how is it possible to import more rows than exist?!?
Comment #2
amitaibuAre you using the latest version?
Comment #3
edvanleeuwenAs I stated in my oirignal post, I used the latest dev at that time, 3 October.
For now and for me, this is not a problem any longer, because I migrated and done some changes manually.
Comment #4
brightbold@edvanleeuwen — If you solve your own problem it's nice if you post the solution to help other people with the same problem. I'm also getting the
Skipped OgMigrateRoles due to unfulfilled dependencies: OgMigrateMembershipmessage so I'd love to know what you did to resolve this!Comment #5
edvanleeuwenAs I said earlier, I have done this by doing manually adjustments. This was performed directly in the database with a couple of SQL statements constructed in an Excel file. This is not something I can pass on nor am I able to script this.
My situation was caused by changing to the 2.x in production without testing it enough. So I thought everything was okay despite the errors. My bad.
Moreover, the original request was to explain the results, not so much solve them.
I think it is best to wait migrating until an official release is out. If you would like to test or experiment, please do so in a development environment and restore your database if any errors occur.
(BTW: If I would have had a solution, I would have given it, so there is no need for lecturing me).
Comment #6
amitaibu> I think it is best to wait migrating until an official release is out.
Well, the official release will have the same issues as the dev, so better figure them out and solve them before..
Comment #7
edvanleeuwenYou're absolutely right, but what I meant was to use and try it in a non-production environment before, in order to see if the migration is succesfull and only proceed if there aren't any errors.
I have tested it myself, but the messages I got were not very helpfull to determine whether the migration was stable enough. Therefor, I went to production too soon and had to correct a lot manually. That's why I have created the issue in the first place.
Comment #8
joelpittetDrupal 7 reached end-of-life and the D7 version of Organic Groups is no longer being developed. To keep the issue queue focused on supported versions, we’re closing older D7 issues. If you still have questions about using Organic Groups on Drupal 7, feel free to ask. While we won’t fix D7 bugs anymore, we’re happy to offer guidance to help you move forward. You can do so by opening (or reopening) a D7 issue, or by reaching out in the #og channel on Drupal Slack.
If this issue is still relevant for Drupal 10+, please open a follow-up issue or merge request with proposed changes. Contributions are always welcome! 💙