Enable it via:
$this->Crud->mapAction(
'login',
'CrudUsers.Login'
);
Note
Before applying any configuration to an action
it must be mapped first.
If the action has not been mapped an exception will be raised.
Test or modify if the Crud Action is enabled or not.
When a CrudAction is disabled, Crud will not handle any requests to the action, and CakePHP will raise the normal
\Cake\Error\MissingActionException
exception if you haven’t implemented the action in your controller.
Warning
If you have enabled Crud and you are still receiving a MissingActionException
, ensure the action is enabled and
that the controller has the \Crud\Controller\ControllerTrait
implemented.
To test if an action is enabled, call the enabled
method on the action.
$this->Crud->action()->enabled();
To disable an action, call the disable
method on the action.
$this->Crud->action()->disable();
To enable an action, call the enable
method on the action.
$this->Crud->action()->enable();
To disable or enable multiple actions at the same time, Crud Component
provides helper methods.
The enable
and disable
method can take a string or an array, for easy mass-updating.
$this->Crud->enable('index');
$this->Crud->enable(['index', 'add']);
$this->Crud->disable('index');
$this->Crud->disable(['index', 'add']);
Note
These methods simply calls the enable
and disable
method in each Crud Action
class, and do not provide any magic
other than mass updating.
Warning
While it’s possible to update the enabled
property directly on an action using the config
methods,
it’s not recommend, as important cleanup logic will not be applied if you use the config()
method directly.
This is a list of events emitted from the Login Crud Action
.
Please see the Events Documentation for a full list of generic properties and how to use the event system correctly.
TODO
TODO
Called after the Controller::beforeFilter()
and before the Crud action.
It’s emitted from CrudComponent::startup()
and thus is fired in the same cycle
as all Component::startup()
events.
Triggered when a CrudAction
is going to handle a CakePHP request.
It’s emitted from CrudComponent::beforeFilter
and thus is fired in the same cycle as all Controller::beforeFilter
events.
Simple and event driven wrapper for SessionComponent::setFlash
.
The Crud Subject contains the following keys:
SessionComponent::setFlash
.SessionComponent::setFlash
.SessionComponent::setFlash
.SessionComponent::setFlash
.Entity
from the previously emitted event.All keys can be modified as you see fit, at the end of the event cycle they will be passed
directly to SessionComponent::setFlash
.
Defaults are stored in the messages
configuration array for each action.
If you do not want to use this feature, simply stop the event by calling it’s stopPropagation()
method.
If you’d like to customise the flash messages that are used, perhaps you’re using friendsofcake/bootstrap-ui. It’s actually quite simple to do, and can be done as part of the component configuration or on the fly.
public function initialize()
{
$this->loadComponent('Crud.Crud', [
'actions' => [
'edit' => [
'className' => 'Crud.Edit',
'messages' => [
'success' => [
'params' => ['class' => 'alert alert-success alert-dismissible']
],
'error' => [
'params' => ['class' => 'alert alert-danger alert-dismissible']
]
],
]
]
]);
}
If you’d like to configure it on the fly you can use the eventManager to change the event subject as the event is emitted.
$this->eventManager()->on('Crud.setFlash', function (Event $event) {
if ($event->subject()->success) {
$event->subject()->params['class'] = 'alert alert-success alert-dismissible';
}
});
Simple and event driven wrapper for Controller::redirect()
.
The Crud Subject contains the following keys:
Controller::redirect()
.Controller::redirect()
.Controller::redirect()
.Entity
from the previously emitted event.All keys can be modified as you see fit, at the end of the event cycle they will be passed
directly to Controller::redirect()
.
The redirect $url
can be changed on the fly either by posting a redirect_url
field from your
form or by providing a redirect_url
HTTP query key.
The default for most redirects are simply to return to the index()
action.
Invoked right before the view will be rendered.
This is also before the controllers own beforeRender callback.