fyaconiello

I am planning on making a community (free) Bullhorn Plugin. Which I will have available for download on github and the wordpress plugins site. However, I haven’t started development on the project yet. If you want it soon (rather than eventually) we can talk pay/donations to accelerate the process.

https://github.com/fyaconiello/wp-bullhorn is where i’ll be developing.

huh, well you may have a very hard time setting this up if you don’t know about crons. Do you have a developer you are working with or is it just you?

Well that is pretty easy. What are you using for hosting? Can you create cron jobs? Unfortunately, Bullhorn’s API is slow, and will cause the wp schedule event requests to time out. So we’ll have to create a cron script that can be executed for syncing purposes.

Also, Bullhorn doesn’t have a feed, you will have to pull the list of jobs using SOAP requests.

What Bullhorn features are you looking to use in your site? Also, the plugin I developed was done for another company, and is owned by that company. So I won’t be posting that code. I am looking to create a community version of it though. It may be slow going however, b/c I won’t be reusing anything.

Are you still looking to do this? The company I work for just developed a plugin that creates 2 custom post types: job-order, and corporate-user as well as a custom taxonomy: bullhorn-categories. Job-order and corporate-user are connected via scribu’s Post2Post plugin. There is a cron script that pulls/creates/updates all job-orders + bullhorn-categories from the Bullhorn API that are set to isOpen=1, and all of the corporate-users that are attached to those open job-orders.

The other part of the plugin is hook implementations for the Gravity Forms plugin. There is a form created for people to apply to jobs. When people apply for the job a candidate entry is sent to Bullhorn via the Bullhorn API (with a resume file upload). Also, all of the corporate-users that are attached to the applied for job get a copy of the gravity forms email.

That is essentially the features and workflow that I created.

@ashley
it appears your plugins main file bp-restrict-profile.php has what i’m assuming is debugging code on line 77. I HOPE that those aren’t active credentials for your database. You may want to remove them regardless. also in the future use the WP DB constants DB_NAME,DB_USER, DB_PASSWORD, DB_HOST.

Well, I’ve worked out most of the errors present in the API through Webgistix customer support. They were pretty quick about making fixes once I pointed out their errors.

They said they would review my suggestions to make their API better. But I’m not really holding my breath.

If anyone is interested, email support[at]webgistix[dot]com. Suggest they:
1. Prefix their responses with xml declarations.
2. Use a standard credential for all four api requests. They currently have:
2a. Shipping API: CustomerID, Password
2b. Tracking API: Customer, Password, Username
2c. ItemCreation API: Customer, Password
2d: Inventory API: CustomerID, Password

Some of the Passwords aren’t the same throughout. There is no where to get a Username for the Tracking API aside from contacting support.

@bschoenbaechler:

I would love to write integration into ANY other shipping fulfillment system, but my client already has a history with Webgistix. They are dead set on using both that and wp-ecommerce. They are moving away from their Magento install.

@everyone else:

I’m finding out Webgistix’ API is a load of bollocks. They have simple (and terrible) errors in their xml.

example 1:
<?xml version=”1.0″?>

The line above is missing before all of their responses. Most, if not all, of PHP’s XML parsers require that line to be there or throw a parse error.

example 2:
<ItemCreationReport>
<ItemCreationError>
<ItemID>MPL-MPC-KVS-04-HLSP-PACK01-000-SPET01-V</ItemID>
<Success>false</Success>
</ItemInsertionError>
</ItemCreationReport>

On line 2 they open an ItemCreationError tag, and on line 5 close a ItemInsertionError.

That is some bad juju.