In deploying the Geo module to a Drupal installation, I am seeing the error:
PHP Fatal error: Call to undefined method GeoSimple::sqlFieldDefinition() in geo/modules/geo_field/geo_field.module on line 59
...which is completely borking the installation on most pages.

CommentFileSizeAuthor
#12 geo-sqlfielddefinition_undefined-820000-12.patch3.29 KBagileware
#5 geo_openlayers_0.patch3.88 KBstrk

Comments

strk’s picture

strk commented

Confirmed (see http://drupal.org/node/824694)
This came out for me with CVS HEAD, adding a Geospatial field to a content type, using postgresql

strk’s picture

strk commented

Some more documentation in geo.api.inc would help...

I'm trying to figure if the idea is to really distinguish between geo_load and geo_sql_load or not.
I see the latter calls the former, but not the other way round. And the only way to use geo_load
and have it use a database would be to explicitly add an handler member in the argument (untyped array, not helping).

So, who's doing the wrong thing here ? geo_field missing to call geo_sql_load ?

strk’s picture

strk commented

The patch attached to bug http://drupal.org/node/804878 addresses this issue successfully

strk’s picture

strk commented

http://drupal.org/files/issues/geo_openlayers_0.patch <-- this is the patch fixing this for me, does it count as "reviewed & tested" status ? (i actually just tested, no review)

strk’s picture

strk commented
StatusFileSize
new geo_openlayers_0.patch3.88 KB

I duplicate the patch here, just in case it'd get replaced in the other issue.
The other issue should really be just for Openlayers V2 Support.

strk’s picture

strk commented

should the geo_openlayers module be renamed geo_field_openlayers_widget ?
As I think it's time to work on geo_field_openlayers_formatter module....

allie micka’s picture

allie micka
she/her
commented
Status: Active » Postponed (maintainer needs more info)

I haven't looked at #804878 much, as it's almost impossible to vet an überissue like that.

It's important that we leave unreleated things like openlayers support and formatter questions out of this issue, or we'll never be able to clearly identify what the root of the issue is, how to fix it, and whether or not it has been fixed without

@mrtorrent (et all) can you clarify the steps you took that led you to that error message? Please provide us with the kind of information we need to reproduce this message.

Thanks!

levelos’s picture

levelos commented

Very simple to replicate:
* Vanilla Drupal 6.17 install using MySql
* enable CCK, Views, and Geo (latest dev release)
* Add a GeoSpatial field, with any settings

Voila, fatal PHP error!

strk’s picture

strk commented

Here's my case:

* Vanilla Drupal 6.17 install using PostgreSQL
* enable CCK, Views, and GEO (CVS HEAD)
* Add a GeoSpatial field, with any settings

Voila, fatal PHP error!

mrtorrent’s picture

mrtorrent commented

@Allie, sorry I wasn't clear in the initial report. I've not tested it on a vanilla install, so thanks to loubabe and strk for doing that, but like them all I did was enable geo (CVS HEAD) and geo_field and have a content type with a geo_field.

strk’s picture

strk commented

http://drupal.org/comment/reply/813300 contains another report of the same bug, which I'm closing as duplicate.
Note that the patch in #5 only touches the geo_field module, despite the name.

@loubabe, @mrtorrent: did you try that patch ?

agileware’s picture

agileware commented
Status: Postponed (maintainer needs more info) » Needs review
StatusFileSize
new geo-sqlfielddefinition_undefined-820000-12.patch3.29 KB

Here is a version of the patch in #5 that doesn't have the unrelated WKT/openlayers line.
I will take the removed portion back to #804878: Openlayers V2 Support.

Patch is made for HEAD.

Seems to fix the problem for me (as per #8 & #9).