Duplicates locations by sync/update

I’m always surprised by invalid facebook locations ??
Did you read this (especially the fix I mention): https://www.ads-software.com/support/topic/now-all-locations-are-created-again-even-if-they-exist/

The reasoning is that EME is checking on name+location info and if the location info is invalid (or non-existing) it can pose a problem. But if you apply the mentioned fix, remove all your duplicate locations and sync again it should be ok.

Like just posted in another thread:

Wait a minute … I think I see something. There are 2 settings in FB-sync:
– Use coordinates for locations
– Use name for locations (which in fact uses name+address info)

The second one uses a function that comes from EME (not the FB sync plugin) called eme_get_identical_location_id. That function used to ignore coordinates (which was wrong) and got corrected in EME.
But in this case it should ignore these coordinates anyway, since that is what is desired … I need to create a new function etc …

Please try out the dev-version which you can download here:
https://www.ads-software.com/plugins/eme-sync-facebook-events/advanced/

If it works ok, I’ll release first thing tomorrow (after midnight here).

No feedback?

Sorry for my late response. Yesterday evening I tried your first advice https://plugins.trac.www.ads-software.com/changeset/1849858/

The effect was that an import of the events with the mentioned locations wasn′t possible. Each try causes a failure.

And right now I tried the dev version and it causes also a failure when I try to sync this event: https://www.facebook.com/events/1712134208880601/?event_time_id=1712134285547260. Heres the message:

Graph returned an error: Unsupported get request. Object with ID ‘1712134285547260’ does not exist, cannot be loaded due to missing permissions, or does not support this operation. Please read the Graph API documentation at https://developers.facebook.com/docs/graph-api

The url you use is not correct. Try just https://www.facebook.com/events/1712134208880601/ or just 1712134208880601 . The extra ‘?event_time_id=…’ is probably the cause.

To me it seems that the whole single-event-import is broken.

The automated cron-sync seems to work fine now.

But the single-import causes the mentioned failure.

I tried these events:
https://www.facebook.com/events/1795715117399035/
https://www.facebook.com/events/346366229204498/
https://www.facebook.com/events/180894259210027/

@andiemacht: Please don’t hijack a thread. This problem is unrelated to the subjec of this thread.

Also: while the examples you give indeed pose problems, other event ids work just fine. So I assume it is related to the permissions for these events.

Example of one that works (and all other events in my fb window work too):
https://www.facebook.com/events/182093175885521/