So basically in the plugins event handler, you assign the events you want to hook into, to a custom function you write...

Here a plugin binds to the mailbox plugin to be able to send push notifications on new messages:

public function genericInit()    {        

OW::getEventManager()->bind('mailbox.ping', array($this, 'sendNotification'));  

}

This binds the sendNotification function to the mailbox.ping event so the sendNotification function executes along with anything else bound to that event.

Then some of the sendNotification function:

    public function sendNotification( OW_Event $event )

    {

        $eventParams = $event->getParams();

        $params = $eventParams['params'];

        if ($eventParams['command'] == 'mailbox_api_ping')

        {

            return $this->onApiPing($event);

        }

        if ($eventParams['command'] != 'mailbox_ping')

        {

            return;

        }

        if ( !OW::getUser()->isAuthenticated() )

        {

            $event->setData(array('error'=>"You have to sign in"));

            return;

}

        Blah Blah Blah...

        Command has been verified, User is Authenticated -> (Grab User?) Email Logic here

        (Email command verification will be different from all this)

}

You'll likely need to reverse your specific event_handler to create your event handler and event function.

Here is the important part... 

While you are developing, you're bound to break stuff and if you break something after binding to a certain event, it will break that event and all functions tied to it usually, until you get your function code fixed... 

So don't panic if the event (emails?) stop working after you bind to the event and start coding your custom event function.

Just keep working through it to find and fix your bugs and chances are your event will start working again once everything in your custom function is right.

There are certain procedures that must be followed when creating a plugin.

Here is a skeleton plugin that I was able to learn some from:

https://developers.oxwall.com/store/item/695

This is the plugin I used to reverse engineer how to hook into Oxwall events:

https://github.com/oxwall/mailbox

Specifically this event_handler.php:

https://github.com/oxwall/mailbox/blob/master/classes/event_handler.php

Notice in my post above, I only hook into 1 event, but you can see multiple events are defined in:

public function genericInit()

Same should be for whatever plugin/event you're trying to hook into.

I suggest downloading multiple plugin zip's and looking at all their internals for similarities and differences to know what is commonly included in plugins.

I am thinking about putting all the helpful info I've been given by Dave and other dev's in a plugin howto.

You can do it, trust yourself, don't give up and just keep trying...

Development is all trial and error until you get the hang of it!

Amazing! Thanks so much that will teach me a lot! Happey new year.

P.S. Most of the plugins I created I used reverse engineering :)

To achieve this functionality from a plugin, you can follow these steps:

Create an Event Listener: Create a plugin that listens for the 'admin.user_list_action_render' event. This event is triggered when the admin user list is rendered, and you can use it to add your custom email verification functionality.

Add a Custom Action: In the event listener, add a custom action button or link that the admin can use to verify the user's email. This can be done by modifying the $params array passed to the event listener.

The Forum post is edited by bloxd io Jan 5 '19