Project:Support desk

Jump to: navigation, search

About this board

vde   Welcome to MediaWiki.org's Support desk, where you can ask MediaWiki questions!

There are also other places where to askCommunication: IRCCommunication#Chat, mailing listsMailing lists, Wikimedia Developer Support, Q&A, mwusers (unofficial forum) etc.

Before you post

Post a new question

  1. To help us answer your questions, please always indicate which versions you are using (reported by your wiki's Special:Version page):
    • MediaWiki
    • PHP
    • Database
  2. Please include the URL of your wiki unless you absolutely can't. It's often a lot easier for us to identify the source of the problem if we can look for ourselves.
  3. To start a new thread, click "Start a new topic".

After Upgrade to 1.30 some TOC anchor with German Umlauts or special Characters wont work

3
Mrniceguy1977 pc (talkcontribs)

Dear All

we recentyl upgraded from MediaWiki 1.23 to 1.30 and also migrated from SQL Lite to My SQL - so far everything worked except some Path Informations within an article but that could be fixed without any problem. The only Problem which still remain is that some anchor Links within the TOC wont work because they have German umlauts or some special characters in it.

Ill allready tried to delete an Article and save it new and when i take an look into the http source file ill cant see why it shouldnt work:

Source Code Example (TOC):

<li class="toclevel-2 tocsection-29"><a href="#L.C3.B6sung_2"><span class="tocnumber">8.4</span> <span class="toctext"><b>Lösung 2</b></span></a></li>

Anchor within Article:

<h2><span class="mw-headline" id="L.C3.B6sung_2"><b>Lösung 2</b></span></h2>

As i said before the Problem also occures when there is some special character in the TOC for Example:

<li class="toclevel-1 tocsection-30"><a href="#Darstellungsfehler_aller_Art_wie_falsche.2Ffehlende_Texte_und_Grafiken"><span class="tocnumber">9</span> <span class="toctext">Darstellungsfehler aller Art wie falsche/fehlende Texte und Grafiken</span></a>

Anchor: <h1><span class="mw-headline" id="Darstellungsfehler_aller_Art_wie_falsche.2Ffehlende_Texte_und_Grafiken">Darstellungsfehler aller Art wie falsche/fehlende Texte und Grafiken</span></h1>

How can i fix that issue? Thank you in advance, regards

Mrniceguy1977 pc (talkcontribs)

Additional Information: We use Windows Server 2016, IIS, MySQL and PHP 5.6 - what i found out is that on our testing enviroment ill added the Visual Editor Extension and as soon as i open an article within the new Visual Editor and go to Preview every Link work but actualy ill got the problem that it wont save the information. Maybe some can give me a clue how to manage the above mentionend issue with this additional information. Thank you in advance and have an nice day

Malyacko (talkcontribs)

What is "the issue"? You listed the actual results but not the expected results it seems?

Reply to "After Upgrade to 1.30 some TOC anchor with German Umlauts or special Characters wont work"

Historical info and other facts vs. Mainsteam media

3
Summary by AKlapper (WMF)

Off-topic discussion for mediawiki.org as it is about the content of some other wiki

85.191.189.171 (talkcontribs)

Hey, I edited info (corrected terms of territory and added the fact that it was occupied and still is), but it was reverted due to it not being "friendly" towards one specific religious group who lately got a big thing for censorship, and I got a message explaining that it had to follow mainstream media. What is that all about?

Zahkrosis (talkcontribs)

It's a very sensitive topic for many, so as to not be fully direct on to what it is, I will leave a hint:

The government of the people who occupy the territory of the country they're in doesn't allow equal rights, killed (literally killed) the previous government and is a terrorist organisation.

AhmadF.Cheema (talkcontribs)

This support forum is primarily for queries related to the MediaWiki software (the application that runs Wikipedia). For questions related to Wikipedia content, it would be better if you ask them at w:Wikipedia:Teahouse.

Johnywhy (talkcontribs)

How to transclude all namespaces (including custom namespaces)?

thx

Ciencia Al Poder (talkcontribs)

You transclude pages, not namespaces. Do you mean transcluding a page on a specific namespace? Or transclude a list of namespace names?

Johnywhy (talkcontribs)

A list of namespace names

Ciencia Al Poder (talkcontribs)
Johnywhy (talkcontribs)

is that the only way to query MySql tables, and display result on a wiki page?

Ciencia Al Poder (talkcontribs)

Namespaces are not in the database. They're configured in PHP. This is one option. Another option is to code a parser extension yourself to do that.

Johnywhy (talkcontribs)

the page you linked says "mw.site.namespaces - Table holding data for all namespaces"

Is that a text file, and not a table?

I do have some custom namespaces in my localsettings.php, but are you saying all default namespaces are defined in localsettings.php?

Ciencia Al Poder (talkcontribs)

It's a Lua table, not an SQL table, like there are HTML tables and such.

Wargo (talkcontribs)

Default namespaces are in core code and your namespaces in LocalSettings.

Johnywhy (talkcontribs)

what is "mw.site.namespaces"?

Wargo (talkcontribs)

If you install Extension:Scribunto you can use Lua to give more functions to templates. It is one of variables, arrays you can acces to read certain data.

Bawolff (talkcontribs)

If you have a specific namespace you want to get the name of and you have its id number, you can do {{ns:number here}}

There is no way in MediaWiki core to get a full list of defined namespaces from wikitext. As others have mentioned above, the information can be obtained using the scribunto extension, which adds Lua as an alternative language for writing templates.

Reply to "Transclude All Namespaces?"
Chauncey edgar (talkcontribs)

I have a new install of mediawiki 1.30.0. It's running on a physical server (not a VM). My php version is 5.6.35. The database is mysql 5.6.40. All this is running on FreeBSD 11.1-RELEASE-p9 with apache 2.4.33.

Here's the issue: I got wikimedia installed and running. Login worked fine. Afterwards, I enabled SSL on the wiki site. Now, when a user logs in, he gets redirected to https://example.comindex.php/Main_Page - note the lack of a '/' between the domain and 'index.php...' - and of course it can't be found. If you manually put the '/' where it belongs, Main_Page loads properly. Before I enabled SSL, this worked correctly. Any ideas? Thanks.

PS - I'd rather not leave apache running until a couple of other unrelated things are resolved.

Ciencia Al Poder (talkcontribs)

If clicking on the logo doesn't redirect you to the faulty address, I'd say the problem may be in redirect rules from apache (if you have any)

Chauncey edgar (talkcontribs)

Clicking the logo gets me to the correct Main_page; but I have to click the Back button in my browser in order to see the logo. Immediately after login, I only see my browser's "not found" page.

Thanks.

Chauncey edgar (talkcontribs)

Another way to phrase the question: when a user enter his password and clicks 'Log in,' which file processes the login and generates the URL?

AhmadF.Cheema (talkcontribs)

Unless you have changed anything in MediaWiki core files, the issue shouldn't be from there.

Can you show your Apache redirect rules (if any), and the values for $wgScriptPath, $wgArticlePath from your LocalSettings.php file.

Reply to "New login problem"
92.239.152.76 (talkcontribs)

I'm struggling to find ANYTHING related to how MediaWiki will be updated for GDPR compliance.

I really don't want to have to remove my wiki, but I can't find anything to help with this.

Malyacko (talkcontribs)

You could explain why exactly you think that you'd have to "remove your wiki" because of which specific aspect of the GDPR.

2001:16B8:10E3:E700:BCD7:8BBA:F67D:B20B (talkcontribs)

In how far should MediaWiki be affected by the GDPR? MediaWiki only is a tool, which allows putting arbitrary data in it. MediaWiki itself however does not contain any restrictions, what kind of data that might be and for the developers of the MediaWiki software it is impossible to control, what a single installation might be used for.

The users are responsible for the content they are putting up in their wikis. This content then could be affected by the GDPR. However, this data also would be affected, if put up inside a different tool, e.g. inside a WordPress blog or inside a Drupal installation.

92.200.127.85 (talkcontribs)

My concern is how personal data, once saved in MediaWiki, can be removed after a personal request. The "eternity" of revisions, the ability to "never forget" is a main topic for with MediaWiki. In Drupal and in WordPress you would delete a node or a post, and the content is gone. As we all know wikis work different. Maybe how wikis work is as a concept itself non-compliant with the GDPR, we'll see.

Moreover, WordPress releases these days a new version, where users have the ability to request a copy of all of THEIR special content provided to a certain platform and are able to download their "contribution package" afterwards. What will Mediawiki do, if a contributor does a request like this, pointing to GDPR?

This is how MediaWiki is affected by GDPR.

Penguin Waddles (talkcontribs)

What a website running MediaWiki does in response to a GDPR request to delete information or request a copy of all information depends on the owner of the website and his/her jurisdiction. MediaWiki has no easy built-in way to comply.

If someone was to submit a request to me, I'd ignore it because I'm in the US and despite what the EU claims, I'm not subject to any laws but US laws. All foreign court orders can be ignored too. So to Americans and others outside the EU, the GDPR really is a non-issue.

TheDJ (talkcontribs)

> So to Americans and others outside the EU, the GDPR really is a non-issue.

The "non-issue" part, sort of depends on if you want to be able to set foot in the EU at some point later in your life. Just something to consider.

Rocketpipe (talkcontribs)

The problem i see is that mediawiki stores user attributes and does not give the user control of how the attributes are used. Consider just the user name - it is attached to every edit made by the user. The user has no ability to remove any of those references.

It might be sufficient if the user was told of this limitation at the time that they selected their username.

CayceP (talkcontribs)

I too was looking on finding any information whether MediaWiki is GDPR compliant and whether the privacy statements needs to be changed. Even Wikipedia doesn't seem up to the par regarding this topic (somebody raised the issue back in February on the Wikipedia Mailing list), see https://www.quora.com/In-GDPR-what-will-happen-with-sites-like-Wikipedia-regarding-the-EU-regulation-in-terms-of-personal-information and https://lists.wikimedia.org/pipermail/mediawiki-l/2018-February/047224.html

Another issue could be that the account e-mail addresses are stored in MySQL databases unencrypted/in plain text.

This post was hidden by 196.72.158.67 (history)
92.200.127.85 (talkcontribs)

No, the problem is not that email addresses are stored, the problem arises if a user wants his data deleted or handed over. No consent is eternal due to GDPR, if you need consent from users to save their data, they have the right to revoke at any time.

Penguin Waddles (talkcontribs)

How do you propose enforcing such a "right" against a foreign website outside the EU's jurisdiction?

TheDJ (talkcontribs)

Every user can delete his or her email adres, simply by blanking it in the preferences. E-mail addresses are not required in MediaWiki.

Also, with regard to Wikipedia, when people use the site, they release their contributions under a license, which you could consider to be a legally binding contract. Now in the EU, if I go to a company, and tell them i want them to delete all their contracts with my name in them, i'm pretty sure that even under GDPR, you can pretty much ignore this.

Now I realize that not everyone has a WMF type of setup. However. Mediawiki is a tool and it has no requirement on you to make it 'easy' to comply with GDPR. If you need to go into the database to blank the text of a revision, well you can do that, no problem.

Ciencia Al Poder (talkcontribs)

The user is able to remove the consent by entering in their Special:Preferences and unset the email AFAIK

CayceP (talkcontribs)

I'm not a lawyer but was appointed DPO by my company and I spent the last weeks and months with this topic:

  • Old, existing laws (like the Cookie policy) are still applicable when GDRP become effective (as it has been for the last two years). So if your Wiki's server is located in the EU and/or you are catering to EU based users, you may want to use Extension:CookieWarning, if you aren't already. Text of warning/explanation may have to modified accordingly.
  • GDRP demands implementation of "appropriate, cost-effective controls" to protect the personal data of EU residents. It's still debated whether GDRP demands encryption, per se. Text uses words "such as encryption", "may include encryption", "as appropriate (...)pseudonymisation" etc. so this are more suggestions than a demand For SEO reasons and because Google Chrome will marks web pages without SSL/TLS certs as "not secure" soon, you may want to use a SSL certificate for your wiki anyway. Maybe your hoster can offer free Let's encrypt certs?
  • If your wikis' SQL DB is breached, you have to inform authorities and your users which information wereaffected/stored (usually IP address for all editors) and e-mail address, user names First and last name if you request them from your user for logged users) (see GDPR Article 34).
  • You may want to ask your users whether they are older than 16 years upon sign-up or if they have the consent by their parents.
  • I would update the wiki privacy, if not done already, that IP address (for all editors), E-mail addresses and User names (for registered users) are stored which is technically required for tracking and roll back of edits and that user agree to that upon sign-up or editing your wiki, that who they have to contact if they want to have their account deleted.
  • I would add the part with unset e-mail as mention above. Since an e-mail address is not required for registering this may only affect wikis that use emailconfirmed for editing privileges (for example for Anti Spam measures, YMMV).
  • I would also add the name of an Admins/Mod(s) on the privacy article in case somebody wants information about their stored data. I would add link how they can close their account.
  • Also add which data protection legal authority is responsible for your country/(or federal state like in Germany), this is also required by GDPR,
RichardHeigl (talkcontribs)
Reply to "GDPR compliance"

How to make a MediaWiki website "more" compliant to GDPR?

7
Biologically (talkcontribs)

Though this question (topic) may seem as a duplicate of this previous topic (Topic:Ucy8sfl44i6n6i51) posted on Support desk but that contained more discussions on the effect of GDPR than how to make it compliant. So, thought of starting this thread in an attempt to list all the practicable methods to make a MediaWiki installation (website) "more" GDPR compliant.

Just to avoid confusion -

1. This topic is NOT on how to change MediaWiki software to make it GDPR compliant (if at all necessary), it is on any website build on MediaWiki software. So, this focuses on extensions, scripts, or anything you can think of that may make the website more GDPR compliant.

2. Absolute compliance is not possible on public MediaWiki websites, at least for the website administrators, as most of the content are posted by the users. So the title is how to make it “MORE” GDPR compliant.

3. Please try to suggest anything about general MediaWiki websites that can be a problem due to GDPR and all the possible ways to correct or at least circumvent this problem.

I request all the active members to please share your valuable thoughts on this matter.

P.S.

I found this support desk to be the most helpful and active part of this website, so decided to ask it here.

Biologically (talkcontribs)

One discussion from Topic:Ucy8sfl44i6n6i51 -

Problem (mentioned by @Rocketpipe) - the username is attached to every edit make by the user. The user has no ability to remove any of those references.

Possible solution (also suggested by @Rocketpipe) - It might be sufficient if the user is told of this limitation during the account creation process.

Biologically (talkcontribs)

From topic Topic:Ucy8sfl44i6n6i51

Problem (mentioned by @CayceP) - the account e-mail addresses are stored in MySQL databases unencrypted/in plain text.

Possible solution (suggested by @Ciencia Al Poder) - this should not be a problem, as

  1. the email addresses are accessed only by the system admin.
  2. MediaWiki software is able to decrypt the email addresses even if encrypted, to use them for sending emails.
  3. Anyone with access of MediaWiki code or shell can decrypt them using the software
  4. The users have control to see their email addresses and delete them if they want to.
Biologically (talkcontribs)

From Topic:Ucy8sfl44i6n6i51

Problem (anonymous user) - the problem arises when the user wants to delete or hand over their data.

Possible solution (suggested by @TheDJ) -

  1. a user can delete his/her email address by removing it in the preference. Email address is not required by MediaWiki.
  2. The user releases his/her contributions under the license mentioned in the specific website.
  3. Database user can delete a specific contribution if needed.
CayceP (talkcontribs)

Please see my reply to the other topic (is there way to merge them?)

ETA: Copy and paste from the other thread:

I'm not a lawyer but was appointed DPO by my company and I spent the last weeks and months with this topic:

  • Old, existing laws (like the Cookie policy) are still applicable when GDRP become effective (as it has been for the last two years). So if your Wiki's server is located in the EU and/or you are catering to EU based users, you may want to use Extension:CookieWarning, if you aren't already. Text of warning/explanation may have to modified accordingly.
  • GDRP demands implementation of "appropriate, cost-effective controls" to protect the personal data of EU residents. It's still debated whether GDRP demands encryption, per se. Text uses words "such as encryption", "may include encryption", "as appropriate (...)pseudonymisation" etc. so this are more suggestions than a demand For SEO reasons and because Google Chrome will marks web pages without SSL/TLS certs as "not secure" soon, you may want to use a SSL certificate for your wiki anyway. Maybe your hoster can offer free Let's encrypt certs?
  • If your wikis' SQL DB is breached, you have to inform authorities and your users which information were affected/stored (usually IP address for all editors) and e-mail address, user names First and last name if you request them from your user for logged users) (see GDPR Article 34).
  • You may want to ask your users whether they are older than 16 years upon sign-up or if they have the consent by their parents.
  • I would update the wiki privacy, if not done already, that IP address (for all editors), E-mail addresses and User names (for registered users) are stored which is technically required for tracking and roll back of edits and that user agree to that upon sign-up or editing your wiki, that who they have to contact if they want to have their account deleted.
  • I would add the part with unset e-mail as mention above. Since an e-mail address is not required for registering this may only affect wikis that use emailconfirmed for editing privileges (for example for Anti Spam measures, YMMV).
  • I would also add the name of an Admins/Mod(s) on the privacy article in case somebody wants information about their stored data. I would add link how they can close their account.
  • Also add which data protection legal authority is responsible for your country/(or federal state like in Germany), this is also required by GDPR,
Biologically (talkcontribs)

Hi, you can copy-paste the reply here. So that all the answer can be found in one place. Thank you for the all the solutions suggested by you.

RichardHeigl (talkcontribs)
Reply to "How to make a MediaWiki website "more" compliant to GDPR?"

When I attempted to configure a wiki family in Localsettings.php, it failed gracefully.

4
Newman2 (talkcontribs)

MediaWiki Version: 1.30

PHP Version: 5.6.36

MySQL Version: 5.6.39-cll-lve

In my Localsettings.php file I have been trying to configure a wiki family on my wiki, and it did not work well at the time. The site failed gracefully, leaving an error message saying that it was not possible to determine the wiki ID. Is there a way to fix this problem? What is wrong with the wiki family setup code? The code that the wiki had looked like this:

if ( defined( 'MW_DB' ) ) {

''// Set $wikiId from the defined constant 'MW_DB' that is set by maintenance scripts.''

$wikiId = MW_DB;

} elseif (isset($_SERVER['SERVER_NAME']) && $_SERVER['SERVER_NAME'] == 'wiki1.example.org') {

''// Add a value to the $wikiId variable for e.g. https://wiki1.example.org/'' 

$wikiId = 'wiki1';

} elseif (isset($_SERVER['SERVER_NAME']) && $_SERVER['SERVER_NAME'] == 'example.org' && substr($_SERVER['REQUEST_URI'], 0, 6) == '/wiki2') {

''// Add a value to the $wikiId variable for e.g. https://example.org/wiki2''

$wikiId = 'wiki2';
} else {
''// Fail gracefully if no value was set to the $wikiId variable, i.e. if no wiki was determined''
die( 'It was not possible to determine the wiki ID.' );
}
Bawolff (talkcontribs)

If using $wgConf and SiteConfiguration, you can use the --wiki command line option to select the right wiki

Newman2 (talkcontribs)

How do you get to use the wiki command line option? Where is it located? It is hard to locate things in SiteConfiguration.

Bawolff (talkcontribs)

Sorry, i read too quickly. I thought you were talking about maintenance scripts.

You could try and get what the current server is by looking at $wgServer (That variable should be registered by the time LocalSettings.php is loaded)

Reply to "When I attempted to configure a wiki family in Localsettings.php, it failed gracefully."
Julznova (talkcontribs)

Hi,

I'm attempting to use visualeditor over https, but when I attempt to edit an article using visualeditor I'm constantly getting curl error 55:

"Error loading data from server: apierror-visualeditor-docserver-http-error: (curl error: 55) Failed sending data to the peer. Would you like to retry?"

Localsettings.php:

wfLoadExtension( 'VisualEditor' );

        $wgDefaultUserOptions['visualeditor-enable'] = 1;

        $wgDefaultUserOptions['visualeditor-editor'] = "visualeditor";

        $wgHiddenPrefs[] = 'visualeditor-enable';

//      $wgVisualEditorParsoidURL = 'https://mydomain.net:8143';

$wgVirtualRestConfig['modules']['parsoid'] = array(

        'url' => 'https://mydomain.net:8143',

        'domain' => 'localhost',

        'prefix' => 'localhost',

//      'forwardCookies' => false,

//      'parsoidCompat' => false

);

Stunnel parsoid.conf:

cert = /etc/httpd/conf/ssl/mydomain.net.crt

key = /etc/httpd/conf/ssl/mydomain.net.key

CAfile = /etc/httpd/conf/ssl/root.crt

[parsoid]

accept  = 8143

connect = 8142

Parsoids localsettings.js:

'use strict';

exports.setup = function(parsoidConfig) {

        // Do something dynamic with `parsoidConfig` like,

        parsoidConfig.setMwApi({

        uri: 'https://mydomain.net/wiki/api.php'

        });

};

I've tried millions of different combinations of uri/url, any help is greatly appreciated.

Ciencia Al Poder (talkcontribs)

If the setup instructions don't help, you should try to debug the issue yourself by inspecting the traffic the browser generates (use F12 to see the requests, where they are sent and if the URL makes sense). Open the RESTBase url from your browser and make sure it opens the documentation page.

If this is not a problem, you'll have to look at parsoid and RESTBase error logs, and if there's anything obvious, check communication between RESTBase, Parsoid and MediaWiki with a packet sniffer like tcpdump

Reply to "VisualEditor curl error 55"
221.153.37.97 (talkcontribs)

When I search on my wiki, it always list the result of search.

It's same when I type exact word.

I think when my keyword is exactly same with article name, it's much more proper that the article just show up. not listing results.

But I couldn't find the option of this. Is there someone can help me?

Reply to "just open the article when search"

Undesired line break after template

1
73.183.172.9 (talkcontribs)

I’ve been trying to use multiple templates in a row like this:

{{Tlx}}{{Tlx}}

With Template being something basic like the output still is

Hello World. Hello World.

as opposed to the desired result

Hello World.Hello World.


What am I missing?

Reply to "Undesired line break after template"