Uninstall this Fieldtype, consistent with optional Module interface
- Checks to make sure it's safe to uninstall this Fieldtype. If not, throw an Exception indicating such.
- It's safe to uninstall a Fieldtype only if it's not being used by any Fields.
- If a Fieldtype overrides this to perform additional uninstall functions, it would be good to call this parent uninstall method first to make sure uninstall is okay.
Usage
$fieldtype->uninstall();
Exceptions
Method can throw exceptions on error:
WireException
- Should throw an Exception if uninstall can't be completed.
Hooking Fieldtype::uninstall()
You can add your own hook events that are executed either before or after the Fieldtype
method is executed. Examples of both are included below. A good place for hook code such as this is in your /site/ready.php file.
Hooking before
The 'before' hooks are called immediately before each Fieldtype
method call is executed. This type of hook is especially useful for modifying arguments before they are sent to the method.
$this->addHookBefore('Fieldtype::uninstall', function(HookEvent $event) {
// Get the object the event occurred on, if needed
$Fieldtype = $event->object;
/* Your code here, perhaps modifying arguments */
// Populate back arguments (if you have modified them)
});
Hooking after
The 'after' hooks are called immediately after each Fieldtype
method call is executed. This type of hook is especially useful for modifying the value that was returned by the method call.
$this->addHookAfter('Fieldtype::uninstall', function(HookEvent $event) {
// Get the object the event occurred on, if needed
$Fieldtype = $event->object;
// An 'after' hook can retrieve and/or modify the return value
$return = $event->return;
/* Your code here, perhaps modifying the return value */
// Populate back return value, if you have modified it
$event->return = $return;
});
Fieldtype methods and properties
API reference based on ProcessWire core version 3.0.236