Hi

My content types are set to have only 1 location instance, but it looks like a lot now have 2 location entries and so show up twice in the associated location views results. As there is only 1 instance allowed, there is no way of deleting the second location data set without a db edit:

select * from location_instance
join location on location.lid = location_instance.lid
where nid = the node id you are looking for

It looks like most entries are duplicates with the same co-ords [and so do not seem to show up twice on the views results?] but one has a valid uid and the other has a uid of 0. Some entries do not have the same co-ords though and these are the ones causing the problem in the views results.

I am not sure if this is a bug or an EBKAC.
Any ideas why there are multiple entries?
Or how to prevent it?

Thank you for your help
ice70

Comments

legolasbo’s picture

legolasbo
he/him
Primary language Dutch
Location Middelburg
commented
Issue summary: View changes
Status: Active » Closed (outdated)

Closing support tickets that have been inactive for over a year to clean up the issue queue. Please reopen if this is still an issue.

chx’s picture

chx commented
Category: Support request » Bug report
Status: Closed (outdated) » Active

I can still reproduce this. Every node update adds records into location with the same address but lat, long and source set to 0 causing search to produce (broken) duplicates. I can provide database dumps, Dockerfile or SSH access as necessary.