I'm a little confused how to get the right markers to show up at a specific node using contextual filters.

I have 2 locations fields:
1 = geofield
2 = entity reference to a node that has a geofield.

This means when creating the node you can choose a geofield location or an entity referenced node or both. I created a block with the map that shows one of the two or both fields using contextual filters (content:NID) so that it only shows the right markers.

The problem is that it only shows the first selected field at the format settings when both fields are highlighted at 'Name of latitude field in Views query'. when I select one field is shows the marker(s) of that field so it works but not when I select two fields.

Hope someone knows the solution. Thank you

CommentFileSizeAuthor
#7 Multi-locations per View result row.png1.74 MBrdeboer
#5 2.png74.23 KBQNDY
#3 1.png67.17 KBQNDY

Comments

rdeboer’s picture

rdeboer
Location Melbourne
commented

Hi QNDY,
Thank you for your interest in IPGV&M.

One thing I recommend to determine if this is a bug or not, is to add an Attachment display to your existing map View, showing the same result set as a table.

If your table shows two Geofields per row then you may have hit a bug in IPGV&M.
If your table does not show two Geofields per row, then you need to work on your View a bit more.

If there is a bug, and your site is small would you be able to use the Backup&Migrate module and send me a copy of your db? This type of bug can only be solved efficiently with a debugger running locally on my laptop.

Rik

rdeboer’s picture

rdeboer
Location Melbourne
commented

If you are not seeing all entity refs, the patch from #15 in this Entity API issue may help: https://www.drupal.org/node/1378656#comment-5922278

QNDY’s picture

QNDY commented
StatusFileSize
new 1.png67.17 KB

Thank you for the quick reply. I cloned the block and deleted the relationship and contextual relationship. Now the block shows both node types. So I guess the multiple fields are correct in the map settings or maybe I am not fully understanding it. I put a screenshot with the view attachment viewed on the specific node that has one entity ref geo and 1 geo in the node itself.

rdeboer’s picture

rdeboer
Location Melbourne
commented

Hi QNDY,
Thanks for the screenshot. So yes that looks good. You have two lat/lon field, one Geocode and one Gecode_Value.

Now I'd love to see your Views map setup and finally the resulting map where it all goes wrong...

That will give me a better handle on what goes wrong...

Cheers,
Rik

QNDY’s picture

QNDY commented
StatusFileSize
new 2.png74.23 KB

Hi RdeBoer,

This is the export of a clone with a block including the ref and contextual filter:

$view = new view();
$view->name = 'clone_of_maps';
$view->description = '';
$view->tag = 'default';
$view->base_table = 'node';
$view->human_name = 'Clone of Maps';
$view->core = 7;
$view->api_version = '3.0';
$view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */

/* Display: Master */
$handler = $view->new_display('default', 'Master', 'default');
$handler->display->display_options['title'] = 'Where';
$handler->display->display_options['use_more_always'] = FALSE;
$handler->display->display_options['access']['type'] = 'perm';
$handler->display->display_options['cache']['type'] = 'none';
$handler->display->display_options['query']['type'] = 'views_query';
$handler->display->display_options['exposed_form']['type'] = 'basic';
$handler->display->display_options['pager']['type'] = 'some';
$handler->display->display_options['pager']['options']['items_per_page'] = '5';
$handler->display->display_options['style_plugin'] = 'ip_geoloc_leaflet';
$handler->display->display_options['style_options']['grouping'] = array(
  0 => array(
    'field' => '',
    'rendered' => 1,
    'rendered_strip' => 0,
  ),
);
$handler->display->display_options['style_options']['map_height'] = '300';
$handler->display->display_options['style_options']['ip_geoloc_views_plugin_latitude'] = array(
  'field_geocode_venue' => 'field_geocode_venue',
  'field_geocode' => 'field_geocode',
);
$handler->display->display_options['style_options']['ip_geoloc_views_plugin_longitude'] = '';
$handler->display->display_options['style_options']['center_option'] = '0';
$handler->display->display_options['style_options']['cluster_differentiator']['cluster_differentiator_fields'] = array(
  '' => '',
);
$handler->display->display_options['style_options']['cluster_differentiator']['zoom_ranges'] = array(
  1 => '',
);
$handler->display->display_options['style_options']['cluster_differentiator']['cluster_tooltips'] = 1;
$handler->display->display_options['style_options']['cluster_differentiator']['cluster_outline'] = '0';
$handler->display->display_options['style_options']['cluster_aggregation']['aggregation_function'] = 'average';
$handler->display->display_options['style_options']['cluster_aggregation']['ranges']['small'] = '10';
$handler->display->display_options['style_options']['cluster_aggregation']['ranges']['medium'] = '100';
$handler->display->display_options['style_options']['cluster_aggregation']['ranges']['large'] = '1000';
$handler->display->display_options['style_options']['map_options']['maxzoom'] = '18';
$handler->display->display_options['style_options']['map_options']['zoom'] = '10';
$handler->display->display_options['style_options']['map_options']['scrollwheelzoom'] = '1';
$handler->display->display_options['style_options']['map_options']['dragging'] = '1';
/* Relationship: Entity Reference: Referenced Entity */
$handler->display->display_options['relationships']['field_venue_moment_target_id']['id'] = 'field_venue_moment_target_id';
$handler->display->display_options['relationships']['field_venue_moment_target_id']['table'] = 'field_data_field_venue_moment';
$handler->display->display_options['relationships']['field_venue_moment_target_id']['field'] = 'field_venue_moment_target_id';
/* Field: Content: Title */
$handler->display->display_options['fields']['title']['id'] = 'title';
$handler->display->display_options['fields']['title']['table'] = 'node';
$handler->display->display_options['fields']['title']['field'] = 'title';
$handler->display->display_options['fields']['title']['label'] = '';
$handler->display->display_options['fields']['title']['alter']['word_boundary'] = FALSE;
$handler->display->display_options['fields']['title']['alter']['ellipsis'] = FALSE;
/* Field: Content: Geocode */
$handler->display->display_options['fields']['field_geocode_venue']['id'] = 'field_geocode_venue';
$handler->display->display_options['fields']['field_geocode_venue']['table'] = 'field_data_field_geocode_venue';
$handler->display->display_options['fields']['field_geocode_venue']['field'] = 'field_geocode_venue';
$handler->display->display_options['fields']['field_geocode_venue']['relationship'] = 'field_venue_moment_target_id';
$handler->display->display_options['fields']['field_geocode_venue']['label'] = 'Geocode_venue';
$handler->display->display_options['fields']['field_geocode_venue']['click_sort_column'] = 'geom';
$handler->display->display_options['fields']['field_geocode_venue']['settings'] = array(
  'data' => 'full',
);
/* Field: Content: Geocode */
$handler->display->display_options['fields']['field_geocode']['id'] = 'field_geocode';
$handler->display->display_options['fields']['field_geocode']['table'] = 'field_data_field_geocode';
$handler->display->display_options['fields']['field_geocode']['field'] = 'field_geocode';
$handler->display->display_options['fields']['field_geocode']['click_sort_column'] = 'geom';
$handler->display->display_options['fields']['field_geocode']['settings'] = array(
  'data' => 'full',
);
/* Sort criterion: Content: Post date */
$handler->display->display_options['sorts']['created']['id'] = 'created';
$handler->display->display_options['sorts']['created']['table'] = 'node';
$handler->display->display_options['sorts']['created']['field'] = 'created';
$handler->display->display_options['sorts']['created']['order'] = 'DESC';
/* Filter criterion: Content: Published */
$handler->display->display_options['filters']['status']['id'] = 'status';
$handler->display->display_options['filters']['status']['table'] = 'node';
$handler->display->display_options['filters']['status']['field'] = 'status';
$handler->display->display_options['filters']['status']['value'] = 1;
$handler->display->display_options['filters']['status']['group'] = 1;
$handler->display->display_options['filters']['status']['expose']['operator'] = FALSE;

/* Display: Block */
$handler = $view->new_display('block', 'Block', 'block');
$handler->display->display_options['defaults']['arguments'] = FALSE;
/* Contextual filter: Content: Nid */
$handler->display->display_options['arguments']['nid']['id'] = 'nid';
$handler->display->display_options['arguments']['nid']['table'] = 'node';
$handler->display->display_options['arguments']['nid']['field'] = 'nid';
$handler->display->display_options['arguments']['nid']['default_action'] = 'default';
$handler->display->display_options['arguments']['nid']['default_argument_type'] = 'node';
$handler->display->display_options['arguments']['nid']['summary']['number_of_records'] = '0';
$handler->display->display_options['arguments']['nid']['summary']['format'] = 'default_summary';
$handler->display->display_options['arguments']['nid']['summary_options']['items_per_page'] = '25';

So the configurations are precisely the same as the first screenshot above but then of course with the map format. The second screenshot shows the settings of the map. I only selected the 2 fields and kept the rest the same. The block shows only the first selected field in the map settings. when deselecting the first field it shows the second field (non entity) and vice versa.

Thanks!

rdeboer’s picture

rdeboer
Location Melbourne
commented
Title: Using entity ref & contextual filters » Handle multiple locations per Views result row
Category: Support request » Feature request

HI QNDY,
Thanks for the above.

Big slap against the forehead!

What was I thinking? The option to select multiple lat/lon fields for the map came about for cases when people wanted to create maps with locations from different content types. So you might have a View that has Museums and Restaurants and for historic reasons these do not use the same field for lat/lon (hell, one may be using a Geofield while the other uses Location). So in that case, with each View result row pertaining to either a Museum or a Restaurant, the module will automatically pick up from each row the lat/lon field that is not empty.

The module was never meant to cater for your use-case, where one View result row has TWO locations on it to put on the map.

I'll have a look at what's involved to make this happen. Could be a biggy...

Rik

rdeboer’s picture

rdeboer
Location Melbourne
commented
Assigned: QNDY » rdeboer
Status: Active » Fixed
StatusFileSize
new Multi-locations per View result row.png1.74 MB

Just checked in a mod that should give you what you are after. Try the latest IPGV&M 7.x-1.x-dev

See the screenshot below. The two yellow markers belong to the same View result row, labeled "CBD" in the table below the map.

In this example CBD is a term in a "Region" vocabulary. Each Region term has one or two Geofields attached to it. The first Geofield is the Centre of Region, the second is a Point of Interest in the region.
If a term has only one Geofield set, then only one marker will be shown.

Multiple locations per View result row

QNDY’s picture

QNDY commented

Hi,

I just the dev and It works like a charm! Nice job and thank you for the quick replies and fixes!!

rdeboer’s picture

rdeboer
Location Melbourne
commented

Yay! HIgh-five!

Status: Fixed » Closed (fixed)

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