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.
Working on a number of sites recently, the designs I have been provided with have contained a “featured post” section [widget] in the sidebar. This got me looking in the plugin repository for a widget plugin to feature a post. What I found was lots of plugins but nothing that was flexible enough for me to use. Therefore I went about building my own Featured Post Widget to use on sites in the future.
If you do a search for Featured Post Widget in the WordPress.org plugin repository you end up with a number of different results, of plugins which indicate they do just that. Some I am sure are very good out of the box solutions for many people, however I want something flexible that I an use on all sites where the output markup and the options are perhaps going to need tailoring to the site in question. From a quick inspection of some of the plugins it as clear that I was going to have to write my own.
Whilst building a plugin recently I found a change in WordPress 4.4 which actually broke my plugin, but was very easy to fix. The problem was with a custom post type that had completely disappeared from the admin menu. Here is why it disappeared and how I got it back again!
First a little background about the plugin in question. It used a post type in order for the user to add a single post. The content of this single post was then outputted with a shortcode and therefore I did not want the post type to have a permalink page at all. For this I had set the
public argument used in
false. I also did not want the regular post type menu item to show in the backend, as I was adding my own menu item and therefore I had set the
show_ui argument to
false too. This worked fine in WordPress 4.3.1 and when I added my own menu item using
add_menu_page() which used the edit post screen for the content for a post within the custom post type the menu item showed up no problem.
When I recently upgraded the site to WordPress 4.4 there was a large problem. The menu item completed disappeared. After some digging around and making some changes to test what was going on, I found the problem. The fix was to set
false but to set
When I tweeted about this issue, John Blackbourn, one of the core developers kindly responded with a link to a post outlining the changes.