Plugin and Event engine that allows for the implementation of plugins to customize and extend your software with ease. (Composer Package)
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
tests fixed code style and updated to use PSR-4 autoload logic Jan 22, 2015
.gitignore Adapting to new loader package Nov 30, 2012
LICENSE adding unit testing Oct 6, 2012 Update Feb 29, 2016
composer.json fixed code style and updated to use PSR-4 autoload logic Jan 22, 2015 changes to readme Oct 11, 2012

Foolz PHP Plugin system

A very complete plugin system to let you claim that your application supports plugins!

You will need PHP 5.4 for this to work. You can install it through Composer and Packagist.

Build Status


  • Hooks

    Place them in your code to execute events. Unlike several other packages, these Hooks allow interacting with the data and can hold the scope of the class.

  • Events

    The events happen when a Hook with the same key is encountered. Events accept static methods and Closures, as well as a priority, because you can stack them and have them passing variables to each other.

  • Result

    The object that Hooks and Events share, and return. They keep your code clean from mysterious function parameters and even more confusing return values.

  • Plugin

    The internal package handler. Plugins are actually Composer packages. Use the bootstrap file to create new events and use the install/uninstall/upgrade hooks.

  • Loader

    The packages utility. It looks into the folders you tell it to, finds plugins, loads them and give you the arrays.

  • PlugSuit (trait)

    Add plugins automatically to your classes. It adds a before and after hook, and lets you override the parameters passed to the methods.

What will you have to do? You must use the Loader class to create your own administration panel and run the plugins you choose to run. Since it doesn't have any database bind (or any dependency at all), you must create an enabled/disabled system yourself.

Some examples follow.

You can go in-depth with these explanations with the following pages:

Hooks and Events

The most basic part of the package. You can use Hook and Event anywhere in your code, not only in the plugins.


use \Foolz\Plugin\Hook as Hook;
use \Foolz\Plugin\Event as Event;

// define an Event

// the Hook triggers it
$result = Hook::forge('triggerOnThis')->execute();

// echoes 123
echo $result->get();


We coded the result package to avoid confusion with cascading Events. This is why Events only get one parameter, that we use to call $result.

As this is where most of the mistakes are made, any unset parameter or unset result without explicit fallback will cause an exception.



// define an Event
	$increment = $result->getParam('increment')

// define another Event editing the parameters with lower priority (lower number is higher priority, default is 5)
	$increment = $result->getParam('increment')

// the Hook triggers it
$result = Hook::forge('triggerOnThis')
	->setParam('increment', 0)

// echoes 2 (we increased the number in each event)
echo $result->get();

// echoes 1 (we edited the parameter only in the first event)
echo $result->getParam('increment');


We have two classes for dealing with plugin packages: Plugin and Loader.

Here's an example of how would you load the plugins you choose to run:


$loader = Loader::forge()->setDir('main', '/path/to/plugins/');

$enabled_plugins = array('foolz/fake', 'foolz/kynet');

foreach ($loader->getPlugins('main') as $plugin)
	if (in_array($plugin->getConfig('name'), $enabled_plugins))

Get more info about plugins.