CiviCRM Community Forums (archive)

I successfully enabled civicrm_og_sync.module ...(removing txt from the .info filename)

on activation, the module as advertised made 1 way sync of my OG groups and drupal users to CiviCRM
1) keeping the users and groups correctly associated
2) making two groups (one admin) for each organic group

so far, so good.

next, tried adding a user to an organic group to see if it updates CiviCRM.  No luck. threw error
Sorry. A non-recoverable error has occurred.
We experienced an unexpected error. Please file an issue with the backtrace
Return to home page.
next, tried adding a new organic group.  No luck ... threw same error.

next, tried disabling (but not uninstalling) civicrm_og_sync.module and re-enabling
no effect on the above problem.

Am I doing something wrong or having misplaced expectations?
Does the one way sync work for others?  Or is it just sync the first time the module is installed?

Thanks

note that we've only started supported the og_sync.module since v2.1.2

lobo

In our definitition, support means we will do our best to debug and fix issues reported against it.

The code was included in prior releases more for developers as a starting point. We've cleaned up and tested the code in 2.1.2. We'll also start documenting them in more detail over a period of time

lobo

I might add a bit of info here.  It might be a cause of some of the problem or at least useful to someone who has a similar installation.

Before reading that the CiviCRM autoinstaller required the package to be in the sites/all/modules directory I had originally placed it in my sites/groupsalive.com.grhc/modules directory because I had only intended it to be used on the "grhc" site.  To use the autoinstaller, I copied the civicrm directory to the correct location at sites/all/modules  but did NOT delete the original copy.

I have a multisite drupal installation with one codebase and all sites in the same drupal database with seperate prefixed table sets. There are symlinks in the drupal root pointing users to the respective subsites/subfolders. I did not do a multisite install of CiviCRM because I only intended it to be used with one of the drupal sites.  I don't know if this was correct.  The only config change this seemed to require was including the line

define( 'CIVICRM_UF_BASEURL'      , 'http://www.groupsalive.com/grhc/' );
in my civicrm.settings.php file.  Everything seemed to work pretty well.

Until this morning.  In an attempt to clean things up, I removed the original copy of civicrm folder from sites/groupsalive.com.grhc/modules.  This prevented me from accessing any civicrm functionality on my site.  Apparently, CiviCRM as activated in drupal was using the copy in that local site location rather than the one in the sites/all/modules location.  This is not surprising in retrospect since drupal looks first in the individual sites modules files.

What is surprising is that when I removed it, deactivated and then reactivated the module ( correctly, I thought) from the only one left (sites/all/module) ... civicrm did not work.

Everything works correctly again when I copy the civicrm folder back to the original location (sites/groupsalive.com.grhc/modules)

I know this is complicated.

Any idea what I am missing?