[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fP0HPSLeg8Bf9Tzqgv8FBPBf-KFb0IrBOgX38wLzQ_PQ":3},{"slug":4,"display_name":5,"profile_url":6,"plugin_count":7,"total_installs":8,"avg_security_score":9,"avg_patch_time_days":10,"trust_score":11,"computed_at":12,"plugins":13},"pbearne","Paul Bearne","https:\u002F\u002Fprofiles.wordpress.org\u002Fpbearne\u002F",6,5050,95,22,91,"2026-04-04T16:08:03.243Z",[14,41,62,82,103,118],{"slug":15,"name":16,"version":17,"author":5,"author_profile":6,"description":18,"short_description":19,"active_installs":20,"downloaded":21,"rating":22,"num_ratings":23,"last_updated":24,"tested_up_to":25,"requires_at_least":26,"requires_php":27,"tags":28,"homepage":34,"download_link":35,"security_score":36,"vuln_count":37,"unpatched_count":38,"last_vuln_date":39,"fetched_at":40},"author-avatars","Author Avatars List\u002FBlock","2.1.25","\u003Cp>This plugin makes it easy to \u003Cem>display lists of user avatars\u003C\u002Fem>, grouped by user roles, on your (multiuser) site. It also allows you to \u003Cem>insert single avatars\u003C\u002Fem> for blog users or any email address into a post or page – great for displaying an image of someone you’re talking about.\u003C\u002Fp>\n\u003Cp>It makes use of built-in WordPress (core) functions to retrieve user information and get avatars.\u003C\u002Fp>\n\u003Cp>Integrates with: Gutenberg, BuddyPress, xprofile, Multisite, Wpmu, BBPress, co-authors.\u003C\u002Fp>\n\u003Cp>Avatar lists can be inserted into your sidebar by adding a widget or into posts\u002Fpages by using a \u003Ca href=\"http:\u002F\u002Fauthoravatars.wordpress.com\u002Fdocumentation\u002Fauthoravatars-shortcode\u002F\" rel=\"nofollow ugc\">shortcode\u003C\u002Fa>. The plugin comes with a tinymce editor plugin which makes inserting shortcodes very easy.\u003C\u002Fp>\n\u003Cp>This also provides Gutenberg Block for use with the Gutenberg editor.\u003Cbr \u002F>\nPlease help with the plugin Translations at https:\u002F\u002Ftranslate.wordpress.org\u002Fprojects\u002Fwp-plugins\u002Fauthor-avatars.\u003C\u002Fp>\n\u003Cp>Both the shortcode and widget and Gutenberg Block can be configured to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Show a custom title (widget only)\u003C\u002Fli>\n\u003Cli>Only show specific user groups and\u002For hide certain users\u003C\u002Fli>\n\u003Cli>Limit the number of users shown\u003C\u002Fli>\n\u003Cli>Change the sort order of users or show in random order\u003C\u002Fli>\n\u003Cli>Adjust the size of user avatars\u003C\u002Fli>\n\u003Cli>Optionally show a user’s name or biography\u003C\u002Fli>\n\u003Cli>Show users from the current blog, all blogs or a selection of blogs (on WPMU\u002FMultisite)\u003C\u002Fli>\n\u003Cli>Group users by their blog (when showing from multiple blogs), and show the blog name above each grouping.\u003C\u002Fli>\n\u003Cli>Support users from Co-Author Plus, Ultimate Member, BBpress and BuddyPress (xprofile)\u003C\u002Fli>\n\u003Cli>Limit the number of avatars per page for large sets by adding a page_size to the shortcode e.g. “page_size=30” (shortcode only)\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Additionally, single user avatars can be inserted using the \u003Ca href=\"http:\u002F\u002Fauthoravatars.wordpress.com\u002Fdocumentation\u002Fshow_avatar-shortcode\u002F\" rel=\"nofollow ugc\">show_avatar shortcode\u003C\u002Fa> and configured to:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Adjust the size of the user avatar.\u003C\u002Fli>\n\u003Cli>Align the avatar left, centered or right.\u003Cbr \u002F>\nThe Gutenberg Block support both single user avatars and role based selections of avatars\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Please report bugs and provide feedback in the \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Ftags\u002Fauthor-avatars?forum_id=10#postform\" rel=\"ugc\">wordpress support forum\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Plugin support:\u003C\u002Fstrong> In 2011, Ben stepped down as maintainer of the Plugin, handing over ownership to co-author Paul Bearne, who continues to provide support and drive the development of new features.\u003C\u002Fp>\n","Display lists of user avatars using widgets or shortcodes. With Gutenberg support.",4000,378912,96,32,"2025-11-28T17:22:00.000Z","6.9.0","3.0","",[29,30,31,32,33],"author","avatar","block","image","profile","http:\u002F\u002Fauthoravatars.wordpress.com\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fauthor-avatars.2.1.25.zip",98,3,0,"2025-01-07 00:00:00","2026-03-15T15:16:48.613Z",{"slug":42,"name":43,"version":44,"author":5,"author_profile":6,"description":45,"short_description":46,"active_installs":47,"downloaded":48,"rating":49,"num_ratings":7,"last_updated":50,"tested_up_to":25,"requires_at_least":51,"requires_php":27,"tags":52,"homepage":58,"download_link":59,"security_score":60,"vuln_count":38,"unpatched_count":38,"last_vuln_date":61,"fetched_at":40},"wp-site-verification-tool","WP Site Verification tool","1.0.9","\u003Cp>This is a simple tool that helps you provide the site verification code and file generator for any service that needs to verify the site\u003Cbr \u002F>\nvia a comment \u002F meta in the head section or via a file URL.\u003C\u002Fp>\n\u003Cp>This is a generic site certification tool.\u003Cbr \u002F>\nTo use it, just add the plug-in and turn it on as needed.\u003Cbr \u002F>\nYou will no longer need to FTP a file to the site root or add extra tags to the header.php in the template to enable your site to be verified by third-party services.\u003C\u002Fp>\n\u003Cp>Some examples:\u003Cbr \u002F>\nGoogle webmaster tool needs a file called \u003Cstrong>googleXXXXXXXXXXXXX.html\u003C\u002Fstrong>  with no contents.\u003Cbr \u002F>\nOR\u003Cbr \u002F>\n\u003Cstrong>\u003Cmeta name=”google-site-verification” content=”XXXXXXXXXXXXXXXXXXXXXXXXXXXXX” \u002F>\u003C\u002Fstrong> in the HTML head,\u003Cbr \u002F>\nWithout this plugin, you would have to create a file and FTP it to your server or edit your template. With the plugin, you can generate the verification method needed automatically via the control panel.\u003C\u002Fp>\n\u003Cp>Similarly, Trustwave SSL wants a file called \u003Cstrong>cert.html\u003C\u002Fstrong> with the contents of\u003Cbr \u002F>\n\u003Cstrong>“Trustwave SSL Validation Page”\u003C\u002Fstrong>\u003C\u002Fp>\n","A tool to enable verification of site ownership via file or meta tag.",1000,28774,74,"2025-11-28T17:32:00.000Z","3.6",[53,54,55,56,57],"certification","site-verification","tool","vip","webmaster","http:\u002F\u002Fwordpres.org\u002Fwp-vite-verication-tool","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-site-verification-tool.1.0.9.zip",100,null,{"slug":63,"name":64,"version":65,"author":5,"author_profile":6,"description":66,"short_description":67,"active_installs":68,"downloaded":69,"rating":38,"num_ratings":38,"last_updated":70,"tested_up_to":71,"requires_at_least":72,"requires_php":73,"tags":74,"homepage":80,"download_link":81,"security_score":60,"vuln_count":38,"unpatched_count":38,"last_vuln_date":61,"fetched_at":40},"matador-jobs","Matador Jobs Lite","3.9.9","\u003Cp>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\u002Ftheming, 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.\u003C\u002Fp>\n\u003Cp>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!\u003C\u002Fp>\n\u003Ch3>3.9.9\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Bugfix: Fixed bug that caused a delay in an application being synced when there was only one pending application.\u003C\u002Fli>\n\u003Cli>Bugfix: Fixed a critical (site breaking) error that was encountered only when Admin Emails were turned off and a site disconnection occurred.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.8\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Enhancement: Adding a Domain Path plugin header to support improvements to WordPress’ translation files loading.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.7\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>Bugfix: (Bullhorn Integration) Fixed issue causing the import categories cache to not save as expected.\u003C\u002Fli>\n\u003Cli>Bugfix: (Bullhorn Integration) Modified the process in which the Bullhorn Country data cache is refreshed, preventing a stale cache from returning invalid\u002Fmissing Country data and impacting user applications. The cache is now persistent and a separate mechanism is in place to refresh it regularly.\u003C\u002Fli>\n\u003Cli>Enhancement: Added WordPress filter \u003Ccode>matador_application_field_should_skip\u003C\u002Fcode> 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.\u003C\u002Fli>\n\u003Cli>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 \u003Ccode>matador_application_field_should_skip\u003C\u002Fcode> filter to their customized template.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.6\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.5\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Enhancement: Allowed HTML tags in a job description is expanded to now also support \u003Ccode>\u003Cblockquote>\u003C\u002Fcode>, \u003Ccode>\u003Cs>\u003C\u002Fcode>, \u003Ccode>\u003Csub>\u003C\u002Fcode>, \u003Ccode>\u003Csup>\u003C\u002Fcode>, and \u003Ccode>\u003Cu>\u003C\u002Fcode>. This is largely to support updates in the Bullhorn ATS rich text editor, but is good practice for all job descriptions in future integrations.\u003C\u002Fli>\n\u003Cli>Enhancement: Added filter \u003Ccode>matador_get_currency_codes\u003C\u002Fcode> 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.\u003C\u002Fli>\n\u003Cli>Bugfix: Fixed an issue causing currency code data to not load as intended for users of certain world currencies.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>Bugfix: Updated Matador Jobs Block Editor Blocks to support changes to block registration slated for the soon-to-be WordPress 6.8 release.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>Misc: Updated references to our Matador Jobs Pro documentation website to ensure links match valid articles.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.4\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Bugfix: The uploaded files metabox will now display again after going missing on Application admin views with 3.9.0.\u003C\u002Fli>\n\u003Cli>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\u002Fdevelopment sites frustrating for site admins and developers.\u003C\u002Fli>\n\u003Cli>Bugfix: (Bullhorn Integration) Fixed an issue causing the job_general_location to still not save correctly. 2nd times the charm here?\u003C\u002Fli>\n\u003Cli>Bugfix: (Bullhorn Integration) Fixed an issue during import causing the “is hybrid job” flag to not be saved.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.3\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>Bugfix: (Bullhorn) Fixed an issue where a Bullhorn job import for a job without a city\u002Flocality and a state\u002Fprovince would create a “job general location” with only a comma. Now, a missing city and state will result in an empty\u002Fnot set “job general location.”\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.2\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.1\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>Bugfix: Fixed issue causing the packaging of Matador Jobs Lite to be incorrect, creating issues for our Lite users.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>3.9.0\u003C\u002Fh3>\n\u003Ch3>Key New Features\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Matador Jobs Editor Blocks\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>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:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Jobs\u003C\u002Fli>\n\u003Cli>Jobs Filters\u003C\u002Fli>\n\u003Cli>Jobs Search\u003C\u002Fli>\n\u003Cli>Application\u003C\u002Fli>\n\u003Cli>Application Link\u003C\u002Fli>\n\u003Cli>Job Description\u003C\u002Fli>\n\u003Cli>Job Field\u003C\u002Fli>\n\u003Cli>Job Relative Age\u003C\u002Fli>\n\u003Cli>Job Link\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>See our guide to building block-based Matador layouts on our docs website ().\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Application Screening\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>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\u002For 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”.\u003C\u002Fp>\n\u003Cul>\n\u003Cli>“Reject” will remove the application data from the site and never submit it to your ATS system.\u003C\u002Fli>\n\u003Cli>“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.\u003C\u002Fli>\n\u003Cli>“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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Application Screening will be powerful for users who are experiencing high volumes of unqualified candidates and\u002For spam applications. It is also useful for users who wish to more finely manage their ATS database.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Enhanced Logging\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>All logged items are now assigned a “Severity” by the developers. Severity are levels of importance, and are, least important to most important, are:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Note, to log items which are extremely detailed pieces of information for debugging and validating function.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>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\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003Cli>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.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>Along with this enhanced logging functionality, come the following highlights:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>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”.\u003C\u002Fli>\n\u003Cli>Added filter \u003Ccode>matador_activity_log_verbose\u003C\u002Fcode> 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.\u003C\u002Fli>\n\u003Cli>Enhancement: Four new constants are now supported related to logging. Defining these in a \u003Ccode>wp-config.php\u003C\u002Fcode> file will give a site developer power to override and hide the associated user settings:\u003C\u002Fli>\n\u003Cli>\n\u003Cul>\n\u003Cli>\u003Ccode>MATADOR_LOGGING_ENABLED\u003C\u002Fcode> allows developers to turn on Matador Activity Logging.x\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cul>\n\u003Cli>\u003Ccode>MATADOR_LOGGING_DAYS\u003C\u002Fcode> allows developers to define the number of days of logs to keep and removes the setting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cul>\n\u003Cli>\u003Ccode>MATADOR_LOGGING_SEVERITY\u003C\u002Fcode> allows developers to define the logging severity level and removes the setting.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cul>\n\u003Cli>\u003Ccode>MATADOR_LOGGING_VERBOSE\u003C\u002Fcode> allows developers to configure whether arrays of metadata related to the action spawning the log entry should be printed into the logs.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Enhancements & Bugfixes\u003C\u002Fh3>\n\u003Cp>\u003Cstrong>Jobs\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>“Sync” job button is added to the Block Editor view of the Job Posting to ensure feature parity with the older Classic Editor.\u003C\u002Fli>\n\u003Cli>A Job Archive will now only be available via the front-end UI if the setting for an archive is turned on.\u003C\u002Fli>\n\u003Cli>Optimized database calls around the get job by ID function for Bullhorn. Four database calls are now optimized down to two.\u003C\u002Fli>\n\u003Cli>Fixed an issue where the jobs shortcode would not accept values from the \u003Ccode>jobs_per_page\u003C\u002Fcode> attribute. This is actually a change to support a long-time error in documentation, as docs described \u003Ccode>jobs_per_page\u003C\u002Fcode> while \u003Ccode>jobs_to_show\u003C\u002Fcode> was the intended attribute name.\u003C\u002Fli>\n\u003Cli>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 when failing to find a post meta value for the field. This brings it in line with the behavior of other conditionals and in parity with its documentation. Further, the function was calling esc_html() on data, and some data was stored as an object, which was resulting in a fatal error. This method now detects if the retrieved metadata is an object or array and avoids the error. Finally, if the retrieved data is an object and has a name property, then the is returned as the meta value. To get the full object, use \u003Ccode>get_post_meta()\u003C\u002Fcode> instead.\u003C\u002Fli>\n\u003Cli>Fixed an issue causing Matador Jobs Lite sites to not have access to Salary related settings from the 3.8.x family of patches. These settings have been extended to Lite users.\u003C\u002Fli>\n\u003Cli>REST API is enabled for Matador Jobs Job Postings.\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cstrong>Taxonomies (Locations, Categories, Etc)\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cul>\n\u003Cli>A new “auto suggest” input type for taxonomy search is now available: text input with datalist. This input type uses existing taxonomy terms to autosuggest values to users as they fill in the input. By default, this feature is not enabled to maintain backward compatibility  …\u003C\u002Fli>\n\u003C\u002Ful>\n","Connect your WordPress site with your Applicant Tracking System. Cache job data locally and display it with style inside your WordPress theme.",20,12480,"2025-05-07T00:01:00.000Z","6.8.5","5.5.0","8.1",[75,76,77,78,79],"ats","bullhorn","career-portal","job-board","oscp","https:\u002F\u002Fmatadorjobs.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fmatador-jobs.3.9.9.zip",{"slug":83,"name":84,"version":85,"author":5,"author_profile":6,"description":86,"short_description":87,"active_installs":88,"downloaded":89,"rating":38,"num_ratings":38,"last_updated":90,"tested_up_to":91,"requires_at_least":92,"requires_php":93,"tags":94,"homepage":100,"download_link":101,"security_score":102,"vuln_count":38,"unpatched_count":38,"last_vuln_date":61,"fetched_at":40},"fluid","Fluid","1.0.0","\u003Cp>\u003Ciframe loading=\"lazy\" title=\"Publishers Expand Your Monetization Reach with Fluid.\" src=\"https:\u002F\u002Fplayer.vimeo.com\u002Fvideo\u002F283521499?dnt=1&app_id=122963\" width=\"750\" height=\"422\" frameborder=\"0\" allow=\"autoplay; fullscreen; picture-in-picture; clipboard-write\">\u003C\u002Fiframe>\u003C\u002Fp>\n\u003Ch3>Expand Your Monetization Reach\u003C\u002Fh3>\n\u003Cp>Capture revenues beyond advertising and traditional paywalls. Fluid is a new revenue partner for publishers. Fluid enables you to create new direct revenues from your readers and audience.\u003C\u002Fp>\n\u003Cp>With Fluid readers can pay to access a single article, video and more. You decide. Fluid is completely turnkey.\u003C\u002Fp>\n\u003Cp>Existing Fluid users (i.e., consumers) can pay to access content on your website with just a couple clicks. Simple, frictionless.\u003C\u002Fp>\n\u003Ch3>Publisher Features\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>Set your price-per-article (or single piece of content)\u003C\u002Fli>\n\u003Cli>Enable Fluid Gateway across your entire website or only when an ad-blocker is detected\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Join Our Exclusive Launch Partner Program\u003C\u002Fh3>\n\u003Cp>Gain early access, get preferred terms, white glove service and more. We are inviting a few select partners to participate in our exclusive Launch Partner Program. For more information and to sign-up go to \u003Ca href=\"https:\u002F\u002Fwww.fluid.us\u002Fpublishers\u002Fpartners-program\" rel=\"nofollow ugc\">Fluid Launch partner Program\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Set-Up Costs\u003C\u002Fh3>\n\u003Cp>Free for publishers. No cost to you, we will cut you the checks.\u003C\u002Fp>\n\u003Ch3>Why Fluid?\u003C\u002Fh3>\n\u003Cp>Current paywalls and subscriptions don’t (necessarily) scale for the majority of publishers. However, publishers need a pathway to monetize consumers directly. In fact, when we surveyed consumers most are willing to pay something to access a single piece of content if given the means.\u003C\u002Fp>\n\u003Ch3>Learn More About Fluid\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fwww.fluid.us\u002Fpublishers\" rel=\"nofollow ugc\">https:\u002F\u002Fwww.fluid.us\u002Fpublishers\u003C\u002Fa>\u003C\u002Fp>\n","WordPress Integration for Fluid.us mircopayment Fluid is a new revenue partner for publishers. Capture revenues beyond advertising and traditional pay …",10,1423,"2018-08-07T12:52:00.000Z","4.9.29","4.4","5.6",[95,96,97,98,99],"accept-payments","micro-payments","micropayments","payments","paywall","https:\u002F\u002Ffluid.us","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Ffluid.1.0.0.zip",85,{"slug":104,"name":105,"version":106,"author":5,"author_profile":6,"description":107,"short_description":108,"active_installs":88,"downloaded":109,"rating":38,"num_ratings":38,"last_updated":110,"tested_up_to":111,"requires_at_least":112,"requires_php":27,"tags":113,"homepage":116,"download_link":117,"security_score":102,"vuln_count":38,"unpatched_count":38,"last_vuln_date":61,"fetched_at":40},"wp-password-protect-publication","WP Password Protect Publication","1.0.2","\u003Cp>A simple plugin that adds a password to the publication metabox. This is to help avoid accidental publication.\u003C\u002Fp>\n\u003Cp>Think of obituaries that you keep updated but you don’t want to get published by mistake!!!\u003C\u002Fp>\n\u003Cp>The password component is loaded onto the editor for posts and pages by default.\u003C\u002Fp>\n\u003Cp>Use the filter “wp-password-protect-publication-supported_post_types” to adjust the supported post types.\u003C\u002Fp>\n","Add a password file to the publication metabox to protect against accidental publication of drafts or updating of published post and pages",1522,"2023-07-24T14:09:00.000Z","6.3.0","3.0.1",[114,115],"password","protect-publication","http:\u002F\u002Fbearne.ca","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-password-protect-publication.1.0.2.zip",{"slug":119,"name":120,"version":121,"author":5,"author_profile":6,"description":122,"short_description":123,"active_installs":88,"downloaded":124,"rating":38,"num_ratings":38,"last_updated":27,"tested_up_to":91,"requires_at_least":125,"requires_php":27,"tags":126,"homepage":132,"download_link":133,"security_score":60,"vuln_count":38,"unpatched_count":38,"last_vuln_date":61,"fetched_at":134},"wp-vote","WP Vote Lite","1.2.0","\u003Cp>If your company or organization holds meetings that require that a pre-determined percentage of members must vote for any resolutions to carry,\u003Cbr \u002F>\nour WP Vote plugin can help you achieve quorum by allowing your members to vote online.\u003C\u002Fp>\n\u003Cp>WP Vote records and creates reports on who voted, when they voted and how they voted.\u003C\u002Fp>\n\u003Cp>It is also designed to handle online proxy ballots.\u003C\u002Fp>\n\u003Cp>There is a PRO version that have move voter and Question Types along wwith inport of voters and export of results contact paul@bearne.ca for upgrades.\u003C\u002Fp>\n","Online voting system for minuted meetings.",2914,"4.5",[127,128,129,130,131],"elections","proxy-vote","quorum","vote","voting","http:\u002F\u002Fwp-vote.com","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fwp-vote.1.2.0.zip","2026-03-15T10:48:56.248Z"]