Support » Plugin: Matador Jobs Lite » Multiple Job Postings

  • Resolved jfaul4820

    (@jfaul4820)


    Jobs are being posted multiple times on the website yet only show one time in bullhorn.

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Author Paul Bearne

    (@pbearne)

    Hi,

    This can be due to a couple of things:

    Is it just new jobs at a duplicated?
    Do you see jobs set as a draft in WP?
    if so check that you timezone match on Bullhorn and WP

    We have fixed this in the next version

    Or the listing got messed on sync

    In both cases. It is safe to delete ALL jobs in WordPress and do a manual sync to get a clean set of jobs

    The next version is now available as a beta version to are Pro(paid) customers and we will release to the lite once it has been tested

    The pro version has better support for Google Jobs and access to the add-ons etc.

    I hope this helps

    Paul
    paul@matadorjobs.com

    Plugin Author Jeremy Scott

    (@jeremyescott)

    Since there has been no follow-up to this, I’m going to mark this as resolved, but first I’m going to add this:

    We discovered an issue in Matador Jobs (Pro and Lite) 3.4.x where a failure (due to bad configurations for Google Indexing API) may interrupt the saving of the job post metadata, which as of 3.4.0 included a datapoint that was used to identify when an imported job was already in the system (and thus should result in a revision/update) or wasn’t in the system (and thus should result in a new job being saved).

    While we cannot fix the cause of the issue, which is a misconfiguration in the Google Indexing API credentials, we did create two fixes for Matador coming in the 3.5.0 release next week, they are:

    – Save the “duplicate check” data point immediately on job save and before from the normal meta flow, which should prevent a failure in that process from preventing the duplicate check data point from being saved.
    – Handle failures with Google Indexing API calls more gracefully, so they do not interrupt otherwise successful routines.

    In a future release, likely our 3.5.1 release, we will also include a better notice for site operators whose Google Indexing API credentials are not working.

    That said, it is possible Paul’s answer helped out already. I’m marking this as resolved.

Viewing 2 replies - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.