miunosoft

Michael Uno

<h4>Handle Massive Number of Actions</h4>
<p>Do you have specific tasks which need to run at your desired time? Do you use WordPress as a proxy to generate data from external sources? As WordPress has evolved into a phase of application platforms, a more enhanced task management system needed to emerge.</p>
<p>Currently, with WP Cron, if you register a large number of actions, for example, 1000 tasks to run immediately and one of them stalls, it affects all the other actions preventing them from being loaded at the scheduled time. Also, the scheduled tasks won’t be triggered if there is no visitor on the site. The goal of this plugin is to resolve such issues and become the perfect solution for WordPress powered back-end application servers to provide full-brown API functionalities.</p>
<h4>What it does</h4>
<ul>
<li>(optional) creates periodic background access to the site. </li>
<li>triggers tasks registered by the site owner at desired time or interval.</li>
</ul>
<h4>Built-in Actions</h4>
<ul>
<li><strong>Delete Posts</strong> – performs bulk deletion of posts based on the post type, post statuses, taxonomy, and taxonomy terms.</li>
<li><strong>Send Email</strong> – sends email to specified email addresses.</li>
<li><strong>Clean Transients</strong> – deletes expired transients (caches).</li>
<li><strong>Check Web Sites</strong> – accesses specified web pages and checks certain keywords.</li>
<li><strong>Run PHP Scripts</strong> – runs PHP scripts of your choosing.</li>
</ul>
<h4>Custom Action Modules</h4>
<ul>
<li><strong><a href="https://wordpress.org/plugins/auto-post/" rel="ugc">Auto Post</a></strong> – creates posts automatically.</li>
</ul>
<h4>Extensible</h4>
<p>This is designed to be fully extensible and developers can add custom modules including actions and occurrence types.</p>
<h4>Create a Custom Action</h4>
<p>You can run your custom action with Task Scheduler and run it at scheduled times, once a day, with a fixed interval, or whatever you set with the plugin.</p>
<p>Place the code that includes the module in your plugin or <code>functions.php</code> of the activated theme.</p>
<p><strong>1.</strong> Decide your action slug which also serves as a WordPress <em>filter</em> hook.</p>
<p>Say, you pick <code>my_custom_action</code> as an action name.</p>
<p><strong>2.</strong> Use the <code>add_filter()</code> WordPress core function to hook into the action.</p>
<pre><code>/**
 * Called when the Task Scheduler plugin gets loaded.
 */
function doMyCustomAction( $isExitCode, $oRoutine ) {

    /**
     * Do you stuff here.
     */
    TaskScheduler_Debug::log( $oRoutine->getMeta() );
    return 1;

}
/**
 * Set the 'my_custom_action' custom action slug in the Select Action screen
 * via Dashboard -> Task Scheduler -> Add New Task.
 */
add_filter( 'my_custom_action', 'doMyCustomAction', 10, 2 );
</code></pre>
<p>Please note that we use <code>add_filter()</code> not <code>add_action()</code> in order to return an exit code.</p>
<p>Return <code>1</code> if the task completes and <code>0</code> when there is a problem. You can pass any value except <code>null</code>.</p>
<p><strong>3.</strong> Go to <strong>Dashboard</strong> -> <strong>Task Scheduler</strong> -> <strong>Add New Task</strong>. Proceed with the wizard and when you get the <strong>Select Action</strong> screen after setting up the occurrence, type <strong>my_custom_action</strong>, the one you defined in the above step.</p>
<p>The action slug set in the field will be triggered at the scheduled time.</p>
<p>It will be easier for you to modify an <a href="https://gist.github.com/michaeluno/5819636448947e7ab733" rel="nofollow ugc">existent code</a>. You can download the zip file and install it on your site.</p>
<h4>Create a Custom Action Module</h4>
<p>If you want your action to be listed in the <strong>Select Action</strong> screen, you need to create an action module.</p>
<p>To create an action module, you need to define a class by extending a base class that Task Scheduler prepares for you.</p>
<p><strong>1.</strong> Define your custom action module class by extending the <code>TaskScheduler_Action_Base</code> class.</p>
<pre><code>class TaskScheduler_SampleActionModule extends TaskScheduler_Action_Base {

    /**
     * The user constructor.
     * 
     * This method is automatically called at the end of the class constructor.
     */
    public function construct() {}

    /**
     * Returns the readable label of this action.
     * 
     * This will be called when displaying the action in an pull-down select option, task listing table, or notification email message.
     */
    public function getLabel( $sLabel ) {         
        return __( 'Sample Action Module', 'task-scheduler-sample-action-module' );
    }

    /**
     * Returns the description of the module.
     */
    public function getDescription( $sDescription ) {
        return __( 'This is a sample action module.', 'task-scheduler-sample-action-module' );
    }    

    /**
     * Defines the behaviour of the task action.
     *  
     */
    public function doAction( $isExitCode, $oRoutine ) {

        /**
         * Write your own code here! Delete the below log method. 
         * 
         * Good luck!
         */
        TaskScheduler_Debug::log( $oRoutine->getMeta() );

        // Exit code.
        return 1;

    }

}
</code></pre>
<p>In the <code>doAction()</code> method of the above class, define the behaviour of your action what it does. The second parameter receives a routine object. The object has a public method named <code>getMeta()</code> which returns the associated arguments.</p>
<p><strong>2.</strong> Use the <code>task_scheduler_action_after_loading_plugin</code> action hook to register your action module.</p>
<p>To register your action module, just instantiate the class you defined.</p>
<pre><code>function loadTaskSchedulerSampleActionModule() {

    // Register a custom action module.
    include( dirname( __FILE__ ) . '/module/TaskScheduler_SampleActionModule.php' );
    new TaskScheduler_SampleActionModule;

}
add_action( 'task_scheduler_action_after_loading_plugin', 'loadTaskSchedulerSampleActionModule' );
</code></pre>
<p><strong>3.</strong> Go to <strong>Dashboard</strong> -> <strong>Task Scheduler</strong> -> <strong>Add New Task</strong>. Proceed the wizard and when you get the <strong>Select Action</strong> screen, choose your action.</p>
<p>You can set your custom arguments in the <strong>Argument (optional)</strong> field if necessary.</p>
<p>The set values will be stored in the argument element of the array returned by the <code>getMeta()</code> public method of the routine object.</p>
<p>It will be easier for you to modify an existent module. Get an example action module which comes as a plugin from <a href="https://github.com/michaeluno/task-scheduler-sample-action-module" rel="nofollow ugc">this page</a>. Download and activate it on your test site. Then modify the code, especially the <code>doAction()</code> method which defines the behavior of the action.</p>
<h4>Create Threads</h4>
<p>When your routine is too heavy and gets hung often, you can create threads that performs sub-routines of the main routine.</p>
<p><strong>1.</strong> Define your thread class the <code>TaskScheduler_Action_Base</code> class.</p>
<pre><code>class TaskScheduler_SampleActionModule_Thread extends TaskScheduler_Action_Base {

    /**
     * Returns the readable label of this action.
     *
     * This will be called when displaying the action in an pull-down select option, task listing table, or notification email message.
     */
    public function getLabel( $sLabel ) {
        return __( 'Run a PHP Script', 'task-scheduler' );
    }

    /**
     * Defines the behavior of the task action.
     */
    public function doAction( $isExitCode, $oThread ) {

        // Do your stuff
        $_aThreadArguments = $oThread->getMeta();
        TaskScheduler_Debug::log( $_aThreadArguments );
        return 1;

    }
}
</code></pre>
<p><strong>2.</strong> Instantiate the thread class.</p>
<p>In the <code>construct()</code> method of your action module class introduced above that calls threads, instantiate the thread class by passing a custom action name. Here we pass <code>task_scheduler_my_thread</code> as an example.</p>
<pre><code>class TaskScheduler_SampleActionModule extends TaskScheduler_Action_Base {

    public function construct() {
        new TaskScheduler_SampleActionModule_Thread( 'task_scheduler_my_thread' );
    }

    ...

}
</code></pre>
<p><strong>3.</strong> Create a thread.</p>
<p>In the <code>doAction()</code> method of your action module class, create a thread with the <code>createThread()</code> method. The parameters are:</p>
<pre><code>createThread( $sThreadActionHookName, $oRoutine, array $aThreadOptions, array $aSystemTaxonomyTerms=array(), $bAllowDuplicate )

1. `$sThreadActionHookName` - (string, required) the slug that serves as an action hook name
2. `$oRoutine` - (object, required) the routine object that is passed to the second parameter of `doAction()`` method.
3. `$aThreadOptions` - (array, required) an associative array holding arguments to pass to the thread.
4. `$aSystemTaxonomyTerms` - (array, optional) an array holding taxonomy terms for the system the plugin provides. Default: `array()``.
5. `$bAllowDuplicate` - (boolean, optional) whether to allow threads to be created with same arguments. Default: `false`.
</code></pre>
<p>Make sure the return value is <code>null</code> so that the routine will not close. Here we assume the <code>$_aData</code> variable holds lots of items so it must be processed separately by threads.</p>
<pre><code>class TaskScheduler_SampleActionModule extends TaskScheduler_Action_Base {
    ...
    public function doAction( $isExitCode, $oRoutine ) {

        // Assuming this is big.
        $_aData = array(
            array(  'a', 'b', 'c' ),
            array(  'd', 'e', 'f', 'g' ),
            array(  'h', 'i' ),
        );

        foreach( $_aData as $_aDatum ) {
            $_aArguments = array(
                'datum' => $_aDatum,
                'foo'   => 'bar',
            );
            $this->createThread( 'task_scheduler_my_thread', $oRoutine, $_aArguments );
        }

        // Do not close this routine by returning 'null'. When all the threads are done, this routine will be automatically closed.
        return null;

    }
    ...
}
</code></pre>
<p><strong>4.</strong> Process Passed Data from a Routine to a Thread.<br />
In the thread class, retrieve the passed data.</p>
<pre><code>class TaskScheduler_SampleActionModule_Thread extends TaskScheduler_Action_Base {

    ...

    /**
     * Defines the behavior of the task action.
     */
    public function doAction( $isExitCode, $oThread ) {

        // Do your stuff
        $_aArguments = $oThread->getMeta();
        $_sFoo       = $_aArguments[ 'foo' ];  // is 'bar'
        $_aDatum     =  $_aArguments[ 'datum' ]; // is either array(  'a', 'b', 'c' ), array(  'd', 'e', 'f', 'g' ), or array(  'h', 'i' )

        TaskScheduler_Debug::log( $_aArguments );
        return 1;

    }

}
</code></pre>
<p>The entire code will look like this.</p>
<p>Action Module Class:</p>
<pre><code>class TaskScheduler_SampleActionModule extends TaskScheduler_Action_Base {

    /**
     * The user constructor.
     *
     * This method is automatically called at the end of the class constructor.
     */
    public function construct() {
        new TaskScheduler_SampleActionModule_Thread( 'task_scheduler_my_thread' );
    }


    /**
     * Returns the readable label of this action.
     *
     * This will be called when displaying the action in an pull-down select option, task listing table, or notification email message.
     */
    public function getLabel( $sLabel ) {
        return __( 'Sample Action Module', 'task-scheduler-sample-action-module' );
    }

    /**
     * Returns the description of the module.
     */
    public function getDescription( $sDescription ) {
        return __( 'This is a sample action module.', 'task-scheduler-sample-action-module' );
    }

    public function doAction( $isExitCode, $oRoutine ) {

        // Assuming this is big.
        $_aData = array(
            array(  'a', 'b', 'c' ),
            array(  'd', 'e', 'f', 'g' ),
            array(  'h', 'i' ),
        );

        foreach( $_aData as $_aDatum ) {
            $_aArguments = array(
                'datum' => $_aDatum,
                'foo'   => 'bar',
            );
            $this->createThread( 'task_scheduler_my_thread', $oRoutine, $_aArguments );
        }

        // Do not close this routine by returning 'null'. When all the threads are done, this routine will be automatically closed.
        return null;

    }

}
</code></pre>
<p>Thread Class:</p>
<pre><code>class TaskScheduler_SampleActionModule_Thread extends TaskScheduler_Action_Base {

    /**
     * Returns the readable label of this action.
     *
     * This will be called when displaying the action in an pull-down select option, task listing table, or notification email message.
     */
    public function getLabel( $sLabel ) {
        return __( 'Run a PHP Script', 'task-scheduler' );
    }

    /**
     * Defines the behavior of the task action.
     */
    public function doAction( $isExitCode, $oThread ) {

        // Do your stuff
        $_aArguments = $oThread->getMeta();
        $_sFoo       = $_aArguments[ 'foo' ];  // is 'bar'
        $_aDatum     =  $_aArguments[ 'datum' ]; // is either array(  'a', 'b', 'c' ), array(  'd', 'e', 'f', 'g' ), or array(  'h', 'i' )

        TaskScheduler_Debug::log( $_aArguments );
        return 1;

    }

}
</code></pre>
<p>Don’t forget to instantiate the action module class.</p>
<pre><code>new TaskScheduler_SampleActionModule;
</code></pre>
<h4>Terminologies</h4>
<ul>
<li><strong>Task</strong> – a rule which defines what kind of action routine to be performed at a specified time.</li>
<li><strong>Routine</strong> – a main action routine created by a task. Depending on the action, it creates an action thread to divide its routine.</li>
<li><strong>Thread</strong> – a divided action sub-sequential routine created by a routine. For example, The email action creates threads and sends emails per thread instead of sending them all in one routine to avoid exceeding the PHP’s maximum execution time.</li>
</ul>


Task Scheduler

WebTechGlobal

<p>Created to offer a workflow and in early stages. This plugin is part of the WebTechGlobal projects<br />
system which brings many plugins together to make a service orientated project<br />
management environment.</p>
<p>Plans for this plugin include being able to create new tasks from any device. The<br />
development goal<br />
is to be able to quickly record ideas, faults, customer requests and general<br />
requirements a project may have.</p>
<p>When integrated with other WTG plugins what you can offer customers, clients and<br />
developers will increase greatly i.e. the tickets plugins will offer the ability<br />
to turn a ticket into a task for developers to complete and the creator of the<br />
ticket will get updates on the task completion even when the ticket is closed.</p>
<p>The main goal is a transparant development environment that everyone within a<br />
websites community can access in one way or another i.e. displaying tasks<br />
publicaly so that freelancers can access and offer to complete them.</p>
<h4>Main Links</h4>
<ul>
<li><a href="http://www.webtechglobal.co.uk/wtg-tasks-manager/" title="WebTechGlobals Task Manager Portal" rel="nofollow ugc">Plugins Portal</a></li>
<li><a href="http://forum.webtechglobal.co.uk/viewforum.php?f=40" title="WebTechGlobal Forum for Task Manager" rel="nofollow ugc">Plugins Forum</a></li>
<li><a href="https://www.facebook.com/pages/WTG-Tasks-Manager-for-WordPress/302610946614839" title="WTG Task Manager Facebook Page" rel="nofollow ugc">Plugins Facebook</a></li>
<li><a href="http://www.webtechglobal.co.uk/category/wordpress/wtg-tasks-manager/" title="WebTechGlobal blog category for tasks manager" rel="nofollow ugc">Plugins Blog</a></li>
<li><a href="http://www.twitter.com/WebTechGlobal" title="WebTechGlobal Tweets" rel="nofollow ugc">Plugins Twitter</a></li>
<li><a href="http://www.youtube.com/playlist?list=PLMYhfJnWwPWD5P2vNf2c9gRsRNqRSVSoV" title="Official YouTube channel for WTG Tasks Manager" rel="nofollow ugc">YouTube Playlist</a></li>
</ul>
<h4>Feature List</h4>
<p>Remember this plugin is a beta so the list will be short for a while.</p>
<ol>
<li>Use WYSIWYG editor to describe tasks in detail.</li>
<li>Tasks are made as a custom post type.</li>
<li>Every post box can be added to the Dashboard as a widget.</li>
</ol>
<h3>Plugin Author</h3>
<p>Thank you for considering WTG Tasks Manager.</p>
<h3>Donators</h3>
<p>These donators have giving their permission to add their site to this list so that plugin authors can<br />
request their support for their own project. Please do not request donations but instead visit their site,<br />
show interest and tell them about your own plugin – you may get lucky.</p>
<ul>
<li><a href="" title="" rel="nofollow ugc">Ryan Bayne from WebTechGlobal</a></li>
</ul>
<h3>Contributors: Translation</h3>
<p>These contributors helped to localize WTG Tasks Manager by translating my endless dialog text.</p>
<ul>
<li>None Yet</li>
</ul>
<h3>Contributors: Code</h3>
<p>These contributers typed some PHP or HTML or CSS or JavaScript or Ajax for WTG Tasks Manager. Bunch of geeks really!</p>
<ul>
<li>None Yet</li>
</ul>
<h3>Contributors: Design</h3>
<p>These contributors created graphics for the plugin and are good with Photoshop. No doubt they spend their time merging different species together!</p>
<ul>
<li>None Yet</li>
</ul>
<h3>Contributors: Video Tutorials</h3>
<p>These contributors published videos on YouTube or another video streaming website for the community to enjoy…and maybe to get some ad clicks.</p>
<ul>
<li>None Yet</li>
</ul>
<h3>Version Numbers and Updating</h3>
<p>Explanation of versioning used by myself Ryan Bayne. The versioning scheme I use is called “Semantic Versioning 2.0.0” and more<br />
information about it can be found at http://semver.org/</p>
<p>These are the rules followed to increase the WTG Tasks Manager plugin version number. Given a version number MAJOR.MINOR.PATCH, increment the:</p>
<p>MAJOR version when you make incompatible API changes,<br />
MINOR version when you add functionality in a backwards-compatible manner, and<br />
PATCH version when you make backwards-compatible bug fixes.<br />
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.</p>
<h4>When To Update</h4>
<p>Browse the changes log and decide if you need any recent changes. There is nothing wrong with skipping versions if changes do not<br />
help you – look for security related changes or new features that could really benefit you. If you do not see any you may want<br />
to avoid updating. If you decide to apply the new version – do so after you have backedup your entire WordPress installation<br />
(files and data). Files only or data only is not a suitable backup. Every WordPress installation is different and creates a different<br />
environment for WTG Task Manager – possibly an environment that triggers faults with the new version of this software. This is common<br />
in software development and it is why we need to make preparations that allow reversal of major changes to our website.</p>


WTG Tasks Manager Beta

Task management with a plan - this plugin will grow to meet the needs of online business managed within WordPress.

Task Scheduler vs WTG Tasks Manager Beta