I am not sure what is going on. But the store locator is only showing 1 item on the maps page. In the conf area I have changed this to 1,5,10,50 and it never returns more than one. In the JSON exporter in the view I have it displaying multiple items. I even set it to show random items with displaying 10 and every time i reload the map it shows a new listing. But know where that I can specify amount of items to show up will it show any more than 1 single item.. Anyone have any idea what is going on or could be causing this? It was displaying everything and as soon as I went live with the site now it only displays a single item. I didn't change any settings though. So now I have this live site running and the map is not working properly. Any help on this would be greatly appreciated!

Comments

DTWtoMSY’s picture

DTWtoMSY CreditAttribution: DTWtoMSY commented

Mine is showing only two stores despite additional locations. I am stumped too.

DTWtoMSY’s picture

DTWtoMSY CreditAttribution: DTWtoMSY commented

Figured it out. You changed your geocoder settings after you had entered your first store. Go to Structure > Content > Store Location and reset your gsl_geofield. Then go through each article of content for your stores and hit edit / save and it will automatically update.

skalfyfan’s picture

skalfyfan CreditAttribution: skalfyfan commented

damn. I just updated to the latest dev release and now I have this issue too. No matter what I try only a single location shows up.

I've gone in and resaved the content type gsl_geocoder field. I've resaved all my content. Still nothing. Only 1 result. Hrm.

skalfyfan’s picture

skalfyfan CreditAttribution: skalfyfan commented

fix was to:

a) write a quick module that exports and imports store_location node data to a CSV.
b) uninstall google store locator module
c) ensure that content type and view was deleted (the location export view still does not get deleted on uninstall. had to manually do this.)

re-install google store locator module. configure it. then imported my CSV which I exported to recreate all my store location nodes.

It works again now!

not sure what the issue was but I updated my store locator module from v1.0 to the latest dev build and no matter what I did the map would always showed 1 location.

DTWtoMSY’s picture

DTWtoMSY CreditAttribution: DTWtoMSY commented

Writing a module to fix something like that sounds like fun...

I went to a responsive theme recently that doesn't display the map. Unfortunately, that's not the only issue. Although it appears to locate the nearest store if the user accepts, running a city name search pulls up only one particular city. Works perfectly on desktop and nonresponsive design. I'm baffled. I have a guy in another area of the state that's supposed to check back with me tomorrow to see if his phone pulls up the correct information for his geographic region.

hoZt’s picture

hoZt CreditAttribution: hoZt commented

Rolling back to version 7.x-1.0 solved the problem at least until I update again.

ak55’s picture

ak55 CreditAttribution: ak55 commented

Hi I had this problem before with 7.x-1.1 and it's working in our sites.
I remember I fixed this by adding 'Content:Nid' in the JSON view.
Somehow the new version uses Nid to identify each location I think.

camprandall’s picture

camprandall CreditAttribution: camprandall commented

Ok, so this is an easy fix. You need to change the label of the Nid in the json view to "nid", all lowercase. That's what the module js code expects.

javijevi’s picture

javijevi CreditAttribution: javijevi commented

Yes, changing every t('Nid') to t('nid') in the following files worked for me:

sites/all/modules/google_store_locator/google_store_locator.views_default.inc
sites/all/modules/views/modules/tracker.views.inc
sites/all/modules/views/modules/node.views.inc
sites/all/modules/views/modules/comment.views.inc

recrit’s picture

recrit CreditAttribution: recrit commented
Assigned: Unassigned » recrit
Status: Active » Fixed

The generation of the store id has been updated in the latest 7.x-1.x-dev as of commit 8843949.
The updated id generation checks the following:

  1. "uniqueid" property - The view can output this field to implement any custom unique id.
  2. "nid", "Nid" - Support legacy views.
  3. Else: an id is generated for the store.

Status: Fixed » Closed (fixed)

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