Release Announcements – sMyles Plugins WordPress and WHMCS Plugins Wed, 21 Jun 2017 03:54:35 +0000 en-US hourly 1 WP Job Manager Emails 2.1.0 Released! Custom post status, featured/unfeatured, [date] and [time] shortcodes, and more! Fri, 21 Apr 2017 21:47:27 +0000 Today, version 2.1.0 of the WP Job Manager Emails plugin was released, which includes a few bug fixes, some enhancements, and some awesome new features!  Some of the new features include full support for custom post statuses, featured and un-featured email hooks, pending payment to pending approval email hook, [date] and [time] shortcodes, and more!  Below i’ll go over all of these new features, bug fixes, etc!

New Features

Custom Post Statuses

As you can see in the image on the right, version 2.1.0 now includes full support for custom post statuses on Job, Application, and Resume post types.  These hooks are dynamically generated based on your custom post statuses and will all show up under the Custom Post Status Action Hooks in the hook dropdown.   This is a major revamp of the post status handling as everything is dynamically generated now, based on custom and default statuses.

WP Job Manager Emails Custom Post Status Hooks

WP Job Manager Emails Custom Post Status Hooks

So as an example, if you added a custom status to Applications, we will call it Rejected, and for keeping things simple in this example, we will say the only default statuses are Interviewed and Hired (default are actually new, interviewed, offer, hired, and archived). The plugin will automatically generate every possible hook between your custom status, any other custom statuses, and the default statuses.

So in our example from above, the new dynamically generated hooks would be rejected_to_hired, rejected_to_interviewed, hired_to_rejected, and interviewed_to_rejected.

Basically it’s customstatus_to_defaultstatus and defaultstatus_to_customstatus.  If you have additional custom statuses, it will also generate customstatus_to_customstatus.

Featured and Un-Featured Hooks

WP Job Manager Emails Featured Un-Featured Hooks

WP Job Manager Emails Featured Un-Featured Hooks

New hooks were added to send emails when a listing is updated and set as a Featured listing from Un-Featured, as well as Un-Featured to Featured listing.

In the image to the left, you can see there is also an available configuration option that will show when you select a featured or un-featured hook from the dropdown, that will allow you to configure to send the email when the listing is initially created.


[date] and [time] Shortcodes

WP Job Manager Emails [date] shortcode custom format example

WP Job Manager Emails [date] shortcode custom format example

Two new shortcodes were also added, [date] and [time], to allow you to output the date or time that the email is sent.  By default the WordPress Date and Time format (from Settings > General) i used to format the output, but you can also very easily customize this.

To customize the format of the output, all you need to do is use the attribute format and then specify a PHP date format to use.

An example of this would be, [date format=”Y-m-d”] which would output in this format: 2017-04-21

The [date] and [time] shortcodes are “technically” doing the same exact thing, I added them both to make it easier for beginners, as if you wanted to, you could include the time format characters in the [date] shortcode (or vice versa) and it would output as you configured it.

Other Features

pending_payment_to_pending email hook and templates

I’ve also added in this release the new pending_payment_to_pending email hook.  This is very useful if you want to send an email after payment has been made on a listing, but is still requiring approval.

Email templates were also added for this hook, and it can be used on both Jobs and Resumes.

New claim created via Admin Area email hook

What’s Next?!

Along with all the new features that have been added, i’ve also started the work on expanding the [if] shortcode, which will soon allow you to extensively customize your email templates.  You will be able to add conditionals (AND,OR), as well as false statements, and some custom function handling.

Soon you will be able to add [if] shortcodes in your email templates, like these (just examples):

// AND conditional logic
[if job_salary AND candidate_available][/if]

// OR conditional logic
[if candidate_available OR candidate_sendall][/if]

// Has "Some Text" in the title somewhere
[if job_title contains('Some Text')][/if]

// Equals exactly
[if job_location equals('Orlando, FL')][/if]

// Greater than or equal to
[if job_salary GTE('50,000')][/if]

The expanded [if] shortcode handling is not available in this latest release, but it will be included in an upcoming release.

I’ve also started handling of core emails as well, which includes the New Account, Lost Password, and a few others, which will be included in the next release as well 🙂


Bug Fixes

This release includes a few minor bug fixes in the last release.  Related to the Claim Listing addon plugin, the admin email was not being sent when a new claim was created, and the hooks were somewhat confusing to users.  This release fixes that issue, and adds a new hook new_claim_created_admin_area that will only be fired when a new claim is created via the Admin area (will not send when created from frontend of site).  The two other Claim Listing email hooks I added “Frontend” to clarify in their description. When you have an email template enabled for one of these emails (frontend ones), it will override and replace the default email sent by the plugin.

The framework used for the dropdowns in the admin area, has also been updated to patch a bug with Internet Explorer 11 where the dropdown would reopen by itself, as well as a bug where there were instances where you may be unable to select a hook from the dropdown.

Code was also added to dequeue the sloppy Bootstrap 3 Shortcodes plugin that enqueues it’s JavaScript on all pages, which caused conflict with my plugin’s dropdowns and javascript.

Fixed a few PHP warnings, issue where using single quotes in the subject line would show the encoded value (') instead of the single quote (it would still send the email with single quote).

There was also an issue with the [listing_url] shortcode which was fixed as well.

]]> 1
WP Job Manager Packages Released! Sun, 29 Jan 2017 10:03:38 +0000 Over a year in the making, WP Job Manager Packages has now been released!  Require users to purchase a package to view, browse, or apply/contact any job (listing), as well as browse, view, contact, and view full candidate name on Resumes.  Supports WooCommerce Subscriptions!

Currently integrates with WooCommerce to handle all payment, and order processing.

View Resume Placeholder and Form Output

View Resume Placeholder and Form Output

Packages can contain limits, with a full admin management on the backend, and jQuery powered table on the frontend for users!  On sale for initial release, only $29.99!



WP Job Manager Visibility Integration Example

Integration with the Visibility plugin in groups. Requires WP Job Manager Visibility

This also brings a major integration for the WP Job Manager Visibility plugin, as when you combine both plugins, you can create unlimited groups based on packages created with WP Job Manager Packages AS WELL AS WP Job Manager WooCommerce Paid Listings packages!


]]> 0
Field Editor 1.6.4 Release – New HTML5 Fields and WPML Fixes Sat, 10 Dec 2016 01:24:05 +0000 The maintenance release of WP Job Manager Field Editor 1.6.4 includes a few new features (HTML5 email, url, and tel input types), as well as a few minor bug patches, and the most important of this release, numerous patches and fixes for WPML compatibility, which I will go into detail about below:


Let’s start off with the most frustrating part of this release, dealing with WPML compatibility.  If you’re using WPML you may have recently noticed that when you save a field, it doesn’t actually update on the list table with the information you saved, which ended up being due to WPML returning a cached value, even though when you save a field, my plugin unregisters the old value, registers the new one, and then passes the new value through translation again to generate the updated list table.  To make matters even worse, the PHP documentation (which is almost non-existent in WPML code base) says

If a translation exists, it will return it. Otherwise, it will return the original string
  — which I found was clearly NOT true because it was returning the old value, even when there was no translation for the old or the new value!

Any normal developer would think, well i’m sure there’s some code they have that can quickly clear the cache and fix this issue … which was also not true!  Even the code provided by WPML didn’t work, and I ended up having to spend numerous hours to come up with my own hack to force it to clear the cache and fix the problem!

While debugging this issue I also found a problem where under the “context” in WPML, there were instances where option label/values were being duplicated in the string translation database table.  You may have noticed context that said something like Job Listing Fields Listing Fields … which was a duplicate of Job Listing Fields context.  This was due to a minor bug in my plugin that was looping through array values (option label/value), and when it was passed through the translation function, WPML was automatically adding it to the string translation database, causing duplicate entries for the same field.  Just make sure when you update to this latest release, that you have your translations set correctly in the Job Listing Fields context and not the Job Listing Fields Listing Fields context (same for Company and Resume).  Translations should have already been pulled from the correct context, but it’s always good to double check.

I have also removed the language filters from the field list table area that were automatically added by WPML, as they did not do anything and the fields are always going to show in whatever language you have the admin area configured in.

Other minor bug fixes

A few other minor bugs were fixed in this release as well, including an issue where HTML5 validation would fail if you were using taxonomy term-select field type, due to core WP Job Manager plugin setting the “none” value to -1, whereas it needs to be an empty string.

There was also an issue with taxonomy values not populating correctly whenever a user would duplicate a listing from their dashboard area, this has been fixed as well.

Job Type Multiple Setting

I have also now removed the “Enable multiple types for listings” setting from the core WP Job Manager setting page, as this will automatically be configured based on whatever field type you have configured the field as.  If you have not configured that field, it will still return the correct value to the core plugin.  This is the same way that the job_tags field works.

New HTML5 Field Types

In this release i’ve also added 3 new HTML5 field types, email, URL, and tel (telephone).   Let’s go through each new field type and why I added it, as well as what benefits it brings to your site.

  • email – the email field type is useful for HTML5 validation of email addresses.  Using this field type will prompt the user to input a correctly formatted (and valid) email address, if the field is required, or if they have entered a value that does not meet validation.
  • URL – just like the email type above, this will help to validate a URL with HTML5 and requires the protocol to be entered (http://, https://, etc) to meet validation.
  • tel – this field type is different from the others above, as there isn’t really any validation done on this field (unless you configure pattern in advanced tab), and will output and look just like a standard text input field.

Why should you use HTML5 input field types?

The main reason for me adding these field types, as well as the reason you should try and use them whenever possible, is mainly for your mobile clients/visitors.  The benefit of using these field types will help mobile devices to automatically show the best keyboard associated with that field type.  So for example with the email field type, it will set the @ and . keys on the keyboard for quick access.  Same with URL, it will set a .com and and forward slash as the quick access keys, making it easier, and quicker for your mobile visitors to fill out forms.  The tel field type will also show the numeric keyboard as default over the standard keyboard.

Now there are two Phone/Telephone field types?

You may have noticed that there is already a Phone field type included with the plugin.  The difference between the new HTML5 tel input type, and the existing phone input type, is that the Phone input type uses the International Telephone Input jQuery plugin on top of the HTML5 tel input, to provide a better user experience with a flag dropdown box, auto format, etc.

That’s it for this maintenance release, please let me know if there are any issues with the new features or the fixes that were included!

]]> 0
New Feature: Show/Hide specific fields based on selected package Thu, 29 Jan 2015 02:31:09 +0000 With the release of WP Job Manager Field Editor 1.2.4 comes a new feature for WooCommerce Paid Listings.  You can now configure fields that you only want to show on specific packages, or even on multiple packages.  A new tab has been added in the modal called Packages and with a little bit of configuration you can get your site up and running with completely different forms based on what package the user selects!

Find more information on the documentation page for Show/Hide specific fields based on selected package

]]> 0
WP Job Manager Field Editor Released! Tue, 01 Jul 2014 00:28:58 +0000 Today I am happy to say I have released version 1.0.0 of my WP Job Manager Field Editor.

]]> 0