Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.we are using vid to connect a node (revision) to location-data
but this module thinks we are doing this by nid!
critical because location_views useles because of this!
quick and easy patch...
| Comment | File | Size | Author |
|---|---|---|---|
| vid_instead_nid.patch.txt | 639 bytes | Tobias Maier |
Comments
Comment #1
karens commentedI just want to think this through since none of the other views examples have been using vid. You're probably right, but I'll get back to you on this.
I've set up a separate project for the location_views module to make it easier to track bugs and feature requests. Moving this issue to that page.
Comment #2
karens commentedForgot to move the issue...
Comment #3
karens commentedI went ahead and put this change in the latest cvs. It seems logical, I just can't figure out why other views modules aren't doing it. I'm not really using revisions, so I welcome feedback on whether or not it's working right.
Comment #4
karens commentedForgot to change status, reopen if there are problems.
Comment #5
Tobias Maier commentedvid == version id
location uses vid because someone may change the nodes' location between the revisions
this means the location is linked to a specific vid of a node-nid
your filter looks which vid fits to the current vids in the node table
vid and nid are the primary keys in the node-table
both are unique
i hoped this helped to understand the issue
Comment #6
karens commentedI understand what the vid is and how it works, and like I said, it makes sense to use it. I was just wondering why other examples did not use it and whether that was a signal that there is some reason not to. Anyway, it's in there now, so if everything seems to work right, then it was the right way to do it :-)
Comment #7
(not verified) commented