Disable Geocoding trigger while importing

  • Resolved just4me67

    (@just4me67)


    2 years, 3 months ago

    Hi, I use AllImport Pro (latest version) and this jobmanager import addon for WP Job Manager. I really like the plugin but there is one thing I would like to change.

    We use an external Feed for importing jobs into WP. We want to import this file every 30 or 60 minutes. Every import is about 600 to 700 jobs imported.

    I use the _job_location field as a custom field because I have all data I need delivered by the feed. But I also need the Geocoding API for a radius location search.
    Now when I import all jobs, every job sends a request to geocoding API which I don’t need and don’t want! Because when importing 700 jobs per hour this sends (700jobs*24hours*30days) about 500000 requests per month to the Geocoding API. This will cost us a lot of money for google.
    Is there any chance to disable the geocoding requests while importing the jobs?

    I would really appreciate if someone has an idea for me.

    • This topic was modified 2 years, 3 months ago by just4me67.
Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Author WP All Import

    (@wpallimport)

    Hi @just4me67,

    Is there any chance to disable the geocoding requests while importing the jobs?

    You can remove your Google Geocoding API key from the import template to stop our add-on from making Geocoding requests to your account.

    Thread Starter just4me67

    (@just4me67)

    Hi, thank you for your answer.
    But this is not working because in your code (/classes/class-importer-jobs-location.php) you use the API Key which is inserted in WP Job Manager settings. Message “Obtaining Google Maps API key from the WP Job Manager settings”…
    And the API in the WP Job Manager Settings I need for a radius search function so I can’t leave this field empty.
    For now I disabled the cURL call by commenting some lines in your plugin code.
    It is not update safe in that way but it works.

    Plugin Author WP All Import

    (@wpallimport)

    Hey @just4me67,

    Sorry, you’re absolutely right, and I’m not sure why it didn’t do that in my tests (unless I just missed it). In any case, I’ve added an internal task to add an option or a filter to disable geocoding requests, and/or disable fetching the key from WP Job Manager, in a future release.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Disable Geocoding trigger while importing’ is closed to new replies.