API Reference Mishka Installer v0.0.1

modules

Modules

This event is triggered whenever a user's role is successfully deleted. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_info(), ip(), endpoint(), modifier_user(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user is successfully logged in. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_info(), ip(), endpoint(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user is successfully logged out. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_id(), ip(), endpoint(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user is successfully added or edited. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_info(), ip(), endpoint(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user is successfully added or edited. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_info(), ip(), endpoint(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user's role is successfully saved or edited. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_info(), ip(), endpoint(), modifier_user(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user accesses form an authorisation. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_id(), entries(), ip(), endpoint(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user gets an error for authorisation. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes extra(), ip(), endpoint(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user is unsuccessfully logged in. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_info(), ip(), endpoint(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

This event is triggered whenever a user is successfully logged in. if there is any active module in this section on state, this module sends a request as a Task tool to the developer call function that includes user_info(), ip(), endpoint(). It should be noted; This process does not interfere with the main operation of the system. It is just a sender and is active for both side endpoints.

mix-tasks

Mix Tasks