Posted on

Matador Jobs 3.9.13

On Tuesday, February 10, 2026 we released Matador Jobs 3.9.13 to all our users. This hotfix release contains minor enhancements and bug fixes that support further stability of our software and user experience while we finish work on Matador Jobs 4.0.0.

Release Notes

  • Enhancement: (Bullhorn) Added filter matador_bullhorn_client_corporation_create_body to modify the body of the Client Corporation create request call.
  • Bugfix: (Core) Fixed an issue with backward-compatibility handling for legacy uses of the matador_variable_job_taxonomies filter.
  • Bugfix: (Admin) Fixed an issue recently created causing the remote source ID to not display in the WordPress admin list screen for the Matador job listings post type.
  • Bugfix: (Editor) Fixed an issue causing Matador’s WordPress Block Editor blocks to fail to fetch taxonomy terms.
  • Bugfix: (Bullhorn) Fixed an issue causing the Bullhorn category sync to fail when a job is assigned to more than five categories.

Update Now!

Matador Jobs 3.9.13 is released for automatic* update to all subscribers as of Tuesday, February 10, 2026. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

* Please Note: some versions contained bugs that required users install manual updates. See here if you are having trouble receiving an automatic update.

Posted on

Announcement: Deprecation of Matador Jobs Pro – Teams Notifications Extension

With the release of Matador Jobs Pro – Teams Notifications 1.0.2, we are announcing that this extension will be deprecated as of March 31, 2026. We want to provide you with further context about why this decision was made.

Why Is This Happening?

Microsoft recently announced the deprecation of the system that the Teams Notifications extension relies on to send messages (webhooks). You can read more about this change here: Retirement of Office 365 Connectors within Microsoft Teams.

After careful consideration, we determined that the new system Microsoft is implementing would be too complex for most users to implement and manage. Additionally, supporting this system would introduce a level of complexity we believe would detract from our ability to deliver the best possible experience across all our extensions.

What Does This Mean for Users?

  • Webhooks will stop functioning on March 31, 2025, and as a result, the Teams Notifications extension will no longer work correctly beyond this date.
  • For users seeking similar functionality, we recommend our Slack Notifications and Discord Notifications extensions, which provide seamless integration with their respective platforms. You can learn more here:

We understand this may be an inconvenience for Teams users and appreciate your understanding. If you have any questions or concerns about this change, please don’t hesitate to reach out to us.

Thank you for continuing to trust Matador Jobs to power your recruitment workflows!

Posted on

Matador Jobs 3.9.12; Tested to WordPress 6.9

On Tuesday, December 2, 2025 we released Matador Jobs 3.9.12 to all our users. This hotfix release contains minor enhancements and bug fixes that support further stability of our software and user experience while we finish work on Matador Jobs 4.0.0.

This release coincides with WordPress 6.9’s release, which releases today, and is fully supported by this version of Matador Jobs.

Release Notes

  • Modified the 3.9.0 application screening feature to give developers ways to create custom actions.
    • Add a custom button to the application screening using the matador_application_screen_control_options filter (3.9.0).
    • Add the custom application screening actions first with the matador_application_screen_allowed_actions filter.
    • Program the action and hook it with either matador_application_screen_custom_action or matador_application_screen_{$action}_action actions.
    • See our docs site (https://docs.matadorjobs.com/articles/custom-screening-actions/) for a complete example.
  • Bugfix: Fixed an error in our All-In-One SEO Third-Party Plugin support where if job sync fails in progress, JSON+LD metadata is not saved properly.
  • Bugfix: Fixed the wording on the setting determining if multiple job submissions by the same candidate should be permitted or not. Now the setting name and description accurately reflect the behavior of the setting (when off, multiple submissions by the same candidate will result in multiple job submissions).
  • Internationalization: Updated translations files.
  • Misc: Tested up to WordPress 6.9, which releases today, on 2025-12-02.

Update Now!

Matador Jobs 3.9.12 is released for automatic* update to all subscribers as of Tuesday, December 2, 2025. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

* Please Note: some versions contained bugs that required users install manual updates. See here if you are having trouble receiving an automatic update.

Posted on

Check Your Matador Jobs Site After Today’s Bullhorn Downtime

Earlier today Bullhorn ATS experienced a system-wide outage and users of Matador Jobs should double check their websites are operating properly.

On November 17, 2025 between approximately 10am and 11:30am EST, the the Bullhorn Status page reported downtime for the Bullhorn ATS, which impacted users of Matador Jobs. When a Matador Jobs kicks off a sync automation, it will attempt to refresh its Authentication Token by submitting a Refresh Token and the expired Authentication Token. During a downtime like we experienced today, the one-time use Refresh Token can be “consumed” while the new Authentication Token is not received due to the downtime. The result is a disconnection from Bullhorn.

Have no fear! In most cases, Matador Jobs Pro’s automatic reconnect routine steps in during these rare occurrences and will save the day. Sometimes, however, something may not work. Usually, this happens when user-provided Bullhorn REST API credentials are invalid, often due to a password expiration.

Today, we have already assisted a users in reconnecting their sites after the downtime ended. In those cases, both were not automatically reconnecting due to an expired REST API User password.

If you need help getting your site reconnected to Bullhorn, please visit our guide to Reconnecting/Reauthorizing Matador Jobs with Bullhorn.

Posted on

Matador Jobs 3.9.11

On Tuesday, July 22, 2025 we released Matador Jobs 3.9.11 to all our users. This hotfix release contains minor enhancements and bug fixes that support further stability of our software and user experience while we finish work on Matador Jobs 4.0.0.

Release Notes

  • Enhancement: A RankMath SEO feature which redirects a user to a custom “not found” page when a resource is not found is now disabled for Matador Jobs job postings due to the dynamic nature of the content Matador Jobs manages and a need for a removed job to actually serve an HTTP 404 error.
  • Enhancement: Added the matador_bullhorn_submit_candidate_to_job_body filter to enable customization of the fields set on the Job Submission during application sync.
  • Bugfix: Added a code protection for a rare issue caused by changes to the server configuration of the uploads directory after creation. This could also be triggered by improper migrations.
  • Bugfix: Fixed a bug in the jobs-listing-job.php and job-aside.php templates which caused some job parts not to rendered when an empty string is passed as a label.

Update Now!

Matador Jobs 3.9.11 is released for automatic* update to all subscribers as of Tuesday, July 22, 2025. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

* Please Note: some versions contained bugs that required users install manual updates. See here if you are having trouble receiving an automatic update.

Posted on

Matador Jobs 3.9.10

On Thursday, June 10, 2025 we released Matador Jobs 3.9.10 to all our users. This hotfix contains enhancements and bug fixes that support further stability of our software and user experience while we finish work on Matador Jobs 4.0.0.

Release Notes

  • Enhancement (Bullhorn Integration): Recent changes to the Bullhorn API made it so that the smsOptIn field can now only be set on Candidate record create. A change is implemented in this version of Matador Jobs to adhere to this change with the Bullhorn API.
  • Bugfix: Fixed a bug caused by a possible WordPress Core bug that caused code that loads a Matador Settings page to break WP Admin when the user directly accesses the wp-admin/users or wp-admin/network folders. Normal WordPress admin use would not encounter this.
  • Bugfix: Code designed to suppress deleted post warnings by the Yoast SEO Premium plugin was not working as intended. Yoast SEO Premium, as a practice, notifies site operators when a page is removed that they should create a HTTP 301 REDIRECTION record. This would be incorrect if done on Job Listings posts, as most search engines and aggregators want job postings to be served with HTTP 410 GONE or HTTP 404 NOT FOUND when they are removed.
  • Misc: Updated formatting on CHANGELOG.md to fix a Markdown parsing error causing the change log to be difficult to read prior to 3.9.0.

Update Now!

Matador Jobs 3.9.10 is released for automatic* update to all subscribers as of Thursday, June 10, 2025. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

* Please Note: some versions contained bugs that required users install manual updates. See here if you are having trouble receiving an automatic update.

Posted on

Matador Jobs 3.9.9

On Tuesday, May 6, 2025 we released Matador Jobs 3.9.9 to all our users. This hotfix contains minor bug fixes that support further stability of our software and user experience.

Release Notes

  • Bugfix: Fixed bug that caused a delay in an application being synced when there was only one pending application.
  • Bugfix: Fixed a critical (site breaking) error that was encountered only when Admin Emails were turned off and a site disconnection occurred.
  • Bugfix: (Bullhorn Integration) Added error suppression to the method we use to compress processed resume HTML data to prevent issues caused by malformed HTML. This is further supporting changes introduced in 3.9.6 and 3.9.7.

Update Now!

Matador Jobs 3.9.9 is released for automatic* update to all subscribers as of Tuesday, May 6, 2025. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

* Please Note: some versions contained bugs that required users install manual updates. See here if you are having trouble recieving an automatic update.

Posted on

Extension Updates May 2, 2025

Over the weeks ending May 2, 2025 and April 25, 2025, the Matador Jobs Pro team released two updates to Matador Jobs Pro extensions with enhancements, bugfixes, and more.

Job Syndication Feeds 2.2.5

Our extension which generates up to 20 XML-formatted job feeds so external aggregators can consume and distribute your job data was updated on May 2, 2025, with the following changes:

  • Bugfix: Updated the Match2 feed to resolve XML structure bugs.
  • Bugfix: Fixed issue where the plugin is trying to load styles for the admin settings, but a stylesheet for the admin settings is not included in the plugin.
  • Misc: Tested up to WordPress 6.8

(Bullhorn) Job Object Customizer

Our extension which gives users a graphical user interface to customize the downloaded job object for users of the Bullhorn integration users was updated on April 22, 2025, with the following changes:

  • Enhancement: Updated plugin to support Matador Jobs 3.9.7 taxonomy registration methods.
  • Bugfix: Changed to WordPress 6.7 & 6.8 Just In Time Translations changes.
  • Misc: Requires Matador Jobs Pro 3.9.7
  • Misc: Tested up to WordPress 6.8

Update Now

These updated extensions are released for automatic* update to all Matador Jobs Pro – All Access subscribers. Download updates from your WordPress Admin Plugins management screen or them from MatadorJobs.com. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

Posted on

Matador Jobs 3.9.8

On Tuesday, April 29, 2025 we released Matador Jobs 3.9.8 to all our users. This hotfix release contains another update to support smooth, responsive translations for international users.

Release Notes

  • Enhancement: Added “Domain Path” plugin header to improve translations loading given recent updates to WordPress 6.7 and 6.8 and how those versions handle translations files.

Update Now!

Matador Jobs 3.9.8 is released for automatic* update to all subscribers as of Tuesday, April 29, 2025. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

* Please Note: some versions contained bugs that required users install manual updates. See here if you are having trouble recieving an automatic update.

Posted on

Matador Jobs 3.9.7

On Tuesday, April 22, 2025 we released Matador Jobs 3.9.7 to all our users. This hotfix release contains some important updates for all users to ensure a smooth upgrade to WordPress 6.8 and to users that integrate with the Bullhorn ATS to ensure applications sync to their ATS.

Support for WordPress 6.7 & 6.8 Just In Time Translations

A key aspect of this hotfix release is fixing Internationalization/Translations (i18n) issues introduced by changes to WordPress 6.8.

WordPress 6.7 began to roll out “just in time” translations to improve performance for all users of the platform. Matador Jobs, largely, did things right when it came to i18n but there were a few places where we tried to translated strings too early. Older WordPress was made to compensate for our flaws, but newer WordPress wanted us to do it right and gave us PHP Notices (a type of error). When a user had WP_DEBUG on in any way, this notice would have the effect of breaking translations loading. With WordPress 6.7, we fixed several issues, the recently release of WordPress 6.8 finalized the move to “just in time” i18n and exposed more small issues.

One of the most difficult of these issues was fixing a translations issue around how we created taxonomies (ie: categories and job types) for your jobs. We created data objects early in Matador’s load order to later use to create taxonomies but this was too early for WordPress 6.8. The fix itself was simple, but it needed to be backward compatible! We have four extensions that added taxonomies using the old method too, but more importantly, we have a lot of users who customized their sites with special additional taxonomies, and making sure old code continues to work with our updates was critically important.

Our developer invested 12 hours to ensure smooth functionality with WordPress 6.8 and later as well as full backward compatibility for our users. We are excited to get it out to all our users, especially those who see the bugs it fixed impacting their 18n for their site.

This release coincides with some updates to Matador Jobs All Access extensions with fixes for the same issue. We are investigating and testing all our extensions to ensure we completely close the book on this pesky WordPress update’s impact on our users.

Release Notes

  • Bugfix: To update Matador Jobs for WordPress 6.7 & 6.8 just-in-time translations features, some translatable strings declared at Matador instantiation were moved elsewhere in load order. This fixes an issue where, when WP_DEBUG was on, PHP NOTICE messages would cause Translations files to not load.
  • Bugfix: (Bullhorn Integration) Some processed Bullhorn resumes were too large to be processed by the solution we devised to in 3.9.6 to make resumes smaller, so a different solution that is more reliable is included in this version.
  • Bugfix: (Bullhorn Integration) Fixed issue causing the import categories cache to not save as expected.
  • Bugfix: (Bullhorn Integration) Modified the process in which the Bullhorn Country data cache is refreshed, preventing a stale cache from returning invalid/missing Country data and impacting user applications. The cache is now persistent and a separate mechanism is in place to refresh it regularly.
  • Enhancement: Added WordPress filter matador_application_field_should_skip on the default Application form template to give developers using the default template access to a way to programmatically skip application fields. Users on modified application templates should refresh their template version.
  • Enhancement: (Bullhorn Integration) In the event of missing Bullhorn Country data, the Country field in the application will now be disabled, and authenticated editor and administrator users will be shown a message encouraging them to initialize a Bullhorn sync. This will only occur, due to changes to how the Bullhorn Country data is cached, when new sites are created or object caches or transients are cleared. This requires users to be using the default application template or that they have added the new matador_application_field_should_skip filter to their customized template.

Update Now!

Matador Jobs 3.9.7 is released for automatic* update to all subscribers as of Tuesday, April 22, 2025. If your subscription has expired, renew it on your account page. If you find any issues, please send a support request.

* Please Note: some versions contained bugs that required users install manual updates. See here if you are having trouble recieving an automatic update.