Wow. Just when I thought it couldn’t get any cooler. (Not to toot my own horn).

The next version of Quality Control (currently awaiting review) takes things to the next level. In reality there are very few new “features” for the average user. However, things have been cleaned up, and made ridiculously easy to use.

I’ve set it up now so each “module” of Quality Control is loaded through add_theme_support. This way, child themes can effortlessly remove built in features like milestones, categories, tags, assignment, and notifications. Not only is it easy to remove features, but it’s almost just as easy to add them. A new class has been introduced that handles creating new taxonomies automatically. It will automatically add it to the navigation, ticket meta, admin backend, ticket listing columns, save the information when publishing tickets, and add the fields to the form. It’s awesome. Here is how it is used:

In functions.php of your child theme add:

add_action( 'after_setup_theme', 'quality_child_test', 11 );

function quality_child_test() {
	add_theme_support( 'ticket-priority' );
	require_if_theme_supports( 'ticket-priority', locate_core_file( 'inc/modules/priorities.php' ) );
}

Then create a file in /inc/moddules/ called priorities.php (this is in the child theme directory)

<?php
/**
 * @package Quality_Control
 * @subpackage Ticket Taxonomies
 * @since Quality Control 0.2
 */

if ( ! class_exists( 'quality_ticket_priority' ) ) :
/**
 * Create the status taxonomy. Nothing custom here.
 *
 * @since Quality Control 0.2
 */
class quality_ticket_priority extends quality_create_taxonomy
{
	/**
	 * Just create the name, slug, and labels. The rest is
	 * done automagically.
	 *
	 * @since Quality Control 0.2
	 */
	function quality_ticket_priority() {
		parent::quality_create_taxonomy(
			'ticket_priority',
			'priority',
			array(
				'name' => __( 'Priorities', 'quality' ),
				'singular_name' => __( 'Priority', 'quality' ),
				'search_items' => __( 'Search Priorities', 'quality' ),
				'popular_items' => __( 'Popular Priorities', 'quality' ),
				'all_items' => __( 'All Priorities', 'quality' ),
				'update_item' => __( 'Update Priority', 'quality' ),
				'add_new_item' => __( 'Add New Priority', 'quality' ),
				'new_item_name' => __( 'New Priority Name', 'quality' ),
				'edit_item' => __( 'Edit Priority', 'quality' )
			)
		);

		$this->actions();
	}
}
endif;

$ticket_priority = new quality_ticket_priority;

This will automatically add a new taxonomy called “Priority”. Amazing.

Quality Control 0.1.5 brings a few changes to the table. From the changelog (which isn’t really that specific)

1. Created a ticket form template tag.
2. Added the ability to assign users to tickets.
3. Added permission options to setings.
4. Other optimizations/code fixes.
5. State permalinks aren’t hard coded in loop.php and single.php

The one I am most happy about is merging all the front-end ticket submission form code into one function. I’ve set this up in an almost identical manner as the comment_form function found in WordPress. You can filter the array of inputs, making it much easier (and possible) for Child Themes to exclude certain fields without having to edit the theme directly.

A basic permission system has also been put in place. It allows you to assign one or more users to a specific ticket. Then you are able to decide how those tickets act/appear to users who are not assigned (hide the ticket, read only, or readable and writable.)

Along with multiple other bug fixes/optimizations, I fixed some hard-coded permalinks that where causing some trouble.

With each iteration, the customizability through Child Themes improves. Hopefully it will eventually get to a point where no theme files ever need to be edited. But that might be an unrealistic goal.

Get Quality Control