Status: | obsolete |
Progress: | 100% |
Version: | 1.9.0.1 - 2.3.1 |
$smwgOnDeleteAction
Configuration parameter details: | |
Name | $smwgOnDeleteAction |
Description | Sets whether the update process for when a page / property and its value assignments are deleted should be send to the job queue |
Default setting | See below |
Software | Semantic MediaWiki |
Since version | |
Until version | |
Configuration | Installation |
Keyword | performance · job queue |
__NOBREADCRUMBLINKS__
$smwgOnDeleteAction
is a configuration parameter that is used to move the update process for when a page / property and its value assignments are deleted to the job queue and thus to improve it. The configuration parameter was introduced in Semantic MediaWiki 1.9.0.1Released on an unknown date unknown versions of MediaWiki. It was removed in Semantic MediaWiki 2.4.0Released on an unknown date unknown versions of MediaWiki in favor of configuration parameter $smwgEnabledDeferredUpdate
Sets whether updates to pages are queued and executed after edits.1
Default setting
$smwgOnDeleteAction = array(
'smwgDeleteSubjectAsDeferredJob' => false,
'smwgDeleteSubjectWithAssociatesRefresh' => false
);
The default setting represents the legacy behaviour of Semantic MediaWiki 1.8.0Released on an unknown date unknown versions of MediaWiki and lower where a subject is directly deleted when "action=delete" is executed.
Available options
smwgDeleteSubjectAsDeferredJob
- Defers the deletion process to a background job.smwgDeleteSubjectWithAssociatesRefresh
- Allows to refresh entities that are connected to a deleted subject.
Changing the default setting
To modify the setting to this configuration parameter, add one of the following lines to your "LocalSettings.php" file after the enableSemantics()
call:
$smwgOnDeleteAction = array(
'smwgDeleteSubjectAsDeferredJob' => true,
'smwgDeleteSubjectWithAssociatesRefresh' => true
);
smwgDeleteSubjectWithAssociatesRefresh
is enabled the deletion process is being handled as a deferred background job with smwgDeleteSubjectAsDeferredJob
enabled, too.
Notes
- If configuration parameter
$smwgEnableUpdateJobs
Sets whether tasks are deferred until after a page was edited by using the job queue is disabled (not default) then the deletion process will always run directly even thoughsmwgDeleteSubjectAsDeferredJob
(see above) is enabled. - In case the deletion is executed as deferred job it is further suggested that the job queue is being run repeatedly within a narrow time frame to avoid an increased backlog.
See also
- <translate> bug <tvar name=1>59204</tvar></translate> about the rationale for this configuration parameter
References
- ^ gh:smw:1435