Based on the fact that a devel.module "dev render" displays $location data of the node, I've been trying for days to use that information in a computed_field, combined with a gmap.module gmap_simple_map() function, to display the current nodes mapped location.

Problem? computed_field doesn't actually see the $location array, despite the fact both devel.module, and a call within the template files, both see this information when making a call to $node.

Is this a location.module, or computed_field.module, issue? and can this be fixed? I have a lot of things I wanted to do with this combination of gmap.module, location.module, and computed_field.module, but unfortunately I'm having to put all of these on hold until I can find a solution to this issue :/

Comments

Raving’s picture

Raving commented
Category: feature » bug

Add Taxonomy_Field.module... same problem. Nobody got any ideas?

Raving’s picture

Raving commented
Priority: Normal » Critical

Done some further playing, and using the module_weight.module to set computed fields weight to that of Devel.module (88), it appears this is not a weighting issue... I'm not exactly code orientated, and have tried looking at the code of both devel and computed field to see how each module pulls it's $node variables as there is obviously a difference there, and am kind of lost :/

Please, can anyone shed some light on this issue? It's annoying the hell out of me as every angle of attack I've taken so far, to do what I want to do, always seems to rely on computed field, which inturn doesn't want to see the variables it needs too. Devel seems them as being a part of $node, why doesn't computed field? :(

Raving’s picture

Raving commented
Priority: Critical » Normal
Status: Active » Closed (duplicate)

Finally getting somewhere... Looks like this could be related to http://drupal.org/node/202384 as after applying, Content_Taxonomy.module created fields are now exposed :)