Title: Matador Jobs Lite
Author: Paul Bearne
Published: July 6, 2018
Last modified: December 2, 2025
---
Search plugins
This plugin **hasn’t been tested with the latest 3 major releases of WordPress**.
It may no longer be maintained or supported and may have compatibility issues when
used with more recent versions of WordPress.
# Matador Jobs Lite
By [Paul Bearne](https://profiles.wordpress.org/pbearne/)
[Download](https://downloads.wordpress.org/plugin/matador-jobs.3.9.12.zip)
* [Details](https://pcm.wordpress.org/plugins/matador-jobs/#description)
* [Reviews](https://pcm.wordpress.org/plugins/matador-jobs/#reviews)
* [Installation](https://pcm.wordpress.org/plugins/matador-jobs/#installation)
* [Development](https://pcm.wordpress.org/plugins/matador-jobs/#developers)
[Support](https://wordpress.org/support/plugin/matador-jobs/)
## Description
Connect your Bullhorn Account with your WordPress site and display your valuable
jobs on your new self-hosted job board. Matador makes this as easy as it sounds,
and lets you seamlessly integrate a powerful job board–a major marketing tool for
your business–directly into your WordPress site. Everything that is great about
WordPress is extended to Matador: great out-of-the-box SEO, easy templating/theming,
endless customization options, and more. Matador goes further by listing your jobs
with incredible job-specific SEO customization (optimized for Google Jobs Search),
and more.
Use Matador’s powerful settings to connect our “Apply Now” button for jobs to a
page that will collect applications, or look into purchasing Matador Jobs Pro to
accept applications from Matador and see them turned into candidates submitted to
jobs directly in your Bullhorn Account!
### 3.9.10
* 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`.
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 changelog to be difficult to read prior to 3.9.0.
### 3.9.9
* 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.
### 3.9.8
* Enhancement: Adding a Domain Path plugin header to support improvements to WordPress’
translation files loading.
### 3.9.7
* 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. Please note: some
Matador Jobs extensions are also causing this issue, but WordPress PHP NOTICE
messages are associating the issue with Matador Jobs core. We are actively working
on updating all extensions so this issue is resolved finally.
* Bugfix: (Bullhorn Integration) Some processed Bullhorn resumes were too large
to be processed by the solution we devised to remove presentational tags from
the resume text in 3.9.6. A new solution requiring greater processing time, but
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.
### 3.9.6
* Bugfix: (Bullhorn Integration) Candidate objects returned from the Bullhorn API
following resume processing will have presentational HTML tags removed to prevent
situations where highly stylized HTML candidate descriptions cause the data object
to exceed data limits.
### 3.9.5
* Enhancement: Allowed HTML tags in a job description is expanded to now also support`
`, ``, ``, ``, and ``. This is largely to support
updates in the Bullhorn ATS rich text editor, but is good practice for all job
descriptions in future integrations.
* Enhancement: Added filter `matador_get_currency_codes` to give developers the
ability to modify the list of currency codes used by Matador. The defaults are
from an ISO Currency Codes list, so should be good for most users without modification.
* Bugfix: Fixed an issue causing currency code data to not load as intended for
users of certain world currencies.
* Bugfix: Fixed an issue causing the Application Processing log data to not save
to the database as intended, leaving the sync log data section of the application
transcript blank.
* Bugfix: Fixed an issue causing WordPress to experience a fatal error on versions
prior to 6.7. Matador Jobs Block Editor blocks leveraged improved WordPress Editor
Blocks loading routines introduced WordPress 6.7, but was missing a required
check. This check is now added and in place. That said, we always strongly recommend
our users run the most up-to-date version of WordPress for security and stability
purposes.
* Bugfix: Fixed an issue causing translatable strings to be untranslatable due
to WordPress 6.8 “just-in-time” translation loading. This affected labels for
Jobs Orderby Search Options. Note: there are more strings that are affected by
the WordPress 6.8 “just-in-time” changes, and we are working hard to get all
of them fixed before WordPress 6.8 releases.
* Bugfix: Updated Matador Jobs Block Editor Blocks to support changes to block
registration slated for the soon-to-be WordPress 6.8 release.
* Bugfix: (Bullhorn Integration) Fixed an issue that was causing Matador Jobs Pro
to sync applications slower than intended. For high-volume sites this could create
a backlog over long periods of time resulting in the volume getting too far ahead
of incoming applications. This fix will ease that problem and prevent it in the
future.
* Misc: Updated references to our Matador Jobs Pro documentation website to ensure
links match valid articles.
* Misc: Matador Jobs is tested up to WordPress 6.8, with no fatal or blocking errors,
however full support for changes to translations loading will come in an upcoming
patch.
### 3.9.4
* Bugfix: The uploaded files metabox will now display again after going missing
on Application admin views with 3.9.0.
* Bugfix: Fixed an issue encountered only by logged in admin users when accessing
cached Matador forms. Cross-site request forgery protections were not being properly
refreshed on cached pages for admin users. While this did not impact most customer
users, it made testing staging/development sites frustrating for site admins
and developers.
* Bugfix: (Bullhorn Integration) Fixed an issue causing the job_general_location
to still not save correctly. 2nd times the charm here?
* Bugfix: (Bullhorn Integration) Fixed an issue during import causing the “is hybrid
job” flag to not be saved.
* Bugfix: (Bullhorn Integration) Fixed an issue during import causing the “is remote
job” flag to also be saved when a job is a hybrid job.
### 3.9.3
* Bugfix: Fixed issue with the reset button in default search, previously the reset
button was unable to clear the form and reset the search query params in some
circumstances.
* Bugfix: (Bullhorn) Fixed an issue where a Bullhorn job import for a job without
a city/locality and a state/province would create a “job general location” with
only a comma. Now, a missing city and state will result in an empty/not set “
job general location.”
* Bugfix: Fixed issue allowing servers running PHP 7.4 to PHP 8.0.x to initialize
Matador. Please upgrade to PHP 8.1, the minimum supported version of PHP for
the plugin.
### 3.9.2
* Bugfix: Fixed issue causing admin javascript to fail to load, impacting the use
of Matador Jobs settings screens when the WP_DEBUG or WP_SCRIPT_DEBUG is true
or WordPress environment is set to DEVELOPMENT.
* Bugfix: Fixed issue with readme.txt file formatting that caused information about
the plugin to not load properly when displayed on WordPress.org plugin repository
and in the WordPress plugins admin screen.
### 3.9.1
* Unaddressed Known Issue: Matador Jobs 3.9.0 and 3.9.1 have an issue causing admin
javascript to fail to load, impacting the use of Matador Jobs settings screens
when the WP_DEBUG or WP_SCRIPT_DEBUG is true, or WordPress environment is set
to DEVELOPMENT. This will be addressed in 3.9.2 ASAP.
* Bugfix: Fixed issue causing the packaging of Matador Jobs Lite to be incorrect,
creating issues for our Lite users.
### 3.9.0
### Key New Features
**Matador Jobs Editor Blocks**
We finally are confident in our WordPress Block Editor Blocks, and release them
for our users to build robust front-end displays! Our editor blocks have 100% parity
to our old shortcodes, and in fact add new features to customize display. Included
blocks are:
* Jobs
* Jobs Filters
* Jobs Search
* Application
* Application Link
* Job Description
* Job Field
* Job Relative Age
* Job Link
See our guide to building block-based Matador layouts on our docs website ().
**Application Screening**
Application Screening, code-named “Traffic Lights”, gives users a method to control
whether an application is synced to the external ATS. When enabled, the Application
Screening feature will hold an application until a recruiter reviews (screens) it
and performs an action. The recruiter will receive an email and/or notification
on messaging apps (when Slack, etc, services are enabled) with a summary of the
application data. The notification (and screens in the WordPress admin) will include
action links that give them the recruiter the option to “reject”, “add”, or “apply”.
* “Reject” will remove the application data from the site and never submit it to
your ATS system.
* “Add” will create a new person or candidate record in your ATS, but not submit
that candidate for associated role. This allows recruiters to build a database
of candidates even when the candidate may be unfit for the applied role.
* “Apply” will create a new person or candidate record in your ATS and then link
the record as a job submission. This option may not appear for candidates who
submit information on the general application form.
Application Screening will be powerful for users who are experiencing high volumes
of unqualified candidates and/or spam applications. It is also useful for users
who wish to more finely manage their ATS database.
**Enhanced Logging**
Matador Jobs 3.9.0 completely overhauls the event logging. Logs are an incredibly
useful tool for site admins and developers alike to monitor how Matador is functioning.
Since our initial release, new log entries have been added as Matador has grown
in complexity and new quirks have been discovered, and this means logs were getting
extremely detailed and long. Some sites were creating log files so huge that they
were impacting site storage limits. While this information helps our users–and us,
when debugging issues–understand what is going on, some log items are not necessary
when a site and external connection is deemed operating effectively. This overhaul
cleans up some legacy logging code, making it more efficient, and it also gives
users granular control over what is logged so only the information a site admin
needs is taking up space.
All logged items are now assigned a “Severity” by the developers. Severity are levels
of importance, and are, least important to most important, are:
* Note, to log items which are extremely detailed pieces of information for debugging
and validating function.
* Notice, to log items that modify or impact behavior in a way that is determined
by settings or user filters. This type of log is helpful for us to discover the
cause of “unexpected” behavior being the result of forgotten customizations or
misunderstood settings values.
* Warning, to log items that imply something unexpected occurred, usually due to
malformed external data or connection issues, but that does not affect Matador’s
ability to run. For example
* Error, to log items that are errors that impact Matador’s ability to complete
a task, and that interrupts Matador’s operation. Examples could include disconnections
from external integrations or bad application data. These can trigger admin email
alerts as well.
* Critical, to log items that Matador cannot recover from. These are usually unexpected
errors and often a result of misuse of Developer Filters or issues with external
connections that Matador developers have not written code to handle.
* Info, to log items that are important to the user for purely informational purposes.
These always log. These can be confirmation of completed syncs, applications
received, and more.
Along with this enhanced logging functionality, come the following highlights:
* Users can set a setting or filter to choose which level of severity are written
to the logs. “Info” items will always be logged. Default is “Warning”.
* Added filter `matador_activity_log_verbose` which prints associated array data
or object data to the logfile in addition to the log entry. This will create
an extremely verbose, detailed log and should only be enabled during developer
debugging.
* Enhancement: Four new constants are now supported related to logging. Defining
these in a `wp-config.php` file will give a site developer power to override
and hide the associated user settings:
- `MATADOR_LOGGING_ENABLED` allows developers to turn on Matador Activity Logging.
x
* - `MATADOR_LOGGING_DAYS` allows developers to define the number of days of logs
to keep and removes the setting.
* - `MATADOR_LOGGING_SEVERITY` allows developers to define the logging severity
level and removes the setting.
* - `MATADOR_LOGGING_VERBOSE` allows developers to configure whether arrays of
metadata related to the action spawning the log entry should be printed into
the logs.
### Enhancements & Bugfixes
**Jobs**
* “Sync” job button is added to the Block Editor view of the Job Posting to ensure
feature parity with the older Classic Editor.
* A Job Archive will now only be available via the front-end UI if the setting
for an archive is turned on.
* Optimized database calls around the get job by ID function for Bullhorn. Four
database calls are now optimized down to two.
* Fixed an issue where the jobs shortcode would not accept values from the `jobs_per_page`
attribute. This is actually a change to support a long-time error in documentation,
as docs described `jobs_per_page` while `jobs_to_show` was the intended attribute
name.
* Fixed two issues and improved one behavior related to The Template_Support::the_job_meta()
function. First, it will return an empty string instead of false …
## Screenshots
[⌊Options page - Bullhorn Import settings⌉⌊Options page - Bullhorn Import settings⌉[
Options page – Bullhorn Import settings
[⌊CV/resume upload form⌉⌊CV/resume upload form⌉[
CV/resume upload form
[⌊Notifications options page⌉⌊Notifications options page⌉[
Notifications options page
[⌊Jobs listings in the admin⌉⌊Jobs listings in the admin⌉[
Jobs listings in the admin
## Blocks
This plugin provides 13 blocks.
* Matador Application Form Display the Job Application.
* Job Search Search Jobs by keyword, ID, category, type, etc.
* Job Search Keyword Field The keyword field for the jobs search
* Job Relative Age Display the relative age of the job posted day versus today,
ie: '5 days ago' or 'Just Now'.
* Job Field Display a specific job field
* Job Application Link Display a job application link
* Job Search Submit The submit button for the jobs search
* Job Taxonomy Filters Display a job taxonomy filter.
* Job Search Reset Button The reset button for the jobs search
* Jobs Order By Display a Jobs Order By Element which enables your users to determine
how jobs are ordered
* Job Search ATS ID Field The ATS ID field for the jobs search
* Job Description Display the job description
* Job Search Taxonomy Field The taxonomy field for the jobs search
## Installation
This section describes how to install the plugin and get it working.
1. Upload the plugin files to the ‘/wp-content/plugins/matador-jobs-pro’ directory,
or install the plugin through the WordPress plugins screen directly.
2. Activate the plugin through the ‘Plugins’ screen in WordPress
3. Configure the plugin by going to Matador Jobs > Settings.
4. Connect your site to Bullhorn by clicking on ‘Bullhorn Connection Assistant’ on
the Settings Page, and following the. prompts.
## FAQ
### Does this Require a Bullhorn Account?
You must have an active Bullhorn Account to use Matador’s Bullhorn Import/Export
features. It technically will function as a stand-alone jobs board without a Bullhorn
Account, but there are better options out there for that.
### How Do I Get Bullhorn API Credentials?
You must submit a ticket to Bullhorn support. Merely informing them you will be
using Matador should give them all the info they need to help you, as we are now
Bullhorn Marketplace Developer Partners and they know what a new Matador user needs.
That said, we recommend first installing the plugin, activating it, and starting
the Bullhorn Connection Assistant before you do this. Follow the prompts in the
easy-to-use assistant and Matador will generate a copy-and-paste email you can send
to Bullhorn Support to get you started.
### So Matador downloads jobs from Bullhorn. Does it accept applications too?
Yes, if your a user of Matador Jobs Pro or All-Access. Once you’ve connected to
Bullhorn and synced your first jobs, your visitors can apply to the jobs. Based
on settings, the applications will be sent to your Bullhorn either immediately or
in the next regularly scheduled sync with Bullhorn.
If you are only right now a user of the free Matador Jobs Lite, not yet. Matador
Jobs lite allows you to designate a destination page for the “Apply” button, but
you will need to handle your own applications, perhaps with a contact form plugin.
If you’d like more information on Matador Jobs Pro or All-Access, visit [https://matadorjobs.com/](https://matadorjobs.com/).
### How Can I Customize the Look of Matador?
Our documentation site [https://docs.matadorjobs.com/](https://docs.matadorjobs.com/)
explains how to use our template system, theme functions, shortcodes, and actions
and filters to make your site look amazing. You can also watch out for occasional
client showcases on our where we feature creative and amazing looking implementations
of Matador.
### How Can I Customize the Function of Matador?
Matador is built by WordPress users for WordPress users. We included hundreds of
Actions and Filters to help you customize how it works just like WordPress core.
Some of those are documented at [https://docs.matadorjobs.com/](https://docs.matadorjobs.com/)
while others can be discovered with a quick code review.
But that requires a developer and hours of work! If you haven’t already, check out
our many official extensions that are viewable at [https://matadorjobs.com/products/](https://matadorjobs.com/products/).
These extend Matador’s core functionality in ways that can make each site feel unique!
You can use an unlimited number of these All-Access Add-Ons with any Matador Jobs
All-Access plan.
If you need something and you don’t see an add-on, feel free to write us. Leave
a comment in the Support Forum or with our Pro support system [http://www.matadorjobs.com/support/](http://www.matadorjobs.com/support/)(
requires Matador Jobs Pro or All-Access). Simple modifications might already be
documented and we can point you to them. And if you have a more complex modification,
we may be able to take your input and idea and turn it into another All-Access Add-
On.
### Where can I get support?
Users of Matador Jobs Lite should use the plugin’s WordPress.org support forum.
Users of Matador Jobs Pro and All-Access annual or lifetime plans can use our support
ticket system at [http://www.matadorjobs.com/support/](http://www.matadorjobs.com/support/).
## Reviews
There are no reviews for this plugin.
## Contributors & Developers
“Matador Jobs Lite” is open source software. The following people have contributed
to this plugin.
Contributors
* [ Paul Bearne ](https://profiles.wordpress.org/pbearne/)
* [ Jeremy Scott ](https://profiles.wordpress.org/jeremyescott/)
[Translate “Matador Jobs Lite” into your language.](https://translate.wordpress.org/projects/wp-plugins/matador-jobs)
### Interested in development?
[Browse the code](https://plugins.trac.wordpress.org/browser/matador-jobs/), check
out the [SVN repository](https://plugins.svn.wordpress.org/matador-jobs/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/matador-jobs/) by
[RSS](https://plugins.trac.wordpress.org/log/matador-jobs/?limit=100&mode=stop_on_copy&format=rss).
## Changelog
3.9.12
* Enhancement: 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 AllInOne 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 on 2025-12-02.
3.9.11
* 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 pages
due to the dynamic nature of the content Matador Jobs manages.
* Enhancement: Added the `matador_bullhorn_submit_candidate_to_job_body` filter
to enable customisation 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.
## Meta
* Version **3.9.12**
* Last updated **10 months ago**
* Active installations **10+**
* WordPress version ** 5.5.0 or higher **
* Tested up to **6.8.11**
* PHP version ** 8.1 or higher **
* Language
* [English (US)](https://wordpress.org/plugins/matador-jobs/)
* Tags
* [ats](https://pcm.wordpress.org/plugins/tags/ats/)[Bullhorn](https://pcm.wordpress.org/plugins/tags/bullhorn/)
[career portal](https://pcm.wordpress.org/plugins/tags/career-portal/)[job board](https://pcm.wordpress.org/plugins/tags/job-board/)
[OSCP](https://pcm.wordpress.org/plugins/tags/oscp/)
* [Advanced View](https://pcm.wordpress.org/plugins/matador-jobs/advanced/)
## Ratings
No reviews have been submitted yet.
[Your review](https://wordpress.org/support/plugin/matador-jobs/reviews/#new-post)
[See all reviews](https://wordpress.org/support/plugin/matador-jobs/reviews/)
## Contributors
* [ Paul Bearne ](https://profiles.wordpress.org/pbearne/)
* [ Jeremy Scott ](https://profiles.wordpress.org/jeremyescott/)
## Support
Issues resolved in last two months:
1 out of 1
[View support forum](https://wordpress.org/support/plugin/matador-jobs/)
## Donate
Would you like to support the advancement of this plugin?
[ Donate to this plugin ](https://matadorjobs.com)