Over a million developers have joined DZone.
{{announcement.body}}
{{announcement.title}}

Taming WordPress Taxonomies

DZone's Guide to

Taming WordPress Taxonomies

· Web Dev Zone
Free Resource

Learn how to build modern digital experience apps with Crafter CMS. Download this eBook now. Brought to you in partnership with Crafter Software

A while back I wrote a short series of articles on programatically manipulating taxonomies in WordPress. If you didn’t see the series it included:

But what do you do if you are not a coder? Well to make life easier I have created a plugin which will give users of WordPress greater control over the taxonomies that are available to them. I have called this plugin the Taxonomy Toolkit and it has the following features:

  1. The adding and removal of terms from posts en-mass.
  2. Adding and removing your own custom taxonomies for finer control over how your data(posts) is displayed on your website.
  3. Adding and removing terms from built in taxonomies, taxonomies added by other plugins and custom taxonomies added using the toolkit.

The plugin follows the WordPress coding standards to ensure that the plugin is built in a robust and maintainable way.

Here are a couple of screenshots.

manage_posts_taxo_buttons

manage_posts_top_table

manage_taxos

help

So where can I get this plugin? Well it should be available soon on CodeCanyon, the Envato website. I will post an update here as soon as it is.

Crafter is a modern CMS platform for building modern websites and content-rich digital experiences. Download this eBook now. Brought to you in partnership with Crafter Software.

Topics:

Published at DZone with permission of Chris Odell, DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

THE DZONE NEWSLETTER

Dev Resources & Solutions Straight to Your Inbox

Thanks for subscribing!

Awesome! Check your inbox to verify your email so you can start receiving the latest in tech news and resources.

X

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}