Today, Matador Jobs was updated to provide our users with a follow-up to last week’s critical update that addressed changes made at Bullhorn that caused Matador to not work as expected. This hotfix includes tools to support our users in ultimately recovering from the consequences of the bug.
Added a bulk Application Sync button to the applications view. Will re-try all failed applications from the issue addressed in 3.3.6 and any failed applications for the last two weeks.
Added a filter matador_application_batch_sync_allowed_statuses to allow you to extend the statuses included in a batch sync. This may come in handy in the future when we expand the statuses assigned to applications that fail.
Added a filter matador_application_batch_sync_duration to allow you to extend of duration applied in a batch sync. If, for example, you want to apply a batch sync to jobs older than two weeks, you can do this via this filter.
Fixed spelling/grammar error in the application processing overlay.
Added escaping functions to prevent errors encountered during an application sync when Matador checks for existing candidates. Candidates with names that included a single quotation mark/apostrophe caused the search to be badly formatted and thus present an error, which in turn caused the application sync to fail altogether.
Again, we know this issue caused many of you inconvenience. During Paul’s and my 4 years working with Bullhorn API’s, we’ve of course encountered times where a change at Bullhorn has interrupted our code. We’ve worked hard the last week since this bug was first reported to us to create a fix, first, and add tools to help you recover. We will continue to be focused on the stability of Matador our commitment to service to you, our users!
Today, Matador Jobs was updated to provide our users with a critical update that addresses changes made at Bullhorn that caused Matador to not work as expected. We highly recommend you complete this update as soon as possible.
Enabled sync re-try for applications with the status of “Unable to sync”.
Updated messaging around reasons that an application sync may fail.
Updated the way a Bullhorn request was being made that was causing it to fail after the September 2018 Bullhorn ATS software upgrades.
We are observing an issue on some Bullhorn users’ accounts where a Bullhorn resume parse may return a badly structured candidate object that later results in a failure when Matador tries to create a candidate with that object. We have included a temporary work-around until we can help our partners at Bullhorn resolve this issue.
Fixed an issue where a “Re-try Sync” routine on an application would result in an HTTP 430 error under certain caching circumstances.
In addition to completing this update, we highly recommend you review your applications in Matador Jobs Pro and, where a failure occurred due to this issue, you should click on “Re-try Sync”.
We know this will cause many of you inconvenience. During Paul’s and my 4 years working with Bullhorn API’s, we’ve of course encountered times where a change at Bullhorn has interrupted our code. We’ve worked hard the last two days since this was first reported to us to create a fix. Even if you didn’t notice the problem, know that we were here doing our best to fix it as quickly as possible for you!
Bullhorn have just published an article by Matador developer Jeremy Scott on how Google for Jobs optimization can increase search traffic to your jobs website.
Based on the experience of building Google for Jobs optimization into the Matador software, the article explains what Google for Jobs is, how it works and offers a high-level overview of how to optimize your company’s website.
We’ve put a lot of time into ensuring that Matador Jobs integrates really effectively with Google for Jobs search and we know it can make a huge difference. We have one customer who reported a 75% increase in organic search traffic to her site in one month.
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 WordPress.org.
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.
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.
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 WordPress.org.
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).
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 WordPress.org’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.
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.
A minor bugfix update to address an issue discovered resulting in Candidate records not saving custom application field data.
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.
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.
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.
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