WP Job Manager Field Editor – sMyles Plugins https://plugins.smyl.es WordPress and WHMCS Plugins Mon, 08 Apr 2019 19:33:27 +0000 en-US hourly 1 https://wordpress.org/?v=4.6.14 WP Job Manager Field Editor 1.8.9 Released – Multiple Auto Ouput, Sortable Uploads, HTML5 Required, WPJM 1.32.0+, and more! https://plugins.smyl.es/release-announcements/wp-job-manager-field-editor-1-8-6-released-multiple-auto-ouput-sortable-uploads-wpjm-1-32-0-and-more/ https://plugins.smyl.es/release-announcements/wp-job-manager-field-editor-1-8-6-released-multiple-auto-ouput-sortable-uploads-wpjm-1-32-0-and-more/#respond Tue, 05 Feb 2019 23:28:12 +0000 https://plugins.smyl.es/?p=166281 Today I am happy to say that I have released a long awaited updated for the Field Editor plugin, version 1.8.9, which adds support for WP Job Manager 1.32.0+, the ability to select multiple auto output locations, sortable file uploads, and mobile support for multiselect fields  — including dynamic child taxonomy feature, conditional logic, and  more.  See the full changelog here for all updates, fixes, and changes.  Below i’ll explain all the updates, and how compatibility is being handled for WP Job Manager 1.32.0+ for the time being.

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

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.

WP Job Manager Field Editor HTML5 Required Validation iPhone Fill Out Field

iPhone Fill Out Field

WP Job Manager Field Editor HTML5 Required Validation iPhone Select an Item

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

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

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

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

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

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

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

https://plugins.smyl.es/release-announcements/wp-job-manager-field-editor-1-8-6-released-multiple-auto-ouput-sortable-uploads-wpjm-1-32-0-and-more/feed/ 0
WP Job Manager Field Editor 1.8.5 – Dynamic Taxonomy Child Dropdowns, Exclude Terms, Output CSV, and more! https://plugins.smyl.es/blog/wp-job-manager-field-editor-1-8-5-dynamic-taxonomy-dropdowns-exclude-terms-output-csv-and-more/ https://plugins.smyl.es/blog/wp-job-manager-field-editor-1-8-5-dynamic-taxonomy-dropdowns-exclude-terms-output-csv-and-more/#respond Sat, 03 Nov 2018 20:20:38 +0000 https://plugins.smyl.es/?p=162582 I’m happy to say that today is the release of version 1.8.5 of the WP Job Manager Field Editor plugin, which includes numerous highly requested features, bug fixes, enhancements, and more!  At the top of the list is the new Dynamic Taxonomy Child Dropdowns, which I have been working on for well over 4 months!  Dynamic Taxonomy Child Dropdowns allow you to customize any single or multiple select taxonomy fields, to dynamically show children terms, in a separate, completely customized, and dynamically shown dropdown!  Here’s what it looks like in action:

WP Job Manager Field Editor Dynamic Taxonomy Child Dropdowns Demo

WP Job Manager Field Editor Dynamic Taxonomy Child Dropdowns Demo

Dynamic Taxonomy Child Dropdowns

Please see the documentation page (which includes tutorial video) for Dynamic Taxonomy Child Dropdowns, here:

Dynamic Taxonomy Child Dropdowns

I appreciate everyone’s patience while I worked on getting this new feature released.  Unfortunately it was not an easy task, and ended up running into all kinds of issues with compatibility, and functionality … and instead of shipping a broken version of the plugin, I spent many sleepless nights testing, updating, and working on this latest release.

Template Updates

Both the term-select-field.php and term-multiselect-field.php templates have been updated in this release, if you’re using your own custom template overrides, please make sure you update them to match the new versions, to support the dynamic child dropdowns.

Previous versions of Field Editor did not include the term-select-field.php so please make sure you check any template overrides.

Other Updates

Included with this update are a few other features (a couple listed below), you can find the full list on the changelog.

Advanced Field Configuration Tab

Advanced Field Configuration Tab

Exclude Terms

Under the advanced tab you will now also see a text box where you can enter in TERM ID values to omit from showing in the dropdown.  To specify multiple terms, separate them with a comma.

Output CSV

For multiple field types you will also now see an “Output CSV” option.  Enable this to output multiple values as Comma Separated Values (instead of linebreak, or wrapping with value wrapper)



Final Thoughts

I hope you guys are as excited to use these new features, as I am to release them.  This release adds over 2,200 lines of new code base, and has been in the works for numerous months, testing, debugging, and working on compatibility.

I have tested standard functionality in Jobify, Listify, Listable, Listee, WorkScout, and all standard WP Job Manager templates without any issues.  If you do come across a problem, please be sure to open a support ticket and let me know, so I can work on a fix for it.

https://plugins.smyl.es/blog/wp-job-manager-field-editor-1-8-5-dynamic-taxonomy-dropdowns-exclude-terms-output-csv-and-more/feed/ 0
Field Editor 1.8.1 Release – Logic Animations, Shortcodes, Fixes, and More! https://plugins.smyl.es/release-announcements/field-editor-1-8-1-release-logic-animations-shortcodes-fixes-and-more/ https://plugins.smyl.es/release-announcements/field-editor-1-8-1-release-logic-animations-shortcodes-fixes-and-more/#respond Wed, 11 Apr 2018 22:13:01 +0000 https://plugins.smyl.es/?p=152815 Today, April 11, 2018, version 1.8.1 of the Field Editor addon for WP Job Manager has been released.  This update includes new features including the ability to customize the conditional logic animations using Velocity.JS, a new if_custom_field shortcode, passing custom values for logic through a filter, and more!

Conditional Logic Animations/Transitions

This release includes an update that adds the ability to configure your conditional logic transitions/animations, using the very popular and widely used, Velocity.JS framework.   This is completely optional, and you can leave this disabled to maintain the origin/existing show/hide handling … but if you would like to customize it, hop on over to the field editor settings page, and enable this new feature and give it a try!

if_custom_field Shortcode

If any of you started using the new conditional shortcode features available in the Field Editor addon, you will be very happy to know that this release adds a new shortcode (3 actually), to alleviate the initial bug when using conditional shortcodes, due to the fact that you can’t nest shortcodes inside each other ( see here for more details ).

Well, i’m happy to say that you now have 3 available shortcodes to use, if_custom_field, if_resume_field, and if_job_field.  All three of these shortcodes do exactly the same thing, but having multiple available, allows you to nest if statements, inside other if statements ( see docs for more details ).

This also introduces a much easier to use syntax for the shortcodes, as you no longer have to make sure that you use the right attribute/argument based on the field type.  Previously, if you wanted to do a check on a single value field (non-taxonomy, non-multivalue), you had to use the if_contains or if_equals argument … and with multiple field types or taxonomies, you had to use has_value or has_value_containing.. well no more of that!

The new syntax will automagically determine the correct method to use, and will do everything for you.  All you have to do now is choose between using equals or contains:

[if_custom_field key="job_category" equals="north"]
North Category!

Head on over to the conditional shortcodes documentation for more details, including examples and more!

Admin Only fields in Conditional Logic

This release also fixes a bug in the conditional logic configuration area, where you were originally able to select an admin only field, to be used in the logic … which technically would never work correctly, as admin only fields never exist on the frontend .. so when the logic attempts to process and check the value, there’s no way to do that.

One would think, being as it’s an admin only field, for both security and peace of mind ..you would never want that visible or stored on the frontend of your site.  Well you would be surprised, as I got some grief from a few clients saying that the plugin had bugs I wasn’t fixing … which I can understand … somewhat … but I always take security and optimization of my plugins VERY seriously, and there’s no way i’m going to expose admin only fields on the frontend by default.

So with that said, you can no longer select admin only fields to be used for conditional logic checks …. by default, that is.

I still understand there may be a need to expose certain fields for functionality, or logic handling .. and those fields may not be something that needs to be “secured” from the user (it could be a value of yes, or no, etc).

That is why I have added multiple ways to enable admin only fields, to pass values to frontend for all admin only fields, for only certain ones, and more.

Head on over to the Conditional Logic Admin Only Fields documentation for more details, and examples.

Other Misc Fixes and Updates

You can see all of details for bug fixes, and updates, located on the Changelog page for WP Job Manager Field Editor

https://plugins.smyl.es/release-announcements/field-editor-1-8-1-release-logic-animations-shortcodes-fixes-and-more/feed/ 0