Reference:ContentTransfer: Difference between revisions

Latest revision as of 06:28, 2 June 2025


Overview
Description:	Enables pushing content from one wiki to another
State:	stable	Dependency:	BlueSpice
Developer:	HalloWelt	License:	GPL-3.0-only
Type:	BlueSpice	Category:	Administration
Edition:	BlueSpice farm	Version:
View user help page

Features

Users can copy up to 200 pages per transfer from a wiki to the same namespace of a target wiki.

Pages that already exist in the target wiki can be manually merged by activating the extension MergeArticles.

Depending on the settings selected on the ContentTransfer special page, the following files are copied:

the selected wiki pages
the related category pages
the book page associated with wiki pages
the templates associated with wiki pages
attached files

Configuration

In on premise installations, the functionality is already activated.

Additional settings

$wgContentTransferIgnoreInsecureSSL = false; // Ignore invalid SSL certificates (for test systems)
$wgContentTransferPageLimit = 200; // Max number of pages to be allowed at one 
$wgContentTransferOnlyContentNamespaces = true; // Only allow content namespaces to be selected in filters
$wgContentTransferAllowTalkNamespaces = false; // Allow talk namespaces to be selected in filters

Certificates

If self-signed certificates are being used (and if no outbound connections are allowed) one must set

$GLOBALS['wgWikiFarmConfig_internalServer'] = 'http://wiki-web:9090';

in data/bluespice/pre-init-settings.php.

Technical Information

Technical details for BlueSpice cloud can differ in some cases.

Requirements

MediaWiki: 1.43.0

Integrates into

ContentTransfer

Special pages

ContentTransfer

Permissions

Name	Description	Role
content-transfer	Transfer content to other wikis	admin

Configuration

Name	Value
ContentTransferAllowTalkNamespaces	false
ContentTransferEnableBetaFeatures	false
ContentTransferIgnoreInsecureSSL	false
ContentTransferOnlyContentNamespaces	false
ContentTransferPageLimit	200
ContentTransferTargets	array ( )

API Modules

content-transfer-do-push-single
content-transfer-get-pages
content-transfer-purge-pages
content-transfer-push-info

Hooks

LoadExtensionSchemaUpdates

PDF exclude - start

To submit feedback about this documentation, visit our community forum.

PDF exclude - end

@@ Line 1: / Line 1: @@
-{{BSExtensionInfobox
+{{BSExtensionInfo
 |desc=Copies new or existing wiki pages into a different wiki. (v3.2 and up)
 |status=stable
 |developer=HalloWelt
 |type=BlueSpice
-|edition=BlueSpice Farm (deactivated)
+|edition=BlueSpice farm
 |compatible=BlueSpice
-|category=Quality Assurance
+|category=Administration
 |license=GPL v3
-|active=No
+|features=Users can copy up to 200 pages per transfer from a wiki to the same namespace of a target wiki.
-}}
-{{wcagCheck
-|wcagStatus=2-testing complete
-|wcagCheckedfor=Authoring tool
-|wcagTestdate=2022-08-10
-|wcagLevel=AA
-|wcagSupport=partially supports
-|wcagWorkaround=no
-|wcagComments=Small keyboard issue: Transfer button is difficult to focus. Could use shortcut like VE Save button (Shift+alt+S)
-Screenreader accessibility: multiple issues
+Pages that already exist in the target wiki can be manually merged by activating the extension [[:de:Referenz:MergeArticles{{!}}MergeArticles]].
-erm:
+Depending on the settings selected on the ContentTransfer special page, the following files are copied:
-|extensionType=extended
-|extensionFocus=organizer
+* the selected wiki pages
+* the related category pages
+* the book page associated with wiki pages
+* the templates associated with wiki pages
+* attached files
+==Configuration==
+In on premise installations, the functionality is already activated.
+=== Additional settings ===
+ <span class="nv" style="box-sizing: inherit;">$wgContentTransferIgnoreInsecureSSL</span> <span class="o" style="box-sizing: inherit;">=</span> <span class="k" style="box-sizing: inherit;">false</span><span class="p" style="box-sizing: inherit;">;</span> <span class="c1" style="box-sizing: inherit;">// Ignore invalid SSL certificates (for test systems)</span>
+ <span class="nv" style="box-sizing: inherit;">$wgContentTransferPageLimit</span> <span class="o" style="box-sizing: inherit;">=</span> <span class="mi" style="box-sizing: inherit;">200</span><span class="p" style="box-sizing: inherit;">;</span> <span class="c1" style="box-sizing: inherit;">// Max number of pages to be allowed at one</span>
+ <span class="nv" style="box-sizing: inherit;">$wgContentTransferOnlyContentNamespaces</span> <span class="o" style="box-sizing: inherit;">=</span> <span class="k" style="box-sizing: inherit;">true</span><span class="p" style="box-sizing: inherit;">;</span> <span class="c1" style="box-sizing: inherit;">// Only allow content namespaces to be selected in filters</span>
+ <span class="nv" style="box-sizing: inherit;">$wgContentTransferAllowTalkNamespaces</span> <span class="o" style="box-sizing: inherit;">=</span> <span class="k" style="box-sizing: inherit;">false</span><span class="p" style="box-sizing: inherit;">;</span> <span class="c1" style="box-sizing: inherit;">// Allow talk namespaces to be selected in filters</span>
+===Certificates===
+If self-signed certificates are being used (and if no outbound connections are allowed) one must set
+<syntaxhighlight lang="text">
+$GLOBALS['wgWikiFarmConfig_internalServer'] = 'http://wiki-web:9090';
+</syntaxhighlight>
+in <code>data/bluespice/pre-init-settings.php</code>.
 }}