Reference:Replace Text and Reference:BlueSpicePrivacy: Difference between pages

(Difference between pages)
No edit summary
Tag: 2017 source edit
 
No edit summary
Tag: 2017 source edit
 
Line 1: Line 1:
{{BSExtensionInfobox
{{BSExtensionInfo
|desc=Provides a form to let administrators do string replacements on the entire wiki, for both page contents and page titles.
|status=stable
|status=stable
|developer=Yaron Koren, Niklas Laxström
|developer=HalloWelt
|type=MediaWiki
|type=BlueSpice
|edition=BlueSpice pro, BlueSpice free, BlueSpice Farm, BlueSpice Cloud
|edition=BlueSpice pro, BlueSpice Farm, BlueSpice Cloud
|compatible=MediaWiki
|compatible=BlueSpice
|category=Administration
|category=Security
|license=GPL v2+
|features={{Messagebox|boxtype=note|icon=|Note text=This extension is no longer bundled with BlueSpice free starting v. 4.2.}}
|docu=https://www.mediawiki.org/wiki/Extension:Replace_Text
The extension '''Privacy'''  allows users to maintain their privacy and enables site maintainers to comply with the GDPR.
|features={{Messagebox|boxtype=note|icon=|Note text=The replace text operation is a deferred operation and is placed in the job queue. It is possible that the changes are not immediately shown on all affected pages.


''runJobs.php'' can be run from the ''maintenance'' folder to do the replacement immediately and to process the job queue.|bgcolor=}}
Users can:
}}


'''ReplaceText''' is a MediaWiki extension that provides both a special page and a command line script that allows administrators to search and replace any text in wiki pages and titles across the wiki.
*Request anonymization: The requests are directed to a site administrator for approval. If approved, the user is anonymized by the system.
*Request removal: The requests are directed to a site administrator for approval. If approved, the user is deleted from the system with all their data.
*Retrieve all data stored about them in the system.
*Give and revoke consent to the privacy policy.


It allows site administrators to:


Replacing the text is done in 3 steps on the ''Special:ReplaceText'' page:
*Manage anonymisation and deletion requests.
*Get an overview of the privacy policy and cookie consent of all users.
 
== User for automated tests ==
For the special test user <code>NoConsentWikiSysop</code>, the privacy consent requirement is bypassed, allowing automated test access to the wiki.
}}
 
==Cookie settings overview==
{| class="wikitable" style=""
|-
!COOKIE NAME
!DESCRIPTION
!TYPE
|-
| colspan="3" style="border-left-style:none;border-right-style:none;border-top-style:solid;border-bottom-style:solid;" data-ve-attributes="{&quot;style&quot;:&quot;border-left-style:none;border-right-style:none;border-top-style:solid;border-bottom-style:solid;&quot;}" |'''MediaWiki'''
|-
|$wgCookiePrefixBlockID
|This is usually the block ID concatenated with an HMAC in order to avoid spoofing (T152951), but if wgSecretKey is not set will just be the block ID.
|necessary, if block exists
|-
|$wgCookiePrefixUseDC
|A cookie to tell all CDN edge nodes to "stick" the user to the DC that handles this POST request (e.g. the "master" data center).
|necessary, if in use
|-
|$wgCookiePrefixUseCDNCache
|Have the user briefly bypass CDN so ChronologyProtector works for cacheable URLs.
|comfort
|-
|$wgCookiePrefixUserID
|ID of the logged in user ( only for logged in users )
|necessary
|-
|$wgCookiePrefixUserName
|Username of logged in user ( only for logged in users )
|necessary
|-
|$wgCookiePrefix_session
|Session ID for the current session
|necessary
|-
|<span style="color: rgb(4, 30, 73)">$wgCookiePrefixmwuser-sessionId</span>
|<span style="color: rgb(4, 30, 73)">Client-side session ID</span>
|necessary
|-
|$wgCookiePrefixforceHTTPS
|Force HTTPS for logins
|necessary
|-
|$wgCookiePrefixLoggedOut
|Force HTTPS for logins
|comfort
|-
|$wgCookiePrefixnotificationFlag
|Used for Echo notifications
|comfort
|-
| colspan="3" style="border-left-style:none;border-right-style:none;border-top-style:solid;border-bottom-style:solid;" data-ve-attributes="{&quot;style&quot;:&quot;border-left-style:none;border-right-style:none;border-top-style:solid;border-bottom-style:solid;&quot;}" |'''BlueSpice'''
|-
|$wgCookiePrefix_MWCookieConsent
|State of the user's cookie consent
|necessary
|-
|$wgCookiePrefixVEE
|Visual editor - user preference - VisualMode or wikitext
|comfort
|-
|<span style="color: rgb(4, 30, 73)">$wgCookiePrefixBlueSpiceDiscovery</span>
|<span style="color: rgb(4, 30, 73)">State of various stateful components in the skin</span>
|<span style="color: rgb(4, 30, 73)">comfort</span>
|}


# Entering the existing and the new text as well as selecting the namespaces and other options
# Checking the pages on which the text appears. Possible adjustment of the page selection
# Performing the replacement.


{{wcagCheck
{{wcagCheck
|wcagStatus=2-testing complete
|wcagStatus=2-testing complete
|wcagCheckedfor=Authoring tool
|wcagCheckedfor=Web, Authoring tool
|wcagTestdate=2022-08-08
|wcagTestdate=2022-08-08
|wcagLevel=AA
|wcagLevel=AA
|wcagSupport=partially supports
|wcagSupport=partially supports
|wcagWorkaround=no
|wcagWorkaround=no
|wcagComments=keyboard accessible.
|wcagComments=* Login step: checkboxes to confirm privacy policies do not receive initial focus. [https://support.hallowelt.com/issues/29401 erm: 29401]
 
Special:Privacy_Center page: check icons are not labelled  [https://support.hallowelt.com/issues/31373 erm:31373]
Screenreader issues: no form field labels, warning box has no aria-label; initial focus for replacement founds is not set, so it is difficult to select pages.
|extensionType=core
|extensionType=extended
|extensionFocus=reader
|extensionFocus=admin
}}
}}

Latest revision as of 16:23, 14 March 2023

Extension: BlueSpicePrivacy

all extensions

Overview
Description:

Management page for user privacy settings

State: stable Dependency: BlueSpice
Developer: HalloWelt License: GPL-3.0-only
Type: BlueSpice Category: Security
Edition: BlueSpice pro, BlueSpice Farm, BlueSpice Cloud Version: 4.1+

Features

Note:This extension is no longer bundled with BlueSpice free starting v. 4.2.

The extension Privacy allows users to maintain their privacy and enables site maintainers to comply with the GDPR.

Users can:

  • Request anonymization: The requests are directed to a site administrator for approval. If approved, the user is anonymized by the system.
  • Request removal: The requests are directed to a site administrator for approval. If approved, the user is deleted from the system with all their data.
  • Retrieve all data stored about them in the system.
  • Give and revoke consent to the privacy policy.

It allows site administrators to:

  • Manage anonymisation and deletion requests.
  • Get an overview of the privacy policy and cookie consent of all users.

User for automated tests

For the special test user NoConsentWikiSysop, the privacy consent requirement is bypassed, allowing automated test access to the wiki.

Technical Information

This information applies to BlueSpice 4. Technical details for BlueSpice Cloud can differ in some cases.

Requirements

  • MediaWiki: 1.36.0
  • BlueSpiceFoundation: 4.1

Integrates into

  • BlueSpicePrivacy

Special pages

  • PrivacyAdmin
  • PrivacyCenter
  • PrivacyConsent
  • PrivacyPages

Permissions

Name Description Role
bs-privacy-admin Execute Privacy administrative action admin, accountmanager

Configuration

Name Value
PrivacyConsentTypes array ( 'privacy-policy' => 'bs-privacy-prefs-consent-privacy-policy', 'terms-of-service' => 'bs-privacy-prefs-consent-tos', )
PrivacyCookieAcceptMandatory true
PrivacyCookieConsentProvider 'native-mw'
PrivacyDeleteUsername 'DeletedUser'
PrivacyEnableRequests true
PrivacyPrivacyPolicyLink ''
PrivacyPrivacyPolicyMandatory false
PrivacyPrivacyPolicyOnLogin true
PrivacyRequestDeadline 30
PrivacyTermsOfServiceLink ''

API Modules

  • bs-privacy
  • bs-privacy-get-all-consents
  • bs-privacy-get-requests

Hooks


Cookie settings overview

COOKIE NAME DESCRIPTION TYPE
MediaWiki
$wgCookiePrefixBlockID This is usually the block ID concatenated with an HMAC in order to avoid spoofing (T152951), but if wgSecretKey is not set will just be the block ID. necessary, if block exists
$wgCookiePrefixUseDC A cookie to tell all CDN edge nodes to "stick" the user to the DC that handles this POST request (e.g. the "master" data center). necessary, if in use
$wgCookiePrefixUseCDNCache Have the user briefly bypass CDN so ChronologyProtector works for cacheable URLs. comfort
$wgCookiePrefixUserID ID of the logged in user ( only for logged in users ) necessary
$wgCookiePrefixUserName Username of logged in user ( only for logged in users ) necessary
$wgCookiePrefix_session Session ID for the current session necessary
$wgCookiePrefixmwuser-sessionId Client-side session ID necessary
$wgCookiePrefixforceHTTPS Force HTTPS for logins necessary
$wgCookiePrefixLoggedOut Force HTTPS for logins comfort
$wgCookiePrefixnotificationFlag Used for Echo notifications comfort
BlueSpice
$wgCookiePrefix_MWCookieConsent State of the user's cookie consent necessary
$wgCookiePrefixVEE Visual editor - user preference - VisualMode or wikitext comfort
$wgCookiePrefixBlueSpiceDiscovery State of various stateful components in the skin comfort


Accessibility

Test status: 2-testing complete
Checked for: Web, Authoring tool
Last test date: 2022-08-08
WCAG level: AA
WCAG support: partially supports (workaround: no)
Comments:
  • Login step: checkboxes to confirm privacy policies do not receive initial focus. erm: 29401

Special:Privacy_Center page: check icons are not labelled erm:31373

Extension type: core
Extension focus: reader

Discussions