I get a fatal error when trying to create a geo field on a basic content type. Occurs on line 51 of geo_field.module.

    case 'database columns':
      $geo_type = isset($field['geo_type']) ? geo_type($field['geo_type']) : GEO_UNKNOWN;
      return GeoSQL::sqlFieldDefinition('geo', $geo_type);

Comments

allie micka’s picture

allie micka
she/her
commented

Hi LouBabe (and anyone else kind enough to find this issue before reporting a duplicate one)

Can you see if HEAD and/or the dev release works better? If so, I'll roll a new alpha4 release!

levelos’s picture

levelos commented
Status: Active » Fixed

Thanks Allie, the issue's resolved. I'm evaluating using this on a production for mapping contamination site's along a river. Do you think Geo's ready for use on a production site, given there are competent developers involved?

allie micka’s picture

allie micka
she/her
commented

Thanks a lot for your followup, LouBabe!

Well, that's certainly a loaded question ;)

There's no guarantee at this point that Geo will work super-flawlessly, or that it's got everything you need in it. That's why it's alpha! Having said that, as of the alpha3 release, I have made all of the major changes I intend to make to the architecture and Views support for this module.

This means that you should be able to set up and use Geo now, and take advantage of new features and bug fixes in upcoming releases without doing a lot of backtracking or losing your data. Couple this with the fact that Geo offers access to data collection and analysis functions that simply don't exist anywhere else in Drupal, I would assert that it's a good choice.

It's worth noting that our work is not well-funded. When I spend a lot of dedicated hours working on Geo and other contrib modules, I often can't make payroll for our company - which usually means I don't get a paycheck. This is pretty unsustainable! However, most of the difficult-to-fund heavy lifting is now complete, so we're hopeful to keep this sustainable through Using our services, Direct contributions or just contracting us to work on a particular feature or bugfix.

levelos’s picture

levelos commented

Thanks Allie, that helps.

I hear you on getting paid for your efforts, I find myself in a similar situation at times! We'll definitely turn to you when we have a need and budget for some help. Great work on the modules.

roball’s picture

roball commented

I am encountering the same critical error with alpha 3 (no problems with alpha 2), so I can't use this module on new sites at all. Allie,
when do you think alpha 4 is rolled out?

Thanks.

robertdouglass’s picture

robertdouglass commented

Confirm that HEAD fixes the problem. Would be a great boon if you could roll an alpha 4 =)

roball’s picture

roball commented

I can also confirm that with Geo Module 6.x-1.x-dev (2010-Jan-20) that problem has been fixed. Should probably be released as alpha 4 or even beta 1.

allie micka’s picture

allie micka
she/her
commented

Alpha4 rolled! it's a little early to call a beta just yet :)

Thanks a lot, y'all!

roball’s picture

roball commented

Thanks Allie! Alpha 4 is working fine or me.

Status: Fixed » Closed (fixed)

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