Community noticeboard

Discussion: Central notice changes
This is for the sake of having an open discussion on the changes proposed in this RfC, though I won't really touch much on the last proposal that was added by another person (of course, you're welcome to talk about that as well nonetheless). Hopefully this comment will at least make it clear what the proposals I brought up are intended to mean. Also, please ask nicely if you would like clarity on anything at all.

The first one to discuss is the following:

Central notices with the purpose of soliciting participation from wiki communities for an event or a discussion should last while that event or discussion is open for people to participate. As in, the central notice would only be removed after the event or discussion has closed.

Let's start by saying that this is not changing what a central notice is made for. It's not saying that every discussion gets a central notice, what it's saying applies in the instance when the people who make central notices decide that a discussion will get a central notice, which is still at their judgement. This talk page comment might show some insight on what such judgement it is, which again they would still retain. What changes is specifically the duration of such particular central notices, in that it would be in relation to the discussion that it would be notifying of.

The discussions being referred to can be gleaned from Special:CentralNotice (click "Show archived campaigns" to see the older ones). It is what is meant to gather people to provide their input and feedback, and this description fits, for example, Requests for Comment or Requests for Stewardship. And if they have yet to be closed by the closer, then the closer presumably decided that it needs more time to gather more comments before a conclusion can be drawn. If so, the methods used to notify of the discussion's existence should get continued use to gather more discussion from people.

Another proposal to discuss is the following:

A campaign type can be set for central notice campaigns, allowing users to opt out of specific campaign types in their preferences, specifically in the "Banners" section. Here is a proposal for what campaign types Miraheze should use:
 * Fundraising
 * Surveys
 * Maintenance
 * Requests for Comment
 * Requests for Stewardship
 * Requests for Community Director

To make it clear how to use preferences to opt-out of campaign types, some text instructing people how to do so should be added to central notices.

In technical terms, campaign types are configured with $wgCentralNoticeCampaignTypes in LocalSettings.php.

This can presumably work with ManageWiki to apply for a whole wiki. To sysadmins, this would presumably be done by using a custom variable to set $wgDefaultUserOptions['centralnotice-display-campaign-type-whatever'] = 0.

Now, in regards to how to decide on the campaign types to be used, I'd say that having the communities' consensus is still relevant, in the case of disputes over what should be grouped together or partitioned. And the RfC does show a dispute over whether Requests for Global Sysop should be included, excluded, or grouped with another type. So it would at least be useful to have some sort of discussion with wiki communities to figure out what's best.

In response to other comments in the RfC: Including Requests for Global Sysop in the list of campaign types does not mean that every single one of that request gets a central notice, it is meant to mean that a RfGS would be allowed to get a central notice, which would still have the judgement of the people who make central notices to actually get one. And people should be able to decide for themselves if they want to opt out of seeing certain central notices, and I figure that if someone desires a tool to stop seeing a certain kind of notification, they likely aren't interested in what's being notified about in the first place. Finally, it was concluded in this RfC that there is consensus for community-oriented posts to be posted on Miraheze's social media accounts, therefore a community-elected role would be appropriate.

Feel free to say your thoughts on any of these topics. K599 (talk) 15:29, 1 December 2021 (UTC)
 * And will there be a way to disable CNotice for some, and leave only fundraising? YellowFrogger (✉ Talk  ✐ Edits ) 15:33, 1 December 2021 (UTC)
 * @YellowFrogger As said in the explanation of how campaign types work, people should be able to go into their preferences and opt-out of the types that they don't want to see. K599 (talk) 16:27, 1 December 2021 (UTC)
 * But there has to be an option to hide it across the whole wiki (not just in preferences), but yes, all visitors to a particular wiki would be better. Nobody is obligated to see CNotice either, so it had to have that. Showing only CNotice for fundraising, which is important for Miraheze to maintain the wikis maintenance, the others don't matter (or only matter in Meta). YellowFrogger (✉ Talk  ✐ Edits ) 19:59, 1 December 2021 (UTC)
 * @YellowFrogger I mentioned above that there's presumably a way to make campaign types work with ManageWiki, though I suppose a sysadmin should comment on the method I talked about. K599 (talk) 20:19, 1 December 2021 (UTC)
 * Note that the list of campaign types proposed in my initial comment is based on past central notices as seen on Special:CentralNotice. Of course, feel free to discuss any desired changes to the list. K599 (talk) 03:04, 8 December 2021 (UTC)
 * For some added context, the banner preferences can be seen in Special:Preferences, where it's currently the extension's defaults. These options have been unused probably due to being unrelated to Miraheze. K599 (talk) 03:46, 22 December 2021 (UTC)

DynamicPageList not displaying for most users
Hello. Recently an editor at SideM Wiki brought up that DynamicPageList wasn't working (we use them on pages such as this). I checked the extensions for the wiki, saw that DPL was disabled, and then reenabled it. It works for my account (admin) but not for the other editor (regular user). I also tried logging out and DPL no longer worked. What could be the cause of this? Thanks for any help. Clay (talk) 00:34, 3 December 2021 (UTC)


 * I can't see any issues, has the error been resolved? ~ El Komodos Drago (talk to me) 13:01, 10 December 2021 (UTC)
 * Yeah, I'm not sure what happened but it seems to work when I log out now. Clay (talk) 05:23, 14 December 2021 (UTC)

MediaWiki 1.37 upgrade
In keeping up with our commitment to always provide the newest version of MediaWiki to our users, Miraheze is happy to announce that we'll soon be upgrading our MediaWiki version from 1.36 to 1.37 on 7 December, 2021. The upgrade will take place from 17:00 (UTC) to 20:00 (UTC). During this time, all wikis will be set to read-only meaning that wikis will be uneditable during that period of time.

This MediaWiki upgrade brings little new features that may interest users apart from (perhaps) support for JPEG2000 images. As for technical changes, this MediaWiki upgrade brings plenty of change, consult the release notes for MediaWiki 1.37 for more information. If you have any questions, feel free to ask, thank you! Agent Isai Talk to me! 21:05, 3 December 2021 (UTC)
 * Good YellowFrogger</b> (✉ Talk </b> ✐ Edits </b>)</b> 21:08, 3 December 2021 (UTC)
 * I arrived at Miraheze in version 1.34 and we are already going to version 1.37. We are old. But this new version (as you said), it's not going to be a big deal (and the next one (1.38 that Wikipedia)) has ridiculous changes in the sidebar on Mobile MinervaNeue, the one that you press and open settings, login, etc. The letters just got smaller. Version 1.38 was released quickly after 1.37, which raises doubts. YellowFrogger</b> (✉ Talk </b> ✐ Edits </b>)</b> 21:12, 3 December 2021 (UTC)
 * 1.38 isn't released yet. Wikimedia projects run an alpha version. ~ RhinosF1 - (chat)· acc· c -  21:31, 3 December 2021 (UTC)
 * Lots of pages in the wiki I am subscribed to are now crashing with Fatal errors. Comment streams are also blank and not functioning and giving "Invalid API response". Wanderer2020 (talk) 04:37, 8 December 2021 (UTC)
 * Use Phabricator to report bugs. TylerMagee (talk) 18:26, 11 December 2021 (UTC)

Community Discussion: Wiki creators and creating wikis for themselves
Since an RfC would be too much for just one addition to the Wiki creator policy I am opening a Community Discussion here. As you all know, wiki creators are elected to serve the community and approve/decline wikis that are requested. They can in theory of course also approve their own wikis, but in my view for purposes of objectivity it would be preferred that they had another wiki creator do that.

However, what I'm proposing here isn't a complete ban on wiki creators creating their own wikis, it's simply the possibility for a Steward to remove a wiki creator if they are excessively create wikis for themselves and tend to not be creating wikis for other users.

The following would be added to "Revocation": A wiki creator's rights may also be removed by a Steward if they are mainly creating wikis for their own use and not focusing on their role of creating wikis for other users. Reception123 (talk) ( C ) 08:21, 7 December 2021 (UTC)

Support

 * 1)  as proposer. Reception123 (talk) ( C ) 08:23, 7 December 2021 (UTC)
 * 2)  Wiki creators should serve the community, not themselves. It wouldn't make sense if a wiki creator misused their privileges to create an excessive amount of wikis for themselves without any consequences.  Agent Isai  Talk to me! 08:23, 7 December 2021 (UTC)
 * 3)  The proposal pretty much covered it.  08:25, 7 December 2021 (UTC) ］ |
 * 4)  Why not?  Anpang   Talk   Stuff  08:27, 7 December 2021 (UTC)
 * 5) . This should stop wiki creator spam. TylerMagee (talk) 08:38, 7 December 2021 (UTC)
 * --Magogre (talk) 09:04, 7 December 2021 (UTC)
 * 1)  I don't really have to much to add, the post covered basically what I wanted to say on this issue. TigerBlazer (talk) 11:15, 7 December 2021 (UTC)
 * 2)  Ugochimobi (talk) 11:25, 7 December 2021 (UTC)
 * 3)  Don't get me wrong, I'm fine with wiki creators requesting wikis for themselves and self-approving it, but if it becomes excessive to the point of flooding the farmer log, then it does come off as either disruptive or somewhere between messy and cloggy like a clogged toilet. --DarkMatterMan4500 (talk) (contribs) 11:56, 7 December 2021 (UTC)
 * That's a fair point too, though I was more concerned with objectivity and creating more wikis for yourself rather than for other users. Since it's no secret what actions started this Community Discussion, I would point out that many requests that were made and 'self-approved' would have likely not been approved by another wiki creator, at least not by myself. Wiki creators also decline wiki requests if someone is requesting too many wikis, so it's definitely unfair that a wiki creator can create many wikis for themselves while regular users are told not to create an excessive amount. Reception123 (talk) ( C ) 12:07, 7 December 2021 (UTC)
 * Yes, that's very true. DarkMatterMan4500 (talk) (contribs) 13:50, 7 December 2021 (UTC)
 * 1) All users must respect the content policy and wiki creator is no exception YellowFrogger</b> (✉ Talk </b> ✐ UnEdits </b>) (Bring back patrolled)</b></b> 14:29, 7 December 2021 (UTC)
 * Well the Content Policy as such doesn't mention wiki creators creating an excessive amount of wikis for themselves at all, which is why I opened this Community Discussion, as there needs to be a separate ground beyond the CP removal ground. Reception123 (talk) ( C ) 15:44, 7 December 2021 (UTC)
 * that's right YellowFrogger</b> (✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 23:19, 7 December 2021 (UTC)
 * 1)  Absolutely. I actually think it would be a good convention for a wiki creator to request a wiki and let another wiki creator approve it in the name of transparency, but I won't push for that here. --Raidarr (talk) 14:49, 7 December 2021 (UTC)
 * That's an interesting point yeah, I'm kind of undecided on that but related to what I say below I feel like if a wiki creator wants to create a wiki that they could see be declined by someone else they should wait for someone else to approve, but that's not really a clear question. Reception123 (talk) ( C ) 15:43, 7 December 2021 (UTC)
 * 1)  I agree with what is said above. Maybe this example is too extreme but it is like a judge deciding their own case. Here of course it is not nearly as serious or complicated but the principle still applies in that a judge is someone who is trusted and knows how to apply the law but that does not mean that they are trusted to apply it if they are involved in a case. In my personal view we are not being strict enough and I would go further than this proposal and vote for not allowing wiki creators to create their own wikis at all for reasons of impartiality; can someone really impartially interpret the Content Policy in regards to their own wiki? That is not however the subject here but in consequence I believe that it is perfectly desirable for a wiki creator to be removed if they are not adhering to their original "oath" which is to create wikis for other users, not for themself. I have seen the comments opposing the Steward discretion aspects of this proposal. While there is a point to the argument of not giving up everything to Stewards in this particular case I agree with what is said by Reception123 and believe that it would not necessarily be desirable to have a "direct democracy" model for these removals as is the case for other more positions. Sometimes it is necessary for the community to delegate their powers to Stewards and this situation is to me is one of those times. If Stewards are not trusted by the community then they should open a revocation request instead of attacking the discretionary powers of Stewards. Accordingly it is my strong view that it is not acceptable for a wiki creator to be focusing on creating multiple wikis for themselves and to not be creating almost any wikis for other users. --DeeM28 (talk) 09:23, 8 December 2021 (UTC)
 * 2)  I don't really see how this could be bad.  &mdash;Lakelimbo (talk)&emsp; 19:22, 15 December 2021 (UTC)

Oppose

 * 1) A wiki creator is someone who has the experience and trust to create wikis that can follow Miraheze policy, which you arguably can do best if you yourself are managing it. Whether or not people should be creating their own wikis is a seperate issue, but I don't think there is a distinguishment between doing so "mainly" and not. There is no obligation or commitment as a wiki creator, it is a volunteer position, and I do not support requiring people to "balance" with other wikis. Also, the proposed change is that any Steward can just take the permissions away unilaterally which is definitely a no-go. Changes like that should require consensus. Naleksuh (talk) 21:08, 7 December 2021 (UTC)
 * I also agree with you. No need for early revocation for a single basic reason <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 05:20, 8 December 2021 (UTC)
 * No one suggested that someone should be removed based on one instance and without warning. The suggestion that Stewards would take permissions away as they please suggests a lack of trust in the current Stewards to me which is a different issue altoghether.If there is not currently an obligation on a wiki creator to approve other users' wikis and not just create wikis for themselves, I think there should be, and this new addition to the policy would imply that. Stewards can already take permissions away unilaterally for violations of the Content Policy, so in that regard they already have a similar power, just limited to the CP. While "A wiki creator is someone who has the experience and trust to create wikis that can follow Miraheze policy" is true, what if a wiki creator has lost that trust because they're not creating wikis for users but just for themselves? There should be a way for them to be removed. Reception123 (talk) ( C ) 07:46, 8 December 2021 (UTC)
 * There should be a way for them to be removed. Yes, but that doesn't mean that way should be stewards unilaterally removing it. Also, removal should be because of creating wikis against policies, not by not creating enough wikis for people other than themself Naleksuh (talk) 01:05, 10 December 2021 (UTC)
 * 1)  if a wiki creator is only there approving their own requests, provided they are doing it properly, I see no problem with that - indeed it is beneficial to Miraheze as a whole as it means other wiki creators do not have to deal with them. If they are not doing so properly then a better proposal would be to ban wiki creators from approving their own requests. ~ El Komodos Drago (talk to me) 12:43, 10 December 2021 (UTC)
 * Well yes, the issue isn't about creating a few wikis for ones-self, it's basically about abusing the process and creating an amount of wikis for oneself that otherwise would have not reasonably been approved by any other wiki creator. While there is no hard rule, it is a convention that unless they have a good reason we don't really allow users to create a large amount of wikis for themselves. Reception123 (talk) ( C ) 07:00, 13 December 2021 (UTC)
 * Well propose that rule. It seems like you are trying to eliminate one behaviour by creating a rule banning an entirely separate one that seems (alone) to be harmless. This is bad rule making. ~ El Komodos Drago (talk to me) 11:04, 15 December 2021 (UTC)
 * 1)  – Mainly based on the Naleksuh's reasoning. I agree the removal should be performed if the wiki creator is creating wikis only for their own and/or against policy but it shouldn't be the unilateral decision of a steward to remove the rights without consulting the community. Stewards are trusted, but I do not feel comfortable with the rights being removed unilaterally by a steward if the user is elected by community. If community consultation added to the proposal, I'd completely agree with it. --Magogre (talk)  13:41, 10 December 2021 (UTC)
 * 2)  in part, per what others have said above, namely Naleksuh, Magogre, and El Komodos Drago, but also because I feel this proposal was made in response to a user who speaks little to no English, but who I might also add has created wikis for users and whose Content Policy understanding actually not that bad. As our only Chinese language wiki creator, if their bit was hypothetically removed by a Steward per this criterion, I feel they'd have a difficult time getting it back mainly because of their lack of Meta activity and command of the English language. As well, since the proposal is very, very vague, you potentially have a situation where one Steward might agree with revocation and another Steward might not. Moreover, though I generally prefer Steward discretion rather quantified details, I feel this is a case where it's better to be more explicit. What constitutes "for their own purposes"? One wiki? Ten wikis? 100 wikis? I guess I could potentially support something along these lines, but only an alternate proposal that (a) takes into account the above arguments, (b) quantifies specifics, (c) ideally is part of a larger RfC or an acknowledged prelude to a forthcoming RfC to amend the wiki creator inactivity and revocation clauses (i.e., for example, should the SRE revocation clause still exist? if so, under what conditions?), (d) takes into account the multilingual nature of Miraheze and Meta Wiki, and (e) requires at least super-majority (i.e., 75%) of existing Stewards to agree to the removal, if not unanimity, and only after, say, a thirty (30) day notice and remediation plan had been put forward to the wiki creator in question. Dmehus (talk) 07:37, 13 December 2021 (UTC)
 * To respond to your first point about the specific user I will admit I am not aware in respect of which user this request was made but I believe it is problematic for a wiki creator to speak no English especially if they are approving requests in English. I think it is quite obvious why such a situation is not desirable.
 * In regards to discretion I would currently support a wider discretion for Stewards to remove wiki creators generally beyond simply the Content Policy but based on the other opposes it appears to me that such a wide discretion is not desirable.
 * Regarding your proposal it appears to be too lenient for me. Why do wiki creators need to be given such a large measure of remediation options? If they are not creating wikis for other users they should be removed in my opinion and the community can reinstate them if that is what it wants. While there may be no appetite for this change my view is still that it would be simpler to not allow users to create their own wikis for reasons of impartiality.
 * To respond to the vagueness I am not sure how specifics would make sense in this context and how someone would be able to define a number of wikis that a person can create for themselves. I am confused as to the reason why you believe that in this case general Steward discretion is not appropriate; I think it is.
 * In conclusion my general view is that wiki creators need to be held to a higher level of scrutiny and it is better to remove more wiki creators if that is necessary to preserve the integrity of the process. Wiki creators can always be added back if they pledge to respect the rules and conventions in the future but I disagree with being overly lenient if they are not serving the community but are serving themselves. DeeM28 (talk) 18:43, 16 December 2021 (UTC)
 * The issue, though, is for the user in question, there's not really been any Content Policy issues in their wiki approvals. Dmehus (talk) 05:49, 20 December 2021 (UTC)
 * As for the discretion, I'm not necessarily opposed to Steward discretion, but this was hurried and rushed proposal, which even Reception123 admitted to me on IRC, that did not consider all of the procedural ramifications. What if one Steward disagrees with another Steward's removal? Can the rights be re-added without a community vote? Without some sort of readdition clause, or a thorough remediation and corrective action plan, we'd essentially be substituting one form of mob mentality !voting with another. I do agree with you that I feel for some positions, direct democracy is not the best form of appointment. I would be supportive of granting greater authority and discretion to Stewards to remove the  for more than just a defined inactivity clause or repeated Content Policy understanding and application issues, if we also allowed for Stewards to grant the   bit, perhaps on a temporary basis, where the request tends devolve into mere !voting based on English Wikipedia essays, so as to allow reasonable candidates, perhaps candidates who speak languages other than English, a track record by which the community could assess, from a practical standpoint, whether the user can consistently apply their understanding of Content Policy correctly. So, as an example, in such cases, Stewards could be granted the discretion to grant the bit on a temporary basis (say, for a maximum of 30 days), after which the bit would be automatically removed. Either shortly before their temporary status was due to expire, or after it had expired, the candidate would then be able to have a track record to cite to the community in standing for election as a permanent wiki creator. Additionally, I'm more inclined to support some sort of Meta Wiki only activity for the purposes of the inactivity clause, as we have some wiki creators who are globally active, but have not created one wiki. Thus why I feel a more major overhaul of the policy is needed. Dmehus (talk) 06:07, 20 December 2021 (UTC)

Comments

 * While I don't see the problem with self-approving wiki requests that other wiki creators have self-requested, it becomes a distraction to all others who would want to review the wiki request if it becomes excessive. --DarkMatterMan4500 (talk) (contribs) 12:07, 7 December 2021 (UTC)
 * I think it's worth mentioning that the case which lead to this conversation is a holdout of a time when WCs were appointed with little in the way of community input, and it was done two days before the process changed. Just an observation, not to fault the Steward at the time who made the call. --Raidarr (talk) 14:45, 7 December 2021 (UTC)
 * Indeed, the proposal may serve a limited purpose (for a single user) but I think either way it would make clear to any future wiki creators that when creating wikis for themselves if they choose to do so they should take the chance to think: would another wiki creator really have approved this if I was a regular user? Though of course its main point is limiting excessive wiki creations for ones-self which would not otherwise be approved of by any creator Reception123 (talk) ( C ) 15:42, 7 December 2021 (UTC)
 * By all means, this is very reasonable to do regardless of the 'catalyst' to propose. Plus it solidifies the precedent for new requests in the future. --Raidarr (talk) 15:55, 7 December 2021 (UTC)
 * Reception123 said he's open to having this essentially serve as a non-binding community input session, rather than any sort of binding policy-setting discussion, in view of the strong arguments presented in opposition. So essentially, the comments expressed herein would help to refine the aims of the proposal in a broader RfC that looks at reforming the wiki creator policy, perhaps in January or something. Based on the conversations I've had with Agent Isai on IRC, he seemed receptive to the idea as well. Dmehus (talk) 05:54, 20 December 2021 (UTC)
 * As pointed by the Naleksuh, I also believe a steward should not remove the rights unilaterally and I'd like it if somehow there should be a fixed time for the community to comment on the removal. A note on the AN or SN should be sufficient and anyone should be able to request the revocation of other's rights upon misuse. --Magogre (talk) 05:17, 8 December 2021 (UTC)
 * As commented above, this is already possible for Content Policy violations so this isn't some large new change that gives Stewards significant extra power. While this was never discussed before explicitly, my feeling is that the reason for why wiki creator revocations are Steward discretion rather than community consensus/vote is to avoid mob-mentality, for example people teaming up to remove a wiki creator because they disagree with their specific approval/disapproval of wiki requests. Again, that's just my view, it was never actually discussed in this way. Though either way, as I say above, if you disagree with the current Steward discretion that exists for revocation then that's a different issue because it already exists for CP violations. Reception123 (talk) ( C ) 07:50, 8 December 2021 (UTC)

what will happen now
The truth was I was waiting for Christmas and New Years, the truth was I was waiting for my friend BriZoner to come back and then I deactivate the creation of accounts, also I have to wait because my wiki and miraheze you will never have changes, it is Derpguy109 (talk) 12:58, 8 December 2021 (UTC)


 * I did not understand your comment <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 23:26, 8 December 2021 (UTC)
 * okay, surely nothing happened Derpguy109 (talk) 23:02, 10 December 2021 (UTC)

How long does a rename and moving everything to the new name take?
So 2 days ago i requested renaming my account on the global rename page as i was told by another community member. I am a person who is patient but i just wanna be sure that its normal that it takes longer than an usual request. I also imagine it takes longer because Miraheze just recently upgraded to a newer version and therefore they are very likely busy with other things. Smashidachi (talk) 16:37, 8 December 2021 (UTC)
 * Hi there, thank you for your patience, your account will soon be renamed and done, just have a little more patience as it'll be attended to shortly. Ugochimobi (talk) 16:46, 8 December 2021 (UTC)
 * Thank you for the info. ^^ Smashidachi (talk) 17:39, 8 December 2021 (UTC)
 * No problem :} Ugochimobi (talk) 21:17, 8 December 2021 (UTC)
 * Noting that this rename request has been ✅ by John. Sorry about the delay, unfortunately renames can take a good minute to be addressed. --Raidarr (talk) 21:47, 8 December 2021 (UTC)

how do I change ? thanks
HI. I like to change my from Cases and Materials Unlimited to Cases and Materials Wiki. How do I do that? thanks Pcll99 (talk) 05:39, 9 December 2021 (UTC)


 * To do that, please visit Special:ManageWiki/core on your wiki and change the sitename. Agent Isai  Talk to me! 05:47, 9 December 2021 (UTC)
 * I don't understand "Change SITENAME", but do you intend to change the site name? Do this in Special:ManageWiki/core (links like these located in the sidebar). If you want to change your wiki hosting, open a ticket in phabricator <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 05:47, 9 December 2021 (UTC)

Download Dump
I requested a data-dump, and it seems to have made it and give me this link: https://static.miraheze.org/xedwiki/dumps/xedwiki_xml_c0dc711a8e74375f67d8.xml.gz. However, I get a 404 when I try to do there. Is this a result of the new update? Is it a fixable error? Thank you for your time. Aquatiki (talk) 18:56, 9 December 2021 (UTC)


 * Can you link to the wiki you are generating the dump for. Is it a private wiki? Thanks, ~ El Komodos Drago (talk to me) 12:57, 10 December 2021 (UTC)


 * Should be ... --Aquatiki (talk) 22:51, 10 December 2021 (UTC)

Data Base Error -- Another Eden -- Weapon Manifestation
Hello, Due to the new update to MediaWiki 1.37.0, this link now has a database error: https://anothereden.miraheze.org/wiki/Weapon_Manifestation. Thank you for your time.172.90.43.62 19:42, 9 December 2021 (UTC) 172.90.43.62 19:42, 9 December 2021 (UTC)


 * This is a bug. Mistakes like these have already happened on my wiki, and they've resolved themselves. Probably, if it is, it will go back to normal. Wait for a steward (or admin) to respond and he will analyze your question. <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:56, 9 December 2021 (UTC)
 * If you are experiencing issues, please make a Phabricator task or drop by Discord/IRC to report the issue. Thanks. Agent Isai  Talk to me! 20:30, 9 December 2021 (UTC)

How to add OCR in a Miraheze wiki?
I have a wiki like Wikisource in Bengali Language. It is "গ্রন্থশালা". Here is an index page. Here I want to use Google OCR while proofreading. But, I failed to add OCR in this wiki. So, I am requesting you to help me in this regard. Thanks. MS Sakib (talk) 10:43, 10 December 2021 (UTC)


 * Hello there, kindly as that the Extension:Wikisource be installed. Request on Phabricator. This extension would do what you want. Ugochimobi (talk) 23:12, 10 December 2021 (UTC)
 * @Ugochimobi: Thanks a lot for responding. MS Sakib (talk) 20:36, 11 December 2021 (UTC)
 * no problem, you would find necessary documentation of the extension here. Ugochimobi (talk) 20:58, 11 December 2021 (UTC)
 * @Ugochimobi: I requested in Phabricator. But no solution was found. MS Sakib (talk) 19:55, 14 December 2021 (UTC)
 * It seems it's the Proofread extension that can be the only option, unfortunately. Ugochimobi (talk) 09:00, 15 December 2021 (UTC)

Sanitized CSS
TemplatesStyles doesn't work with sanitized CSS (the ones with @ we use to import fonts). What do I do, Stewards?? <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 17:04, 10 December 2021 (UTC)


 * , go to Special:ChangeContentModel and change the content model of User:YellowFrogger/styles.css into Sanitized CSS. --Magogre (talk) 17:11, 10 December 2021 (UTC)
 * hello, I will see <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 21:41, 10 December 2021 (UTC)
 * "" Why does this appear? <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 01:24, 12 December 2021 (UTC)

Chinese Gyaanipedia
I found that I cannot edit any pages in the main namespace in this wiki and it appears the following: "wikitext" content is not allowed on page (PAGENAME) in slot "Main". Can any stewards help me to debug this? Thanks.

P.S. It also happens in English Gyaanipedia. Ping above. -Matttest (talk) 03:09, 11 December 2021 (UTC)
 * Dmehus is inactive. Mark a system administrator, or open a ticket in phabricator to report bugs <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 02:40, 12 December 2021 (UTC)

What happened to the redlink colors
The redlink colors are suddenly a brighter shade of red, and it is not as visually appealing as the dark red versions. Was this a result of the update? If so, why was this changed? It doesn't really seem like a necessary change since I am pretty sure changing the color of links doesn't make much of a difference software-wise. Sorry if this sounds kind of nitpicky. Blubabluba9990 (talk) 19:31, 11 December 2021 (UTC)


 * Yes. It was after the MW 1.37 update, the links changed color, became clearer: #dd3333 hex. Also, when clicking the right mouse button, the link will glow orange. This is something to be dealt with on Wikimedia and not on Miraheze <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:33, 11 December 2021 (UTC)
 * Ok. Why was this change made, as I don't see any particular reason to change the colors. Blubabluba9990 (talk) 19:35, 11 December 2021 (UTC)
 * I can't find the reason. But I think it's to clarify and draw attention, or to say that something has changed, as I didn't see much difference from this version. <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:36, 11 December 2021 (UTC)
 * Ok. Blubabluba9990 (talk) 19:37, 11 December 2021 (UTC)
 * I believe it was for accessibility reasons. ~ RhinosF1 - (chat)· acc· c -  19:48, 11 December 2021 (UTC)
 * That's what I wanted to say <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:57, 11 December 2021 (UTC)
 * What do you mean by "accessibility reasons"? Blubabluba9990 (talk) 23:08, 11 December 2021 (UTC)
 * I think he meant accessibility because the dark red links are a little harder to determine, while the lighter ones are easier to see. Something like that. Still I prefer the same as usual <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 00:05, 12 December 2021 (UTC)
 * I also admit that I didn't like this change. The old color was: #ba0000
 * You can change them using CSS, switching to the old one, which was:
 * The
 * a {
 * color: #ba0000;
 * } <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:35, 11 December 2021 (UTC)
 * Ok. Blubabluba9990 (talk) 19:35, 11 December 2021 (UTC)
 * I do not recommand this change, this will change the color of all links, better is  --LilyLilyu - smile.svg talk and I will listen · Lilypond Wiki 13:54, 14 December 2021 (UTC)

Imported infoboxes from Wikipedia aren't working
For my wiki, (Link), I wanted to use some infoboxes from Wikipedia. I followed the steps on the Miraheze page on importing infoboxes, but even though the templates for the infoboxes and their /doc versions are imported, it doesn't work. I enabled the extensions that the page explained were required, and it still did nothing. Whenever I want to edit an infobox now, it will let me insert the template, but not provide any fields for me put information into, showing a message that there are "no unused fields." Any help with this would be greatly appreciated. - IAmTheSenate (talk) 21:06, 11 December 2021 (UTC)
 * Hi, I'm the creator of the test page you're probably talking about. Note firstly that the page is in the process of being created and it is not recommended, yet, to follow what was written on it because everything is incomplete and in the middle it may fail. When that message appears explaining about missing module, example: There is no module with that name: Yesno you must create a Yesno module imported from Wikipedia. Your mistake is that the unused fields probably means you didn't put any message in the parameter or something. I've never had this error with me so I'm not exactly sure what this is. <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 22:09, 11 December 2021 (UTC)
 * Your wiki is private, I can't see what's on it. I would even analyze what this is <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 22:12, 11 December 2021 (UTC)
 * If you're ok with doing so, I can add you as a member to analyze the situation. IAmTheSenate (talk) 03:56, 12 December 2021 (UTC)
 * yes I would like to see what's there <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:28, 12 December 2021 (UTC)
 * I've added you as a member now, so hopefully you can help find the problem. Thank you again for helping with this. IAmTheSenate (talk) 19:51, 12 December 2021 (UTC)
 * You must also add the extension TemplateStyles. I saw on your wiki that it is not activated. <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 21:01, 12 December 2021 (UTC)
 * I believe I've done all the things you suggested in the edits, however nothing seems to be working. IAmTheSenate (talk) 21:58, 12 December 2021 (UTC)
 * I should also probably mention that I have not used MediaWiki before, nor Miraheze, so I don't have a full grasp of exactly how to do everything. IAmTheSenate (talk) 22:00, 12 December 2021 (UTC)
 * I also at first struggled to add infoboxes to the wiki.
 * All pages that say: "Page "Name of page/styles.css" must have content model "Sanitized CSS" for TemplateStyles (current model is "plain text")", you delete and recreate with the same content. I saw here that you added the extension <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 22:27, 12 December 2021 (UTC)
 * Will solve? <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 00:03, 13 December 2021 (UTC)
 * Unforutnately no. I changed my user content model to Santitized CSS and I did so with the templates required for, in this case, the country infobox, and now it says they aren't in Santitized CSS when they are. It gives me this message on the template for the country infobox page: Page Module:Documentation/styles.css must have content model "Sanitized CSS" for TemplateStyles (current model is "plain text"). and Page Module:Hatnote/styles.css must have content model "Sanitized CSS" for TemplateStyles (current model is "plain text").
 * I honestly cannot find what is wrong. IAmTheSenate (talk) 03:10, 13 December 2021 (UTC)
 * I will see. So, please, help to know what's going on here. you should also delete and restore the page again, as you had added the TemplateStyles extension. And not to have changed content model <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 03:45, 13 December 2021 (UTC)
 * Hi there, would you add me as a member of your wiki so I can fix this for you? Ugochimobi (talk) 05:35, 13 December 2021 (UTC)
 * Sure, thank you for offering your help. IAmTheSenate (talk) 21:48, 13 December 2021 (UTC)
 * He (Ugochimobi) understands about this and it's interesting that you add him as a member. <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 23:49, 13 December 2021 (UTC)

Sanitized CSS (2)
What does "Sanitized CSS" mean in TemplateStyles? I need help with this. It's saying it need sanitized css but the code is js. Anpang  Talk   Stuff  01:47, 12 December 2021 (UTC)


 * Yo! You can not use Javascript files for TemplateStyles. As the warning notes, it must be sanitized CSS content model precisely. Ugochimobi (talk) 14:40, 12 December 2021 (UTC)
 * I also have these problems. When I go to solve for Special:ChangeContentModel, it bugs saying "Unrecognized or unsupported rule at line 1 character 1" <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:27, 12 December 2021 (UTC)
 * Hi, this means that the current css isn't correct and can not be converted into SCSS. Ugochimobi (talk) 05:29, 13 December 2021 (UTC)

Do you think this RFC would stand a chance?
I have an idea for an RFC (Requests for Comment) about changes to the Content Policy, but and  suggested that I should ask other users first to prevent it from being snowballed, and Agent Isai specifically suggested I go here to ask. Anyway, here are my ideas for changes: FatBurn0000 (talk) 02:28, 12 December 2021 (UTC)
 * 1) Change the rule "Miraheze does not host wikis with the sole purpose to spread unsubstantiated insult, hate or rumours against a person or group of people" to "Miraheze does not allow any pages on wikis with the sole purpose to spread unsubstantiated insult, hate or rumours against a person or group of people" because we do not need any pages with this purpose, whether or not the wiki itself is made to do so.
 * 2) The rule "A wiki must not create problems which make it difficult for other wikis" should have multiple changes:
 * 3) The rule should apply to all wikis, not just Miraheze wikis, because no wiki should be duplicated; the internet doesn't need two versions of wikis. I understand that it is hard to stop the entire internet from duplicating wikis, but it is something that should be stopped, and Miraheze should play a part in stopping it. I do think that since there are no staff for the entire internet and as a result corrupt staff exist on various sites (including wikis), there can be exceptions for non-Miraheze wikis. However, a user must go through every single option in order before requesting this to be an exception (unless the options say they can do otherwise):
 * 4) Review the wiki's quality. If you want to make an exception, then the most ridiculous reason to duplicate wikis is because they have bad quality. If they have bad quality, then they can be improved. If the changes that need to be made are not against the rules, then just try to clean up the wiki.
 * 5) If the change would concern the rules or requires a lot of cleanup, then ask the owner of the wiki (note that what counts as an "owner" includes the founder, a user who adopted the wiki [this only applies to wikis that are hosted by another wiki-hosting site since independent wikis cannot be adopted], the only bureaucrat [if there is only one bureaucrat] and of course, a user who is stated to be the "owner") or, if there is no bureaucrat who would be considered the "owner", the most active bureaucrat, and talk to them about the change. If there are no bureaucrats or all of the bureaucrats are inactive, you should adopt the wiki. However, note that you should try contacting the bureaucrats first regardless, and if the wiki is independent, you are now free to request an exception.
 * 6) If the bureaucrat you contacted disagrees with you, then do not immediately decide that the bureaucrat is corrupt. Try to have a reasonable discussion with them. If you tried to adopt the wiki and your request was denied, unless you agree with the reason, try to continue talking with the user who denied your request and again, don't immediately decide they're corrupt.
 * 7) If the bureaucrat acts in a way you consider unfair, if you can, calmly talk with them about it. If the same happens with the user who denied your request, do the same thing with them.
 * 8) If the bureaucrat continues to be unfair, then it depends on the case on what you do. If the wiki is hosted by another wiki-hosting site, talk to the users with the highest position (whether or not that is stewards, staff or something else) about dealing with the abusive bureaucrat. If the wiki is independent, however, you are now free to request an exception. If the user who denied your request continues to be unfair, then it depends on what position they have. If they have the highest position, then again, you are now free to request an exception. If they do not, however, and someone is above them, they can be reported to a user with the highest position.
 * 9) If the user with the highest position disagrees, then again, try to have a full conversation with them.
 * 10) If the user with the highest position continues to be unfair after a discussion and there is no point in discussing it anymore, then you should ask the stewards of Miraheze, and if they agree with you, then your wiki can become an exception. In case you're wondering where you can request an exception, request it at Stewards' noticeboard before requesting the wiki, and if your request is approved, then you can now request the wiki at Special:RequestWikiQueue, and make sure you link to the discussion for reference.
 * 11) Although I believe this already applies, I think it should be made more clear that the rule does not just apply to duplicating wikis, but also to the following:
 * 12) Creating pages on wikis that contain destructive criticism towards the wiki.
 * 13) Having any content on wikis that the wiki's staff members have stated that they do not want.
 * 14) There should be a rule that states "A wiki must not have pages that are likely to cause drama". Pages that are considered likely to cause drama are:
 * 15) Negative pages about obscure users on the internet
 * 16) Pages about people who do not want a page about them (this does not apply to informative pages)
 * "A wiki cannot create problems for other wikis". But this already applies to all wikis including non-Miraheze external ones. Does this include humor wikis? Can't they also create an article about another wiki? But all the content of a humor wiki shouldn't be taken seriously, that's a fact. <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 02:37, 12 December 2021 (UTC)
 * I agree that humour wikis should be able to create pages about other wikis, but I don't think I said that they couldn't; I only said that if the staff members don't want it they can say that won't allow it. FatBurn0000 (talk) 03:22, 12 December 2021 (UTC)
 * Also, are you sure that Miraheze doesn't allow duplicates of non-Miraheze wikis? According to Raidarr, there are multiple duplicates of Fandom wikis. FatBurn0000 (talk) 03:34, 12 December 2021 (UTC)
 * 1. is intended to address systemic issues. The change is not necessary. The wording is deliberate to reiterate our stance; any pages are included by this wording, and are considered 'content policy issues' already. They can be reported and addressed (by removal at request or if systemic and unaddressed reasonably, by wiki lock until fix or removal).
 * 2. can merit additional, if careful language, so lets see:
 * 2.1. I disagree that Miraheze should gatekeep on this. For one, many Fandom wikis have moved to Miraheze, and Fandom is notorious for being sluggish or unwilling to delete wikis for their ambient revenue, nonetheless the entire staff are typically inclined to move in bypass of your written process altogether. For two, communities with severe enough drama and legitimate enough community schisms should not be subject to your proposed bureaucratic process, especially if the wiki intends to make significant enough stylistic or fundamental changes that would not be feasible for another platform. Again, the level of possibilities make this a potential issue. All in all my stance here is not unlike my stance on politics - 'lets worry about ourselves before worrying about other (nations)'. We actually do have a topical duplication problem in several cases locally even if they don't match the strict requirements that would make content forking an issue, and we could do better from a wiki creation standpoint to be aware of and refuse probable content duplication on Miraheze as well as work to remediate the ones that exist. There are a variety of wikis with strongly overlapped purpose as has researched before. In all I would have to oppose based on the broad stretch of this language, and disagree that it is our role to enforce it anyway.
 * 2.2. 'destructive criticism' is a dangerous precedence for 'your criticism is too steamy for us, delete'. For one that is more of a conduct matter, since it does not pertain directly to wiki content. For two this should be addressed by the local community and local rules. It is not the Content Policy's job to moderate at this level. Indeed, 2.2 here is entirely out of scope for the CP as a whole imo. If you don't like the criticism, rebuke it or ignore it, or if it is sufficiently toxic, remove for incivility and unconstructive purpose, all of which is possible with healthy local management.
 * 3. Already covered in full imo by the premise of the existing rule. Frankly I think this is an attempt to enable your lawyering to bring back a fundamentally problematic concept - pages about people with a critical or negative focus - as a legitimate thing since you will have made the policy more specific, but not actually addressed this detail.
 * Not to assume bad faith, but I believe these changes are born of a desire to enable certain forms of content and to realize a more personal vision of what Miraheze should do and allow which would be more controversial if expressed in full to the wider Meta community. Part of why I suggested to have the concept reviewed first is so this could be expressed informally and if possible, changes made to talk out of this line of thought or even make it malleable instead. Unfortunately given the evident purposes of these points and their niche appeal, I'm afraid this one is not likely to pass in addition to what would be my personal outright oppose in a live RfC. --Raidarr (talk) 11:04, 12 December 2021 (UTC)

FatBurn0000 (talk) 22:03, 12 December 2021 (UTC)
 * 1) Well, it should still be made more clear.
 * 2) This is why there are exceptions to this rule. Also this doesn't necessarily apply to just Fandom wikis.
 * 3) Fair enough.
 * 4) Not all criticism and negativity towards obscure users is guaranteed to be destructive, it is just a common problem that they will be, which has before happened with the Outcasts and other user reception wikis (including Crappy GachaTubers Wiki, a wiki that is unfortunately still open).
 * 1) Not all criticism and negativity towards obscure users is guaranteed to be destructive, it is just a common problem that they will be, which has before happened with the Outcasts and other user reception wikis (including Crappy GachaTubers Wiki, a wiki that is unfortunately still open).
 * I feel like I agree with FatBurn on this, if this is an existing rule, then it should be stated in the content policy. At the very least I think that "sole purpose" is slippery wording. ~ El Komodos Drago (talk to me) 11:22, 15 December 2021 (UTC)
 * And you. Are you going to open an RfC or not? <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 22:32, 12 December 2021 (UTC)
 * There should be a rule stating, "Only one Miraheze wiki should exist for a topic," because duplicate wikis exist. Tali64³ (talk) 00:41, 13 December 2021 (UTC)
 * What I am suggesting is that the rule should be for all wikis, not just Miraheze wikis, with a few exceptions for non-Miraheze wikis in case of abusive staff. FatBurn0000 (talk) 08:21, 13 December 2021 (UTC)
 * A user named Blubabluba9990 opened an RfC <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 00:00, 14 December 2021 (UTC)


 * 1) There isn't any issue with the creation on Miraheze of a wiki that already exists somewhere on the internet. Some proprietary wiki host having a certain wiki does not give them the rights to it.
 * 2) I'm not entirely sure what you're referring to by "destructive criticism", but being able to criticize a wiki on that wiki is essential to accountability.
 * 3) There is no need for a rule such as 2.2.2, as wiki's generally have some form of content policy or guidelines as to what's allowed. Furthermore, the terminology "staff members have stated that they do not want", as that seems to imply that a wiki belongs to its staff, not its community. — Arcversin (talk) 19:52, 14 December 2021 (UTC)

Re: Proposal 3
This is largely covered by the existing rule that "Miraheze does not host wikis with the sole purpose to spread unsubstantiated insult, hate or rumours against a person or group of people". With regards to 3.1, I'm not sure that obscurity should be a big issue - obviously for identifiable individuals there is a GDPR/right to erasure issue here. 3.2 is basically entirely covered and again GDPR/RTE. ~ El Komodos Drago (talk to me) 17:07, 16 December 2021 (UTC)

Edits not saving on English Gyaanipedia
I guess from the last few days it's happening, I have seen this yesterday and tried to resolve it but couldn't able to. I don't know it's a bug or something else.

Whenever I tries to edit any page on English Gyaanipedia it's not saving and this message is poping up '''Error, edit not saved. "wikitext" content is not allowed on page Shaunak Chakraborty in slot "Main"



or can any of you guys please help me with this. Thanking you with due respect. Shaunak Chakraborty (talk) 06:13, 13 December 2021 (UTC)


 * Shaunak Chakraborty, please note I have procedurally ✅ this thread from Administrators' noticeboard to here, where it is now much more in scope. Secondly, to your question, can you clarify this a bit more? Thanks. Dmehus (talk) 06:20, 13 December 2021 (UTC)
 * Actually whenever I am trying to edit any page on English Gyaanipedia not only this above mentioned, this message is popping up and the edits are not saving. I have seen that since last few days other users also don't made any edit which means they also can't able to do that but yes still I can able to edit my userpage, so maybe this thing only affects the main space. This thing is only happening with English Gyaanipedia not with other versions. Can you please help me with this. Shaunak Chakraborty (talk) 06:46, 13 December 2021 (UTC)
 * Did you change the managewiki settings or did some phabricator request? It's like mediawiki got confused that wikitext (which is normal content) isn't allowed in the wiki. <span style="display:inline-block;border:2px solid #bfff00;border-radius:8px;background-image:linear-gradient(to bottom right, #75ff75, #ffff80)"> AP 📨 07:23, 13 December 2021 (UTC)
 * No I didn't change the managewiki settings or doesn't made some phabricator request, but I have tried to figure out this in mediawiki setting but couldn't able to do so. I think now I should put a request on Miraheze phabricator. Shaunak Chakraborty (talk) 08:16, 13 December 2021 (UTC)

Modules
Hello? I'm new here. How can I add a navbox module for my wiki? LiaMinina (talk) 01:26, 15 December 2021 (UTC)


 * Go to Special:Import and scroll down to the "Import from another wiki" section, set Source wiki to meta, set Source page to Module:Navbox, and click Import. It will maybe require more modules so import those too. <span style="display:inline-block;border:2px solid #bfff00;border-radius:8px;background-image:linear-gradient(to bottom right, #75ff75, #ffff80)"> AP 📨 03:03, 15 December 2021 (UTC)
 * Navbox is a more complicated thing just like Infobox. You must first configure them with MediaWiki:Common.css and js from Wikipedia. Any questions, send it to me <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 03:18, 15 December 2021 (UTC)
 * But how do I do that? LiaMinina (talk) 14:33, 15 December 2021 (UTC)

Another suggestion
A new special page or a new Special:ManageWiki section called "Quick templates". The special page would contain lots of buttons with names of commonly used templates (infobox, userbox, documentation, mbox, navbox, etc), clicking one of those buttons will import that template and also all modules needed for it to work. I'm coding an extension that does exactly that too haha <span style="display:inline-block;border:2px solid #bfff00;border-radius:8px;background-image:linear-gradient(to bottom right, #75ff75, #ffff80)"> AP 📨 07:32, 16 December 2021 (UTC)

UI compacting the main navigation menu
Hi! I would love to see main navigation menu on the side be more compact and would suggest removing repetion from 3 sections to be displayed in this way:


 * Request:
 * new wiki
 * new feature
 * adoption
 * RfC's
 * Noticeboard:
 * Community
 * Stewards'
 * Meta Adminis.
 * Miraheze:
 * FAQ
 * Help Center
 * Categories

...what do you think? ZBlace (talk) 07:41, 16 December 2021 (UTC)


 * Isn't it the same? or you meant shortening the text to that? <span style="display:inline-block;border:2px solid #bfff00;border-radius:8px;background-image:linear-gradient(to bottom right, #75ff75, #ffff80)"> AP 📨 08:01, 16 December 2021 (UTC)
 * YES - shortening the text to this version. I think it makes huge difference in mobile access, visibility of Donation link (which is super low at very end) and maybe a little bit in traffic :-) I think also most basic color coding would bot hurt, but that is more complex to negotiate due to color-blind people and branding issues. ZBlace (talk) 08:15, 16 December 2021 (UTC)
 * Why's meta administrators noticeboard with a "i" and fullstop? "Meta Adminis." Typo? And new wiki, new feature, adoption are spelled with no capital letter.
 * Can it be changed to:
 * Requests:
 * Create wiki
 * Request feature
 * Adopt wiki
 * RfC
 * Noticeboards:
 * Community
 * Stewards'
 * Meta admins'
 * Miraheze:
 * FAQ
 * Help center
 * Categories
 * Also, it'd be better if it was a preference instead of everyone getting the shortened sidebar. And another suggestion: move the Donate to Miraheze to the Miraheze: category and make it "Donate" in the shortened version. <span style="display:inline-block;border:2px solid #bfff00;border-radius:8px;background-image:linear-gradient(to bottom right, #75ff75, #ffff80)"> AP 📨 09:07, 16 December 2021 (UTC)
 * Just from the main menu down it? I don't want Random page removed (which I like to keep squishing to see some pages) <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:32, 16 December 2021 (UTC)
 * Just from the main menu down it? I don't want Random page removed (which I like to keep squishing to see some pages) <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 19:32, 16 December 2021 (UTC)

Security disclosure
Community members,

On 15 December, 2021, a security advisory was issued for MediaWiki, the software that powers Miraheze, which disclosed several security issues which allowed malicious actors who willingly attempted to see pages on private wikis to see them. Site Reliability Engineering was made aware of the issue and took steps to patch it temporarily while we upgraded to a newer version of MediaWiki which completely fixed the issue.

Unfortunately, due to an issue with one of our extensions, one of the several vulnerabilities was still exploitable for a short while after we patched all the other security issues. As a result, some pages on private wikis may have been accessible and made fully visible to malicious actors who purposefully attempted to view them using these exploits. We were able to verify that no one used this exploit to view private wiki contents and that the previous MediaWiki vulnerabilities were not used to view private wiki contents in the past few days. In keeping up with our transparency, we are informing the community so that they are aware. If you have any further questions, feel free to reply to this thread, thank you. Agent Isai Talk to me! 20:47, 16 December 2021 (UTC)


 * Hello. What was the extent/function that itself caused this incident? I was about to wonder if this is a new widge. If so, it's one less extension. And, what do you mean, see private wikis? Anyone could see the private wikis? or anyone had to have effort to see the content of private wikis beyond the main page? <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 20:52, 16 December 2021 (UTC)
 * The issues we in MediaWiki Core and made worse by MirahezeMagic. By performing certain actions, (undo, rollback, signature editing), it was possible to view private wiki contents. You would have had to have acted deliberately to view any content. It's not something anyone would have found by accident. ~ RhinosF1 - (chat)· acc· c -  21:53, 16 December 2021 (UTC)

Add Interwiki links to my two Wikis
Hi, I want to add Interwiki links to my two Wikis. The detailed information is as follows.

Wiki to be applied:diamodocs.miraheze.org

Prefix (iw_prefix):dw

Url (iw_url): https://diamowiki.ga/wiki/$1

iw_local:1

Prefix (iw_prefix):hs

Url (iw_url): http://imdchs.rf.gd/$1.html

iw_local:1

Prefix (iw_prefix):hsstudy

Url (iw_url): http://study.imdchs.rf.gd/archives/$1

iw_local:1

Prefix (iw_prefix):dcm

Url (iw_url): http://iamdiamochang.ga/blog/$1

iw_local:1

Prefix (iw_prefix):dcmeta

Url (iw_url): http://iamdiamochang.ga/blog/$1

iw_local:1

Wiki to be applied:diamowiki.ga (diamowiki.miraheze.org)

Prefix (iw_prefix):hs

Url (iw_url): http://imdchs.rf.gd/$1.html

iw_local:1

Prefix (iw_prefix):hsstudy

Url (iw_url): http://study.imdchs.rf.gd/archives/$1

iw_local:1

Prefix (iw_prefix):dcm

Url (iw_url): http://iamdiamochang.ga/blog/$1

iw_local:1

Prefix (iw_prefix):dcmeta

Url (iw_url): http://iamdiamochang.ga/blog/$1

iw_local:1

Thanks. @Diamochang - talk | [mailto:diamochang@gmail.com email me] - 01:19, 18 December 2021 (UTC)


 * This is ✅ at this time, you can visit  and   for the logs. Ugochimobi (talk) 21:47, 18 December 2021 (UTC)

Errors
What errors are you facing? Agent Isai Talk to me! 10:51, 19 December 2021 (UTC)
 * 1) Trying to create or delete this page leads to an error.
 * 2) Trying to import valid XML files also leads to a similar error. Ora &#38; D (talk) 10:44, 19 December 2021 (UTC)


 * 1. Create:
 * The revision #0 of the page does not exist.
 * This is usually caused by following an outdated history link to a page that has been deleted. Details can be found in the deletion log.
 * Delete:
 * Fatal exception of type "LogicException".
 * 2. Fatal exception of type "Wikimedia\Rdbms\DBTransactionError". Ora &#38; D (talk) 11:00, 19 December 2021 (UTC)
 * This probably should be moved to Phabricator, noting the fatal exception, linking to the permalink to this thread. Dmehus (talk) 06:44, 20 December 2021 (UTC)
 * Thanks. It's being handled there. Ora &#38; D (talk) 16:52, 20 December 2021 (UTC)

Block log message not changing
I was trying to change the block log message for a wiki I run (Decyclopedia), and I noticed that the block log message wasn't changing. I tried looking at MediaWiki help pages to try to figure the problem out. I'm editing MediaWiki:Blocklogentry on that wiki. Tali64³ (talk) 18:26, 20 December 2021 (UTC)


 * The message appears to be MediaWiki:Logentry-block-block. I am not sure where, if any, MediaWiki:Blocklogentry is actually used. By the way, using uselang=qqx parameter in the URL will tell you the names of all the messages used on the page. Dylsss (talk) 19:50, 20 December 2021 (UTC)

My ban, and mental health.
im still around thankfully. Wishing all a merry Christmas. Sorry to be a nuisance but all my wikis are dead, can i possibly get my ban lifted or lightened??? Thank you all. Take care. SperosDurrell (talk) 02:26, 21 December 2021 (UTC)


 * You can undo a wiki inactivity in Special:ManageWiki/core of your wiki <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 02:28, 21 December 2021 (UTC)
 * just want to start fresh that's all. Thanks. SperosDurrell (talk) 02:29, 21 December 2021 (UTC)
 * It's great to see you around but it would be nice for you to focus on the wiki you already have. Agent Isai  Talk to me! 02:31, 21 December 2021 (UTC)
 * which one lol? There all dead.... SperosDurrell (talk) 02:34, 21 December 2021 (UTC)
 * link, me??? SperosDurrell (talk) 02:38, 21 December 2021 (UTC)

Mejoras en la piel vector / Improvements in skin vector
Hola. He realizado una propuesta sobre mejoras de la piel vector pero fue desetimada porque excede el alcance técnico de Miraheze.

Encontré que este asunto se está desarrollando en MediaWiki y existe una consulta a la comunidad: Reading/Web/Desktop Improvements/Third prototype testing. Todos pueden participar y experimentar.

Esperemos que pronto se generen los cambios para disminuir la cantidad de caracteres por línea. Lo sugerido es entre 45 a 75. Actualmente, en pantallas de más 1300px caben más de 130 caracteres por línea. La Wikipedia francesa ya adoptó un cambio muy favorable en la piel vector. Saludos a todos. ¡Felicidad y prosperidad! Hugo Ar (talk) 15:27, 21 December 2021 (UTC)


 * Translated by Google Translator


 * Hello. I have made a proposal on vector skin enhancements but it was rejected because it exceeds the technical scope of Miraheze.


 * I found that this topic is being developed on MediaWiki and there is a community query: Reading/Web/Desktop Improvements/Third prototype testing. Everyone can participate and experiment.


 * We hope that the changes will be generated soon to reduce the amount of characters per line. The suggested is between 45 to 75. Community Wishlist Survey. Currently, screens larger than 1300px can fit more than 130 characters per line. The French Wikipedia has already adopted a very favorable change in vector skin. Greetings to all. Congratulations and prosperity! Hugo Ar (talk) 15:27, 21 December 2021 (UTC)
 * You are trying to switch to the new vector, (as well as the French Wikipedia and Portuguese Wikipedia) and take the old one (legacy vector which is the current one), bu the English wiki and the mediawiki site haven't even done that yet, would be an interesting idea, but let's wait for new updates, both on mediawiki and also on high traffic sites, as the new version is a beta <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 16:56, 21 December 2021 (UTC)


 * Hola. Al parecer puede efectuarse el cambio con esto: / Hello. Apparently the change can be made with this:

$wgVectorDefaultSkinVersion = '2'; $wgVectorDefaultSkinVersionForExistingAccounts = '2'; $wgVectorDefaultSkinVersionForNewAccounts = '2'; $wgVectorIsSearchInHeader = true; $wgVectorLanguageInHeader = true; $wgVectorUseWvuiSearch = true;
 * Saludos / Greetings Hugo Ar (talk) 19:11, 21 December 2021 (UTC)

Can I limit namespaces?
I dont necessarily need to do this, but it may be nice, could I set user group rights in such a way that some groups can only edit certain namespaces? If not thats not a problem for me but was just wondering. Or maybe limit certain namespaces to certain usergroups? (excluding the editprotected and edit semiprotected userrights). Thanks for the advice! EmperorOctopus (talk) 22:18, 21 December 2021 (UTC)
 * You can change in Special:ManageWiki/namespaces page of your wiki, select clicking in "submit" (If you choosed a namespace) and it will have a box with the name: Which userright should be needed to edit this namespace? ($wgNamespaceProtection). You type some user right in it <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 22:32, 21 December 2021 (UTC)
 * Thank You! Ill look when I get home. EmperorOctopus (talk) 01:58, 22 December 2021 (UTC)
 * Yeah, so that only has the options for editprotected and editsemiprotected and editinterface. Again what Im asking may not be possible, but Could I limit a new namespace to a custom usergroup? If not that's fine, I'm just curious. Thanks, EmperorOctopus (talk) 03:31, 22 December 2021 (UTC)
 * I will see, thanks <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 03:38, 22 December 2021 (UTC)

template infobox election not working
Hi, when I try to make the infobox election template it doesnt work and says "Script error: No such module "documentation".Script error: No such module "Check for unknown parameters"." And whenever I put with {Infobox election} (with two of these brackets{ on each side)it just says ""Template:Infobox election""

Any help will be appreciated, thanks Papito19 (talk) 00:52, 22 December 2021 (UTC)
 * When "No such module" error appears, it is because there are no modules to make the infobox work. To fix this, do the following, for example, when EX: "Error no module of this type: Yesno", then you will have to create a module with the name yesno from Wikipedia. Anything invite me to check your wiki infoboxes <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 01:05, 22 December 2021 (UTC)
 * where do you put "yesno" sorry im new Papito19 (talk) 01:59, 22 December 2021 (UTC)
 * Invite me to your wiki for me to review if you want <b style="color: #1965e0;">YellowFrogger</b> <b style="color: #069404;">(<b style="color: #069404;">✉ Talk </b> <b style="color: #069404;">✐ Edits </b>)</b> 03:38, 22 December 2021 (UTC)

EditNotify
Hello! ManageWiki has an EditNotify extension. As I understand it, it allows you to notify about fresh changes through the Echo interface. But when I connected it on my wiki, I did not find anything like this. So what does this extension do? DecabristM (talk) 10:12, 23 December 2021 (UTC)
 * Hello! The extension allows registered user to get notified for:

All users who are subscribed for any of the event listed above will be notified for them with a simple alert message (Echo notification) as well as an email. The possible sets of pages for which users can choose to be notified are: Source: https://www.mediawiki.org/wiki/Extension:EditNotify --YellowFrogger (Talk — ✐) 22:44, 23 December 2021 (UTC)
 * Creation of new pages
 * Edit to existing pages - It includes notification to all changes.
 * Change in specific template field - Users get the notification when there is a change in template field
 * Change in specific template field to specific template value - Users are notified when there is a change in template field value
 * All pages - keep track of change or creation of all pages.
 * All pages in one or more namespaces
 * All pages in one or more categories
 * All pages in one or more categories
 * I saw it. I don't understand where the list of attendees is configured to receive these notifications. The documentation only offers a way to change the system files, which I cannot do. DecabristM (talk) 09:07, 24 December 2021 (UTC)

Remove the space between my two tabs
Hi there, I have created two templates, unfortunately there is a gap between them, as you can see on this page : https://fiction.miraheze.org/wiki/Gal_Gadot#R%C3%B4les_principaux I would like to have them "glued" together. How do I remove the space? Thanks in advance. Darkrai18 (talk) 11:46, 23 December 2021 (UTC)


 * You mean you want the 2 tables to be sticked together? <span style="display:inline-block;border:2px solid #bfff00;border-radius:8px;background-image:linear-gradient(to bottom right, #75ff75, #ffff80)"> Anpang 📨 11:49, 23 December 2021 (UTC)
 * Basically, yes. Darkrai18 (talk) 12:01, 23 December 2021 (UTC)
 * Something like this:

Which is:


 * Explaination: Tables are seperated because they have margin values, here in the style= css the top and bottom margins have been set to 0, but the bottom border of the top table will still overlap the top border of the bottom table which will make the border thick so the bottom margin of the top table needs to be -1 instead of 0. <span style="display:inline-block;border:2px solid #bfff00;border-radius:8px;background-image:linear-gradient(to bottom right, #75ff75, #ffff80)"> Anpang 📨 12:34, 23 December 2021 (UTC)
 * I did not understand everything... Concretely, what do I have to change ? Darkrai18 (talk) 12:55, 23 December 2021 (UTC)

Interwiki table
Could you please In the Interwiki table of XComhghall Wiki?
 * 1) Add the prefix   to , and
 * 2) Delete the interlanguage prefix  ,

Thank you very much. — XComhghall (talk) 22:35, 23 December 2021 (UTC)
 * --YellowFrogger (Talk — ✐) 22:40, 23 December 2021 (UTC)
 * This is ✅, thanks. --  Joseph  TB  CT  CA   23:08, 23 December 2021 (UTC)

Huggle
I wondered how to use Huggle with Miraheze. I'd like to continue anti-vandalism efforts easier for the wikis that get vandalized the most. -- Cheers, Bukkit ( Talk • All Contribs ) 00:28, 24 December 2021 (UTC)
 * The Huggle is a great alternative to Twinkle yes, but I ask if it needs to be rollback to revert in Huggle. And also: the recent changes here from Meta is a bit stalled on vandalism; there is not much vandalism here. Even so, vandalism starts mainly with IP addresses. --YellowFrogger (Talk — ✐) 00:39, 24 December 2021 (UTC)
 * Huggle is a tool which was designed with the Wikimedia movement in mind. It seems to require server-side software to be deployed and configured across multiple wikis so this is something that cannot be used on Miraheze. Agent Isai  Talk to me! 00:43, 24 December 2021 (UTC)