A wp-kit component that handles the invoking of controllers and closures

2.0.6 2020-07-24 19:27 UTC

This package is not auto-updated.

Last update: 2024-05-15 08:08:06 UTC


This is a wp-kit component that handles the invoking of controllers and closures based on a condition.

This component was built to run within an Illuminate\Container\Container so is perfect for frameworks such as Themosis, Assely and wp-kit/theme.

Often, WordPress developers want to group their actions and filters in a more defined context but do not want to use a traditional controller and would rather invoke a controller based on a condition rather than a path.

Sure, if we are using Themosis we can use Routes, but we cannot pass in closures directly into the Route condition. With wp-kit/invoker, you can invoke controllers more easily. Examples are below.

Lastly, as expected a Controller is invoked once, and once only during the lifecycle of the application regardless of the number of times the condition is met to invoke the Controller.


If you're using Themosis, install via Composer in the root fo your Themosis installtion, otherwise install in your Composer driven theme folder:

composer require "wp-kit/invoker"


Add Service Provider

Just register the service provider and facade in the providers config and theme config:

//inside theme/resources/config/providers.config.php

return [
	WPKit\Invoker\InvokerServiceProvider::class, // make sure it's first

Add Facade

If you are using Themosis or another Iluminate driven framework, you may want to add Facades, simply add them to your aliases:

//inside theme/resource/config/theme.config.php

'aliases' => [
    'Invoker' => WPKit\Invoker\Facades\Invoker::class,

Add Config File

The recommended method of installing config files for wp-kit components is via wp kit vendor:publish command.

First, install WP CLI, and then install this component, wp kit vendor:publish will automatically be installed with wp-kit/utils, once installed you can run:

wp kit vendor:publish

For more information, please visit wp-kit/utils.

Alternatively, you can place the config file(s) in your theme/resources/config directory manually.

How To Use


use WPKit\Invoker\Facades\Invoker;

// as php function as below

// $callback 	( string / array / callable )
// $hook 		( string )
// $condition 	( string / callable )
// $priority 	( int )
// invoke( $callback, $hook, $condition, $priority );

invoke( 'AppController' );

invoke( 'ProductController@someMethod' );

invoke( function() {

	add_filter( 'pre_get_posts', function($query) {
		$query->posts_per_page = 10;

}, 'wp', 'is_front_page', 80 );

invoke( 'App\Controllers\SingleProductController', 'wp', 'is_product' );

invoke( \App\Controllers\CartController::class, 'wp', 'is_cart' );

invoke( 'ShopController', 'wp', function() {

	return is_shop() || is_post_type_archive( 'product') || is_tax( 'product_cat' ) || is_tax( 'product_tag' ) || is_tax( 'product_brand' ) || is_tax( 'company_portal' );
} );

// using facade

Invoker::match( 'SingleProductController@someMethod', 'wp', 'is_product' );

Invoker::match( 'ShopController', 'wp', function() {

	return is_shop() || is_post_type_archive( 'product') || is_tax( 'product_cat' ) || is_tax( 'product_tag' ) || is_tax( 'product_brand' ) || is_tax( 'company_portal' );
} );

This may see back to front in terms of how Router::match works however we feel it is more intuitive to lead with the callback when using the Invoker.


wp-kit/invoker comes shipped with a Controller that you can extend too to enable you to benefit from the enqueue scripts feature which helps to reduce the amount of code you need to write to output scripts and styles through wp_enqueue_scripts.

Helpfully, wp-kit comes with two functions to more easily add hooks with reference to the current class. These two functions are action and filter; these functions fallback to the traditional functions add_action and add_filter which means they can be used 100% of the time.

namespace App\Controllers;

use WPKit\Invoker\Controller;

class FrontPageController extends Controller {
	var $scripts = [
    	'app' => [
    	    'file' => 'scripts/app.min.js'
	public function getScripts() {
    	$this->scripts['app']['localize'] = [
            'name' => 'myAjax',
            'data' => [ 
                'ajax_url' => admin_url( 'admin-ajax.php' )
        return parent::getScripts();
	public function beforeFilter() {
		add_action( 'woocommerce_thankyou', array($this, 'bigThanks'), 5 );
		action( 'woocommerce_thankyou', 'smallThanks', 5 );
		add_filter( 'body_class', array($this, 'addBodyClasses') );
		filter( 'body_class', 'addMoreBodyClasses' );
	public function bigThanks() {
		echo 'THANKS';
	public function smallThanks() {
		echo 'thanks!';
	public function addBodyClasses( $classes ) {
		$classes[] = 'some-class';
	    return $classes;
	public function addMoreBodyClasses( $classes ) {
		$classes[] = 'some-other-class';
	    return $classes;

Get Involved

To learn more about how to use wp-kit check out the docs:

View the Docs

Any help is appreciated. The project is open-source and we encourage you to participate. You can contribute to the project in multiple ways by:

  • Reporting a bug issue
  • Suggesting features
  • Sending a pull request with code fix or feature
  • Following the project on GitHub
  • Sharing the project around your community

For details about contributing to the framework, please check the contribution guide.


Wordpress 4+

PHP 5.6+


wp-kit/invoker is open-sourced software licensed under the MIT License.