Thanks for working on this.
I guess your patch would have a better luck of getting merged, had it been realised in Setup.php instead of Webstart.php, because the earlier is where MW_CONFIG_FILE is expected to be setup for all entry points, web, maintenance scripts, etc.
Mar 28 2022
An environment variable such as MW_CONFIG_FILE was indeed on my wishlist! It would simplify some farm setups.
Mar 25 2022
It would be useful to have a parameter to ignore existing LocalSettings.php.
Mar 10 2022
I had already tried that before submitting the report. But thanks for the suggestion, @kostajh.
Mar 6 2022
Nov 16 2021
When I wrote the original ticket, I was assuming a certain shared understanding of the Egyptian hieroglyphic writing system. So let me clarify:
Feb 13 2021
What does this error actually mean?
If we were to try to bring the database to a consistent state, what tables and/or columns will be looking at?
Feb 11 2021
We are facing this error as well. Our setup is not master/slave DB.
Dec 16 2020
Jun 4 2020
Does this entail processing the old revisions of pages to include concurrent revisions of templates and link to concurrent revisions of pages as well?
May 14 2020
Mar 24 2020
An instance of MW 1.31.5 running on PHP 7.3.16-1+ubuntu18.04.1+deb.sury.org+1 (apache2handler) has just started to exhibit this exception after I upgraded from PF 4.7 to 4.8.
[5c424fca0b973708eb4db9b7] /%D9%88%D9%8A%D9%83%D9%8A:%D8%AE%D8%B7%D8%A9_%D8%AA%D8%B7%D9%88%D9%8A%D8%B1_%D8%A7%D9%84%D9%85%D8%AD%D8%AA%D9%88%D9%89 MWException from line 355 of /srv/src/mediawiki/1.31.5/includes/MagicWord.php: Error: invalid magic word 'default_form'
Mar 21 2020
- cp -a /srv/repo/umranica/temp to /var/tmp/umranica
- set $wgTmpDirectory = "/var/tmp/umranica";
The permissions on both directories where identical: drwxr-sr-x www-data adm.
Attempting to open a Flow discussion page yielded:
Could not open '/var/tmp/umranica/mw-UIDGenerator-UID-88
Mar 17 2020
Yes, it's about Mediawiki.
Mar 16 2020
Mar 4 2020
Shpuldn't this be a 403/Forbidden response?
I looked at the markup documentation but I cannot find a way to escape. I'm sure I'm missing something trivial!
Mar 1 2020
The mention to the commit in the description above was made inadvertently, and should be removed. I don't know how to escape it!
On a related, I just tried to submit a comment in a discussion for the first time, and got:
[ecdba561febffa874b627f87] Exception caught: Request to parsoid for "wikitext" to "html" conversion of content connected to title "Topic:Vhruneelfm63nzim" failed: 406
Even after having relaxed the strictness of Parsoid. Should I downgrade Parsoid?
For reference: https://www.adequate.at/csv-metadata-editor
Feb 19 2020
You are right. The issue with the performance is different from
comments. I just brought it up prompted by your suggestion of a
It is worth noticing that some non-WMF wikis need to set a locale other than en_US.utf8 to allow for the proper interaction with data stored in external sources.
Thinking of it, I don't think a row offset will help in my case, since I cannot know in advance how many rows are there before the sought one. But it might be useful in other cases.
I do not think there's a way to tell beforehand the number of comment
lines to expect in the header, since the idea is used to include an
arbitrary schema description.
Feb 18 2020
Just in the header, before the rows begin, preceeded by hashes.
Feb 17 2020
Feb 7 2020
Sep 19 2019
@Aklapper - oi, you are right of course, my bad. At least that mystery is solved.
I still don't understand why this was categorized as not a PF issue, though.
Sep 11 2019
To clarify, you want to be able to write something like $wgContentNamespaces[ NS_SRC ] = true;? In that case, you should be able to just write $wgContentNamespaces = NS_SRC; to add the namespace to the array
Jul 26 2019
@ahmad: This task seems to cover several requests. Note that https://www.mediawiki.org/wiki/How_to_report_a_bug asks to "Include only one problem per task", so this task might be closed as invalid as it's very complicated to track progress and status for each of the requests in this single task.
Jul 9 2019
Apr 23 2019
A use-case form non-wikimedia wikis would be: being able to create notification types to be triggered when pages are created having certain criteria; such as a specific category or in a specific namespace.
Feb 26 2019
Feb 12 2019
I just submitted a patch, referenced above, which can be seen in action at https://arabdigitalexpression.org/wiki/مستخدم:أحمد, featuring two icons added to the title: one is a regular "file:" from the wiki, an the other a string of Unicode codepoints representing an emoji+modifier.
Nov 2 2018
The immediate use-case I currently have is not related to Wikimedia:
An implementation of a glossary of localised terms pertaining to informatics and related fields, where discussions on the choices of localisations are very relevant for documenting the process and justifying the choices currently stabilised in the subject page.
Oct 28 2018
Oct 2 2018
Sep 27 2018
Sep 19 2018
Aug 13 2018
But there's also the usecase of having a workflow for handling received form submissions by one or more persons.
At least at Wikimedia, we just use mailing lists/distribution lists or OTRS queues
By "arbitary address" I meant one set by the form administrator, instead of having to be that of a wikiuser account as currently is the case. Not one entered by the form user.
Aug 11 2018
Jul 10 2018
I see your point of course.
Unfortunately I cannot reproduce this now as it seems to me more complex than what I can do at this time. I will keep monitoring for this behaviour, and add to this ticket later on. Reopening it, if necessary.
Jul 9 2018
The actions attributed to 127.0.0.1 were not only the result of extension AutoCreatepage's work.
Some of them were human edits that took place at around the same time. See the log https://genderation.xyz/wiki/Special:contributions/127.0.0.1
Jul 4 2018
Jul 2 2018
Actually this is not a problem. It's a feature request.
Jul 1 2018
Jun 28 2018
Apr 22 2018
The incident was not particular to that extension.
It happened with several regular edits by several reasons.
I don't know if this is related to the fact the editors sessions have been expiring so rapidly and frequently.
But thanks for the explanation.
Apr 21 2018
Apr 16 2018
Apr 14 2018
Apr 4 2018
Apr 2 2018
Jan 3 2018
Dec 21 2017
Yes, what I meant is what @Trizek-WMF understood: The permalink requested is that of the page from the specific moment the comment is made. I.e permalink of page, but displayed with comment metadata.
Dec 18 2017
Dec 14 2017
Nov 16 2017
Dec 11 2016
Dec 10 2016
A bounty is put on the implementation of this: https://www.bountysource.com/issues/39907864-a-mediawiki-extension-to-preview-maff-files
Dec 9 2016
May 30 2016
Sorry. Something is wrong with my report. I need to reproduce again and check.