Active
Project:
Location
Version:
7.x-3.x-dev
Component:
Location_views
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Oct 2012 at 22:01 UTC
Updated:
1 Oct 2014 at 23:25 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
yang_yi_cn commentedI believe I got the same problem.
Say I have node, and another entity type called package, both use location CCK.
I even let them to use different cck field so the should not affect each other at all. However, the Views query generated has something like
so it's only joining based on vid instead of normally with entity API you need
entity_type = "node" AND enitity_id = :id AND revision_id = :ridOn my production I got a lot of nodes and a lot of packages, keep in mind that the entity tables grow their own IDs from 0, so eventually some ID range overlaps as my screenshot shows:
So when my view executes the query on a node, it could accidentally pick a totally unrelated package with the same vid and use that wrong location.
I think this is a critical issue.
Currently I have a workaround, which is to manually increase the other entity's auto increment value to a very large number to avoid the ID conflict in the location instance table.
However, the proposed solution will be to to change the location_instance schema to include entity_type, entity_id and revision_id instead of just nid and vid.
Comment #2
yang_yi_cn commentedComment #3
yang_yi_cn commentedmarked #1969526: Location fields- previously entered user data gets printed on Nodes. as a duplicate of this.
Comment #4
monsoon commentedAny work around or patch in sight?
Comment #5
jaymz commentedAgreed. This is significant problem when a site has locations on different entity types. The problem is very visible on SummerSailstice.com/events - where users are creating event 'nodes', and also registration 'entities' - both have location fields, and the locations are getting mixed up in views.
Let me know if I can help.
Comment #5.0
jaymz commentedmore info
Comment #6
trrroy commentedHere's a workaround I'm using for this with nodes: