Why do I need this?

As mentioned above, themes or even other plugins (like my Field Editor) can add custom fields to WP Job Manager, and when these fields are added, they can potentially be optional fields (OR if you create/save from the admin area, regardless of whether they are optional or not).

If they are optional (or you enter no value from admin area), when WP Job Manager saves a listing it will save that meta value regardless of what the value is (even when it’s empty).  By using this plugin when the listing is saved or updated, it will automatically remove those empty meta values.

Supported Listing Types

• Job Listings
• Resumes (Resume Manager addon)
• Cariera Theme Companies
• Company Manager
• MAS Company Manager
• Techbrise/Astoundify Company Listings

Where can I get a copy?

You can find this for free on the WordPress plugin repository (just search from Plugins > Add New on your site), or at the link below:
https://wordpress.org/plugins/empty-meta-cleanup-for-wp-job-manager/

Empty Meta Cleanup for WP Job Manager

The entire codebase (besides existing cleanup) is open source, and you can report bugs or issues on the GitHub project:
https://github.com/tripflex/wp-job-manager-empty-meta-cleanup

How do I set it up?

There is pretty much no real setup required for this, besides activating it for whatever listing types you want to.

First step is to get a copy of the plugin as mentioned above, and after you activate the plugin you will see a new Meta tab in the associated settings area.

You can see an example of this in the screenshots below.  You can enable or disable the automatic removal for any associated listing type that you would like, and the plugin includes support for Resumes and Companies as well!

Enable/Disable in Job Settings Area

Enable/Disable in Company Settings Area

Enable/Disable in Resume Settings Area

What about existing meta?

If you have an active Field Editor license (version 1.12.2 or newer), there is custom integration included that will scan your entire database for any of these empty meta values, provide you with a list of found values, and then you can confirm to remove them if you wish.

When you have the Field Editor plugin active on your site (version 1.12.2 or newer), when visiting the Meta tab in the associated settings page (Job/Resume/Company), instead of seeing just a checkbox to enable/disable the meta cleaner on save/update, you will also see integration to scan the database for existing empty values.

YOU CAN ALSO ADD CUSTOM KEYS TO SEARCH … just manually enter in the key you want to search for, and then click on it in the dropdown to add to the list to scan for.

You can see an example of this in the screenshots below:

Existing Empty Meta Removal Scan

Empty Meta Removal Results

Requires Field Editor 1.12.2+
Support will be included in the next release of the Search and Filtering plugin as well (TBD)

What else can I do to speed up and optimize my WP Job Manager site?

Install the Index WP MySQL for Speed plugin!!  WordPress natively is not meant for the type of searching and handling required by some large (or even smaller) sites.  Use this plugin to help add indexes and speed up your site:

Index WP MySQL For Speed

As always before using this plugin PLEASE make sure you take a full site and database backup, and PLEASE test on a non-production site to make sure the plugin works the way you want!  

There are numerous filters available if you have specific meta keys you want to omit from the auto removal, check the github project for more details.

Prevent saving empty meta in database

Basically what this does is it prevents any value for a meta field, that is an empty string, or an empty array, from being saved to the database, ultimately meaning your database should only store actual values.  The reason this was not something already done is because of the way the core WP Job Manager plugin works.  It does not check if the value should be saved based on “what” the value is, it just checks if it was submitted with the form and saves it.  For example, if you have a field that is not required, when it is submitted through the form, it is still saved to the database as an empty value (by the core WP Job Manager plugin).  This update adds handling in my plugin that will check every custom or customized field for this.  Please note you must have saved the field using my plugin for this functionality to work on the field.  Even if you don’t want to make any changes to the field, just click on Edit in my plugin, and then save, and it will save the field configuration and the field will now be a “customized” one (even if you didn’t change anything).

This should help alleviate unnecessary database rows and ultimately make your site run faster!  This handling works both in the admin and frontend.  If you want to see it in action, enable the Post Meta Inspector from Debug tab (Field Editor Configuration Page) and try it out in the admin area!

If you want to disable this in the Frontend or Admin area, just add this your child theme’s functions.php file (omit the <?php, there only needs to be one at the top of the functions.php file),  or using the Code Snippets plugin:

https://gist.github.com/tripflex/b2ef3cc6fc1363d0f9cc39af0ee47eac

Include Field Meta in REST API

As there are many mobile apps starting to come out soon (Cariera), some of them will use REST API (or maybe even you do for external services).  A new setting is available under the “Advanced” tab when editing a field, where you can enable this setting.  Please note you will not see this setting for any taxonomy fields as those should already be handled natively depending on how you setup/created custom taxonomies.

Multiple Meta Keys in Auto Populate

You can now use multiple meta key in the auto populate feature!  All you have to do is separate them by a space and the plugin will handle the rest.  As an example, if you wanted to populate a field with a user’s full name, you would just enter first_name last_name in the auto populate field (take note of the space).

Astoundify Companies Plugin

This release adds support for the Astoundify Companies Plugin (yes there’s another one out there), albeit in beta though so please make sure to report any issues you have!  Unfortunately for me with all of the different company plugins out there, and integrations in different themes, it makes it much more difficult to maintain compatibility (or even add it), as they are using different post types, or many other changes/differences that I have to make sure to account for.  This release adds the initial support for the Astoundify version, but there unfortunately is only about 3 or 4 auto output locations available (due to the plugin itself not having hooks in many locations).

If you’re still looking for a Companies plugin I would recommend the free MAS Companies one or the Cariera theme which has it built in, as Astoundify for some reason removed me from their Slack Channel.  Support for this plugin is provided for clients who are already using this plugin, if you are not already, i do not recommend it.

If anything I suggest the Cariera theme as this developer is very active and we stay in constant contact to maintain compatibility.

Other Updates

There’s numerous other updates and fixes included with this release, head on over to the changelog to check them out!

As many of you probably already know, I recently got married in July in Colorado to my beautiful wife Brooke.  Being as though we were living in Orlando, having an out-of-state wedding ended up being way more than we expected (not only in cost, but in time we would have to dedicate to it).  Even having a wedding planner, things just seemed to consistently come up left and right for issues that we would need to deal with.

After getting married, my wife was offered an awesome position in Atlanta for work, and we immediately had to start the process of moving to Atlanta.  As we owned a house in Orlando, our first step was getting all the issues around the house repaired and ready to put on the market.  That along with having well over 50+ showings meant that I constantly had to leave my office to setup at a friends house or coffee shop around the corner.

At that time, the housing market was for sure booming.  Within a week we had 15+ offers on the house, one of which was a cash offer above what the house would appraise for … with the understanding that we would have to be out in two weeks.  Living in this house for over 10+ years and being a hacker/maker/tinkerer you start to accumulate things along the way.  This meant I had to scramble to pack up and clean the entire house ASAP, not to mention the fact that we hadn’t even found a place to move to in Atlanta yet

Luckily for us we had friends who lived a little bit outside of Orlando that were willing to let us move in with them for a bit, until we could find a new location to move to.  This was the first location we moved into after selling the house, only to find out that the internet was spotty and could not support more than a few people using it at a time.  We had another service provider come out and install a new service for internet, which resolved that problem, but unfortunately that was just the start of the issues we would have.

After a few days we started to realize that this situation probably wasn’t going to work out for us.  Having to drive to Atlanta to view houses, then come back and deal with OCD the person we were living with, and then our animals … it resulted in the stress causing my wife to cry almost daily dealing with everything.  We have an older lab who has live in Florida his entire life (so he has no idea what stairs are), and two cats.  The couple we were staying with we found out were allergic to cats (would have been nice to know at first), so the cats had to stay in one bedroom, and our dog had to stay downstairs (before he would sleep with us every night).

At this point I realized this situation wasn’t going to work for us and I had to figure something out.  After about a week of searching, I was able to find an airbnb in Atlanta that wasn’t $8000 a month, and had a master on the main level that would work for our dog.  We immediately booked it and then had to pack up everything from the house we were staying in, and then drive the animals and all our stuff up here in a few different trips.

This is the current situation were in, still looking for places to rent or buy but at least for now we have something that is comfortable, has internet, and I can finally get back into the routine of work and not having to deal with everything else coming up.

The unfortunate part about all of this is how much of my time it has taken up, ultimately causing extensive delays in support responses and plugin updates.

Then to add to everything else, it seems that the database for this site got corrupted for a few days, which I didn’t notice while all this was going on, and had to do an incremental restoration (for pages, products, etc — all orders and subscriptions did not have issues).  Fun stuff

I sincerely apologize if you were a client that has been affected by this, and I promise to do everything I can moving forward to make this right and catch back up.  I really do appreciate your understanding and patience while i’m going through these very stressful and difficult times, and will do everything I can to make sure that this does not happen again.

Thank you again for supporting my plugins and your patience!

UPDATE 10/8/2021:
We submitted an offer on a house that was accepted, inspection was today and went great, we’re hoping to close before the end of the month, so things are looking on the up and up!  I’ve already caught back up with all tickets and am working on needed updates to be released.  Keep an eye out as there will be updates coming out shortly for almost every plugin.  ‘

I really do appreciate everyone’s kind words and patience during this process, I was not expecting the kindness and understanding from everyone in their tickets, you guys are amazing and i’m excited to get back to business and start releasing some of these new features i’ve been working on for the past 6+ months!

This plugin functions pretty much the same as the Job Alerts addon plugin (from wpjobmanager.com), but specifically for Resumes.  There has been numerous requests from clients for this plugin, I hope you guys enjoy it and can’t wait to see what you’re able to build with it!

You can get a copy of the plugin at the link below:

https://plugins.smyl.es/wp-job-manager-resume-alerts/

https://plugins.smyl.es/wp-job-manager-search-and-filtering

It’s hard to believe, but this plugin has been in development for almost 2 years now, and as some of you probably already know if you’re using my plugins, i’m very detailed and picky about having amazing features, that work correctly. I am very happy to say is probably one of the ones i’m most excited about!

Over the past 7 years of developing and supporting both WP Job Manager (core plugin), and my WP Job Manager addon plugins, i’ve helped over 20,000 users to build out their own site using WP Job Manager and/or my addons, and I used that experience to build out one of my best plugins yet.

If there’s one thing i’ve learned from those users, and those who have provided me with feedback — getting your site setup for the first time, can be a daunting and sometimes challenge task. 

As such, I put extra effort and time into building a plugin that is easy to setup, configure, and change, right after installation.  Frontend editing is the future of websites, and having a drag and drop UI interface for this plugin was a must.  A lot of time was spent working with theme developers and working on compatibility to make sure compatibility was available right out the gate.

I want to thank both the Cariera and WorkScout developers as they worked with me for well over a month to add updates and compatibility changes specifically for the Search and Filtering plugin.

This plugin came completely out of the requests and feedback I received from clients, asking about this handling in the Field Editor plugin, and also requesting custom work for specific customizations.  The reason this was not something built into the Field Editor plugin, was because doing so would not bring justice to the Search and Filtering fields.  Had I tried to implement a feature for this in the field editor plugin, it would have resulted in a sub-par feature set, and essentially very limited capabilities and tons of issues.

Thankfully I did not go that route, as after getting in deep with development I realized how much work would be involved with this (5x what I expected).  The benefit of doing this as well, is all the amazing features i’m able to bring to you guys in this plugin.  My goal with building plugins now is to make it is easy as possible on the end user (you) to build your WP Job Manager site, with limited to no knowledge of WordPress or WP Job Manager.  Everybody starts somewhere, right?

One of the benefits of how I built out this plugin as well, is how I used a modern frontend JavaScript framework for the majority of the heavy lifting.  This allows me to add new field types, and features with very limited development work, that can be easily integrated into the plugin.  While that is great for me, and you (because features get released quicker), that’s not the best part!

The BEST part about this, is that I have set this up so the plugin ONLY loads the javascript files needed for your site, based on your setup/configuration, and the fields that you’re using! Yes, you read that right, this plugin will dynamically load the required javascript files, based on the fields you’re using!  You would assume this would be standard practice, but for WordPress it is not.  The majority of sites that take very long to load or are excessive in size, is because of the amount of unused code that is being loaded on the site, because the developer of that theme/plugin has to write their code to support all features, and all possible use case situations.

For example, if you’re not using the Range Slider field type, that javascript code will not be loaded on your site.  If it is being used, the javascript file will be “lazy” loaded (meaning loaded after the page initially shows) using a method called “chunking”.  While this may not seem like a big deal, when you add up every single field type, and every bit of added functionality, it can decrease the size of the page by over 80%!  This is how i’m able to make it so the initial page load for Search and Filtering, is only 180kb.  That’s smaller than most images!  Had every field type, and functionality been included, it would be almost 1mb in size!

Same with when you’re in editing mode, because a lot of extra functionality is required, that functionality is only loaded for admins when they have permission to edit the sections.  The end result is faster loading times for your site, and happier end users.  This took a while to get working correctly with WordPress, but it was well worth it.

I’m so excited about this release, and can’t wait to see what kind of amazing things you guys come up with!

The initial release of the plugin comes with a ton of field types, including Standard Text Field, Locate Me (Geolocation) Text Field, Checkbox, Single Select Dropdown (Select2 or Element UI), Multi-Select Dropdown (Select2 or Element UI), Radio Buttons, Slider, Range Slider, Checklist, Button, Custom HTML Content, Spacer Grid Field, and WordPress Tag Cloud!

Some other field types in development right now, soon to be released, include:

• Google Map (with placement markers) – Estimated Release Jan 16-31, 2021
  – This can be used to show a map with listing locations (if theme does not already support one)
• Google Places Auto Complete/Suggest – Estimated Release Jan 9-16, 2021
• Hidden Field Type – Estimated Release Jan 9-16, 2021
• Date Picker (Range & Single) – Estimated Release Jan/Feb 2021
• Time Picker (Range & Single) – Estimated Release Jan/Feb 2021
• Star/Rating – Estimated Release Jan/Feb 2021
• Switch – Estimated Release Jan 9-16, 2021

After being heavily tested during the beta period, i’m also happy to say that this new frontend editing UI from Search and Filtering plugin, is also being built into the Field Editor v2 (to be released this year)!

I won’t go into all the details in this blog post, but head on over to the product page and check it out!

https://plugins.smyl.es/wp-job-manager-search-and-filtering

First and foremost, MAKE A BACKUP! After backing up your current copy of the Field Editor plugin, MAKE SURE that you thoroughly test the new version!

Reason being, this version switches from using Chosen.js to Select2, which the conditional logic, dynamic child taxonomies, and multiselect fields all rely on.  This update also changes a bit how fields are passed around in the plugin, as well as how auto output is handled.

There shouldn’t be any issues, but depending on your situation (theme, custom configuration, overrides, etc) there could be issues with the switch to Select2 (more details below).

This update also requires WP Job Manager to be a minimum version of 1.32.0 (released January 2019)

Chosen.JS to Select2

As mentioned above, this version switches from using Chosen.js to Select2 (which is standard for WP Job Manager now), the only reason that Chosen.js has been used up until now was I had to rewrite a lot of the conditional logic and dynamic child taxonomies code that was originally coded for Chosen.js.

With the switch to Select2, this opens up the ability for future features like the ability for users to add custom taxonomies from the submit form (coming soon), as well as mobile support for multiselect items, and ultimately better looking select boxes.

If at any time you want to switch back to using Chosen.js, you can do so via the Field Editor Settings page as shown in the screenshot below.  Enable the setting “Chosen”.  

Disable Select2 and use Chosen.JS

This is only recommended as a last resort if you’re having issues.  If you do have problems, please open a support ticket and let me know.  This update also required updates to these field template files:

• multiselect-field.php
• select-field.php 
• term-multiselect-field.php
• term-select-field.php

Please make sure if you’re using template overrides, that you update yours to support Select2.  Open a support ticket if you need help with this.

reCAPTCHA v2 Invisible

reCAPTCHA v2 Invisible

This release also adds support for “Invisible” reCAPTCHA from Google.  This reCAPTCHA type will automatically handle detecting if Google thinks the user is a bot or not, and will decide whether or not to show the reCAPTCHA challenge, whereas the original supported version was a checkbox that required the user to select it before they could submit a listing.

PLEASE NOTE you MUST configure an invisible API key in the settings if you wish to use this feature.  You can not use the original or any existing reCAPTCHA api keys that you have configured already.  This is very easy to setup, and you can do so from Google’s website.

Invisible reCAPTCHA Configuration

To configure using the invisible reCAPTCHA you can do so by selecting “Invisible” under the Size setting for reCAPTCHA.

You can see an example of this in the screenshot on the left.

Cariera Theme Support

After a lot of requests from clients for support with the Cariera theme and the developer of that theme being very responsive, we have spent a lot of time working together to bring you guys an amazing update with lots of features.

The most important update with the theme support, is the support for the Company Fields which is included natively with the Cariera theme.  The “Companies” included with Cariera is basically the same features that you get from WP Company Manager, which is why the integration and support of WP Company Manager, which was a major undertaking, went hand in hand with the Cariera theme.

Support for Cariera theme also includes formatting and the ability to define custom icons to use when using auto output in the “Job Overview”, “Resume Overview” and “Company Overview” area that you can see in the screenshot on the right.  In the Auto Output configuration this area is the “Meta Start”, “Meta End” and “Meta After” areas (for Job, Companies, and Resumes).

Cariera uses Font Awesome 5 Free icons, you can find them here.  Once you find the icon you want to use, just use the value from class for the <i> element.  For example if the icon would be <i class="fas fa-address-card"></i> then you should enter fas fa-address-card into the classes field in auto output configuration.

WP Company Manager Support

One of the biggest updates from this release (besides Select2) is the support for the WP Company Manager plugin.  You will now see a “Company Fields” menu item under the main Companies menu item, where you can use the Field Editor plugin to configure those fields (conditional logic coming soon).  Pretty much everything below also applies to Cariera theme companies.

You will still see the “Company Fields” sub-menu item under the Job Listings main menu, but those should only be one or two at the most (to configure fields like the “Select Company” on job submit page).  When using WP Company Manager (or Cariera) you should probably never need to edit or add fields here (under Job Listings menu item), as they should all be configured under the main “Companies” menu item for editing fields.

Auto Output

Auto output configuration under these new “Company” fields can be configured to output on both Job Listing pages and Company Listing pages (most commonly on job listings).  You should see all the same auto output locations that you have available under job fields.

Shortcodes

When you want to output a specific “Company” field on a Job Listing, you must make sure that you use the field_group="company_fields" parameter/argument, so the plugin knows that you’re trying to output a field that is actually from the “company” and not from a field called “company_name” saved on a job listing.

[company_field key="company_name" field_group="company_fields"]

PHP

This is exactly the same as above, when using PHP to pull values for “Company Fields” you need to specify field_group in the arguments passed to the function.  For example:

<?php the_custom_field( 'company_specific_field', null, array( 'field_group' => 'company_fields' ) ); ?>

The second argument in that function call is null because we want to let the plugin auto detect the Listing ID to pull that value from.  If you want to pull from a specific listing, pass that value instead of null.

Other Updates

A major fix that came around with the companies handling, was fixing issues with the same meta key being used in different field sections.  This required a bit of work to maintain compatibility (for pulling/displaying values and storing configurations), but is now completely possible.

WordPress 5.5 also introduced removing jQuery Migrate, which some of my older code relied on, this has also been fixed in the latest release.

There are also numerous other tweaks and enhancements made to the plugin while these features above were integrated, which is even more reason to make sure and test your site when upgrading!

You can view the full changelog here

1. You should NOT be testing this on a live production site!  This should ONLY be used on development environments!
2. There is currently no way to “Import” or “Convert” existing listings/companies to be used in the new plugin. I am however working on this feature, and need YOUR feedback to let me know how your existing “Companies” are setup!

Finally, by joining the program you agree to the Beta Terms and Conditions

Specifically — after 90 days the beta version will deactivate itself, so you must keep the plugin updated for it to keep working!

Please also join the chat server at https://chat.smyl.es to discuss issues and problems and provide feedback on the beta plugin!

To join the beta program, sign up here:

https://plugins.smyl.es/wp-company-manager

Overview Video:

1. You should NOT be testing this on a live production site!  This should ONLY be used on development environments!
2. If you are using the Capstone theme (version 1.7.2 or OLDER), there are some required file modifications until the theme developer makes changes to his theme to use the native WP Job Manager get_job_manager_template_part function instead of just get_template_part.Instructions on how you can do this yourself, can be found here:
   https://plugins.smyl.es/docs-kb/capstone-theme-changes-for-search-and-filtering-compatibility/
3. Automatic installation of default search and filtering fields is not included in the beta plugin yet, you MUST download the Default JSON Import Files ZIP and then import the JSON file for your theme (or just the default one if there is no specific one for the theme you’re using).
   Search_and_Filtering_Default_JSON_Files

Finally, by joining the program you agree to the Beta Terms and Conditions

Specifically — after 90 days the beta version will deactivate itself, so you must keep the plugin updated for it to keep working!

Please also join the chat server at https://chat.smyl.es to discuss issues and problems and provide feedback on the Search and Filtering beta!

To join the beta program, sign up here:

https://plugins.smyl.es/wp-job-manager-search-and-filtering

Overview Video:

Importing JSON Files:

Building Default Search/Filters Form:

Overview Video

Signup

If you would like to join the beta program and be notified when it is available, you can do so at the link below:

Search and Filtering Beta Signup

WP Job Manager 1.32.0+ Support

As many of you should already know, as of WP Job Manager 1.32.0+ the core handling for multiselect fields has changed from using Chosen.JS library, to Select2  library.  The last blog post I created described in extensive detail why this caused such an issue for the Field Editor plugin, and included instructions on how to downgrade to prior version.

With the release of version 1.8.9, you no longer will need to downgrade to an older version of WP Job Manager!

Temporary Chosen.JS Compatibility

While version 1.32.0+ of WP Job Manager does switch to using Select2 natively, it does still include the Chosen.JS library for compatibility with themes/plugins that require it.  For this release of the Field Editor plugin, the easiest way to handle compatibility while I finish up Select2 integration, was to have WP Job Manager multiselect fields to fallback to using Chosen.JS.

This means you will not need to worry about upgrading to the latest version of WP Job Manager, and having issues with conditional logic, dynamic child taxonomies, or multiselect specific field configurations like max selected, and more.

This release also adds and updates support for mobile devices, and all the features included with the Field Editor plugin, as that was one of the main reasons behind the core switch from Chosen.JS to Select2.  See the “Mobile Device Support” section below for more details.

This does not cause any issues with fields like searching for user in admin area that uses Select2.

If you want to read more specifics on the details of how this was done, see this documentation article.

HTML5 Required Validation

WP Job Manager Field Editor HTML5 Required Validation Scroll To

Enabling HTML5 Required validation allows users to be instantly notified about required fields, instead of having to wait for the page to reload showing the error at the top.

Unfortunately due to numerous compatibility issues with browsers and devices, as well as the fields themselves (wp editor, taxonomy dropdown), the required validation only worked in previous versions on a couple of fields.  With this release I have added numerous lines of code and specific handling to support all the included field types with this plugin.

I’ve also added code to automagically scroll the browser window, centering the invalid field to make it easy for the user to know what field needs to be updated.  See the screenshot on the top/left for an example of this new feature.

iPhone Fill Out Field

iPhone Select an Item

This also includes support for mobile devices, which allows the native browser to direct the user to what field is required and needs to be filled out.

As you can see in the screenshots on the right, iPhone natively does this as well.

These examples include standard text fields, as well as all the other fields, including dropdowns, multiselect, and even WP Editor (which is unheard of!)

iPhone will prompt the user to select an item, fill out a field, and makes the user experience much better in regards to required fields!

This also means no page reloads required just to see invalid fields!

WP Job Manager Field Editor HTML5 Required Validation WP Editor

As mentioned above, this release also includes integration with the WP Editor field type for required fields as well.  This did take some time to figure out, and work to integrate (as there’s nothing online I could find about anybody else doing this)

In order to do this, I had to add the wp-editor-field.php template file to the Field Editor plugin, adding customizations to handle this.

I’ve also added a filter to disable HTML5 required on WP Editor fields (while retaining support for other fields), in the instance that you have issues with this specific WP Editor required integration.  Contact me if you need help with this.

WP Job Manager Field Editor HTML5 Required Setting

Enabling or Disabling the HTML5 required feature is very easy to do, just head over to the Field Editor Settings page, and under the Fields tab, you will see the setting (which can also be seen in the screenshot on the right).

Support was also added in this version for the WP Editor, Taxonomy Select, Taxonomy Multiselect, Flatpickr Date & Time, Multiselect, and Select field types.

Please make sure to test your form if you are using HTML5 required as this is a major update for the handling!

If you are using the Dynamic Taxonomy feature, the HTML5 required handling is required on those specific fields and even if this setting is disabled, it will still be used on only the dynamic taxonomy fields (this is required for this feature).

Multiple Auto Output Locations

WP Job Manager Field Editor Multiple Auto Output Locations

This release also adds a new feature requested frequently by clients, which is the ability to select multiple auto output locations for a single meta key/field.

After upgrading, under the Output tab you will now see another field Additional Output where you can select any additional auto output locations you would like the field to be output at.

I am working on an advanced version of this feature, allowing you to specify custom configuration for each auto output, but in the meantime I went ahead and included this in the latest release until I can finish that feature up.

Sortable Image/File Upload Fields

WP Job Manager Field Editor Sortable File/Image Uploads

This feature is actually thanks for a couple of my clients that provided methods they used to handle this, which made it very easy to integrate into the plugin.

Originally this was only slated to be included for Jobify and Listify theme, but it should work any theme as long as it uses the standard WP Job Manager file upload template.

When using this feature, specifically with the Listify theme, it allows your users to re-order the gallery images after uploading them.

It should also work with any other themes that use multiple file uploads and rely on the ordering of those images/files for output.

WP Job Manager Field Editor Sortable File/Image Uploads Setting

To enable this feature head on over to the Field Editor Settings page, and under the Fields tab you will see a new setting.

By default this is disabled, so you will have to enable this if you want to have this feature on your site.

After enabling the feature and saving, any AJAX file upload fields should now be sortable using drag and drop.

Mobile Device Compatibility

WP Job Manager iPhone Native Select Handling

As mentioned above, the major driving reason behind the core WP Job Manager switch to Select2 from Chosen.JS was for mobile device support.  Chosen.JS natively does not support mobile devices, and relies on the device itself to provide things like multi-select and dropdown selection.

As you can see in the screenshot on the left, iPhone already does a good job of this by providing the select handling natively through the device.  Android also does the same/similar thing regarding select and multiselect fields.  I won’t go into all the details, but there also were numerous issues that had to be dealt with regarding these different mobile devices.

As of version 1.8.9, mobile support has been extended to work with the conditional logic, dynamic child taxonomies, and other features in the field editor plugin, until these features can be moved to Select2.

In this latest release, I spent a bit of time testing and fixing issues with mobile devices, for those who which to stick with Chosen.JS (or older versions of WP Job Manager), until the next major release of the Field Editor which will specifically target and support Select2.

Other Changes

Please see the Changelog for full details on this latest update