Hi!
Mentioned problem was described here:
http://drupal.org/node/1331786
After upgrading to Geofield 7.x-1.0-beta1 (or 7.x-1.x-dev from 2011-Nov-04) it is impossible to add new "Group type" node, node add page just refreshes after clicking "Save" button, and we can see such message in log:
PHP Fatal error: Unsupported operand types in /var/www/sky37.pp.ua/public_html/sites/all/modules/og/og.module on line 286, referer: http://sky37.pp.ua/en/node/add/group?render=overlay
Downgrading to Geofield 7.x-1.0-alpha5 solves this problem, so looks like it is degradation. In my case there are no Geofield fields assigned to "Group type" node (and there are no custom fields at all), and I add new groups manually. Drupal 7.9, Organic groups 7.x-1.3. Would be glad to provide any additional information about this issue.

Comments

Brandonian’s picture

Status: Active » Postponed (maintainer needs more info)

Thanks for the bug report, renat! I can't replicate the issue on a clean install. The stack that I'm currently running is...

- Drupal 7.9
- Geofield 7.x-1.x-dev (with an additional patch from this morning relating to the openlayers module, which I really doubt is playing into this issue)
- Organic Groups 7.x-1.3

If I can get some more info on the content type in question, I can help find a solution. To be honest, since the error is originating from OG itself, I'm skeptical that Geofield is the root source of the issue, but I've been wrong before...

tvilms’s picture

Hi, I can confirm the same problem with respect to the OG module. I was running Geofield 7.x-1.0-beta1 and OG 7.x-1.3. I was no longer able to add groups or manage group memberships. I just rolled back to 7.x-1.0-alpha5 and OG memberships are working again. I believe this is a Geofield bug.

I had a geofield on my Group content type. The geofield was set to geocode from the postal address.

Here are some more details I posted over in the OG issues queue, before you cross-posted over there, in case it helps: http://drupal.org/node/1340926

Brandonian’s picture

Status: Postponed (maintainer needs more info) » Fixed

Time to eat crow...

So, I think the issue had to do with what we were trying to do with #1285706: local solr update. In it, I attempted to provide solr integration for non-node entities, which involved invoking a hook_entity_alter call of dubious nature. Once I reverted that patch back, I no longer had any issues with og access issues. Your mileage may vary, but since that commit happened between alpha-5 and beta-1, I'm 99% sure that's the issue.

Expect a new beta release soon.

RobKoberg’s picture

I can confirm this is fixed in dev, with regard to og group types.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

Anonymous’s picture

Issue summary: View changes

Fixing broken link to issue in OG queue