Last edited 7 months ago
by MLR

Known issues


A BlueSpicePrivacy banner is shown to admin users   v4.3+

Description: Admin users might see a yellow banner indicating that some privacy pages need to be created even if they have already been created for the footer links of the wiki.

screenshot of the alert banner
Privacy alert banner


This is to ensure that the confirmation links during a user's first login exist:

screenshot of login page with privacy acceptance checkboxes
Links to the privacy policy and the terms of services

Help: To make sure the links to the Privacy Policy and the Disclaimer of your wiki link to the correct pages:

  1. Click on the Privacy policy (1) and Disclaimers (2) links in your site footer. These are the pages that need to exist for the notice to disappear:
    screenshot of footer bar
    Footer links to the Privacy page and to the Disclaimer.
  2. If you haven't created these pages yet, create them. If the links lead to existing pages, write down the names of these pages (inklusive Namensraum-Präfix).
  3. Change the content of the following two system messages to the full pagename of these two pages.

    Privacy policy link:
    For the privacy policy link, open the page MediaWiki:bs-privacy-privacypage and change the text to the correct page name for your footer link:
    screenshot of the system message
    Changing the system message to reflect the correct page name.


    Disclaimers link:
    Repeat the same for the Disclaimers link. Open the page MediaWiki:Bs-privacy-termsofservicepage and add the correct name of the linked footer page for Disclaimers (by default, this is Site:General disclaimer)

The yellow alert banner should now be gone.

Missing language switcher on pages where the title area is hidden   v4.3+

Description: Since the language switcher is now located in the title area of wiki pages, pages that use the option __HIDETITLE__ currently cannot show the language switcher.


Help: This will be fixed in the next patch update.

Styles that are defined in templates or in MediaWiki:Common.css might no longer be applied   v4.3+

Description: Because of necessary forward-compatibility changes in the Discovery-skin, some templates might have to be manually updated to show certain styles correctly.


Help: *Affected Styles in MediaWiki:Common.css:
The styles in question need to be prepended with the selector#mw-content-text.
Before:
.myclass h2 {font-size:1.2em;}
After:
#mw-content-text .myclass h2 {font-size:1.2em;}
  • TemplateStyles:
    Templates that rely on the extensionTemplateStyles need to add a wrapper container with its own ID around the affected content. This ID needs to be prepended to the existing selector. The selector #mw-content-text will not work in that case.
    Example:
    .myclass h2 {font-size:1.2em;}
    
    Add the id that you have applied to your new or existing wrapper:
    #myID .myclass h2 {font-size:1.2em;}
    

Some wikis might experience styling inconsistencies for the newly added startpage templates   v4.3+

Description: If a wiki is already using some templates that are included in the new startpage templates (e.g. Image cards), these templates are not overwritten during the upgrade to BlueSpice 4.3.


Help: Any styling issues of any affected templates need to be adjusted manually.

VisualEditor gets deactivated in the Main namespace   v4.3+

Description: When changes are saved in the Namespace manager, the VisualEditor setting gets lost in the Main namespace.


Help: Re-activate the VisualEditor setting for the Main namespace.

The filter on special pages (e.g., "Recent changes") fails to load   -v4.2.6

Description: In some cases, the page Special:RecentChanges does not finish loading.


Help: You can add the following script to MediaWiki:Common.js:

if ( mw.config.get( 'wgCanonicalSpecialPageName' ) === 'Watchlist' ) {
document.body.classList.add( 'mw-rcfilters-ui-initialized' );
}
if ( mw.config.get( 'wgCanonicalSpecialPageName' ) === 'Recentchanges' ) {
document.body.classList.add( 'mw-rcfilters-ui-initialized' );
}



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

No categories assignedEdit

Discussions