Meta:Administrators' noticeboard/Archive 5

__NOINDEX__

Category:Wikipedia pages with incorrect protection templates
Today I present to you a problem that has me completely baffled. If you look at, you can see that it has only translations of Custom domains. That said, the reason that it says "incorrect protection template" is most likely because the original Custom domains is in fact protected, but that doesn't carry over for translations. Do you think there is a fix to this or will this be permanent? Just to clarify once again, this is regarding  --Integer  talk 03:55, 21 January 2021 (UTC)


 * Please note that I have moved this here from SN as this only concerns Meta where Stewards generally should not interfere. Thank you. 07:57, 21 January 2021 (UTC)
 * Also, I noticed this while cleaning up Special:WantedCategories. It is likely caused by a template imported from Wikipedia. 08:26, 21 January 2021 (UTC)
 * Integer Thank you for raising this issue. R4356th was correct in moving this thread from stewards' noticeboard to Administrators' noticeboard, where this request is now more in scope. I would quibble just a bit with the phrasing of R4356th's explanation, though, as stewards do have some managerial responsibility for Meta Wiki. It's a governance structure that is somewhat complicated, to put it mildly. For example, Meta bureaucrats oversee most local user group permissions requests requiring a community election (i.e., at Requests for permissions) or which can only be granted by Meta bureaucrats as a discretionary appointment at Administrators' noticeboard (i.e., interface administrator) whereas stewards oversee the global group permissions requests plus one local Meta user group permission request, wiki creator, which was functionally implemented as a local rather global user group for various reasons, but it very much is a global role (i.e., it's just only used on Meta, essentially). Meta bureaucrats generally close most local Meta Wiki discussions, whereas stewards close most global discussions. ManageWiki settings changes are done by stewards. Extensions are enabled by stewards, though in most, but not necessarily all, cases, stewards should consult with a Meta bureaucrat to see whether a community discussion of some sort is needed. In short, it's quite complicated. Alas, I digress. Nevertheless, R4356th is correct that stewards have little concern for which pages or templates are appropriate to Meta, or even such matters as how pages should be titled, generally speaking. Thus, Administrators' noticeboard is the best venue for anything concerning Meta Wiki only. Most requests here can be handled by either a Meta administrator or Meta bureaucrat, whether a community discussion is warranted or not. That's not to say that there may never be a particular request at Administrators' noticeboard that would never be handled by a steward, depending on the specific change required. For example, a minor change to Special:ManageWikiDefaultPermissions might be requested here, though community noticeboard would probably still be a better venue, it's not unreasonable for it to be requested here. In any case, to your specific question, I've gone ahead and just ✅ Template:Pp-template that was causing this issue. While we could have corrected the template to improve the category by which the template categorized pages, since it was only used on one or perhaps two pages, it wasn't really used. And, to be honest, unless we have a bot like AnomieBOT that updates the page protection icons automatically when page protection levels change or expire, these errors will be commonplace. Since one can easily view the protection status in the "page information" feature of a given page, it's not that useful. Hope that helps. Dmehus (talk) 13:21, 21 January 2021 (UTC)
 * Got it, and very much! Integer  talk 13:23, 21 January 2021 (UTC)
 * Integer ✅. Dmehus (talk) 13:28, 21 January 2021 (UTC)

Request for Updating Miraheze
Could someone please update the news section in "Miraheze" to note that Miraheze now hosts more than 4000 wikis? Thank you. 10:52, 21 January 2021 (UTC)


 * R4356th I'm going to mark this as ❌ because (a) we've hosted over 4,500 wikis before and (b) a large swath of closed wikis is due to be added to Special:DeletedWikis in the next few days, which will likely drop us below 4,000 wikis again. Thus, if it's considered significant enough news to note on Main Page, I'd rather wait until it's over 4,100-4,200 wikis. Dmehus (talk) 11:08, 21 January 2021 (UTC)
 * : ( Okay. 11:10, 21 January 2021 (UTC)
 * Yeah, I have to agree as I believe we did once update the News like that and afterwards it was quite awkward when the number went down because of the wikis deleted per the Dormancy Policy Reception123 (talk) ( C ) 20:05, 21 January 2021 (UTC)

Request for Reviewing Template:Documentation
Could someone please review Template:Documentation? It has a Lua error. I am guessing you may have to import a Lua module. Thank you. 17:38, 20 January 2021 (UTC)


 * ✅ Integer talk 21:25, 20 January 2021 (UTC)
 * Please leave importing to admins from the next time. We should attribute the module authors by importing instead of merely copy-pasting. This is due to legal reasons. I hope this helps. To admins, this is ❌. 21:34, 20 January 2021 (UTC)
 * Oh, ok. Got it. Will note this for future reference. Integer talk 21:36, 20 January 2021 (UTC)
 * For what it's worth, past practice on Meta Wiki with respect to importing versus copying and pasting has been...mixed, to say the least, often without even a required edit summary linking to the source page (via an interwiki page link). Thus, while it's true attribution is required, full history attribution is not required, provided an edit summary link to the source page is included. Best practice here is to say something like, where   is the source page from English Wikipedia. Dmehus (talk) 23:50, 20 January 2021 (UTC)
 * R4356th I don't see where there's a Lua error on either Template:Documentation or Template:Documentation/doc. Can you clarify what you mean just a bit? Thanks. Dmehus (talk) 23:52, 20 January 2021 (UTC)
 * The errors have been fixed by copy-pasting the required modules mentioned in the error by Integer. However, as we do not have any link to WP or MW.org stating that we imported them from those sites in a widely visible place for modules, conventionally, we import them instead of merely copy-pasting. This is what you are requested to do now. 09:23, 21 January 2021 (UTC)
 * R4356th I don't see where Integer fixed these issues by copying and pasting, though, unless you don't mean Template:Documentation and Template:Documentation/doc? I just don't see a revision issued by this user. These templates we did actually import correctly, though; however, we could do well to provide a link in an edit summary to the source templates, so I will do that now. Assuming it was only these two templates, I'm going to mark this as ✅ following my correction. Dmehus (talk) 12:31, 21 January 2021 (UTC)
 * The template needed a Lua module which Integer copy-pasted themselves. This sadly means that this is ❌. 13:16, 21 January 2021 (UTC)
 * I am assuming you forgot about this. 22:01, 21 January 2021 (UTC)
 * R4356th Oh, you didn't link to the Lua module. I thought I checked Module:Documentation and saw it was already imported or properly attributed, but I'll have another look. What other module(s) need to be imported? Dmehus (talk) 22:25, 21 January 2021 (UTC)
 * It needed some other module. I cannot remember the name right now. Perhaps, can. Nevertheless, I will recheck the template.  12:51, 22 January 2021 (UTC)

Request for Making a Translation-related Configuration Change
Hello, as a Meta Translation Administrator, I would like  (can be found in the Localisation section) to be checked in ManageWiki. It will help translators by showing machine translation suggestions. Thank you. 16:08, 21 January 2021 (UTC)

✅. Dmehus (talk) 21:42, 21 January 2021 (UTC)
 * R4356th I personally would have no objections to this. I'm going to ping Reception123 to this thread to say whether he feels this needs a full Administrators' noticeboard discussion. I personally don't feel it does, as we have no policy on translations. We primarily rely on users' common sense that only those users who know a language should be doing translations in said language. This is a tool that would help users who know a language, but may not be native speakers of said language. Dmehus (talk) 18:12, 21 January 2021 (UTC)
 * Since it doesn't ultimately change the workflow of this wiki and just provides a translation aid I would personally think it's fine to proceed without a formal discussion, especially since I can't really see a reason to oppose this. I don't think it would encourage users doing machine translations, but if that happens they can be told accordingly. Reception123 (talk) ( C ) 20:01, 21 January 2021 (UTC)
 * Yeah, that's a good way of looking at it, I think. Additionally, if the extension proposed to add any new local Meta user groups, or alter existing Meta user groups in a significant way, I would also think we'd want to have a local community discussion on Meta Wiki. As you and R4356th have articulated, this is just adding an additional tool to existing translators' and translation administrators' toolkits to ease their translation work. If it becomes an issue, then we may need to have a larger community discussion towards adopting as translation policy or guidelines for translators to adhere to, but we can have that policy discussion at a later time when it's required. Accordingly, this requested settings change is now
 * Thank you very much. 21:55, 21 January 2021 (UTC)
 * Um... I do not see any change? 22:00, 21 January 2021 (UTC)
 * Hrm, are you still seeing no change? Is there any other setting change needed? Dmehus (talk) 22:27, 21 January 2021 (UTC)
 * I still do not see any change. I will take a look at the Translate extension's documentation and Miraheze's mw-config repositroy. 12:49, 22 January 2021 (UTC)
 * I took a quick look at Yandex's translation service and looks like the languages I have tested with are supported. I will further look into this. 14:16, 22 January 2021 (UTC)
 * On second thoughts, a really simple answer could be that we are not paying Yandex. 14:18, 22 January 2021 (UTC)
 * Never mind. I think I found the problem. I will make a pull request. 14:24, 22 January 2021 (UTC)
 * CSP seems to be causing this. Universal Omega has made a pull request to add Yandex to the CSP whitelist. 15:49, 22 January 2021 (UTC)
 * Per finding on Discord or IRC, this has likely been caused by Miraheze's API key becoming invalid. 16:01, 22 January 2021 (UTC)
 * R4356th Ah, that makes the most sense actually because I was sure I'd used the Yandex translation hints on TestWiki in the past year. Nevertheless, if you can advise when this has been corrected, that'd be awesome. Thanks Dmehus (talk) 23:27, 22 January 2021 (UTC)
 * Miraheze was using a free API key given by a user (they cannot remember where they got it) which got expired in August of 2020. So I am not sure whether it is coming back. 13:33, 23 January 2021 (UTC)

R4356th Ah, okay, thanks for the update. Yeah, we likely don't have the budget to pay for a premium API key. I thought I saw that the Translate extension has configuration variables that can work with either of Google Translate, Yandex Translate, Bing Translate, and possibly even Naver Translate? I wonder if either of those has a free plan, without usage limitations, that we could try. Dmehus (talk) 17:27, 23 January 2021 (UTC)

meatball
Ho ho ho,

links to, but it is 301'ing to. One less 301s are always better, so can we modify this?

Thanks. &mdash; revi  14:30, 26 January 2021 (UTC)
 * ✅,--MrJaroslavik (talk) 14:35, 26 January 2021 (UTC)

Translation administrator
I know I don't have many edits yet, but yes, the number of edits would increase if I had translation administrator rights: I could use them to translate pages and also mark them for translation. On my chat page, I was talking to a Miraheze user when I asked how I could help Miraheze and collaborate with others so if I understood correctly, translation was taken up. Therefore, I would like the rights of a translation administrator. Anton (talk) 20:20, 28 January 2021 (UTC)


 * Anton I'm not opposed to this, but which language(s) do you speak fluently or fairly fluently, and on which wiki(s) have you used the Translate extension? Thanks. Dmehus (talk) 20:23, 28 January 2021 (UTC)


 * I speak Swedish, Spanish and French, moderately English and Finnish well. I have learned Russian, but I do not know about than a couple of sentences.  Yes, and I would use that Translate tool.  In addition to this, I would mark the pages for translation - and I would translate them as well. --Anton (talk) 20:34, 28 January 2021 (UTC)
 * Anton I'm going to put this on hold for a week or two, at minimum, as I would like to see you doing some translations first in languages in which you're most fluent, doing translation reviews of existing translations, and experimenting with the translation administration tools on one of your wikis. How's that? Dmehus (talk) 20:39, 28 January 2021 (UTC)
 * While I am not an administrator, I would suggest you to become an active translator first. 20:39, 28 January 2021 (UTC)
 * Yeah, that's what I was suggesting as well. Basically, you don't need translation administrator tools to translate. If you're active translating, you'll usually be invited to participate in fairly short order. Dmehus (talk) 20:43, 28 January 2021 (UTC)
 * Okay, you can grant me translator rights and later even a translation administrator :) it's good to go to traffic.  I am now really going to participate in Miraheze. Anton (talk) 20:47, 28 January 2021 (UTC)
 * You do not need the Translator rights to translate anything here! You can just visit Special:Translate or click the "Translate" button on any translatable page. I hope this helps. :) 20:50, 28 January 2021 (UTC)
 * Thank you!  This helped.  I got started! Anton (talk) 21:08, 28 January 2021 (UTC)
 * Anton ✅! I'll follow up with you in a couple weeks on your user talk page. Dmehus (talk) 01:23, 29 January 2021 (UTC)

FuzzyBot breaks bulleted lists
FuzzyBot breaks bulleted lists, see Special:Diff/159755 and Miraheze/eo for example. Why does this keep happening and what can we do about it? --Sabelöga (talk) 12:54, 30 January 2021 (UTC)


 * I am to blame for this, apparently. I updated the translation syntax which seems to have caused this. Having said that, we should always keep the syntax up to date from time to time. I will look into switching back to the previous one in a few hours. We should consider making an upstream task on Wikimedia Phabricator regarding this as well. Also a note for Interface Admins: it may be possible to fix the issue with CSS. 13:46, 30 January 2021 (UTC)
 * Do you have a list of broken pages? 16:05, 30 January 2021 (UTC)
 * For what it's worth, I don't think R4356th's translation edits or administration is to blame for this. If I'm understanding correctly, this occurs when a translated source page is marked for translation. The Translate extension, via FuzzyBot, adds  with a Translate extension-specific CSS class that breaks bulleted lists. It's an upstream bug almost certainly, but usually what translators do is they just remove this special div the next time they go to update the translation subpage. Dmehus (talk) 16:18, 30 January 2021 (UTC)
 * What Dmehus said above seems right. Updating the syntax should had used another HTML element. 17:56, 30 January 2021 (UTC)
 * Okay, so how does one manually update the translation syntax?
 * Also, I do think there is a fix to this as it doesn't seem to happen on MediaWiki.org where the syntax keeps the text on the same line which doesn't split the bullet from the text and prevents this from happening in the first place. --Sabelöga (talk) 07:28, 31 January 2021 (UTC)
 * Never mind the above: the text was aligned that way on the source page which caused the translation to get mangled when FuzzyBot added that syntax. This has been fixed on the discussed page. Oh, and can you do the same on the Main Page? --Sabelöga (talk) 07:36, 31 January 2021 (UTC)

Request for Revoking the User Group from Incnis Mrsi
They have recently made some edits here which actions arguably constitute attacking other users which is obviously not acceptable. Even though their actions cannot be called vandalism, I (as a Meta patroller) think we should patrol their edits till we decide we are fine with them. Thank you. 13:08, 7 February 2021 (UTC)


 * ❌. This could've been considered, perhaps, but given that the user seems to have dropped the stick, I don't feel this is necessary at this time. We'll monitor the situation and take action accordingly. Dmehus (talk) 13:23, 7 February 2021 (UTC)
 * Alright. Thank you for looking into this anyway. :) 13:30, 7 February 2021 (UTC)

Special:MyLanguage in a system message
I recently saw the system message that says "Cookies help us deliver our services. By using our services, you agree to our use of cookies." "More information" "OK", the link directs to Privacy Policy when it should direct to Special:MyLanguage/Privacy Policy. (I don't know if this regards the Stewards, if it does please move this thread) --Sabelöga (talk) 06:25, 19 February 2021 (UTC)


 * I do no know how welcome this message is as I have not really done anything here in the last 24 hours but... this cannot be changed by Stewards or Meta administrators. This must be changed by a Sysadmin. I have made a pull request to change this. 14:48, 19 February 2021 (UTC)
 * R4356th's pull request looks fine to me. I can't think of any reason why not to implement this change, as we're not even adding Special:MyLanguage in an interface message or anything, but yeah, to add to what R4356th said, if it cannot be changed on-wiki, then your best bet is to open a Phabricator task and a system administrator can consider implementing the change&mdash;after first determining if a community discussion is required or not. This is likely a very non-controversial change, as it only helps internationalize our cookie warning message. Additionally, any community volunteer can implement the change, as R4356th has done, and any system administrator can merge it. Dmehus (talk) 15:03, 19 February 2021 (UTC)
 * The change has been merged, by the way. It should be live by now. :) 17:10, 19 February 2021 (UTC)
 * It has, thanks very much :) Anyway, I should really learn how to use Phabricator, but I haven't gotten around to do that yet.. Sabelöga (talk) 20:45, 19 February 2021 (UTC)

Question about Content Policy/fr
En français c'est bourré de fautes de syntaxe --Zazoult (talk) 22:16, 22 February 2021 (UTC)


 * Zazoult Please note I have procedurally moved this question from Talk:Content Policy/fr as talk pages on Meta Wiki are infrequently monitored and because centralized discussion is preferred. In this case, Administrators' noticeboard is the best venue for this question, which translates from the French using Google Translate as, "In French it's full of syntax errors." Do you mean technical syntax errors, or language syntax errors? If the latter, I'd recommend reaching out to either HeartsDo, a French speaking translation administrator on Meta Wiki; Reception123, a French speaking administrator on Meta Wiki, or Gerdami, an active French speaking translator on Meta Wiki. They will likely need you to clarify your question a bit, though. If the former, can you clarify what sort of errors, possibly by way of linking to a specific diff, or quoting a brief example? Thanks. Dmehus (talk) 22:39, 22 February 2021 (UTC)
 * J'ai essayé de retraduire, parce que la synthaxe est très importante il faut quand même que çà soit compréhensible pour les éditeurs ou les créateurs surtout concernant les conditions générales de cette ferme de wiki. Zazoult (talk) 22:48, 22 February 2021 (UTC)
 * Merci Zazoult de vouloir améliorer la traduction française de cette page. Il en reste d'ailleurs beaucoup à traduire. Cependant, " ;Ceci n'est pas une erreur de syntaxe ", en effet, le ";" en début de phrase sert à placer une emphase sur le texte et ne demande ni espace ni minuscule. Cordialement, Gerdami (talk) 07:55, 23 February 2021 (UTC)
 * Zazoult Merci et j'ai juste fait changer comme l'a dit Gerdami, l'histoire du ";". Par contre, juste une dernière question pour savoir: Pourquoi "Politiques et réglementation" en titre pour "Content Policy" ? HeartsDo (Talk / Global / Wiki Creator) 12:22, 23 February 2021 (UTC)

Request for agreement with flood flag while templates maintenanance
Hello administrators, i want ask you if you agree with addition of flood flag to my account while i will continue with templates maintenance later in this week. I've noticed that my mass changes floods out RC, but some users may want have these edits in RC for transparency. Please do not take this as bothering and please do not reply with page about flood flag, it is not policy. I want your opinion :). Thank you,--MrJaroslavik (talk) 10:57, 1 March 2021 (UTC)
 * If you are doing trivial and repetitive tasks, I see absolutely no issue with you adding the flood flag in order to not spam RecentChanges Reception123 (talk) ( C ) 12:01, 1 March 2021 (UTC)
 * It is creation of docs, categorising, sometimes completely rewrite or deletein if its merged or not used, etc.--MrJaroslavik (talk) 12:27, 1 March 2021 (UTC)
 * I personally have no issues with this. While Flood flag is not a policy, it is a guideline of generally and widely accepted customs and practices. Template maintenance isn't specifically mentioned, but categorizing of templates and merging templates should generally be non-controversial. Rewriting depends on the level of rewriting, I think. I personally see no issue with adding  to create documentation subpages, though others may not share this view. I would also just note that the   flag does not suppress edits from RC on the IRC and Discord feeds; it would only affect on-wiki RC. Hope that helps. Dmehus (talk) 15:17, 1 March 2021 (UTC)