In map all data shows very well with marker. But data not display below map as you have given in the screenshot i have installed all required modules expect leaflet. Please check attached screenshot of view.
Do I understand correctly that you want to see a TABLE under your MAP ?
You do this by clicking at the top of the Views UI the Display button Add-> Attachment.
Then on the Attachment thus created, set the Format to Table.
In the middle, under "Attachment settings", select Attach to: Page and Attachment position: After.
That's pretty much it.
Remember that you can Exclude columns from View, both in your map and in your table. These don't have to be the same selection, just make sure you click "This attachment (override)", at the very top of the Field configuration panel. Otherwise your field settings will apply to both the map and the table.
» Attached View Data not inheriting filter settings
Version:
7.x-1.26
» 7.x-1.x-dev
Status:
Closed (fixed)
» Active
Issue tags:
-data not display
G'Day Rik,
This issue was closed, yet it matches my problem well: I'm hoping for a bit more guidance.
The solution outlined above (create a Views attachment and attach to Proximity veiw) sounds simple, but I think there are some more variables involved. Here's how I see the relationship:
Proximity View
- FIELDS: Contains any fields, one of which MUST be the (geofield) - proximity
- FILTERS: Contains any filters, one of which MUST be the (geofield) - proximity, set as exposed, and taking input from a range of sources (including the Geocoder)
- SORT: First sort term MUST be the (geofield) - proximity, sorting on ASC (if you want to display closest results first)
That's it for the Proximity View, and in my case this works fine. I allow users to enter a search term, Google geocodes it, and I get a map display with proximate nodes. Using a pager, I can see the matching result set move out from the refernece point as I page through the results. All good.
Now, let's add a tabluar display below the map. As normal, we go to Views and choose to create a new display, of type=Attachment.
The first item under SETTINGS where we attach the new display to the Proximity View above.
Working down the other options, I think these must be properly set as well:
The last one I think is critical (?) as otherwise the attached tabular view will not know to follow the User's exposed filter input from the Proximity View display.
So: I have done all this, and yet somehow my tablular data is still not clearly filtering (following) the Proximity (map) view.
Basically the attached display does not filter or sort at all....it simply displays the records in proximity order according to *some unknown origin point*... I think this is the heart of the problem. Somehow the attached display is not understanding how to inherit the exposed filter of the Proximity View.
While I assume this is basically an arcane Views problem, it also seems specific to this module's capacity to pass an exposed filter setting to an attached view...and of course there is the possibility of my own misconfigurations.
Just hoping for a bit of guidance or reassurance here as this is the first time I've tried to attach a view to a proximity display.
Hi John,
Sounds to me like you have the correct setup.
Yes "inherit exposed filters" is essential and yes sometimes it drops the ball only to bounce back at a later point. I blame Views but have never been able to put my finger on it consistently.
Have you tried putting the IPGV&M "Set my location" block on the same page? And configuring the Geofield Exposed Filter to use it as the source of origin?
With "Set my location" on the page, the Geofield filter will automatically drop its address box, as the user can use the more sophisticated options of the "Set my location" block.
However the proximity selection (within 10, 20, 30k etc.) remains, if chosen to be exposed.
Don't think it will cause problems. Rather it solves it!
I don't have a View like that handy at the mo, but I believe that is how I've done it in the past.
Rik
Thanks for the help, Rik. As you suspected, Views automagically sorted out the problem of two exposed filters. Inheriting the filter values (and pager) was all it took for the linked displays to start working properly.
Very impressed wtih the power you have built in to the IPGeoLoc framework...a whole new level of "out of the box" goodness is inviting me to have even more fun!
Comments
Comment #1
RdeBoerDo I understand correctly that you want to see a TABLE under your MAP ?
You do this by clicking at the top of the Views UI the Display button Add-> Attachment.
Then on the Attachment thus created, set the Format to Table.
In the middle, under "Attachment settings", select Attach to: Page and Attachment position: After.
That's pretty much it.
Remember that you can Exclude columns from View, both in your map and in your table. These don't have to be the same selection, just make sure you click "This attachment (override)", at the very top of the Field configuration panel. Otherwise your field settings will apply to both the map and the table.
Hope this helps.
Rik
Comment #2
satrece CreditAttribution: satrece commentedHi RdeBoer,
Yes, your understanding is correct and solution also perfect.
Thanks for the help
Comment #3
RdeBoerGreat. Good luck with it all!
Comment #4
boabjohn CreditAttribution: boabjohn commentedG'Day Rik,
This issue was closed, yet it matches my problem well: I'm hoping for a bit more guidance.
The solution outlined above (create a Views attachment and attach to Proximity veiw) sounds simple, but I think there are some more variables involved. Here's how I see the relationship:
Proximity View
- FIELDS: Contains any fields, one of which MUST be the (geofield) - proximity
- FILTERS: Contains any filters, one of which MUST be the (geofield) - proximity, set as exposed, and taking input from a range of sources (including the Geocoder)
- SORT: First sort term MUST be the (geofield) - proximity, sorting on ASC (if you want to display closest results first)
That's it for the Proximity View, and in my case this works fine. I allow users to enter a search term, Google geocodes it, and I get a map display with proximate nodes. Using a pager, I can see the matching result set move out from the refernece point as I page through the results. All good.
Now, let's add a tabluar display below the map. As normal, we go to Views and choose to create a new display, of type=Attachment.
The first item under SETTINGS where we attach the new display to the Proximity View above.
Working down the other options, I think these must be properly set as well:
Attachment position: After
Inherit contextual filters: Yes
Inherit exposed filters: Yes
The last one I think is critical (?) as otherwise the attached tabular view will not know to follow the User's exposed filter input from the Proximity View display.
So: I have done all this, and yet somehow my tablular data is still not clearly filtering (following) the Proximity (map) view.
Basically the attached display does not filter or sort at all....it simply displays the records in proximity order according to *some unknown origin point*... I think this is the heart of the problem. Somehow the attached display is not understanding how to inherit the exposed filter of the Proximity View.
While I assume this is basically an arcane Views problem, it also seems specific to this module's capacity to pass an exposed filter setting to an attached view...and of course there is the possibility of my own misconfigurations.
Just hoping for a bit of guidance or reassurance here as this is the first time I've tried to attach a view to a proximity display.
Thanks indeed!
Comment #5
RdeBoerHi John,
Sounds to me like you have the correct setup.
Yes "inherit exposed filters" is essential and yes sometimes it drops the ball only to bounce back at a later point. I blame Views but have never been able to put my finger on it consistently.
Have you tried putting the IPGV&M "Set my location" block on the same page? And configuring the Geofield Exposed Filter to use it as the source of origin?
With "Set my location" on the page, the Geofield filter will automatically drop its address box, as the user can use the more sophisticated options of the "Set my location" block.
However the proximity selection (within 10, 20, 30k etc.) remains, if chosen to be exposed.
Is "all displays" set for filters and sorts?
Rik
Comment #6
boabjohn CreditAttribution: boabjohn commentedHey there Rik, thanks for the pointers...will give them a try in the morning.
Just a quick clarification: when you say:
Wouldn't that cause problems by assigning an exposed filter to both the (master) Proximity Display as well as the (slave) Attached display?
Comment #7
RdeBoerDon't think it will cause problems. Rather it solves it!
I don't have a View like that handy at the mo, but I believe that is how I've done it in the past.
Rik
Comment #8
boabjohn CreditAttribution: boabjohn commentedThanks for the help, Rik. As you suspected, Views automagically sorted out the problem of two exposed filters. Inheriting the filter values (and pager) was all it took for the linked displays to start working properly.
Very impressed wtih the power you have built in to the IPGeoLoc framework...a whole new level of "out of the box" goodness is inviting me to have even more fun!
Cheers.
Comment #9
RdeBoerThanks John,
Great to hear you've got it working
"...a whole new level of "out of the box" goodness is inviting me to have even more fun!"
Yep, especially when you enable Leaflet, Leaflet More Maps and Leaflet MarkerCluster.
Have you tried the new cross-highlighting as seen here: http://regionbound.com/coffee-prices-across-melbourne ?
This page is handy too, if you're not sure about all the map options: http://regionbound.com/Drupal-IPGVM-map-configuration
Rik