Last updated April 3, 2014. Created on November 13, 2012.
Edited by Erich Schulz, magdmartin, arruk, adriancotter. Log in to edit this page.

Database Issues

If your database has a hyphen(-) in it, please make sure #1926418: OG Migrate fails if database name contains hyphen is resolved before reporting any new issues.

Setup

In order to upgrade Organic Groups from Drupal 6 or from OG 7.x-1.x to 7.x-2.x, the following modules must be installed and enabled:

Execution

Once the required modules have been enabled

  1. Make a backup of both your files and database.
  2. Download the latest version of OG 7.x-2.x (this can done via drush or ftp).
  3. Run update.php. If you're unsure what this means, go to the following URL and follow the instructions:
    http://yoursite.com/update.php
    After running the update script, you may get the message "The content access permissions need to be rebuilt. Rebuild permissions." Wait to rebuild permissions until after running the migrate scripts.
  4. Navigate to:
    http://yoursite.com/admin/content/migrate
  5. You should see the migrates that are still pending:
    OG Migrate Classes
  6. Check All of the new Migrate Classes for OG, select Import, then click on Execute.
    Run new OG Migrate Classes
  7. You should now see information regarding how many records were updated and when:
    og migrate results
  8. If some of your items are not migrated over, or there is an issue after migrating, try the latest dev version of OG. You can also look at:
  9. Once you are happy your migration is complete you are free to delete the now deprecated `og` table per #2226945: is the `og` table really deprecated

Looking for support? Visit the Drupal.org forums, or join #drupal-support in IRC.

Comments

thirdender’s picture

After the registration step, the migrate page just shows the error:

MigrateException: Failure to sort migration list - most likely due to circular dependencies involving OgMigrateContent,OgMigrateUser,OgUiMigrateAddField,OgUiSetRoles in migrate_migrations() (line 80 of /sites/all/modules/migrate/migrate.module).

Any ideas?

fbouzek’s picture

gpenn’s picture

When I try to upload OG-7.x-2.0 (through the "Install new module" function on my Modules page), I get the message "Organic groups is already installed." (I already have OG-7.x-1.5.)

Does "Download the latest version of OG 7.x-2.x (this can done via drush or using the graphical web interface)" mean parking the newer version somewhere else? I've not used drush, and I'm not sure what "graphical web interface" means.

Thanks for your help.

G. Penn

MD3’s picture

Yes, I was referring to the Update Manager ("Install new module") when I wrote the article. I always use Drush to manage websites, so I apologize for not testing that before I wrote it.

It looks like you're going to have to either use the FTP Method or install Drush. Either way, please make sure you create a backup of your drupal website and database before proceeding with this upgrade.

Rosamunda’s picture

The migration process is just to migrate existing content, right? I mean, if you have 1 group, with a couple of contents and users, you could do it manually.
Or is it any other stuff?

I do ask because I have this site that I have to manually migrate some information (adding OG audience to certain nodes, and adding some people inside some groups... by hand).

Now I find this explanation, and I just want to make sure that you can manage the same thing with a manual migration (and I´m not missing any feature that the automatic migration process does).

Thanks!

Rosamunda
Buenos Aires | Argentina

chiebert’s picture

These steps were very helpful - thanks to everyone who's contributed to them.

One note/question on rebuilding permissions: I was prompted to rebuild after running update.php, which I tried as above before running the migrations. When I tried - the process failed about 70% of the way through with "An AJAX HTTP error occurred. HTTP Result Code: 500". The only other content access module enabled was Field Permissions. I disabled that and tried again - same result. So I just ran the migration anyway (successfully, by the reports), and then rebuilt the permissions - no error this time.

So question: does the order matter?

DamienMcKenna’s picture

FYI, for anyone who's using Drush to run a system upgrade, or save their sanity, all of the commands can be run via Drush too, e.g. drush migrate-status to see the list of available tasks, and drush migrate_import OgUiSetRoles to run them.

--
Damien McKenna | Mediacurrent

oranges13’s picture

I have all the aforementioned modules installed and I am trying to migrate organic groups from a Drupal 6 database. The three OG Handlers do not appear in my list. What am I doing wrong? I have OG 7.x-2.2 and Migrate 7.x-2.6-beta1 installed.

jlea9378’s picture

I ran into the same problem. Use Migrate 7.x-2.5 instead.

pjcdawkins’s picture

I had that problem but it was resolved after clearing all caches (again).

Drupoth10’s picture

I was able to execute the migration to OG 7.x-2.3 successfully thanks to this post, but unfortunately, all of my site's content is now showing up in one of my groups, and all of the content has been stripped out of the other groups. After an extensive search, I figured out that the initial error I got (which gave me the WSOD), the "call to undefined function og_get_group()", was happening because the "og_get_group" function has been depricated in the latest version of OG.

So according to this post (https://drupal.org/node/1522026#comment-7823093) I commented out the line containing the depricated "og_get_group()" function. After I did that, the WSOD went away, but I realized that all of my site's content (I'm talking articles, descriptions of Drupal Commerce items, group descriptions, etc.) was being filtered into just one of my groups. It looks horrible, and even if I create new groups, the problem persists.

Has anyone else run into this problem? If so, how did you handle it? If not, do you have any idea how I might resolve this?

pjcdawkins’s picture

I'm sympathetic but the problem here was that you commented out a line without understanding it: if you remove code, the software is not going to work properly!

Drupoth10’s picture

I hear what you're saying, pjcdawkins, and thanks for your response. But do you have an alternative to hacking the module? Because from all of my research, there are two alternatives: either live with a WSOD (obviously not an option) or comment out the depricated function. I'm sure there's a third solution that doesn't involve hacking the module (I understand this isn't the Drupal way), but I haven't found it. And the managers of OG are horrible at explaining what to do in light of this depricated function (witness this laziness on display here: https://drupal.org/node/1670642).

Do you know something I don't? If so, I'd love to hear any ideas on how to fix this mess. Thanks!

MD3’s picture

Hi Drupoth10, I understand your frustration. OG can be a nightmare somedays (and makes you wonder why you're not using taxonomy terms instead!).

The issue you reference is regarding the og_views module. Amitaibu stated in that issue (comment #2) that he's no going to port the module. Why, might you ask? Long story short, he's using entities so that everything is integrated into views automatically.

What this means for you is that you should be using Viewfield OR a combination of page/panels and views to display the content you want. Here's a rough step by step guide:

  1. Recreate the views you're currently using (fields, filters, etc).
  2. Add a contextual filter (advanced dropdown on the right) on each view that sorts by your og field (could be named anything. It's the field that contains what organic group/s your content is a part of. Probably OG membership: Entity id or OG membership: Group ID. Filter by OG Membership to narrow the list down when adding a new filter). Under the When the filter value is NOT available section, select Provide default value, Current OG group from context. Your Group Type is probably Node.
  3. If you're using Viewfield, add a new Viewfield field to your content types you used og_views for. If you're using panels / pages, override the default display for those content types.
  4. In a Viewfield, set up your default argument to be [node:nid] (or if your groups are users:[user:uid]; etc). In panels / pages, make sure you're using a Views Content Pane type and pass the correct context (nid, uid, etc).

Walla! That should do it. A bit complicated, I know, but this is because we're generalizing everything in Drupal so that everything uses the same code instead of maintaining hundreds of modules that essentially do the same thing. Good luck!

Drupoth10’s picture

Thank you, MD3. I've been trying to get someone to respond to me for a long time, so your response is very welcome. I'll try out your work-around and let you know if it works. Thanks again!

Drupoth10’s picture

Hi MD3, and thanks again for your post. I tried to implement the changes you suggested, but I’m pretty confused at this point. I tried to attach an image of the effect I’m going for, but I can't figure out how (anyway, it’s a picture of how one of my groups looks now that OG Views has been deprecated, so it’s a little messed up). Anyway, the old setup includes a panel at the top of the left sidebar that contains a link for creating new content, a panel under that for listing group members, a third panel under that containing a link to unsubscribe from the group, and the overall body of the page, which lists all of the group members' posts that they have created.

I have several points of confusion, which include the following:

1) I recreated the overall view for one of my groups (based on your suggestion). It seems to me that the next most important thing is to create the panel in the left sidebar that contains the “add more content” link, so that content (in the form of posts) can populate the main body of the page. But I can't figure out how to do this. Should I use the OG Extras module to recreate the panel that contained the “add more content” link? (See this post about using OG Extras to add content links).

2) Should I use the Entityreference Prepopulate module , as the above linked page suggests, when recreating the “add more content” panel?

3) How do I make this recreated “add more content” panel interact with the list of posts so that whenever someone fills out the form to add new content and hits “save”, the post ends up in the list of posts in the body of the groups page?

4) Once I’ve recreated the view, which I did at your suggestion, I added a contextual filter, trying to add both “OG membership: Entity id” and “OG membership: Group ID.” But since I’m not sure how to actually create content for this new view, I obviously can’t check it to make sure it’s working.

I think I’ll stop asking questions here -- though I have many more -- because I think that answers to them might get the ball rolling. As you can see, I’m majorly confused and would benefit from any help you can give me. Thanks.

MD3’s picture

Hi Drupoth10, glad that got the ball rolling for you!

It looks like pictures aren't allowed in these comments. That's interesting!

Just to clarify, you don't create content for the view. The view shows you a list of what's in the Database (it's literally doing a SELECT query). So, if you create a view of users, the view will show users as you create them. You can have a unlimited number of views that show things about users, nodes, etc. If your view is empty, it's because you don't have any content on your site or your filters are too strict and returning no results.

1). Yes, try that module first.

2). If OG Extras doesn't do it for you, use the instructions you linked to.

3). That's the whole point of views! When new content is created, the view will be updated. If your views are set up correctly, the user will go to the add new content page, save the new content, and be redirected back the group page where it should show up automatically. You could do AJAX trickery with a popup and adding new content, but start with the simple method first!

4). You need to use ONE of those filters, not both. Just try them out one at a time and see what works. When you edit a view, you can preview it below. You can also provide it a contextual filter (in this case the group id or gid). Enter a group id in the preview area and hit preview to test your view!

If you need further help, please take a look at my profile and PM me. I think an hour on join.me will clarify most of your questions!

Drupoth10’s picture

Thank you for your response, MD3. I'll try to follow your instructions and see if I can get somewhere. I've been looking at dozens of tutorials, forums, etc. for weeks and can't seem to figure out what I'm doing wrong. I'll definitely PM you if I can't make headway. Thanks for your help!

Drupoth10’s picture

Hey @MD3,

I PM-ed you yesterday. I know it seems like a lot of questions, but I actually think I'm really close to solving my issues. Please let me know your thoughts on my PM when you get a chance. And thanks again for your help!

adriancotter’s picture

A basic question which I am not seeing an answer to, what does unimported or ignored mean here? For me, the module said there were 98 things, 69 were imported, 25 were unimported, 4 were ignored?

What does this mean for the site, or for my content? 'Tis not obvious to me.

Cheers,
Adrian

mermentau’s picture

The "+" should possibly removed from

Migrate 7.x-2.5+, including the UI

above. With the latest dev I couldn't get Migrate classes for OG to show up. I had to roll back to the Migrate 7.x-2.5 version and while I haven't run the migration yet at least the Migrate classes are there to work with.

Small thing, but might save someone some hours of grief.

MD3’s picture

Feel free to change the wording as you see fit (maybe the latest stable release) but developer versions are always just that: for developers willing to take a chance for a special feature or test for bugs!

SangersDrupalDude’s picture

subscribe

Senior Drupal Web Developer
Wellcome Trust Sanger Institute

SangersDrupalDude’s picture

wasnt added as a dependancy.

Senior Drupal Web Developer
Wellcome Trust Sanger Institute

SangersDrupalDude’s picture

Processed 523 (0 created, 521 updated, 0 failed, 2 ignored) in 27 sec (1157/min) - continuing with 'OgMigrateMembership'
Processed 688 (0 created, 687 updated, 0 failed, 1 ignored) in 27.6 sec (1493/min) - continuing with 'OgMigrateMembership'
Processed 718 (0 created, 718 updated, 0 failed, 0 ignored) in 27.7 sec (1553/min) - continuing with 'OgMigrateMembership'
Processed 548 (0 created, 547 updated, 0 failed, 1 ignored) in 27.7 sec (1183/min) - continuing with 'OgMigrateMembership'
Processed 873 (0 created, 873 updated, 0 failed, 0 ignored) in 27.7 sec (1888/min) - continuing with 'OgMigrateMembership'
Processed 481 (0 created, 481 updated, 0 failed, 0 ignored) in 10.4 sec (2781/min) - done with 'OgMigrateMembership'
Processed 36 (0 created, 36 updated, 0 failed, 0 ignored) in 0.6 sec (3625/min) - done with 'OgMigrateRoles'
Processed 2084 (2084 created, 0 updated, 0 failed, 0 ignored) in 26.5 sec (4717/min) - continuing with 'OgMigrateUserRoles'
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '65-0-1196' for key 'PRIMARY': INSERT INTO {og_users_roles} (uid, gid, group_type) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 65 [:db_insert_placeholder_1] => 1196 [:db_insert_placeholder_2] => node ) (/www/www-staging/drupal.sandbox.sanger.ac.uk/htdocs/includes/common.inc:7222)
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2121-0-1196' for key 'PRIMARY': INSERT INTO {og_users_roles} (uid, gid, group_type) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 2121 [:db_insert_placeholder_1] => 1196 [:db_insert_placeholder_2] => node ) (/www/www-staging/drupal.sandbox.sanger.ac.uk/htdocs/includes/common.inc:7222)
SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry '2356-0-944' for key 'PRIMARY': INSERT INTO {og_users_roles} (uid, gid, group_type) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => 2356 [:db_insert_placeholder_1] => 944 [:db_insert_placeholder_2] => node ) (/www/www-staging/drupal.sandbox.sanger.ac.uk/htdocs/includes/common.inc:7222)
Processed 957 (954 created, 0 updated, 3 failed, 0 ignored) in 12.4 sec (4628/min) - done with 'OgMigrateUserRoles'

There were duplicates in the source data, so I have deleted these to prevent it happening next time I attempt the migrate

Senior Drupal Web Developer
Wellcome Trust Sanger Institute

SangersDrupalDude’s picture

I did my own in the end

/**
* Migrate to og x2 roles and perms
*/
function postmigrate_update_7029() {
  $memberperms=array(
  array('og'=>'create book content'),
  array('og'=>'create forum content'),
  array('og'=>'create group_event content'),
  array('og'=>'delete own book content'),
  array('og'=>'delete own forum content'),
  array('og'=>'delete own group_event content'),
  array('og'=>'update any book content'),
  array('og'=>'update any forum content'),
  array('og'=>'update any group_event content'),
  array('og'=>'update own book content'),
  array('og'=>'update own forum content'),
  array('og'=>'update own group_event content'),
  );
  $adminperms=array(
  array('og_ui'=>'manage members'),
  array('og'=>'create book content'),
  array('og'=>'create forum content'),
  array('og'=>'create group_event content'),
  array('og'=>'delete any book content'),
  array('og'=>'delete any forum content'),
  array('og'=>'delete any group_event content'),
  array('og'=>'delete own book content'),
  array('og'=>'delete own forum content'),
  array('og'=>'delete own group_event content'),
  array('og'=>'update any book content'),
  array('og'=>'update any forum content'),
  array('og'=>'update any group_event content'),
  array('og'=>'update own book content'),
  array('og'=>'update own forum content'),
  array('og'=>'update own group_event content'),
  );
  $queryffs = db_select('og_role', 'og_role');
  $queryffs->addField('og_role', 'rid');
  $queryffs->addField('og_role', 'name');
  $queryffs->innerJoin('og', 'og', 'og_role.gid=og.gid');
  $queryffs->addField('og', 'etid');
  $recordsffs = $queryffs->execute();
  foreach ($recordsffs as $recordffs) {
    if($recordffs->etid!=''){
      db_update('og_role')->fields(array('gid' => $recordffs->etid))->condition('rid',$recordffs->rid, '=')->execute();
    }
    if($recordffs->name=='member'){
      foreach($memberperms as $value){
        foreach($value as $module=>$permissionname){
          db_insert('og_role_permission')->fields(
            array(
              'rid' => $recordffs->rid,
              'permission' => $permissionname,
              'module' => $module,
            )
          )->execute();
        }
      }
    }
    if($recordffs->name=='administrator member'){
      foreach($adminperms as $value){
        foreach($value as $module=>$permissionname){
          db_insert('og_role_permission')->fields(
            array(
              'rid' => $recordffs->rid,
              'permission' => $permissionname,
              'module' => $module,
            )
          )->execute();
        }
      }
    }
  }
  $queryffs = db_select('og_users_roles', 'og_users_roles');
  $queryffs->addField('og_users_roles', 'rid');
  $queryffs->addField('og_users_roles', 'uid');
  $queryffs->innerJoin('og', 'og', 'og_users_roles.gid=og.gid');
  $queryffs->addField('og', 'etid');
  $queryffs->addField('og', 'gid');
  $recordsffs = $queryffs->execute();
  foreach ($recordsffs as $recordffs) {
    if($recordffs->etid!=''){
      db_update('og_users_roles')->fields(array('gid' => (int)10000+(int)$recordffs->etid, 'group_type'=>'node'))->condition('gid',(int)$recordffs->gid, '=')->condition('rid',(int)$recordffs->rid, '=')->condition('uid', (int)$recordffs->uid, '=')->execute();
    }
  }
  $queryffs = db_select('og_users_roles', 'og_users_roles');
  $queryffs->addField('og_users_roles', 'gid');
  $queryffs->addField('og_users_roles', 'uid');
  $queryffs->addField('og_users_roles', 'rid');
  $recordsffs = $queryffs->execute();
  foreach ($recordsffs as $recordffs) {
    if($recordffs->gid!=''){
      db_update('og_users_roles')->fields(array('gid' => (int)$recordffs->gid-(int)10000))->condition('gid',(int)$recordffs->gid, '=')->condition('rid',(int)$recordffs->rid, '=')->condition('uid', (int)$recordffs->uid, '=')->execute();
    }
  }
}

just need to add default group perms and job done.

Senior Drupal Web Developer
Wellcome Trust Sanger Institute

qaisers’s picture

I am trying to follow the steps but at admin/content/migrate I am getting the following error. Can someone help me with this?

PDOException: SQLSTATE[HY000]: General error: 1364 Field 'group_name' doesn't have a default value: INSERT INTO {migrate_status} (machine_name, class_name, arguments) VALUES (:db_insert_placeholder_0, :db_insert_placeholder_1, :db_insert_placeholder_2); Array ( [:db_insert_placeholder_0] => OgMigrateMembership [:db_insert_placeholder_1] => OgMigrateMembership [:db_insert_placeholder_2] => a:2:{s:10:"class_name";s:19:"OgMigrateMembership";s:12:"machine_name";s:19:"OgMigrateMembership";} ) in MigrationBase::registerMigration() (line 385 of sites/all/modules/migrate/includes/base.inc)

RegB’s picture

If you make it to Step 5 and you DON'T see the Migrate Classes -- what should you do? Is there any way to manually migrate? Or is there a way to manually create the missing classes?

I see the code listed above, but don't have a clue how or if I could use it on my site.

arruk’s picture

These steps worked great for me with one caveat. When I went to rebuild permissions I got an ajax error. This may have been because I rebuilt the permissions before I did the migrate -- bad reading on my part. This error was easily fixed using the following two patches which I found at these nodes. The error may have been prevented by following the instructions better, but if not, here is the solution.

https://drupal.org/node/1699242 <-- first patch
Then run
https://drupal.org/node/1473674

I thought it would be useful to have this here.

qaisers’s picture

I was stuck in group permission for a while following did the trick for me
Goto
Config.. > Organic Groups > Field Settings

Select Bundle: Group
Select: Group Visibility

Add Field

Try to re-built permission.

Lars Bo Jensen’s picture

I can't get this to work. I have been following the above instructions. Along the way I get these errors (if someone can point me in some direction, I would be thankful):

Notice: Undefined index: label in entity_views_field_definition() (Zeile 191 von C:\web\ackl\sites\all\modules\entity\views\entity.views.inc).
Notice: Undefined index: label in entity_views_field_definition() (Zeile 191 von C:\web\ackl\sites\all\modules\entity\views\entity.views.inc).
Notice: Undefined index: label in entity_views_field_definition() (Zeile 191 von C:\web\ackl\sites\all\modules\entity\views\entity.views.inc).

Update #7200
Failed: DatabaseSchemaObjectExistsException: field_data_group_audience cannot be renamed into field_deleted_data_31: A table field_deleted_data_31 already exists. in DatabaseSchema_mysql->renameTable() (Line 307 in C:\web\ackl\includes\database\mysql\schema.inc).

PDOException: SQLSTATE[42S22]: Column not found: 1054 Unknown column 'base.language' in 'field list': SELECT base.id AS id, base.name AS name, base.description AS description, base.status AS status, base.module AS module, base.language AS language FROM {og_membership_type} base WHERE (base.status IN (:db_condition_placeholder_0, :db_condition_placeholder_1, :db_condition_placeholder_2)) ; Array ( [:db_condition_placeholder_0] => 3 [:db_condition_placeholder_1] => 2 [:db_condition_placeholder_2] => 6 ) in EntityAPIController->query() (Zeile 187 von C:\web\ackl\sites\all\modules\entity\includes\entity.controller.inc).

Warning: array_keys() expects parameter 1 to be array, null given in drupal_schema_fields_sql() (Zeile 7033 von C:\web\ackl\includes\common.inc).

http://geradezu.dk - Beratung und Gestaltung im Bereich online Präsenz

Akshita’s picture

We have built our site with OpenPublic as a base.

We had 2 security updates prompts:

1. Drupal Core : 7.26

2. Organic Group : 7.x-2.5

This is what I did:

First updated the Drupal Core to 7.26 from 7.x-2.4 and ran https://mysite/update.php which was success and skim through the site to make sure everything was working fine ------- This had no issues

Secondly updated the Organic Group when ran the update.php it alerted for the entity reference dependency module so installed the module and enabled it. Now when I run the update.php I get the following error:

Fatal error: Class 'EntityCacheControllerHelper' not found in /var/www/profiles/openpublic/modules/contrib/entity/includes/entity.controller.inc on line 292

Any help is appreciated.

Thanks in advance
Revathi

Triumphent’s picture

@Lars. I have the same problem. Have you ever found the solution for all those error messages?

Triumphent’s picture

Surely, other users have had the same issue.

Erich Schulz’s picture

wish someone had posted something like this...

     drush -y @members ard --destination ~/uboxmembers201403017.tar
     drush -y @members dis context
     drush -y @members cc all
     drush -y @members up entity
     drush -y @members cc all
     drush -y @members up views
     drush -y @members up entity
     drush -y @members dl migrate
     drush -y @members en migrate_ui
     drush -y @members dl entityreference
     drush -y @members en entityreference
     drush -y @members dl views_bulk_operations
     drush -y @members en views_bulk_operations
     drush -y dl og --destination=/var/local/www/members.example.org/htdocs/sites/all/modules
     drush -y @members updatedb
     drush -y @members mi --all
     drush -y @members cc all
bkirkham’s picture

Erich-
I can understand the rest of the drush commands, but the second line disables the Context module, and it doesn't get re-enabled later. Is there a particular reason for this?
-Brian

kip stanning’s picture

had a big problem the last couple of days after upgrading og from og-7.x-1.x to og-7.x-2.x. the community website i worked on uses private organic groups to form subgroups of site-members during travels organized by the website-owner.

after upgrading (of course locally and using drush) the content of the groups was gone. tried a lot of things only to make the whole content of the site appear as the content of the group. i noticed that in some way the views i used in the page manager did not receive the group id to filter the output correctly.

finally i had the idea to set up a fresh drupal install and build private groups on that fresh d7-site. the videoseries of @bjlewis2 at www.modulesunraveled.com was a big help. i then exported the views "OG nodes" and "OG members" to my updated local site and succeeded in getting the content pane "OG content" to work properly. problems perceived in "OG members" though until i printed the output of the respective views and compared it.

the important discoveries i want to share here:
1. it was best to use displays of type "Content Panes" to make the group-specific filter work.
2. in og-7.x-1.x the argument-parameters in section "Pane settings" were set to "Og-group ID" which was not automatically changed during migration.
3. in og-7.x-2.x i hat to set the argument-parameters in section "Pane settings" to "Content ID" (obviously reflecting the changed way of creating the group ID in og-7.x-2.x) every time i created a new view of type Content Pane. cloning the view was not enough since the argument-input-parameter was not cloned to the new view and had to be set manually to "Content ID".

hope to help others this way!
regards karl
screenshots: https://dl.dropboxusercontent.com/u/8653657/scsh-arginp-og7x1x.jpg https://dl.dropboxusercontent.com/u/8653657/scsh-argInp-og7x2x.jpg https://dl.dropboxusercontent.com/u/8653657/scsh-panesettings.jpg

update: another problem that was easily solved in og-7.x-1.x and caused serious troubles in og-7.x-2.x was building a list of titles of the group content in a pane shown aside the full view of a group-content node. i was mislead by the above solution to use "argument input" in pane settings and did not manage in 4 days to find the proper setting (does it exist?). the solution was much easier: set the "argument input" to "no argument" and use "provide default value" in "contextual filter". as the default value set "current OG group from context". activate the option "specify validation criteria" and set the validator to "OG group", group type to "node" and - in my case - action if ... not validate to "hide view".

frustrating days behind me, thriumph of finally getting it done is a considerable compensation.
regards
karl

emjayess’s picture

There's no mention or explanation here-in that I can find regarding OG-related rules which, in my case, wound up being made inactive. Now, I don't know if these rules are incompatible with new OG, or if I can safely activate them, or perhaps if the job they were doing may have been assimilated in to the new version of OG.

--
Matt J. Sorenson (emjayess)
d.o. | g.d.o. | twitter

lguigo’s picture

I don't see migration class of og module into content/migrate

harderj1’s picture

Updating OG 7.x-1.x to 7.x-2.x. All required modules installed and updated. Installed the latest version of OG. Ran updates successfully. Went to admin/content/migrate but there are no migrations listed. Checked to see if the groups were working as expected, but they aren't. Problems all over the place. Does anything special need to be done to get the migration to show up in admin/content/migrate?

Jody Lynn’s picture

With newer versions of migrate I believe you need to run
drush mreg
Once I ran this, the og migrations showed up.

--Zivtech--

dzy’s picture

Still can't see og class, i am using og 2.7 + migrate 2.7 , or og dev + migrate 2.7 , or og 2.7 + migrate 2.5.
is there another module i need enable/disable?

SomebodySysop’s picture

OG 7.x-2.7, Migrate 7.x-2.7+5-dev, Drupal-to-Drupal Migration 7.x-2.1, Entity api, Entity reference and VBO installed. Cleared caches and ran drush mreg. Still no OG migrations viewable at admin/content/migrate/. Anything else to check?

benrj’s picture

Using og 2.7 + migrate 2.7+30-dev and migrate 2.7
also tried with migrate 2.7 - dev.

Tried clearing cache, as well as running migrate_static_registration() (which is what drush mreg does)

Anyone have any ideas?

benrj’s picture

Specifically, the migrate API definitions in OG are not compatible with recent versions of Migrate.

I ended up un-installing Migrate and installing the 2.5 version as some above have said. Once I did that, the migrations showed up for me.

I'm not sure what the drawbacks are of this approach at this point..