Bureaucrats, confirmed, Administrators
4,558
edits
Changes
Jump to navigation
Jump to search
recommend to replace baskets extension
| This extension allows the utilization column of the Baskets tables to be edited directly using AJAX and saving values into 'basket' tables rather than in the traditional wiki-text revision tables.
| 1.4.3, 2018-05-25
| Unable to find example"Baskets" can be found in the hierarchy list of the leftnav under the 'Compliance' folder. The page name, by convention, is 'Baskets' e.g. https://clienttest.dm.dcstemporary.com/Baskets This is really neat, and very advanced. However, now that Visual Editor is available, I'd suspect that the user experience of editing large tables in Visual Editor would be much better. '''Replace Baskets with Visual Editor'''
|-
| [https://github.com/debtcompliance/mediawiki/wiki/Extensions#dcscommon DcsCommon]
| pervasive
|-
| [https://github.com/debtcompliance/mediawiki/wiki/Compliance-Checklist DcsComplianceChecklist]| purpose?Provides a dropdown list of loans and responsibility terms by which the table can be filtered on the CheckList page (by convention)
| release?
| yes
|-
| [https://github.com/debtcompliance/mediawiki/tree/master/extensions/DcsJobAdmin DcsJobAdmin]
| See [https://github.com/debtcompliance/mediawiki/wiki/Background-jobs Background info on Background jobs]. Creates a Special Page [https://clienttest.dm.dcstemporary.com/Special:DcsJobAdmin Special:DcsJobAdmin] where you can start a new job; or view current and historical jobs. Each job type loads it's own form into the Admin page. The job runner extends the Maintenance class, and loops over running jobs to provide some progress reporting. It saves the most recent 10 jobs to a 'history' list.
There are functions in the code for:
* Return a list of the currently running jobs sorted by start time.
** UpgradeAttachments
Each (or almost all?) PHP file is backed by a perl file which was the basis for the PHP development? I'm not really sure why everything . Everything is written twicebecause it all started back when the best framework for handling MediaWiki jobs was a perl bot framework. Things have changed significantly over the recent past for MediaWiki and the job queue.
According to [https://github.com/debtcompliance/mediawiki/wiki/Extensions#dcsjobadmin the documentation], it allows you to manage jobs. But, I'm wondering how much this is actually used? The job queue should be run automatically by cron, and the administrative user shouldn't have to worry about it really. If there is a usage pattern where job execution is time sensitive, there is a use for an Admin function; but I'm curious about the usage patterns that create large or numerous jobs. Otherwise, set wgJobRunRate to zero, and put it into cron `0 0 * * * root /usr/bin/php /var/www/example.com/www/w/maintenance/runJobs.php > /var/log/runJobs.log 2>&1`
