Matador Jobs maintenance release 3.3.5

Today, Matador Jobs was updated to provide our users with a few minor updates and minor bug fixes in lieu of a major release which is coming very soon. Lets dive in to see what this includes!

Unlike a hotfix release, this minor release, while addressing some bugs, does not fix any bugs we determined to be “major” or “breaking”. That said, if you’ve encountered these, you might like to know these are exterminated:

  • A bug that caused some users’ admin sites to timeout during a user-initiated job sync is now fixed. This bug was more of a source of confusion than something that broke a site, though rarely a large job sync could be restarted by a panicked admin and accidentally create two copies of a job.
  • Some issues with the Matador default CSS for Applications were addressed. Many users, when customizing their sites, just fixed these not thinking they were even a bug, but our goal is to have a seamless out-of-the-box experience, and these display errors were getting in the way of that.
  • Some of our Lite users encountered an issue with the “Apply” button not linking properly to their application page. This is now fixed.

In addition to those bug fixes, we added some useful new features:

  • You can now filter the job title and description before its saved to the database using the matador_import_job_title and matador_import_job_description filters. This is helpful especially for appending or prepending data, adding images, etc.
  • You can now tell Matador to use a custom Bullhorn field for the job title or job description using the matador_import_job_title_field and matador_import_job_description_field filters. If your company chooses to use a custom text field for a “marketing job title” and use the job order title in a descriptive way, then you can do now do that.
  • Allowed HTML tags for a job are now expanded. Specifically, <video> and <img> tags are now allowed for import. For reference, when Matador imports a job description, that HTML is validated for your sites’ protection. In the past, the validation and sanitization was a little more restrictive by not allowing some HTML tags that we now flagged as “safe”.
  • Finally, we updated a UI element in Matador settings. It now looks like a toggle switch as opposed to an on or off checkbox. We hope this helps our users more clearly understand the impact of certain settings choices.

As I mentioned, we are continuing work on our next major release, which should continue to improve our interactions with Google for Jobs and improve our shortcode output. This update, we anticipate, in the next 3-5 weeks.

Matador Jobs Pro users can update their sites by going to WP Admin > Plugins starting now. Matador Jobs Lite users may need to wait a day or so while we push our updates to

Matador Jobs hotfix release 3.3.4

Today, Matador Jobs was updated to address a few minor and two major issues discovered during our customers’ use of Matador Jobs and its extensions. This hotfix release addresses only those issues while we continue work on the next major release of Matador.

This past week, Matador users helped us discover two issues that we determined require another hotfix release of Matador. To ensure your Matador-powered sites continue to run as smoothly as possible, we recommend our users log into their site and use the WordPress plugins page to update their version of Matador. Here is what’s inside:

First up, we addressed a bug that we believe is actually one we traced back to Bullhorn itself. While we wait for Bullhorn to fix the bug, we modified how Matador handles it. This bug is caused when certain candidate’s resumes are formatted in a way that causes Bullhorn’s resume parser, which Matador uses, to return a bad candidate object. Matador will now fail more gracefully when it encounters that issue. A future version of Matador will email the recruiter when a candidate cannot be synced due to this issue or one like it.

Second, we found an issue around 3.3.0’s new Anti-Spam Honeypot feature. It was using a function name that was protected by an earlier version of PHP (or that PHP says, you can’t name your function that!), and our development tools didn’t point it out to us. If your specific setup was affected by this, we are sincerely sorry! We renamed the function something else, fixing the error.

We also included updates that addressed six other minor issues that we had completed updates on. There were also some updates to the filters around the applicant and recruiter confirmation emails. 

Matador Jobs hotfix release 3.3.3

Today, a minor release for the Matador Jobs Pro and Matador Jobs Lite was released to fix an issue discovered this week, plus one more fix present since 3.1.0. This is a fully backward-compatible release and is a recommended update for all users.

What’s Inside

Matador 3.3.0 released necessary changes and enhancements to functionality around the matador_taxonomy() function and [matador_taxonomy] shortcode. One such adjustment made it more likely a site would continue working if javascript was disabled by users, but in this change, when a site operator had set up their site just right, there was a bug that caused some site operators’ sites to return no jobs in search results when their users submitted searches that did indeed match jobs. This hotfix release returns behavior to normal for those sites and any in the future who set up their search in that way.

The other bugfix included 3.3.3 addresses an issue discovered following release 3.1.0 where the “Sync Now” button that shows on the jobs page in the admin section would not show up if there were no jobs in the database. This is of course counter-productive, as the point of that button is to get jobs added to Matador! The button now properly appears on the page at all times.

You can update to Matador Jobs Pro 3.3.3 from the WordPress plugins page or by clicking on “Account” in the main menu and downloading it from your user page. Users of Matador Jobs Lite can update from the WordPress plugins page after our update applies on

reCAPTCHA by Google hotfix 1.0.1

Today, a minor release for the Matador Jobs Pro reCAPTCHA by Google extension was released to fix an issue discovered following its release.

We determined that the reCAPTCHA form element would load even if reCAPTCHA was disabled either programmatically or manually by the site operator. When displayed in this state, the reCAPTCHA field would not be validated, so this wasn’t a bug that interrupted users from submitting applications.

Site operators with Matador Jobs Pro will be presented with an upgrade notice and those with a valid Matador Jobs All-Access license will be able to download the update automatically from your WordPress Admin Plugins page. You may also download the most recent update from the extensions page (requires a login to access downloads).

Matador Jobs 3.3.1 and reCAPTCHA by Google Extension

The Matador team is working hard, and just two weeks since our previous major release (which itself was only two weeks from its predecessor), we are proud to bring you the release of Matador Jobs 3.3.1 and announce the release of our newest All-Access Add-On: reCAPTCHA by Google.

I’m going to try to simplify our release announcements for our general audience and leave the more technical details for you to catch in the changelog from here out. These release posts will highlight important new features or bug fixes but try to keep more minor and especially developer-focused changes in the background. So, lets dive in!

Matador Jobs 3.3.1

3.3.1’s new features are centered around two key areas of Matador: the application and the shortcodes. One is a core feature of Matador, the other how you make Matador look right for your company and brand.

Around the Application, we first added an Anti-Spam technique referred to as a “honeypot”. This technique greatly reduces, but does not eliminate, spam while avoiding the use of CAPTCHAs that can be tough on users with poor sight. Second, to greatly reduce duplicate submissions, we added a behavior that disables duplicate submissions altogether while also adding a visual “processing” cue for the user to let them know what is going on.

Our [matador_taxonomy] shortcode and its shortcuts including [matador_categories], etc, now accept new parameters to modify the sorting of the taxonomy’s terms (aka categories) and an option to show taxonomies that have no jobs in them (we hide empty taxonomies by default). The [matador_search] taxonomy also got an optional reset button, which can be added to the search form by including ‘reset’ in the ‘fields’ parameter. 

3.3.1 includes 6 bugfixes including one that fixes the bug that cause all job application confirmations to be also sent to the site administrator email. 3.3.1 includes 1 UI and 1 Accessibility related changes, as well 11 ‘developer’ changes that update templates, filters, and actions to make it easier to customize Matador for your site.

Edit to original post: Following the release of 3.3.1, an issue was encountered when preparing our release of Matador Jobs Lite for’s Plugin Repository. Also, we identified one additional issue that shipped with the release. These two items were addressed and included in hotfix 3.3.2 less than 18 hours after the initial release of 3.3.1.

We are still hard at work at fixing our known issues we discussed in the 3.2.0 release, but unfortunately are unable to address those with this release. We have some solutions in the works, but as they represent major changes in behavior, we are being extra careful to not rush their release. We also received a bug report the day before this release that demonstrated conditions that may cause pagination to not work when using the shortcode instead of a Post Type Archive template. Our goal is fix all of these issues in the next few weeks.

All changes in this release are described in full detail in the changelog section of the Matador readme.txt. I will not be including full changelogs in release announcements moving forward.

reCAPTCHA by Google Extension

Form security is a big deal for many site operators. While I personally prefer a more friendly user experience without a form CAPTCHA, Paul feels they work too good and has them installed all over this site.

It is my hope that anti-spam measures in 3.3.1 will be perfect for many of our users, but sometimes that extra layer of security is preferred. So if the Anti-Spam behaviors added in 3.3.1 aren’t enough for you or if you want even more security, we are excited to announce the new Matador Jobs Pro Extension: reCAPTCHA by Google.

A Matador-powered application with reCAPTCHA

Its works pretty simply… right before the end of your form is a reCAPTCHA by Google box, and users are prompted to click “I’m not a robot”. Then some magic juice runs to make sure the user isn’t a robot, and a checkbox appears.

For more about this Extension and, if you’re an All-Access subscriber, download it for your site, visit the Extension’s page.

Matador Jobs release 3.2.1

A minor bugfix update to address an issue discovered resulting in Candidate records not saving custom application field data.

The Matador Jobs team discovered a minor, but nevertheless, troublesome bug that affected how non-standard application form data is handled. The issue was likely unintentionally introduced during work on application form handling for 3.1.0, specifically adjustments related to handling privacy policy acceptance, and we’re glad to restore Matador to its intended behavior.



  • Modified how “Notes” items are labeled when saved from an Application. Now should use the registered field’s label instead of a label generated from the form field key.


  • Fixed an issue discovered that caused “Messages” and custom fields to not be saved to the Bullhorn “Notes” for the candidate.

Matador Jobs release 3.2.0

Hot on the heels of release 3.1.0 not even two weeks ago, we are again updating Matador, and this time, again, its a “major” release. Lets dive into what this release includes!

We are trying hard to settle into a predictable release pattern for you. While we aren’t following it to the letter, we are trying our best to use Semantic Versioning for Matador core and extension releases. So when we added functions intended for public use, our minor release became a major one.

That said, don’t let the “major” release tag fool you, 3.2.0 is mostly a minor bugfix release that includes one qualifying change to make it seem bigger than it is. That is a set of new public functions around making it easier for developers who integrate Matador into your theme to access Job Listing taxonomy terms. For example, the categories or industries from the job, or the skills required.

In the bug fix realm, where most of our heavy lifting occurred, we fixed 14 bugs that were discovered since 3.1.0 and 2 that we had carry over from before 3.1.0, for a total of 16. The two biggest bugfixes were around a conflict caused when another plugin loaded the same vendor library as us and one around candidate and recruiter email notifications not sending out.

We also got to take a pass at some UI improvements, and you’ll see a few refinements in the Settings, including another occurrence of the Bullhorn bull to make it clear when Matador actions including reaching out to Bullhorn. We also added new help text and relabeled an option so that it made its consequence on your workflow more clear.

Full changelog is below, but before we go, I want to make clear that we are aware two more high-priority issues that we are actively working on as we speak:

First up, is for clients with many jobs (in excess of 250), we are finding that Matador may timeout when the user conducts a manual sync. This timeout is actually a 100% user interface issue, as the sync continues until it finishes, but its not a good experience for the user. It also cause a user to “try again”, which may result in two syncs running at the same time. This can cause jobs to be duplicated in Matador depending on when these two syncs are run. We have a solution, but its still in development.

Second up, is one around Structured data and Google for Jobs optimization. We recently learned that Google “doesn’t like” it when we delete a job that has been closed from your site. We know our optimization for Google for Jobs is a huge benefit to your sites, so the last thing we want is for Google to be unhappy about this. Their guidance recommends we leave an “artifact” in place so that job seekers finding your job board through Google for Jobs won’t encounter a 404. This artifact will provide dialogue that the position has been closed, and direct users to search for other jobs inside your site. We are working on an update to Matador that creates this behavior, and should release it side-by-side our solution for the first mentioned ongoing issue.

3.2.0 Changelog:


  • New Template Helper matador_get_job_terms for getting a array of terms from 1 or all Matador taxonomies.
  • New Template Helper matador_get_job_terms_list for getting a formatted string of terms from a job’s taxonomy in various formats. Uses a new template ‘job-terms-list.php’ and introduces 6 new actions (matador_job_terms_list_before, matador_job_terms_list_before_terms, matador_job_terms_list_before_each, matador_job_terms_list_after_each,matador_job_terms_list_after_terms, and matador_job_terms_list_after) plus one new filter (matador_job_terms_list_separator ) to support customization.
  • Added filter ‘matador_bullhorn_source_description’ to allow users to customize how Matador lists the “Source” of the job submission.
  • Added filter ‘matador_recruiter_email_subject_no_title’ to allow for adjusting of subject sent to recruiter if not linked to a job.
  • Improved the behavior of matador_is_current_term() to also return true when on a taxonomy archive page.
  • New Template file for Admin Notifications when Bullhorn Connection needs user intervention.


  • Fixed a major issue where certain candidate and recruiter notifications were not being sent when they should’ve.
  • Added code to prevent conflicts when a vendor library is loaded by another plugin or theme after Matador loads. This changes makes existing conflict prevention methods more robust and fool-proof.
  • Fixed bug where, when called directly, matador_the_job_field could throw an error if certain optional arguments were not passed.
  • Fixed a bug where, in the default jobs-taxonomies-lists.php template, a class for the term markup was being made with the title and not slug, creating invalid HTML and not useful classes.
  • Fixed a bug where, in Settings, a checkbox type settings wouldn’t save when all checkboxes are unchecked.
  • Fixed a bug where, when both a Candidate and Recruiter email were being sent, the Recruiter email listed the job applied for twice.

User Interface:

  • Added the Bullhorn Bull icon to the “Manual Sync” button in settings, providing a visual cue to users that this action communicates with Bullhorn.
  • Removed check marks next to checkboxes. Because that didn’t make any sense.
  • Revised wording around the “Classify Applicants” setting and added a long description explaining its impact on a Candidate and Job Submission, hoping to add further clarity to how the setting affects the workflow of various users’ firms.


  • Added a (hopefully temporary) advisory to the Authorize step of the Connection Assistant to warn users of a known issue when logging in for the first time. In the future, we hope to resolve this issue with our Bullhorn partners.
  • Moved templates for emails from /templates/ into /templates/emails. Renamed the templates. Some clients with customized email templates may want to double check if this impacted them, but given these templates were only available for all for less than two weeks, we feel safe making this adjustment now.
  • Refined error logging messages during certain Bullhorn login attempts.
  • Fixed spelling error on an Application Form Field
  • Fixed spelling/grammar errors & formatting in Readme

Matador Jobs 3.1.0 and more!

The Matador Jobs teams is excited to simultaneously announce a major update to Matador Jobs Pro, the official release of Matador Jobs Lite, and first release of eight new Matador Jos Pro Extensions… all at once!

Friday, June 8th was an exciting day for the Matador Jobs team! After weeks of tinkering, testing, and bug fixing, we both gave our thumbs up for the biggest release of Matador Jobs yet. And now I get to share it with you all! This release has 3 exciting parts: a major point release for Matador Jobs Pro to version 3.1.0, the official release of Matador Jobs Lite on, and the initial release of our first 8 Pro Extensions.

Matador Jobs Pro 3.1.0

Lets start with Matador Jobs Pro 3.1.0. We designed this release around improvements to these major areas of Matador: privacy settings/regulation compliance, greater flexibility with structured data creation/presentation, administrator user interface improvements, improvements to the connection tool, and more.

With the implementation of the GDPR in Europe and its implications for website operators worldwide, we studied and considered how Matador might be affected. Unfortunately, since Matador relies on two other software projects which we don’t have control over, we had to wait on both WordPress and Bullhorn to complete their GDPR updates as well. WordPress released their update (4.9.6) in the 2nd week of May and Bullhorn is releasing its updates as we speak and through the end of June. We are not done with our GDPR and overall user privacy and security, but we’ve released tools to aid in compliance. Notably:

  • Settings were added to allow Administrators to add consent fields to all forms.
  • Settings were added to force the erase of local candidate data once its been used to create a Bullhorn candidate; leaving an operator with only a single data source should they be asked to export/erase data.

Matador Jobs’ SEO tools, including and especially structured data, is one feature that sets it apart from others. In fact, our support for structured data–required for Google for Jobs, has resulted in incredible traffic increases for new Matador installs. A client last week installed Matador and set it up but didn’t switch their “Job Opportunities” link to Matador’s pages yet. They woke up the next day to 35 applications! Google scraped their site overnight and the results were unexpected… and awesome. We’ve added some settings to support common user needs related to structured jobs:

  • Ability to show/hide pay rate data from structured data.
  • Ability to set the “Hiring Organization” to either the company (in Bullhorn) or the agency.
  • Ability to turn off structured data; preferred option for internal job boards for companies.

When we made Matador, we envisioned a system where you could be completely hands-off with your website: let Matador handle updating your website for you. In our first six months, we found some of users like spending time in WordPress too. So we added some hopefully useful ways to make that experience better:

  • Adds a button to sync jobs from the Job Listings page.
  • Adds a button to link from the Matador Job listing to the Bullhorn Job page.
  • Adds a link to the Candidate created by Matador from the local application object (provided you don’t auto-delete with the new privacy setting).

Matador Job’s connection tool is part of what makes it so easy to set up. We made some updates to make it even easier.

  • Now will check that the ClientID is a valid ClientID with Bullhorn
  • Now checks the RedirectURI is valid on every page load of the related step and/or the connection doctor, adds a reload button to make it easier to force re-check when the check is invalid, which fixed a bug caused by changing a site’s URL (transferring from live to staging) related to that.
  • Now checks that WordPress “Pretty Permalinks” are enabled before allowing you to connect to Bullhorn; redirects are required.
  • Added a “Skip Assistant” wizard for advanced users to save time during install.

The following other new features to Matador don’t fit a category, but are still awesome:

  • Reworked how Settings actions are handled in a way that sped up Matador admin pages by 2x on average and 3x on save settings.
  • In what had to be the most requested feature since launch, we are excited to announce that email notifications can no be sent directly to recruiters who are designated as “Job Owners” and “Assigned Users”, based on settings.
  • The “Job Owner” and “Assigned User” names are now included, also, as part of the job’s data and available in fields for presentation in the theme if desired.

The full release notes, below, outline other bug fixes, smaller features, and more. Check them out below.

Please note: this update will not install automatically for users of Pro and All-Access like prior updates. The plugin folder name must change to prevent conflicts with our release of Matador Jobs Lite. Because we promised automatic upgrades, we will perform this manual upgrade for no cost if desired. All Pro and All-Access users will be contacted these next few days to coordinate the upgrade. 

Matador Jobs Lite 3.1.0

Many of you (so far) have found us through our work on the free plugin. When we released 3.0.0 in January, we know We delayed for nearly 6 months updating that plugin because we know some of the updates from the old version would break some of your website. It was a unwanted but necessary evil, and we felt only a very long sunset window would be acceptable. That sunset window ended on June 1. We sincerely apologize if your upgrade required some user intervention, but we hope you enjoy the new features and stability in Matador Jobs Lite that our Pro and All-Access users have been enjoying since January!

Following this announcement, Matador Jobs Pro and Matador Jobs Lite will be updated in parallel and will rarely be announced separately.

The First 8 All Access Extensions for Self-Download and Install

Jeremy and Paul worked for 3 years each building sites for Bullhorn users, and if we learned anything from those experiences, we learned that each Bullhorn user is unique. Matador Jobs was built this assumption: if we think 50% or more of our users will need a feature, build it. That said, up to 49% of our users could be left out of features they need if we stopped there. So in addition to building in useful core features, we will build many extensions.

These extensions will serve to expand or improve the experience. Some we will build based on popular demand, others based on partnerships with others in the industry, and some will be built if a user wishes to sponsor it. Without further ado, our first 8 All-Access Plugins:

  • Jobs’ Required Skills
  • Jobs’ Required Certifications
  • Jobs’ Required Specialties
  • Jobs’ Business Sectors/Industries
  • Leads and Referrals
  • Import Jobs By Company
  • Mailchimp Job Alert Emails
  • WordPress Job Manager Integration

See all of them here! In the coming months, we have three more coming soon. They will be:

  • Candidate Export/Erasure
  • Apply by LinkedIn
  • Advanced Applications

We love making Matador for you all. We can’t wait to keep making awesome new updates to support you now and in the future.

Matador Jobs minor release 3.0.5

Today, Matador Jobs received a minor version update to address issues around required form fields and connectivity with Bullhorn. Update your plugins to get the most up-to-date Matador experience.

We’ve been updating Matador at a quick pace, but other than fixing a minor issue here or there, we are going to slow down and begin work on our first major version update after this one. So we wanted to make sure that this (planned) last minor release of the 3.0 line was awesome. We spent a lot of time improving connectivity and the application form for this update, and we hope you find the updates useful!

Release Notes:

  • Feature: Ability to disable SSL verification for sites with self-signed SSL
  • Feature: Added filter to modify the “WHERE” clause in Bullhorn Job Queries
  • Enhancement: Better Errors and Logging around auto reconnect.
  • Enhancement: Better Logging Messages around Application Sync to Bullhorn.
  • Enhancement: a browser-side form validator was added for the Application Form. All fields set to “required” will be validated now.
  • Enhancement: On the application, file type form fields, when included in the shortcode or via the default form defined in the settings, will now be a required field by default. You can still make the field optional with the shortcode, a direct function call, or a filter.
  • Enhancement: Refactored the Jobs Output function into two parts to allow for alternate processing possibilities.
  • Bugfix/Feature: Matador now processes resumes into HTML (instead of text) to support new Bullhorn’s new NOVO User Interface candidate screens (that prefer HTML)
  • Bugfix: Fixed incorrectly named actions in default Matador taxonomies template.
  • Bugfix: Fixed an issue for users that upgraded from a 2.x.x version of Matador Jobs Lite caused by client corporation ID’s being set when they shouldn’t (Client Corporation settings were removed to an add on, mostly because it was rarely used and confusing. Contact us if you are legacy user that needs that feature).