GMap in views attachment ignores views pager
| Project: | GMap Module |
| Version: | 6.x-1.1-rc1 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Here's my setup.. a standard view returns nodes marked with location, and an attached view outputs a gmap above that maps these nodes. This works perfectly!
...except for when you have more nodes than your views pager limit.
Every page after the first maps only the nodes from the first page. These are the correct nodes, AND the correct page limited number of nodes... but they don't match the list returned from the main view.
Maybe gmap has no proper support for being attached to a paging view? I can understand why that may not be popular/obvious, even though it's properly being handed the information for arguments, filters and the like.
My current uber-hack to get around this is to hijack the $view->result in the main view template, load each node individually and feed the lat/long into a marker variable to then get themed as a gmap, completely bypassing the entire gmap attachment.
Yeah.. I know.. it's gross.
If anyone knows a better way, I'm all for it--
#1
Same issue here... Go to page two and the nodes on the map are still page ones nodes.
#2
Subscribing
#3
Any progress on this? Fixed yet?
#4
I'll be testing this soon on the new version of views on a new site to see if it is fixed.. though new versions of views have been nibbling away at bits of my older views lately and causing me lots of headaches... I'll be sure and post here whether it works or not as soon as I try.
#5
subscribing
#6
subscribing
#7
subscribing....would love solution to this
am also using exposed filter in a couple of views, and have same problem with map not reloading when filter used