Over the last 2 years I have been building solutions to integrate Broadbean (and more recently LogicMelon) with WordPress websites. Starting with the stand-alone WP Broadbean plugin I have then started to provide integration solutions for some of the more popular job board plugins and themes. Continuing with this I have now launched, available for sale, my JobRoller Broadbean Add-on plugin for WordPress, to integrate WordPress sites running the JobRoller theme with Broadbean or LogicMelon.
A few years ago I built the WP Broadbean WordPress plugin in order to integrate Broadbean job posting with a WordPress website. This is has proved a highly successful plugin with a number of sites now actively using this. In fact Broadbean themselves are keen for WordPress users to adopt its use. Recently I have been working on another solution for WordPress sites which integrates the very popular WP Job Manager plugin with Broadbean. Allow me to introduce the WP Job Manager Broadbean Add-on.
The WP Job Manager plugin has a number of add-ons that are listed on the add-ons page of the website. You will now see a Broadbean add-on listed, and many thanks to the team for allowing this add-on onto their page for third party add-ons.
I have decided that the plugin will be a paid for product, much like the other add-ons on that page and also that it will be licensed. like many other commercial current commercial plugins. There are two type of license, each lasting for a period of 12 months, giving purchasers support throughout that period as well as updates. The licenses are either for 1 site, priced at £99.99 or for unlimited sites priced at £199.99.
The add-on is activated like a normal plugin would be and contains a settings tab under the WP Job Managers settings page. On here users can set a username and password for their incoming feed as well as activating their license. Also on this page are instructions on what information to pass through to the team at Broadbean in order for them to send the job data to your site.
It is worth noting here that the plugin is dependent on data being sent from Broadbean. This is something that would be specific to your site and therefore needs to be built by the Broadbean integrations team. For this reason they will probably have a charge for this too and it is worth speaking with your Broadbean account manager about this.
So if you are a recruitment business using Broadbean and you have a WordPress website of you own running the WP Job Manager plugin to show jobs on your site, you can know include jobs you post through Broadbean on your site as well. There will no longer be the need to add them in two places!
In early 2014 I launched the first beta version of the WP Broadbean WordPress plugin. This is a plugin to integrate Broadbean Adcourier job postings with a WordPress website. The plugin has evolved and changed since then and therefore lets take a look at some of the plugins features.
Lets outline some of the new features of the plugin which have been introduced after the initial launch:
The plugin has been made as extensible as possible from the start. However as development has progressed it has become more obvious that additional extensible features could be utilised. Many of these have come from developers in the community using the plugin and feeding back to me.
There are now a number of hooks and filters that allow developers to extend upon and alter the functionality of the plugin. For example developers can use a different
inbox.php file which processes each job simply by using a template override. Developers can also use filters to add additional job fields and taxonomies to the job postings should they wish to.
It is worth remembering however the more customisations made with the plugin through its extensible features, the more changes Broadbean will need to make to the feed which is used to send jobs to your site.
Below are some of the new filters you can use:
wpbb_query_var_value– allows you to change the URL query var to which jobs are posted to. This defaults to broadbean but developers could change this to something else.
wpbb_application_form_html– using this filter would allow developers to alter the markup of the application form used to allow candidates to apply for jobs
wpbb_application_allowed_file_types– a filter that allows editing of the file types that are allowed by default in the CV upload field on the application form
wpbb_apply_url– with this filter you can amend the URL used for applying for jobs. This means you could change the URL completely, maybe to use your own form or you could perhaps add additional query variables to the URL which you may use in your application form.
wpbb_admin_sub_menus– allows developers to add a sub menu beneath the main WP Broadbean menu
wpbb_registered_settings– add additional settings to the WP Broadbean settings admin page
There are many new action hooks you can utilise too:
wpbb_job_term_added– a hook that fires after a term has been added to a job when sent through from Broadbean
wpbb_job_field_added– this hooks fires after a field is added (post meta) to a job when sent through from Broadbean
wpbb_job_added– after the job is added along with all the fields and the terms this hook is fired. Can be good for actioning things like clearing search caches etc. which need to be re-built when a new job or post is added.
There are many more and I would encourage you to search the code-base for
The application form has changed along the way to, for the better I think. It now no longer uses a shortcode but instead you select which is your apply page in the WP Broadbean settings page. The application form is then appended to any page content you may have on that page.
The form also now includes a field for a message, something which many users requested.
Finally the form now also allows the upload of Word and Pages documents as well as the original PDF document type. Even these can be changed with a filter.
Attachments to Email Notifications
One of the initial issues with the plugin which was reported to me was that the application form was not emailing Broadbean correctly or not attaching the applicants CV to the email. This is something that is important for the tracking of an application from within the Adcourier system.
These issues have now been fixed and all the emails that are sent through to Broadbean will have the applicants CV attached.
Those are the main changes and alterations to the plugin which I hope make it much better for users and developers to take advantage of. Do remember that I offer a Broadbean Assist service where I can integrate Broadbean with your WordPress site for just £599 which takes the hassle out of doing it yourself.
Over the coming months I have some additional plans for the Broadbean plugin with a view to integrating this into some other services – watch this space. Oh and don’t forget that I recently launched a plugin for integrating WordPress with LogicMelon over at wplogicmelon.com – you can read a little more about this here!
My WP Broadbean plugin to integrate jobs posted via Broadbean Adcourier has been a success in the recent months with many different recruitment companies using the plugin to get jobs they post on Broadbean to appear on their WordPress websites. Now it is time to take the plugin to the next level and coming soon with be the second version of the plugin with updates and enhancements. Lets take a look at what is planned.
Having been working on the plugin for well over 18 months now, in my spare time between projects and with a number of clients using the plugin I have learnt a lot about what changes would enhance the plugin. Here are what is planned in the new release:
This is something that I am passionate about in plugins. The ability for a developer to make modifications and functionality changes without altering the core plugin code itself. In the next release there will be major extensibility offerings, some of which are outlined below.
Better Declaration of Fields for Each Job
At the moment the plugin comes with a set of job fields that are added when each job is published on the site. These include job reference, salary, contact name and email address etc. Adding your own fields up until now has been a little tricky to do and therefore the new version will easily allow you to declare what fields you want (additional) to the defaults. As well as this you can remove the defaults should you wish to do so.
Below is a simple example of how you could add your own fields to a job:
This will add the meta box field on the post editor for the job. Perhaps the best part as well is that it will also handle all of the saving of the post meta when the job gets saved.
It is worth noting here that this field would have to be added to your feed sent by Broadbean. They can do this as support and would not be a problem. In this case we would just need to request that an additional text input field be sent with the XML node
Add Your Own Taxonomies
The plugin comes bundled with some default taxonomies that work well with the default feed that Broadbean uses. Adding your own is also really simple and works in a similar way to the fields as above. Below shows an example of how we would add a new taxonomy for country.
Again this handles all the saving of the terms in this taxonomy when they are sent over to your site. As with fields Broadbean would need to add this field to your feed. The
broadbean_field arg in the code above states which XML node to look for in the feed.
Thanks must go to Dave Smith for his contribution to this part.
WP Broadbean Website
Along with the launch of version 2 of the plugin comes the new WP Broadbean website that is currently in development. The site will feature information and documentation as well as some paid services which users can opt into should they find them useful. More information on this soon.
Visit the current version (rough and ready!) of the WP Broadbean website here.
These are some of the major changes that have been introduced. It is worth noting that they are still in testing and I hope to have the new plugin version launched early in the new year.
With all these changes there is an important note that I need to make. Users that are using the current plugin, version 1.0.2 or lower, the new versions changes are likely to break your version. This is far from ideal I know, but having gone back and forth on a number of occasions this I feel is still the best way forward.
If you are on versions at or below 1.0.2 then I would recommend you add the Block Specific Plugin Updates plugin from the WordPress plugin repository and set it to prevent updating the WP Broadbean plugin until you are ready to move ahead with the new version 2 plugin.