'Location map' block is not visible

Are you using the generic Location or are you using the CCK Location field? I've noticed the CCK Location field does not work with that block and you need to make your own.

I am using "generic" location and same problem - then I switched from the "Newswire" theme to Acquia Marina and the block is displaying correctly...

next question would be, what in the theme is missing (or conflicting) that would cause this?

I am also having this issues and I cannot seem to figure out what is conflicting unless it is javascript. I know then when trying to move the java to the footer once Location will not show up at all, it is very sensitive with java. Any ideas?

The block will only work on /node/%nid pages since the block checks for this condition. Then it checks for $node->locations which location_cck doesn't have as yet.

You can try this patch to add the $node->locations for location_cck #383244-31: location_cck back compat and views support

Let us know if you have success!

Same problem using Acquia Marina 3.x (Fusion/Skinr).

I modified my custom tpl.php file and added this where I wanted the map to show up:

<div class="res-gmap">
<?php print $node->content['field_res_prop_location']['field']['#children'];?>
</div>

The variable name 'field_res_prop_location' is particular to my site. If you enable the devel module and insert the following line somewhere in your tpl.php file: php dsm($node); ?> then reload the page you can find your particular variables in the message section at the top of the page - just drill down through 'content' --> 'field' and so on.

My problem is this works fine in Firefox 3.6.2 but not in Opera 10.1 or IE8. Examining the source shows the div "res-gmap" but it's empty - weird.

All of the gmap scripts are also absent from the source, but not in FF.

UPDATE:It was a permissions issue (as usual)...

tagging

tagging again

is anyone still having a problem with this? taote, typehost, venusrising?? Post back.

If no more information in 2 weeks, we'll mark this closed.

No response in 2 months should validate YesCT's suggestion.

Issue marked as closed and considered resolved.

On second thought lets mark it as fixed instead.

nickl, Thanks! Actually there are probably a bunch of issues that can be marked postponed (needs more information) and if no one responds in 2 week, we (ummm you, others?) can close them.