Display Suite doesn't show location information as collected by location module

You're sure this for Drupal 7 right ? I haven't even tested location and DS for Drupal 7.

I had a similar problem. Locative informations do not appear on pages formatted with a DS layout (i.e. one column) and also the "Location map" block. I solved the location map by using gmap views+argument. But locative information still not show.
Can be interesting that, when I was trying Revisioning module with "inline diff", locative information appeared on my DS formatted pages. But in node view they disappeared. However, Revisioning is causing me other issues, like comment form disappearing on nodes.

Same as Road Runner and #3, no locative informations fields displaying.

It seems the module is still in the works, especially with another branch: "Location 7.x-4.x is in the works and it is a full rewrite to use fields API for everything."

In the meantime, you can create a custom DS field with following code - don't forget to toggle the 'Toggle location display' to disabled at admin/config/content/location, otherwhise, the code is both run in nodeapi and in this field which is a waste of memory.

  $settings = variable_get('location_settings_node_' . $entity->type, array());
  if (isset($entity->locations)) {
    print drupal_render(location_display($settings, $entity->locations));
  }

Hi there,
I have used the suggestion in comment #5 to include location into DS, but now I wondering how can I alter the format in the same way that view does because the output of displaying the whole information (label included).

As you can see in the attached screen-shot there are not formats available.

Thanks.

Mirror Issue #1123338: Locative information is not available in Display Suite

@altrugon - I used views reference field to bring in a custom location view that I made for showing a location map based upon node id argument. I made the views reference field required, limited it to 1 value, and limited the selection to the specific view i want to have show the map on the node. This is a temp. work-around until you can truly customize the location maps through the display suite interface.

Closing this one - as stated on the location page

Location 7.x-4.x is in the works and it is a full rewrite to use fields API for everything.

So as soon that one comes out, the fields will popup automatically.

Sorry using the 7.x-4.x branch no fields poping up :( Any idea how to fix this?

Custom fields is the answer. You'll have to inspect the node which is passed in the $field variable in the function or the $entity object when using the UI.

@swentel; I'm using the code you posted in #5. It works fine but it shows the latitud and longitude. The 'format' dropdown only show 'Default'.
How can I do to show the map instead?

Location not playing nice with Display suite. .. not sure if its location exposing the field elements or ds not seeing them.. but.. turning off ds and styling node level defaults .. it'd be nice to use ds here.. thx

Even though this issue is closed, I'm adding this comment to help anyone who may encounters this issue.

I was able to get the Locative Information to be displayed using Display Suite by creating a custom code field and using a token:

[node:location:name:0]

This worked for our application because only the location name was needed. It seems that it would be possible to use the other location tokens.

I hope that helps someone!

@swentel,

When you changed the status of this to "Closed - won't fix.", you wrote...

"Location 7.x-4.x is in the works and it is a full rewrite to use fields API for everything."

Even now, 4 years later, I don't see a 4.x version of Location. I'd like to ask if you might revisit this issue and reconsider the "won't fix" decision. I would like to show a Gmap of the user's location, not just location fields. As I understand it, that's not possible with DS custom fields.

It's not the job of DS to create integrations for every module. You can achieve this yourself but you'll need to code it yourself using custom field functions like Swentel suggested above.

For a solution, see https://www.drupal.org/project/location/issues/1123338#comment-9424125