Import Locations ignored because already exists

This topic contains 2 replies, has 3 voices, and was last updated by  Kiran 7 years, 8 months ago.

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
  • Author
    Posts
  • #388408

    ktz16
    Expired Member
    Post count: 13

    What is the key when importing locations?

    Here is my example. I am importing locations. I have 14 cities in the US with the name Anderson (each in a unique region). If I try to import the 14 locations, I get “already exists” messages on all 14 records. (see attached ImportLocations.png)

    When I execute the query: SELECT * FROM wp_geodir_post_locations WHERE city = ‘Anderson’

    I get 3 cities returned. (see attached QueryOfAnderson.png)

    What are the criteria for “already exists”? What is you recommended solution to this issue?

    #388411

    Guust
    Moderator
    Post count: 29970

    Normally there is no need to import any locations, see:
    https://wpgeodirectory.com/docs/manage-location/#edit

    Also, you should follow the Google Map API format where possible, see https://wpgeodirectory.com/docs/definitions/#location

    Just in case, I’ll get a developer to look at your question too.

    Thanks

    #388501

    Kiran
    Moderator
    Post count: 7069

    Hi There,

    For same city names, you should use different city slugs by adding region code in prefix or suffix like “al-anderson” Or “anderson-al”.

    Same city slug may update location info or skip the import for that row depends on the option selected from
    – Update item if item with location_id/city_slug already exists.
    – Ignore item if item with location_id/city_slug already exists.

    Let us know.

    Thanks,
    Kiran

Viewing 3 posts - 1 through 3 (of 3 total)

We have moved to a support ticketing system and our forums are now closed.

Open Support Ticket
20% Discount Offer
Hurry! Get your 20% discount before it expires. Get 20% Discount