Friday, we released Matador Jobs 3.5.2, a second minor release to the 3.5.x version of Matador that addresses a few issues found since 3.5.0’s or 3.5.1’s release.

Bugs Squashed:

  • We fixed an issue where a conflict could be created between our implementation of the open-source jQuery.validate() JavaScript library, which we provide for the purpose of form validation, and other plugin or theme use of the tool. When this was present, no forms would get validated, failing to notify the applicant when insufficient data is provided.
  • As part of this, we fixed a security issue where, either by disabling Javascript, failing to load the validation code, or maliciously manipulating form data, a user could bypass the required acceptance of the privacy policy fields.
  • We fixed an issue where an invalid email address submitted to the form would be properly rejected by Matador for security reasons but the user would not be notified.
  • We fixed an issue where multiple “admin notices” would stack, causing an overwhelming list of notices when logging in.
  • We fixed a bug where, during a specific combination of arguments, the Matador Jobs shortcode could fail due our handling of the many different ways the single shortcode is designed to work.

Other Notable Changes:

  • We changed a behavior associated with how Matador notifies you of failed communications with Bullhorn. Previously, our intent was to have every communication failure present an “admin notice” to a logged in WordPress administrator. This meant a warning, “your Matador Jobs is disconnected from Bullhorn” would be displayed. This error persisted even after our build-in connection recovery tool successfully re-established connection. With this release, if the connection recovery tool recovers the connection, the admin notice will be removed.
  • Fixed a spelling error in the default label for an uncommonly used application form field.