Matador Jobs Lite

الوصف

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.8.2

  • Bugfix: When a certain of combination of settings were selected, the recommended value for careerPortalDomainRoot was incorrect. When presented to users, the careerPortalDomainRoot value will be right moving forward.
  • Bugfix: A “nice to have” feature disabled in 3.8.1 due to causing new installations of 3.8.0 to fail was fixed and restored. The recommended value for careerPortalDomainRoot will now be displayed under the “Job Listings Slug” option and under the “Disable CareerPortalDomainRoot Check” option in the Bullhorn Connection Assistant.
  • Bugfix: In order to ensure daily analytics do not send more than intended, Matador now tracks analytics calls via an explicit option instead of a transient. We observed that some sites with aggressive or buggy persistent object caching could send Analytics hourly, which is not the intent.
  • Bugfix: Fixed issue where blank/empty values could be saved to the application data when a checkbox field type was used. When a checkboxes field type is used in the application, an empty value used in form submissions for validation purposes but would persist and be saved into the application data. While often not an issue in and of itself, when syncing an application to Bullhorn, this empty value could result in an IMPROPERLY_STRUCTURED_ASSOCIATION API error when being submitted to HAS_ONE or HAS_MANY field types. This bugfix will prevent the empty checkbox from being saved in the first place while also fix data before API submission to avoid future IMPROPERLY_STRUCTURED_ASSOCIATION API errors.

3.8.1

  • Bugfix: Temporarily removed the “nice to have” feature of 3.8.0 which displays the expected/desired value for the careerPortalDomainRoot in certain settings screens which, due to how this is added to the settings screens, could cause the initial installation of Matador Jobs on fresh WordPress websites to crash. Per our investigation, this only impacted users installing Matador Jobs on a fresh installation of WordPress where the “pretty permalinks” options were not yet set. No active jobs sites were impacted, as the nature of this bug would never have impacted them.

3.8.0

Matador Jobs 3.8.0 contains changes in 318 commits changing 104 files and over 14,000 lines of code revised or added. It is a large update with many quality-of-life changes that will make Matador Jobs more reliable and easier to use for all our users.

This will be the last major version of Matador Jobs to support PHP 5.6 and WordPress versions prior to 5.8. When released early to mid next year, our next version will require PHP 7.4 or higher and WordPress 5.8 or higher.

Connectivity & Stability

Highlights:

  • New Sync (Beta): This release includes a beta release of our updated sync routine. The sync routine was redesigned to pause prior to triggering “long processor killer” triggers at the web host and resume, picking up where it left off, over and over again as needed, to ensure a complete sync consistently occurs. Some users, especially those with more than 2000 active openings, would see syncs fail due to “long process killers.” While this new sync routine is very reliable, we have opted to make it optional until 3.9.0. Opt-in to the new sync by adding this developer flag to your site add_filter( 'matador_experimental_sync', '__return_true' );.

  • CareerPortalDomainRoot Detection: Several Bullhorn systems, including Bullhorn Automation (formerly Herefish) and Bullhorn Publish to Indeed will generate a web address (URL) for the job based on the value in Bullhorn of the careerPortalDomainRoot setting. Matador users who use Matador as their primary job board (or portal) should notify Bullhorn to update this setting. Now, Matador will read the value of careerPortalDomainRoot in Bullhorn and let you know if there is a mismatch. Further, this detection will not trigger on common local, staging, development, or test environments and can be disabled.

  • Added “Cookie Bug” Warning: Long time Matador users will know about the “Cookie Bug.” This is a bug in the Bullhorn authentication system that allows a logged-in user’s cookie to hijack the Matador Jobs authentication with Bullhorn and authorize as that user, not the API user. This has serious potential consequences including job syncs bringing in the wrong jobs and the site being unable to auto reconnect in the event of a downtime. Now Matador can detect when a “Cookie Bug” has occurred and will warn the user.

  • Added Matador Unsafe Password Warning: Matador Job’s auto reconnect routine cannot reconnect when the API User Password has certain “unsafe” characters. Valid Bullhorn passwords can still cause an issue, so Matador will now detect if the password would not allow for an automatic reconnection.

More:

  • Fixed an issue where the “Test Auto Reconnect” routine would result in a disconnection fail following changes to Bullhorn’s API.
  • DISABLE_WP_CRON warnings will now not display as admin notices. Many managed WP platforms have moved to disable WP_CRON and replace it with system cron. This is a good thing! Unfortunately, this also turned our formerly helpful heads-up into an annoying notice for many users.
  • The Administrator Disconnected Site Warning Email will now only send after several attempts have been made to reconnect. This, in combination with the existing 24-hour timeout, should minimize the occurrence of admin warning emails when the software can reconnect naturally. The recent higher occurrence of Disconnection Notices has been due to a high frequency of 429 Too Many Requests errors on the Bullhorn API, which means there is a “traffic jam” on their system.
  • The Administrator Disconnected Site Warning Email has two changes. First, the subject line formerly had the “Site Name” but will now have the “Site URL”. Second, a line is added to the content of the email with the “Site Name” and “Site URL”. These two changes will help site operators differentiate between disconnections of live/production sites and disconnections of local, test, staging, or development sites, and how much urgency they need to apply to the email notification.
  • Fixed a bug that caused logging options to not save on “lite” versions of Matador Jobs.

Marketing/SEO

Highlights:

  • Experience and Education Updates: Google for Jobs Search and other systems that consume Job Structured Data/LD+JSON have new expectations for Experience and Education details. Matador will now serve the updated schema.

  • Employment Types Detection: Matador will now map more user values to the default Job Structured Data/LD+JSON employment types. We still encourage you to review the values you are passing from Bullhorn into Matador Jobs for employment type and ensure they are mapping to Job Structured Data/LD+JSON expected values, especially if your primary language is not English.

  • Integration with All in One SEO (AIOSEO) Plugin: Matador will now integrate its Job Structured Data/LD+JSON features into All in One SEO plugin. This happens automatically when the AIOSEO plugin is included. AIOSEO now joins RankMath and Yoast SEO in the list of 3rd-party SEO plugins that Matador seamlessly integrates with.

More:

  • Matador Jobs can now detect visits by the ‘Googlebot’, aka Google Indexing systems, on jobs. All visits are added to your Matador log file, or if you have Google Indexing API active, you can log only visits after an Indexing API call.
  • Added a validation to the Job Structured Data/LD+JSON inclusion to validate that we indeed have valid JSON. This prevents issues with page validation (ie: from Google Search Console) if the JSON is invalid. Invalid JSON is sometimes created when customization developer filters are improperly used.
  • Fixed issue where JSON+LD was being loaded on certain jobs archive/job listing pages, resulting in possible issues with page validation (ie: from Google Search Console).
  • Updates to Yoast SEO integration to reflect changes to their plugin.
  • Fixed bug on RankMath SEO integration causing the Job Structured Data/LD+JSON to be included in the wrong part of the graph. As of discovery of this error, page validation tools (ie: from Google Search Console) still considered the old (wrong) implementation valid.

Privacy

Highlights:

  • Terms of Service Consent Field: A Terms of Service consent field was added to Application forms. It behaves similarly to the existing Privacy Policy consent field. This gives users the ability to have separate Privacy Policy and Terms of Service consents, which is recommended for adhearance with the ever-changing data security and privacy regulations. This update includes the following:

    • New checkbox form field for Terms of Service with basic text description. International users please send us a literal translation for the field and we will update translations for your language.
    • New admin settings “Require User to Accept Terms of Service” and “Terms of Service Page”. When the “require” setting is toggled on, Matador will add a form field in the application footer that requires applicants to check a box acknowledging the website Terms of Service. If a page is selected in the “page” setting, a link to the WordPress page with the Terms of Service will be included.
    • If your Bullhorn install includes the Candidate Consents object, a new consent will be added for “Accepted Terms of Service” with the justification of “Contract Necessity”. The description will be “Candidate accepted Terms of Service.” followed by a log of their IP address at time of submission.
  • Discontinuing Recognition of “Do Not Track”: Matador Jobs Pro will no longer consider your site users’ web browser “Do Not Track” setting when determining whether to load Matador’s Source Tracking features. This browser-level setting is largely ignored by the big trackers and was intended to only apply to 3rd party, and not 1st party like Matador’s, trackers. We recommend our users review the documentation on Matador Traffic Source Tracking features to ensure compliance with local laws and regulations.

More:

  • The settings section “Application Privacy Settings” is renamed to “Consents, Privacy, and Data Security Settings” to better communicate the expanded purpose of the section.
  • The description text for the Privacy Policy consent saved to the Bullhorn Candidate Consents object will now read “Candidate accepted Privacy Policy.” followed by a log of their IP address at time of submission. Previously, the description was not clear, listing applied jobs.
  • Removed links to the applicant’s submitted files in the application transcript, which was often used as the body text of a recruiter email notification. This makes it easier for those wishing to not distribute those files when considering local privacy law compliance.
  • Remove legacy method for candidate IP address and candidate Privacy Policy Acceptance tracking. Released in 3.4.0, most users never took advantage of the feature Matador included in our code to track the time and date of a Privacy Policy acceptance for a candidate. This is partly due to how complicated it was to set up, requiring no less than 6 developer filters and 4 customText and customDate fields set up in Bullhorn. With 3.7.0 and later 3.8.0, Matador now tracks this data automatically with no setup required in the Bullhorn Candidate Consents Object, and thus we are removing the legacy features in favor of the new, easier to use, replacement.

Templating/Theming

Features:

  • New Shortcode [matador_portal]: A new shortcode [matador_portal] is introduced. This shortcode will help users of “Classic Editor” and “page builders” other than the WordPress block editor to streamline access to a standard “job portal” like page with a single shortcode. See more here.

  • New Shortcode [matador_general_application_link]: A new shortcode [matador_general_application_link] and associated template functions matador_{get}_general_application_link() and matador_{get}_general_application_url() will provide a simple button link to the “General Application”. This must be used in coordination with a new setting “General Application Page” to determine the destination. The purpose is to provide mostly developers an easy way to link to the General Application page, or page that contains an application not assigned to a specific job, while leaving the user space to update or change it at a later time.

  • New option for Taxonomy “method”, “search”: The matador_taxonomy() function (and associated shortcode) now accepts a new value for the ‘method’ argument: search. When passed ‘search’ the link will be to the jobs listing page (as set in settings) or jobs archive with the taxonomy argument appended as if it were a search term. If used on the jobs listing page, this will reset the search, so on the jobs listing page you will still want to use ‘method=filter’. This makes it easy to include the list of taxonomy terms in your design without requiring you to have a taxonomy archive page prepared.

More:

  • Updated default stylesheet to better display the [matador_search] and matador_search() shortcode/function responsiveness on small screens. The changes were designed to be minimal so as not to impact user stylesheets but make it less necessary for user stylesheet overrides to be even necessary in the first place.
  • Reverted a bugfix from 3.7.7 and created a new one that changed behavior around Job Sorting on Taxonomy Archive pages. Our fix was actually too aggressive, and caused sorting rules to be not applied in some instances where they were desired. We reviewed the initial bug report after reverting the flawed patch and came up with a solution that is more reliable.
  • Fixed issue where the [matador_types] and [matador_locations] alias shortcodes, when used with no passed arguments, would result in an “Illegal String Offset” PHP error. This was caused by a WordPress quirk where no arguments passed to a shortcode passes an empty string into the shortcode callback function instead of an empty array. Funnily enough, once again, we have major release with a fix for a bug that has technically existed since launch of Matador! THREE IN A ROW!

Job Import

Highlights:

  • **New Sync*: See notes on the new sync in the “Connectivity and Reliability” section of this Changelog.

More:

  • Matador will now gracefully handle data that comes over the Bullhorn API as multiple values when only a single value was expected. In some cases, it will combine provided values, in others it will use only the first provided value. The reason for this change was because we found users enabled the “allow multiple values” setting in Bullhorn for standard fields that should not, in our opinion, have multiple values, like Job Title. We recommend users do not “allow multiple values” on standard Bullhorn fields, even though Matador can now handle these.
  • Fixed an issue causing dateLastModified and/or dateLastPublished values to be saved in the WordPress database with timezone offset, which caused issues with “last updated” related syncing for sites in a GMT+ timezone (east of Prime Meridian).
  • dateEnd and all customDate job properties from Bullhorn will now properly save as a MySQL-formatted Date & Time object. Previously, dates like these were saved to the database as Unix timestamps, which many third-party templating systems could not format easily.
  • An extremely rare issue could occur when concurrent Bullhorn calls interrupt the other and, if the timing was right, result in some or all jobs being removed from the site until the next uninterrupted sync. Changes to the syncing code were added to ensure that the interrupted sync fails gracefully, instead of destructively, when this occurs. Thank you to Lara at MCM Staffing for bringing our attention to this bug.

Applications/Submissions

Features:

  • New Company and Occupation Form Fields: Added companyName or “Your Current Company” and occupation or “Your Current Occupation” form fields to the core form offering. Include them by passing them to the fields argument of the [matador_application] shortcode or via the matador_default_application_fields filters.

  • New Cover Letter and “Files” Form Fields: Added letter or “Cover Letter” and files or “Other Files (Multiple)” form fields to the core form offering. Include them by passing them to the fields argument of the [matador_application] shortcode or via the matador_default_application_fields filters. Letter will save into Bullhorn as a “cover letter” while “Files”, which we imagine can be repurposed to allow for submission of portfolios or examples of work and/or answers to assessments, will be saved into Bullhorn as “other” type files.

  • Select Candidate “Owner” Setting: Prior to this release, the “owner” in Bullhorn of a new candidate would be the API User. Certain agencies would prefer to set the “owner” based on the Job’s “ownership” and a new setting will allow for this. Select from ‘API User’, ‘Job’s “Owner”‘, or ‘Job’s “Published Contact Recruiter”‘.

  • Existing Candidate’s Name Not Updated: Matador will no longer update a Candidate’s name after an application where a matching candidate record was found. Assumption shall be that a Candidate’s name was correct on initial application. A few rare situations occurred where bad user input on a subsequent application changed a record in an unexpected way. On that note, if a candidate makes submission with a misspelled first name or nickname instead of legal name, a change will now need to be made by the contacting recruiter.

  • Removed Email Validation: With this update, all email address validation is removed from the plugin. Our email address validation was too strong and based on an outdated international standard (RFC2822) which didn’t allow for certain international characters in the email address or name as well as certain internationalized URLs after the @ symbol. New email address standards (RFC6854) are now so relaxed that it is consensus among developers that there is no reliable way to validate the format of an email address without creating false negatives. Further, assuming that risk is deemed worthwhile, even a properly structured email address that passes validation does not a guarantee that an email box even exists at that address. For those reasons we will no longer validate email addresses.

More:

  • Form processing used to reject all empty() values during processing, which included false and zero numbers. We’ve encountered use cases where saving those as-is are necessary. As a result, form processing will now accept zeros and false while still properly rejecting null and empty values.
  • Fixed a bug that could occur when a custom form field passes a string to a field that expects an array of values. Matador will now verify the string value and convert it to a single-member array containing that string.
  • Fixed an error being caused by changes to the Bullhorn API that now enforce previously unenforced length limits to certain fields. User input that exceeds the limits will now be truncated at the character limit.
  • Added handling for changes to the Bullhorn API (or its resume processor) that now return HTTP 500 Internal Server Error errors instead of the former HTTP 400 Bad Request errors when a resume is submitted that cannot be processed.
  • Standardized the methods Matador checks the uploaded file size and extension across various systems (client side validation, server-side validation, etc). Now, in order to change the allowed file types and max uploaded file size, a change only needs to be made in one place.
  • Matador can now set the “File Type” of files saved into Bullhorn. Previously, when a form accepted multiple files, all would be saved as “Resume.”
  • To make accessing submitted files easier, a new dialogue box was added to the Submission record with links to the files and, if processed, the raw data from the resume processor.
  • Improved handling of Field Labels in the Submission transcript (which is saved to the post_content field of the WordPress Submissions post type). The transcript is used both as a backup for the application data in the event of an issue and also as default content in generated emails for recruiters and applicant email confirmations. The field labels will now more consistently draw their values from the application structure as modified by the user’s custom code or the Advanced Applications extension.
  • Added developer filter matador_application_transcript_include_field to be used to remove items from the application transcript. This might include confidential applicant demographics data and other sensitive information that shouldn’t be readily accessible or sent via email.
  • Removed links to the applicant’s submitted files in the application transcript, which was often used as the body text of a recruiter email notification. This makes it easier for those wishing to not distribute those files when considering local privacy law compliance.
  • Submissions (Applications) were showing as available for inclusion in the WordPress menu builder even though they would not load on the site front end. This was unintentional and has been changed; submissions will not be available as options for WordPress menu builder items.

Notifications/Emails

Note: some items that also belong in this category were previously included in the Privacy and Submissions sections.

Highlights:

  • Recruiter Notifications Bullhorn Deeplink: Recruiter Notification emails will now include a deeplink into Bullhorn if the email setting is set to “send email after the candidate sync”.

More:

  • Added filter matador_email_additional_headers to allow developers to add additional headers to Matador-generated emails.
  • Added developer filter matador_email_allowed_html_tags to give users granular ability to extend which HTML tags are allowed in Matador emails. The use case, notably, is from Matador user Nils with WebReact who explained that custom XML tags readable by MSExchange and Outlook can add interactivity to emails on that platform but the XML tags were being stripped by Matador’s security routine. Now a user like Nils can teach Matador that those XML tags are safe to allow in the email.

General

  • Added WP-CLI command wp matador sync: Our first WP-CLI commands are live! This first command, wp matador sync runs the full sync process from WP-CLI. This can be used on webhosts with system cron options and WP-CLI to disable Matador’s sync and rely on a custom sync scheudle. Future updates will expand WP-CLI commands.

  • Added Analytics: Matador will now report simple annonymous analytics when certain actions occur, including plugin activation, upgrade, and connection to Bullhorn. The purpose for these analytics is to help us understand our users’ needs and provide more reliable support. As per our terms of service, we will also share some of these analytics with Bullhorn. Bullhorn likes to know who is using Matador, and accounts marked as Matador users will recieve an enhanced support experience, so everyone wins!

  • Update to Software Licensing and Automatic Updates: Completely overhauled Matador’s handling of Licensing and software updates, fixing many bugs and adding features and utility:

    • Previously Matador would not deactivate a url from a settings change. This would result in users needing to manually deactivate URLs from MatadorJobs.com. Now, a button allows manual deactivation and changing the key triggers automatic deactivation, making it much easier for site owners to authorize production sites after development.
    • Matador respects more wildcard Staging and Development URLs, and will honor WP_ENVIRONMENT_TYPE variables when considering whether to consume an activation against your license.
    • Matador will check your activation every four hours and detect if an external deactivation was made, which helps keep sites working as expected.
    • Matador plugins should now play nice with WordPress Automatic Plugin Updates (since WordPress 5.5).
    • When attempting a site activation, Matador will provide more detailed descriptions of issues, including where helpful, a link to MatadorJobs.com to resolve the issue.

More:

  • Fixed issue causing PHP 5.6 incompatibility. We strongly recommend our users run sites powered by PHP 7.4 or later, however.
  • Fixed issues causing PHP 8.1 incompatibility. Code written for the Traffic/Source feature issues a PHP NOTICE but fixing it will make the code not valid for PHP 5.6. This will updated prior to Matador Jobs 3.9.0 or 4.0.0 which will require PHP 7.4 or later for Matador Jobs.
  • Revised some use of PHP’s DateTime class to use PHP’s DateTimeImmutable instead, which prevents some rare cases where dates could be changed in unexpected ways.
  • To further support extension development, some functions were converted to static functions.
  • Refactored how third-party plugin/theme support is included in the codebase, properly isolating it into separate files for ease of maintenance and code readability.
  • Updated dependence jQuery.Validation from 1.17.0 to 1.19.5
  • Updated dependency mustache/mustache from 2.13.0 to 2.14.2

Previous Versions

  • See CHANGELOG.md

لقطات الشاشة

  • Options page - Bullhorn Import settings
  • CV/resume upload form
  • Notifications options page
  • Jobs listings in the admin

التنصيب

This section describes how to install the plugin and get it working.

  1. Upload the plugin files to the ‘/wp-content/plugins/matador-jobs’ 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.

الأسئلة المتكررّة

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/.

How Can I Customize the Look of Matador?

Our documentation site https://matadorjobs.com/support/documentation/ 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://matadorjobs.com/support/documentation/ 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/. 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/ (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/.

المراجعات

لا توجد مراجعات لهذه الإضافة.

المساهمون والمطوّرون

“Matador Jobs Lite” هو برنامج مفتوح المصدر. وقد ساهم هؤلاء الأشخاص بالأسفل في هذه الإضافة.

المساهمون

ترجمة ”Matador Jobs Lite“ إلى لغتك.

مُهتم بالتطوير؟

تصفّح الشفرة، تحقق من مستودع SVN، أو الاشتراك في سجل التطوير بواسطة RSS.