@bd808 Yes, there is wide consensus among the admins to activate the bridge. Thanks

Here we are:
https://nap.wikisource.org/wiki/Wikisource:Bar#SUBPAGES

Come on! All the Page namespace of all Wikisource projects have subpages: it's the very way they are ordered. If the magic word {{SUBPAGENAME}} does not work, a lot of links fail.
Probably they forgot to set the flag when they created the project... I should have logged it as a bug rather than a request.

@Mpaa transferbot.py doesn't check the ql of the pages. The error is arisen by the API when you try to write the text.

In T173385#5811262, @Mpaa wrote:

In T173385#5809505, @Ruthven wrote:

@Mpaa Well, the same happens without the option ql=4.

ql=4 is not the matter (it is just a filter on the pages the script should use), the 'Validated' code is inside the wikitext of the page.
Or you mean that there are other pages with lower quality level where you have the same issue?
If so, could you post it?

Hi all, sorry to reopen this, but I think that problem I encountered is related.
I am using delete.py under PAWS. I applied the patch above, but I obtain the same result: not being able to "undelete" files in a project where I am sysop.

@Mpaa Well, the same happens without the option ql=4.
@Tpt there is any workaround?

Actually I tested it with the bot account and the sysop account, both resulting in the You are not allowed to change the proofreading status of this page. error when creating a page in ns:Page.
Thus it seems that it is not possible to create or modify ns:Page using pywikibot?

Thanks a lot @Dcljr !

After several weeks of testing, I'm rather sure that it's an OS X issue. But I have no "autoreplace" option activated, or anything similar, apparently.

@Aklapper For instance, it happened on the following pages:

• it.wp Using Brave browser Version 0.66.101 Chromium: 75.0.3770.142 (64-bit) on OS X version 10.13.6, MediaWiki: 1.34.0-wmf.22 415c14d 13:21, 16 set 2019
• it.ws Using Safari browser Version 12.0.1, on OS X version 10.13.6, MediaWiki: same version as above, but happened with older versions as well.
• en.wp, not logged in, in order to rule out gadget interference, same Safari browser and MediWiki version as the former entry.
• NB: I tested under Windows 10 today (Firefox, IE), but wasn't able to replicate the issue. But, as long as it happens randomly, I cannot be sure that it's an OS issue.

@Dcljr Thanks, but never mind: I never liked too much the bureaucracy, and we're doing fine with the virtual namespace Wikisource:Prugetto ; see: https://nap.wikisource.org/wiki/Wikisource:Prugetto:Tecnicismi.

@Dcljr It is possible that I've misidentified the problem (@Alex_brollo Forse tu puoi aggiungere qualcosa in più), but, yes, to obtain this result it seems that we need a namespace alias.

There is a problem with the namespaces. Actually, some names were written in the local language (Neapolitan) instead that in English for the canonical field. This brings some importation errors, and some other general issue.

@Ladsgroup It's the task we talked about, remember? ;) Thanks

In T212883#5418407, @MarcoAurelio wrote:

@Dzahn Is Nnapulitano correct? {{#language:nap}} returns Napulitano.

The wiki is now online. T210752

In T212881#5341855, @Reedy wrote:

I note new wikis were never created in a timely fashion anyway...

Do you mean that it's impossible to create new projects?
In alternative, it's possible to create a project with a working version of Mediawiki? I mean: in the past projects were created (at least in 2003). Why it's not possible to create them in the same way as before, using the same version of the software? (sorry if the question sounds silly)

Just reporting some failing export, which occurs pretty often now. There are really no solution to this?

The error still appears (502 Bad Gateway) - and several users pointed at that.

It seems under control to me. There are spam emails from different sources in "Probably-spam", which is normal, and they have to be moved to "Junk" if they are really spam mails.

On the OTRS interface I set up the filter `00 spam-20190124 smtp-sortant2.phpnet.org`.
The remaining tickets have been moved to Junk.

The same issue seems to appear with image.py. Command line:

Please revert! Huge impact on all the it.source pages with an index (basically, the ones using template VoceIndice).

@rafidaslam Given that we'll deal with volumes/collections numbering, maybe a numeric sorting will suit the project better.

@MarcoAurelio Hi, from the grammar point of view, chiàcchiera is correct; however, chiacchiera is understandable without problems (but corresponds to the pronunciation chiacchièra – which doesn't exist as a word). I hope that's clear. Cheers.

In T210752#4792666, @jhsoby wrote:

The index and page namespaces are defined in the Proofread Page extension, for which I just submitted a patch above. In addition to this, you can localize the names of the following special pages:

• Special:IndexPages
• Special:PagesWithoutScans
• Special:ProofreadIndexOai
• Special:ProofreadIndexOaiSchema

(The last two don't seem to be in use on Wikimedia projects.) @Ruthven, if you can provide translations for these I can add them as well. (Oh, and translations don't have to be in AwkwardCamelCase, but can be in Normal spelling.)

The other namespaces (author and work) are defined in wmf-config.

@MarcoAurelio I propose:

Special pages

@MarcoAurelio for Namespace names 828 and 829, let's use the ones of nap.wiki: "Modulo" and "Modulo_chiàcchiera"

@MarcoAurelio : Rome should be on CET (UTC+1), so if napwiki is on the same time zone, 99% of the users will see their time displayed. For the automatic switch… I dunno, but the model to follow should be itwiki (which seems to work well from that point of view).

The capital city is Rome.
Thanks

Same kind of error when trying to undelete file versions on Commons for for history splitting of overwritten files (File:Catharina Elmsäter-Svärd.jpg)

In T176038#3612022, @Melos wrote:

I'm reading the local discussion. I think local Account Creator flag should be enough for the teacher. I don't see any reason to apply this change.

@akosiaris The problem is still there after the upgrade.

Removing the Online Agent widget solves the issue right away for me as well. It's a nice workaround. Thank you.