Sites not syncing with Bullhorn

  • Resolved synergeticweb

    (@synergeticweb)


    3 years, 7 months ago

    I am having some difficulties with the job listings sync. We recently launched a new site that uses the Matador Jobs Lite plugin. My goal is to convert to a paid pro account, but it’s hard for me to convince the owner to do that until the basic functionality works.

    When I initially set up the plugin, everything seemed like it was working correctly. After we launched, I realized it wasn’t. To verify, we logged into Bullhorn and deleted a job listing and we added a new one.

    On the live site, nothing happened. Neither change was reflected on the site.

    On the old development site, the job we removed from Bullhorn was removed from the site. But the job that we added was never imported. I also noticed there were about 10 other jobs that also never imported. I would guess that the jobs hadn’t updated since the initial import when I installed the plugin.

    Both sites are connected successfully to Bullhorn according to the settings > General > Bullhorn API Connection. On the live site I was also getting WP cron warnings. The live site is hosted with GoDaddy Managed WordPress hosting. After searching these forums, I added define( 'WP_ALTERNATE_CRON', true ); to the wp-config file on the live site. I don’t receive a cron warning anymore, but I am seeing an error of “Matador Jobs Cron Check: Unexpected HTTP response code: 429”.

    I logged into Bullhorn and reviewed the jobs to make sure the new one was published, open, etc. Everything looks fine on that end.

    What should I do next? Thanks!

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Author Jeremy Scott

    (@jeremyescott)

    Hi @synergeticweb!

    Thanks for your questions.

    Regarding the “disconnected live site”: whenever you migrate a site, you should go into the Bullhorn Connection Assistant, copy/save your credentials, and then “Reset Assistant”. The Assistant will run a number of checks, and may find an issue. Typically, the URL of the live site is not registered as an allowed callback URL in Bullhorn, and if that is the case, Matador will make a copy-and-paste email you can send to Bullhorn to get it added.

    Regarding GoDaddy and Alternate Cron… this is tough. The bottom line is that every user of ours on GoDaddy Managed WP never can get it to work. I’m based in Phoenix (GoDaddy’s HQ city) and am friends with GoDaddy management, and after discussing the issues in depth with them, they came to the conclusion that GoDaddy Managed WP isn’t built to support some of the more complex WP Plugins that rely heavily on WP Cron especially. Unlike Pagely, WPEngine, Nexus, and others, GoDaddy Managed WP is Managed WP for the “prosumer” not the “professional.” Our WebHost known issues page section on GoDaddy says this:

    the consensus at this time is that the GoDaddy Managed WordPress Product is not designed for Matador Jobs user’s and we strongly recommend other providers

    So, I hope this was helpful! At the very least, you should be able to get the live site connected by rerunning Connection Assistant, but you will have issues with GoDaddy Managed WP as long as the client is tied to it. (And this goes for any features that rely heavily on Cron, including Matador Lite/Pro, WooCommerce, and others too).

    Jeremy

    • This reply was modified 3 years, 7 months ago by Jeremy Scott.
    Thread Starter synergeticweb

    (@synergeticweb)

    Hi Jeremy, thanks for the reply.

    I understand regarding GoDaddy. I tried to use the suggestion to define alternate cron in the wp config file, but that didn’t work. I will get the live site transferred over to a GoDaddy regular hosting account soon.

    However, I’m still having problems on the dev site. I did what you suggested and reset the assistant. It verified the api callback url was registered. But, it still is not fetching all of the jobs.

    Any other ideas?

    Plugin Author Jeremy Scott

    (@jeremyescott)

    However, I’m still having problems on the dev site. I did what you suggested and reset the assistant. It verified the api callback url was registered. But, it still is not fetching all of the jobs.

    In the settings, go to the Job Listings tab and find the setting “Published Status to Import”. By default, Matador pulls in jobs that are: not archived, not deleted, and where status is not equal to archived. If this setting is set to “All Jobs – Careful!” then I doubt that you’ll miss even one job.

    That said, best practice is to choose “Published – Approved” or “Published – Submitted.” In Bullhorn, there is a way to formally “publish” a job, and if your user has not published the job, if you are using either of the “Published” options here, Matador will not import the job.

    I highly suspect a combination of failure to publish and/or your Published Status to Import setting is causing some jobs to be not published, but like I said, best practice is to publish the jobs at Bullhorn and only import Published Jobs into Matador using a “Published” setting.

    Thread Starter synergeticweb

    (@synergeticweb)

    OK – The setting you described above is set to “Published – Approved”.

    I reviewed the jobs in Bullhorn and they appear to be published correctly. You can view a screenshot of one that isn’t importing at https://paste.pics/CCJSY

    What should I be checking next?

    Plugin Author Paul Bearne

    (@pbearne)

    @synergeticweb Have look at this doc https://matadorjobs.com/support/documentation/published-status-to-import/ as it lays out the process

    To use the Approved setting it needs to setup in Bullhorn try importing Submitted

    You can always do a import all as a test

    Paul

    Plugin Author Jeremy Scott

    (@jeremyescott)

    Hello,

    Now that you are importing Published Submitted or Approved jobs, you further need to ensure that those jobs are Published in Bullhorn. In Bullhorn in the job that is not syncing for you:

    • Edit the job.
    • In the top right, go to Actions Menu
    • From the Actions menu, select Publish (at bottom)
    • Follow steps to publish.

    If the company has a two-step publishing processing (Submitted, Approved) then ask an Administrator to approve the publishing and/or switch Matador to download “Published — Submitted” jobs.

    The whole process is laid out here, though, for some reason, the some of the screenshot images aren’t loading right. We are updating our documentation right now to a new platform so perhaps that has something to do with it.

    • This reply was modified 3 years, 7 months ago by Jeremy Scott.
Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Sites not syncing with Bullhorn’ is closed to new replies.