Community noticeboard: Difference between revisions

From Meta
m (Bot: Archiving 1 thread (older than 14 days) to Community noticeboard/Archive 13)
Line 399: Line 399:
::ty doug. [[User:Hrvcfr|Hrvcfr]] ([[User talk:Hrvcfr|talk]]) 17:50, 19 October 2020 (UTC)
::ty doug. [[User:Hrvcfr|Hrvcfr]] ([[User talk:Hrvcfr|talk]]) 17:50, 19 October 2020 (UTC)
:::No problem. [[User:Dmehus|Dmehus]] ([[User talk:Dmehus|talk]]) 17:54, 19 October 2020 (UTC)
:::No problem. [[User:Dmehus|Dmehus]] ([[User talk:Dmehus|talk]]) 17:54, 19 October 2020 (UTC)
== Local interwiki administrator request ==
Hi, I request local rights for interwiki admininstration for my wikis [[mh:lilypond|Lilypond Wiki]] · [[mh:meingarten|my little garden]] · [[mh:regionalbahnstattbus|Regionalbahn Weinviertel]] (although I said I would not need them, maybe this rights come in handy for some purposes), thank you very much&nbsp;<span style="font: bold 1.1em Georgia, serif;">Lily</span> ([[mh:lilypond|Lilypond Wiki]] · [[mh:meta:User talk:Lily|talk and I will listen]] · [[mh:meingarten|my little garden]] ) 04:45, 21 October 2020 (UTC)

Revision as of 04:45, 21 October 2020

OOjs UI icon userGroup-ltr.svgCommunity noticeboard
This noticeboard is community discussions, generally global in nature or which relate to specific wikis or users. For requests that require Steward or Global Sysop intervention, please see the Stewards' noticeboard. If in doubt, please try here first, and you will be directed there if the matter requires a Steward. For discussion pertaining to Meta only, please visit the Meta Community portal.

On Community noticeboard, you can:

  • Start a community discussion, generally global in nature or which relates to specific wiki(s).
  • Solicit volunteers' assistance to help maintain or write content for your wiki
  • Ask questions with both the global community and system administrators about either Miraheze or some technical aspect of MediaWiki on your wiki
  • Request changes to your wiki's local interwiki table, including change(s) to locally override one or more of the global interwiki table (located on Meta) prefix configurations

If you would like to request...

To add your request, type in a concise title in the box below, then click "Add Topic".

Archives of Community noticeboard [e]   



Okay, ladies and gentlemen, I have a question for you: should we have a wiki on here like the Wiki Gazetteer on FANDOM? Put your vote in the headings below! And remember to sign your posts with ~~~~. Tali64³ (talk) 20:33, 16 July 2020 (UTC)[reply]


  1. Symbol support vote.svg Support Why not? This would not be a bad idea for someone looking for a specific wiki. --Furricane (talk) 21:57, 16 July 2020 (UTC)[reply]
  2. Symbol support vote.svg Support per @Furricane: InspecterAbdel (talk) 21:16, 26 July 2020 (UTC)[reply]
  3. Symbol strong support vote.svg Strong support I strongly support this because we can find more specific wikis. CircleyDoesExtracter(Circley Talk | Global |Email the Cloud) 21:31, 26 July 2020 (UTC)[reply]
  4. Symbol partial support vote.svg Weak support I'm not opposed to this idea, in theory, and I do think that we need to rethink Gazetteer of wikis given that we have ~3,800 current wikis (which is too large for a single page). My main concern, which I expressed in declining the wiki request, was that this may suffer from lack of maintenance and timely updates. As well, by siphoning it away from Meta, we now have yet another wiki we have to somehow promote, so that sort of defeats the purpose of a gazetteer of wikis designed to promote customers' public wikis, doesn't it? Secondarily, I honestly think a better way to go about this is to add additional functionality and data output to the automated list, Special:WikiDiscover. That said, it's a good-faith idea, in theory and if well-maintained, so that is why I am expressing some support, albeit weak. Dmehus (talk) 23:18, 6 August 2020 (UTC)[reply]
  5. Symbol strong support vote.svg Strong support I think this will help in finding wikis. Admittedly, there was once a list on Wikia, but we've dropped it. Onmp314 (talk) 16:23, 27 September 2020 (UTC)[reply]
    @Onmp314: There are still two: the Wiki Wiki and the Wiki Gazetteer. Tali64³ (talk) 22:34, 14 October 2020 (UTC)[reply]


  1. Symbol oppose vote oversat.svg Strong oppose I don't see the need for an entire wiki like this. We already have a page here on meta, Gazetteer of wikis. And in all honesty, a page on meta will most likely be given more notice than another external wiki that some will never visit. As such I am opposing this idea. While a good thought I don't see the need for it. I mean if you want it, go for you, but I don't think it should be a community wiki at all.
    @Universal Omega: There are 4379 wikis currently on Miraheze, too big to list on one page. An administrator could put a link to it on the main page. Tali64³ (talk) 16:35, 15 August 2020 (UTC)[reply]
    @Tali64³: We also have Special:WikiDiscover which lists every wiki on Miraheze.
  2. Symbol oppose vote.svg Oppose Not needed.--MrJaroslavik (talk) 06:29, 25 August 2020 (UTC)[reply]
  3. Weak Oppose.svg Weak oppose if there were a lot of people to add entries for wikis with short descriptions that would work for me but right now I think that the Meta gazeteer is enough and is helpful. DeeM28 (talk) 07:33, 25 August 2020 (UTC)[reply]
  4. Symbol oppose vote.svg Oppose A wiki for this is unnecessary, Gazetteer of wikis on Meta works fine. If there was a way to automate it with Special:WikiDiscover, I might rethink it, but otherwise this would likely get really outdated long-term. K599 (talk) 20:12, 27 September 2020 (UTC)[reply]
  5. Symbol oppose vote.svg Oppose and I would like to note, wiki creations are at the sole discretion of wiki creators and global policy, and I view this as a way to circumvent a decline of mine. Thus, I also recommend a closure of this as not done. Zppix (Meta | CVT Member | talk to me) 05:33, 20 October 2020 (UTC)[reply]


I think it's a fair enough idea but there are many ways to approach it and would need lots of maintenance and would probably create some form of conflict -Bayugoon (talk) 19:45, 19 October 2020 (UTC)[reply]


  1. I'm currently been slowly working on a similar idea over the past month or two just documenting wikis: the Wikiverse. dibbydib 23:38, 22 July 2020 (UTC)[reply]
  2. As a Miraheze wiki creator, when this wiki truly passes through us for approval (I have recently accidentally approved this wiki sent in by @Tali64³:, which due to the ongoing discussion and the incorrect subdomain is currently pending steward review for deletion), it is important for us to know when to approve the wiki and who will be creating it. Therefore, who will be the founding Bureaucrat of the wiki if it passes community discussion?
    @Tali64³ and Universal Omega:: I would be the founder. Tali64³ (talk) 23:23, 14 August 2020 (UTC)[reply]
    @Tali64³: When having community discussions like these, who will be the founder is among what should be discussed. I believe who should be the founder should be among what is discussed here. Thanks!
  3. Relisting for another couple of weeks. Dmehus (talk) 05:20, 1 September 2020 (UTC)[reply]
  4. Relisting for another several weeks. Dmehus (talk) 11:42, 15 September 2020 (UTC)[reply]

A community Developers wiki

I have a proposition for the Miraheze community. For a while now I have been debating whether or not to create a developers wiki for Miraheze. Unlike the template wiki, this wiki will include CSS and JS scripts that anyone can import using mw.loader.load(), it will allow anyone who wants it to use scripts built by the community in their own wikis and/or in their own personal global or local JavaScript or CSS files. After consulting with @Dmehus: on Discord, I decided to get the communities feedback and/or support on this idea, therefore what does the Miraheze community think of this idea?
  • Pictogram voting comment.svg Comment: Yeah, though I don't think it's required to have a community discussion in this case, since it's going to be a community wiki for shared CSS and JavaScript files, among other things potentially, I thought it would be a good practice to have the discussion, especially if it proposes to use the name "Miraheze." Plus, I think it would be helpful for the community to (a) define the initial scope and purpose and (b) establish the founding bureaucrats for the wiki. From there, the local community can help to establish its local policies and further refine its purpose. In general terms, I support this as a community wiki as I think it is sufficiently different than the Template and Miraheze Bots + Tools wikis. I also think it could be useful at reducing the page load times of community-imported and -maintained user scripts, as opposed to always loading them from English Wikipedia and other wikis. Dmehus (talk) 23:17, 24 July 2020 (UTC)[reply]
@Dmehus: yes, some of that is part of my initial thoughts for the reasoning of the wiki. As for using the name Miraheze in it, I think it should be called Miraheze Developers Wiki or something similar. As for bureaucrats of the wiki, any candidate recommendations? And I think a community discussion for this is a good idea. It gives the community a way to give input, and their own unique ideas in it as well.
  • Symbol strong support vote.svg Strong support As proposer I support this, but also because I know JS and CSS pretty well, and would love to have a wiki like this for the Miraheze community.
  • Symbol support vote.svg Support This is a great idea for a new wiki. I think that by doing this, lots of new coding things could be enabled, including possibly global modules and gadgets. Great suggestion. I also have no concerns for this proposal. --Furricane (talk) 23:27, 24 July 2020 (UTC)[reply]
@Furricane: yes, I do believe that a wiki like this could be greatly beneficial in the long run, or at least I hope it can be.
  • Symbol strong support vote.svg Strong support I support this idea because not everyone can do custom CSS and (or) custom JS. Onmp314 (talk) 16:57, 27 September 2020 (UTC)[reply]
  • Symbol support vote.svg Support Sounds like a good idea for having a central place to import JS and CSS. K599 (talk) 20:39, 27 September 2020 (UTC)[reply]
  • Symbol support vote.svg Support per my comments above. Dmehus (talk) 21:00, 27 September 2020 (UTC)[reply]
  • Symbol support vote.svg Support Good. Waldo (talk) 21:56, 27 September 2020 (UTC)[reply]
  • Symbol support vote.svg Support would be a nice place to ask questions with in that area Bayugoon (talk) 19:50, 19 October 2020 (UTC)[reply]

Potential rename and/or expanded scope of Dev Wiki

@Universal Omega: asked me a few days, or perhaps a week, ago if I had posted in this discussion thread about the potential renaming and expanded scope for Dev Wiki yet. Other tasks took priority, but seeing as this thread was due to be archived in the next day or so, I wanted to get this done. So, I'm going to {{ping}} those that participated above and those who participated in the discussion on potential name ideas/expanded scope on Discord.

So, the question is...given that the dev subdomain implies broader usage by and for developers beyond just CSS and JavaScript scripts, @Universal Omega, Void, Lakelimbo, NDKilla, Reception123, and Furricane: and I (did I forget anyone, @Universal Omega:?) basically toyed around with a number of potential new names and subdomains, the top three of which is identified below:

  1. Retain dev and expand the scope, or allow the community, via a future community noticeboard discussion to expand the scope at some point in the future;
  2. Rename subdomain to repo, which would be roughly in line with the current purpose and scope, but open to possibilities later (again, the community would retain the right modify the scope via a community noticeboard discussion); or,
  3. Rename subdomain to cssjs, with a narrow scope; limits us in the future, but entirely accurate; it's not too bad, as we could easily create a separate dev later, though we should reserve that subdomain in the blacklist)

Since @RhinosF1: didn't participate in the Discord discussion and since this doesn't require any advanced rights to close, I nominate him to assess the consensus and close this discussion in a week or two. --Dmehus (talk) 00:01, 7 August 2020 (UTC)[reply]

Nomination of RhinosF1 as closer

@RhinosF1:, please indicate if you would be willing to close this discussion after 1-2 weeks (depending on the weather-related impacts to U.S. eastern seaboard residents).

Additionally, can I get a seconder to second this nomination? (Thought we could probably safely skip a full vote on nominating an uninvolved closer.)

Voting and Vote Tabulation Instructions

You are encouraged to express first and second choices in your !vote. Please do so by indicating, in your !vote for each proposal, whether it is your first or second choice. If no proposal achieves more than 50% of the valid !votes cast, the proposal with the least number of first choice !votes will be dropped, and those users' second choices will then be allocated accordingly, and the results retabulated in a second count.

Proposal 1: dev


  1. Symbol support vote.svg Support
  2. Symbol support vote.svg Support as first choice, since the community remains overall authority over this wiki in terms of its bureaucrat removal (as may be required) and in terms of redefining, or broadening, its scope. Dmehus (talk) 11:50, 22 August 2020 (UTC)[reply]
  3. Symbol support vote.svg Support I think there is no need to rename. Onmp314 (talk) 16:57, 27 September 2020 (UTC)[reply]
  4. Symbol support vote.svg Support Looks nice, and is easy to understand. K599 (talk) 20:47, 27 September 2020 (UTC)[reply]



This is arguably kind of useless, in this case, since the !votes won't be counted, but I'll nonetheless include it.

Proposal 2: repo




This is arguably kind of useless, in this case, since the !votes won't be counted, but I'll nonetheless include it.

  1. Symbol neutral vote.svg Neutral I like this idea as well, but it feels like it has other non-computer science-related use cases (i.e., for an archival- or museum-type wiki). Dmehus (talk) 11:50, 22 August 2020 (UTC)[reply]

Proposal 3: cssjs




This is arguably kind of useless, in this case, since the !votes won't be counted, but I'll nonetheless include it.

  1. Symbol neutral vote.svg Neutral I also liked @NDKilla:'s idea, as it is the most specific and clearly defines this wiki's current purpose, but, at the same time, it really does restrict a future broadening of this wiki's scope to include a broader array of wiki developer resources, for which the community retains the absolute authority to redefine this wiki's purpose via community noticeboard. Dmehus (talk) 11:50, 22 August 2020 (UTC)[reply]


  1. It's also important to point out that, per the approved wiki request, this is a community wiki and the community maintains overall supremacy over this wiki (i.e., its scope, bureaucrats, etc.).
  2. Everyone agreed to use @Lakelimbo:'s great logo for Dev Wiki.

A new wiki for the website's community

The Miraheze Community Wiki is a wiki for the community so people can get to know each other and welcome each other. I know Meta does that, but I think we need a wiki for that stuff.


  1. Symbol strong support vote.svg Strong support I think we need a wiki for this kind of thing InspecterAbdel (talk) 22:44, 27 July 2020 (UTC)[reply]
  2. Symbol partial support vote.svg Weak support but not per any of the above or below, but because community noticeboard has become a catch-all for technical support questions, community discussions, and really anything. The organization is weak, and we could use a community wiki. I have no objections to it, but the main reason for my oppose weak support here is because the purpose is somewhat vague and unclear. I appreciate @InspecterAbdel: bringing this for a community discussion, though, and, since this wiki was simultaneously submitted for approval and created already, I think we should probably shift this wiki towards defining a clear purpose and terms of reference for its existence and the parameters by which the local bureaucrats can be removed (via Community noticeboard) here on Meta. Dmehus (talk) 14:55, 28 July 2020 (UTC) Amended. Moved from weak oppose to weak support Dmehus (talk) 15:31, 28 July 2020 (UTC)[reply]
  3. Symbol support vote.svg Support I think we should have one since fandom has one. Plus it's subdomain is valuable too. AppleCrunchy (talk) 19:16, 14 September 2020 (UTC)[reply]


  1. Symbol neutral vote.svg Abstain I really like to have a community wiki for new users to gather, although we have a Community noticeboard. CircleyDoesExtracter(Circley Talk | Global |Email the Cloud) 17:09, 28 July 2020 (UTC)[reply]


  1. Symbol oppose vote.svg Oppose. No, we don't need such a wiki. This page ("community noticeboard") is exactly for this kind of thing. I don't want to have to check both this page and a dedicated wiki to find out what is happening on the wiki farm, nor learn how such a wiki is organized. Spıke (talk) 04:25, 28 July 2020 (UTC)[reply]
  2. Symbol oppose vote.svg Oppose Per Spike. There is already not enough engagement and usage on Meta, so another wiki is really not what we need. We should focus on Meta. Reception123 (talk) (C) 06:08, 28 July 2020 (UTC)[reply]
  3. Symbol oppose vote oversat.svg Strong oppose. We DO NOT need a community wiki is needed at this time. We already have this page, the community noticeboard, and Requests for Permissions, requests for global rights and requests for stewardship. It seems that it would serve the same service as as most of this meta wiki, and I just see no possible usage for this. I also agree with the comments that Spike has made about having to go back and forth between meta and a community wiki. Sorry, it is just not going to work. --Furricane (talk) 15:10, 28 July 2020 (UTC)[reply]
    @Furricane: I'm hoping you'll consider amending your !vote, per my comments above, as I really don't think @InspecterAbdel:'s goal was for this wiki to replace Meta. The problem with this request is that (a) the wiki shouldn't have been created without a community discussion (not, technically, a requirement, as far as I'm aware, but good practice) and (b) it should've had a clearer purpose, scope, and defined parameters, as we are doing with Dev Wiki and have done with Template Wiki and Miraheze Commons in the past. No community proposals or discussions, or even drafts of such proposals, would've occurred on this wiki. Rather, as I saw it (though vague and unclear), this wiki was meant to be a user collaboration and social connection wiki that would've actually sought to deepen community participation. Participation in this community wiki would've been completely voluntary and not participating would not have meant the user would "miss out" on important community discussions, as I don't think that was ever the intent behind @InspecterAbdel:'s good-faith proposal. Dmehus (talk) 15:27, 28 July 2020 (UTC)[reply]
  4. Symbol oppose vote.svg Oppose Not needed.--MrJaroslavik (talk) 06:34, 25 August 2020 (UTC)[reply]
  5. Symbol oppose vote.svg Oppose I do not think another wiki is necessary for the community because for me Meta is the wiki for the community. DeeM28 (talk) 07:30, 25 August 2020 (UTC)[reply]
  6. Symbol oppose vote.svg Oppose This is unnecessary, Meta already serves essentially the same purpose, and there's not really enough of that kind of "community" activity to need a separate wiki. K599 (talk) 20:27, 27 September 2020 (UTC)[reply]
  7. Symbol oppose vote oversat.svg Strong oppose After reading the first two oppose votes I agree with those users. We should try to engage the community on Meta and we can be doing community oriented activities here. Тишина (talk) 17:15, 12 October 2020 (UTC)[reply]
  8. Symbol oppose vote oversat.svg Strong oppose I agree that the noticeboard is enough and if there was a whole wiki about the community it would be under used and it would require moving around instead of just looking at this one page Bayugoon (talk) 19:55, 19 October 2020 (UTC)[reply]


  • I think the subject is not whether we need a community wiki or not, as we already have a community-centric wiki, but whether we need a miraheze-sanctioned community wiki.I think CN is sufficient, but it seems unusual for a topic to be set up for communication purposes, so someone may need to give an example.I found an image on showing the stroke order of my name, so it might be a good idea to post it, but it takes courage to be the first one.--松•Matsu (talk) 22:53, 5 October 2020 (UTC)[reply]
  • Relist to delay archiving. I will be posting an updated proposal on next steps in the next several days. Dmehus (talk) 02:30, 12 August 2020 (UTC)[reply]
  • Relist to delay archiving. I will be posting an updated proposal on next steps in the next several days. Dmehus (talk) 01:36, 23 August 2020 (UTC)[reply]
  • Relist to delay archiving. I will be posting an updated proposal on next steps in the next several days. Dmehus (talk) 05:21, 1 September 2020 (UTC)[reply]

Template Wiki / Global Interwiki prefixes

Hi, I have several questions. Is it allowed to create own templates in the template wiki? If yes, would it be possible to add a new interwiki prefix for the template wiki e.g. "t" because "templatewiki" is much text. Alternative could you please create a new interwiki prefix "lily" for my Lilypond Wiki? So I could use templates from there in my other wikis which would save me a lot of work. Thank you very much Lily (Lilypond Wiki · talk and I will listen · my little garden ) 11:21, 1 October 2020 (UTC)[reply]

@Lily: Thank you for your question regarding interwiki prefixes. I would be very hesitant, and reluctant, to add single-character prefixes to the global interwiki table here on Meta, mainly because of the huge ambiguity in what they could potentially refer to. More importantly, though, changes to the global interwiki table are currently undergoing a draft a RfC that should go live in several weeks (hopefully). These changes will mainly seek to specify on which wiki the global interwiki table is to be based, who is eligible to edit the global interwiki table, and under what conditions the global interwiki table is to be edited. Nevertheless, I will add that shortcut to your Lilypond Wiki local interwiki table. Dmehus (talk) 14:11, 1 October 2020 (UTC)[reply]
@Lily: I have Yes check.svg locally added the t prefix for Template Wiki to the Lilypond Wiki's local interwiki table with both the forward and transclude flags enabled, per your request. When importing by uploaded XML file, you should now be able to use the t prefix to have users' edits from Template Wiki associated to their Template Wiki profiles (or local Lilypond profiles, where they exist locally). For transwiki importation, if you use that, a GitHub pull request will likely need to be done for your wiki to add this local prefix to the $wgImportSources variable for your local wiki. I wasn't quite sure about the second part of your request, though. To which wiki(s)' local interwiki tables did you want Lilypond Wiki added to? If you wanted that added to the global interwiki table, as the global interwiki table would become very unwieldy in a very short hurry if we added customers' wikis to the global interwiki table, we instead opt to use MirahezeMagic interwiki wikilinks, formatted as [[mh:subdomain:pagename|optional piped link]]. I am to add the lily interwiki prefix to your other wikis' local interwiki tables, if you wish, and also to do the GitHub pull request for Lilypond Wiki. Dmehus (talk) 14:25, 1 October 2020 (UTC)[reply]
@Dmehus: Thank you very much for your answer. If I had lily as interwiki-prefix in my other wikis meingarten and regionalbahnstattbus I could use all the templates from lilypond in this wikis. I still do not know if it is allowed to add templates to the template wiki for ordinary users like me who are not part of the Miraheze stuff. Lily (Lilypond Wiki · talk and I will listen · my little garden ) 15:27, 4 October 2020 (UTC)[reply]
Hi @Lily:, you didn't ask me, but my opinion is that the Template Wiki is for experimentation/development and general-use templates, and not for templates that are merely common to your own wikis. Putting a template on Template Wiki would be like creating a page on Meta to better explain something on your own wikis. It might be, and you might start a thread on this page claiming, that a given template is so ideal for general use that it belongs on Template Wiki. Until that time, I think your approach with interwiki prefixes is the correct way. Spıke (talk) 15:50 4-Oct-2020
Hi @Spike:, thank you for your opinion. You are right, the interwiki prefix in my local wiki tables would be the best solution for me, Lily (Lilypond Wiki · talk and I will listen · my little garden ) 17:20, 4 October 2020 (UTC)[reply]
@Lily: Yes check.svg Done. I've added the lily interwiki prefix to both of those added local wikis' interwiki tables. I should note that you should be able to import templates locally from Lilypond wiki using the file upload (i.e., uploaded XML file) method. If you want to use the transwiki import method, we'll have to add do a GitHub pull request for both of those wikis to add lily as a $wgImportSources import source in the drop-down menu. I enabled the "forward" flags, but not the "transclude" flag. The latter allows for scary transclusion, to transclude a page from another wiki without importing it. It generally works fine for basic pages, but for templates, since there are template dependencies needed on both wikis, it can be, well, scary. Nevertheless, should you wish for that flag to be enabled, {{ping}} me on reply to this thread, or begin a new thread if already archived. To add to what @Spike: said, yeah, anyone can absolutely add templates to Template Wiki. It's a community wiki, albeit not very active of late. The challenge there, too, is with few active local administrators, it can be a challenge to have certain templates imported. Of course, one can always request local sysop permissions at the community portal, especially if needed for template importation. But, as you said, for your needs, it makes sense to concentrate your templates on Lilypond wiki. Dmehus (talk) 18:25, 4 October 2020 (UTC)[reply]
P.S. One more thing related to your regionalbahnstattbus wiki...I noticed that you have not assigned the editmywatchlist and viewmywatchlist to the user group. Was this by design/your intention, or was this an oversight? I usually like to remove my user page from my watchlist on wikis where I visit, so wasn't able to do this. Not a big deal if this was your intention, but just thought I'd mention it if it was an oversight. Dmehus (talk) 18:25, 4 October 2020 (UTC)[reply]
@Dmehus: thank you very much. The thing with the watchlist is an oversight, nobody is visiting this wiki anyway. I have changed the rights, Lily (Lilypond Wiki · talk and I will listen · my little garden ) 18:32, 4 October 2020 (UTC)[reply]
@Lily: Oh, that's great. Thanks so much! I should also mention that, though interwiki administrator is most commonly known as a global role, one can request local interwiki administrator rights on their wiki. I'm currently drafting an interwiki reform RfC, but in the meantime, current global requirements for local interwiki administrator are that you must hold bureaucrat rights on the wiki(s) for which you're requesting. Additionally, if your wiki has any local permissions election rules specifying all or some positions must be elected locally by consensus, then you would need to hold a local election as well. However, looking at this page on your wiki, it looks like just you and Manuela are local bureaucrats, so it's likely not necessary to hold a local election. Should you wish to go this route, you would make a request for local interwiki administrator on stewards' noticeboard, linking to both your local wiki and any local election/permissions request page, if your wiki requires it. Of course, then you wouldn't need a global interwiki administrator to add interwiki prefixes for you, but if you planning on adding many prefixes, then it probably does make sense. Additionally, you also probably meet the global edit requirement for global interwiki administrator, to be honest, so if your activity on Meta were to pick up and you wanted to volunteer in this way, you can request rights for the global group at requests for global rights. Hope this additional information is helpful. Oh, by the way, I do like the work you've put into your wikis, and particularly like your German regional public transportation information wiki. If you ever plan on not being active on your wiki(s), you can request a Dormancy Policy exemption for one or more wiki(s), citing the applicable exemption criterion for each wiki(s) requested, at stewards' noticeboard. Dmehus (talk) 19:24, 4 October 2020 (UTC)[reply]
Thanks again @Dmehus: (it is already hard to count the colons ;-) ). Actually Manuela is my account, too. I have planned to edit as normal user, not as admin, but this was not very comfortable, so I granted both accounts bureaucrat rights. Now I am editing mostly as Lily. I think it is a good thing that only bureaucrats should have interwiki admin rights on a wiki. I am not planning to add more interwiki prefixes, lily will do the trick ;-) Lily (Lilypond Wiki · talk and I will listen · my little garden ) 05:22, 5 October 2020 (UTC)[reply]
@Dmehus: Sorry to bother you again. I have the interwiki prefix lily in my wikis now, but transclusion is still not possible. Interwiki table Meingarten Interwiki table Meingarten the entry in the column "transclude" is "no" Lily (Lilypond Wiki · talk and I will listen · my little garden ) 06:47, 5 October 2020 (UTC)[reply]

──────────────────────────────────────────────────────────────────────────────────────────────────── @Lily: No problem. Yeah, I didn't enable the transclude flag as I wasn't sure if you were wanting to use scary transclusion or not, as you don't need that flag to use the lily interwiki prefix with your template imports by file upload. Nevertheless, it's neat that you want to try out scary transclusion and you have a valid use case, so I've Yes check.svg enabled that flag on both your wikis as requested. Regarding counting the colons, yeah I debated whether or not to {{outdent}} the previous reply, but figured going one more deep wasn't too problematic. Nonetheless I have outdented this reply to start fresh. ;-) Dmehus (talk) 21:27, 5 October 2020 (UTC)[reply]

Thanks again @Dmehus:. Interesting Template {{outdent}} I will check that out, Lily (Lilypond Wiki · talk and I will listen · my little garden ) 02:55, 6 October 2020 (UTC)[reply]
Yes check.svg No problem. Dmehus (talk) 14:25, 6 October 2020 (UTC)[reply]

Exporting my wiki

Depending on my association request, I may have to move the wiki to a private server. Is it possible to export a whole Miraheze hosted wiki including its pictures (jpg, pdf, svg...)

AMITRAM (talk) 10:00, 3 October 2020 (UTC)[reply]

@AMITRAM: Sorry to see you go :( You can export your wiki via Special:DataDump. Good luck with your wiki! Reception123 (talk) (C) 10:06, 3 October 2020 (UTC)[reply]
I don't intend to, and I hope I won't have to. But my association may request it.
I'm sorry to bother you with this, but all my pictures will be exported along with all the wiki content (pictures and theirs old versions of one file ?) ? And then I can import them into my private server ?
AMITRAM (talk) 10:09, 3 October 2020 (UTC)[reply]
@AMITRAM: Yes, actually, Reception123 had not too long ago told me what the purpose of each of the three types of dumps was. XML includes all the public, non-suppressed revisions of your wiki, an image backup includes your uploaded files and images, and a ManageWiki backup includes your configuration settings from ManageWiki. I should also add that by "public," I mean the public revisions accessible to your wiki's audience (i.e., for your private wiki). Hope this helps. Dmehus (talk) 10:32, 3 October 2020 (UTC)[reply]
Thanks to you all for your answers,
I have a specific issue, I've added a new member with a read-only permission yet he can still modify existing pages, how can I prevent him from doing so ?
AMITRAM (talk) 11:27, 3 October 2020 (UTC)[reply]
@AMITRAM: You can modify any permissions by going to Special:ManageWiki/permissions. For example, if you want 'members' not to be allowed to edit, you would uncheck the edit right from their group. Reception123 (talk) (C) 13:41, 3 October 2020 (UTC)[reply]
I went to Special:DataDump for this wiki and I didn't find any options for generating the dump. Is this restricted to administrators? Is the dump compatible with Special:Import? Тишина (talk) 18:12, 10 October 2020 (UTC)[reply]
@Тишина: Yes, Special:DataDump requires the view-dump, generate-dump, and delete-dump to use. By default, as seen here, it is assigned to the sysop user group when wikis are created (though local wiki bureaucrats can change this). There are three types of dumps, one contains the wiki's ManageWiki configuration settings, one contains the wiki's locally uploaded files and images, and the final one is a public XML export of all publicly available information (i.e., non-oversighted revisions, no private user settings, no user IP addresses, etc.). This latter dump is compatible with Special:Import, as it generates a similar XML file that Special:Export does. Note, though, that there is a 250 MB file size limit on wiki imports. Larger imports require a Phabricator ticket. As well, if you are importing a large number of templates and modules with a number of revisions, but which are below that threshold, you may time out and receive a 503 backend fetch error, so you should avoid that and request on Phabricator. Also, you can login to Phabricator using the "click here to login with MediaWiki" button, and it'll use your wiki login credentials to create an account for you. Hope this helps. Dmehus (talk) 21:44, 10 October 2020 (UTC)[reply]
@Тишина: If you want to test the administrator tools, such as Special:DataDump, you can head over to Public Test Wiki, and request permissions, taking care to read its policies and stating a reason for wanting to test the tools. Though less common, you can test the generation of an XML dump of that wiki. Dmehus (talk) 21:46, 10 October 2020 (UTC)[reply]

Working with Mediawiki Media Viewer


I've installed this feature on my wiki so as to make things easier for my users, yet I have two specifics issues :

AMITRAM (talk) 13:42, 5 October 2020 (UTC)[reply]

//// Maybe these should this better be placed on phabricator as tickets ? //// — Preceding unsigned comment added by AMITRAM (talkcontribs) 17:23, 5 October 2020 (UTC)[reply]
@AMITRAM: Phabricator is really for reporting bugs, known issues, configuration errors, feature requests, and security-related issued, so I probably wouldn't go there. If I knew the answer to your problem, I'd answer, but I'm not quite sure what you mean by "Media Viewer" or what the specific issue is. Perhaps you can clarify this a bit? You could also try connecting with us on Discord (you can even verify your wiki account using OAuth once you join our server), or IRC at #miraheze connect. Note that if you join the IRC channel using the Freenode webchat, your IP address will publicly visible in our IRC logs, so you may wish to use the freemium IRC Cloud, which includes a complimentary IRC cloak upon registering for an account. Hope this helps. Dmehus (talk) 21:21, 5 October 2020 (UTC)[reply]
@Dmehus: Thanks, I'm joining IRC to ask for help.
AMITRAM (talk) 08:33, 8 October 2020 (UTC)[reply]
@AMITRAM: Okay, sounds good. I personally recommend using IRCCloud for connecting to the Freenode IRC network, as it includes a complimentary IRC cloak to mask your IP address. Thanks for the update! Dmehus (talk) 14:28, 8 October 2020 (UTC)[reply]

Switch default for recent changes to 45 days

When I see a new wiki I didn't know of, I don't know if that wiki is well maintained or not. And at first sight I don't know the level of activity, so I check Special:Recent changes. The dormancy policy makes it easier to know if wikis have more than 45 days of inactivity, but between 30 and 45 is difficult to know if the wiki is active or not. For this reason I propose to switch the default number of days in recent changes from 30 to 45 days, so people can see in an instant if that wiki is active or not without that range of doubt between 30 and 45 days.
Avengium (talk) 20:31, 6 October 2020 (UTC)[reply]

From a Sysadmin side, change is simple but let's leave for 5-7 days to allow comment. Please note that this will affect all wikis that haven't set a custom value. ~ RhinosF1 - (chat)· acc· c - (on) 20:39, 6 October 2020 (UTC)[reply]
@RhinosF1: Can't we just change this on Meta only, and not for all wikis? That would be my preference. I'd have no objection to increasing the RC value on Meta only to 45 days, or even 60 days really. Dmehus (talk) 21:02, 6 October 2020 (UTC)[reply]
It wouldn't solve the issue presented to us by doing that. ~ RhinosF1 - (chat)· acc· c - (on) 21:55, 6 October 2020 (UTC)[reply]
@RhinosF1: I wondered that originally, too, but the issue is only related to Meta. Unless I've misunderstood something, I believe what @Avengium: is referring to is Meta's RecentChanges, and being able to monitor pages like requests for adoption, Gazetteer of wikis, etc., over a 45 day period instead of the current maximum of 30, no? Dmehus (talk) 22:08, 6 October 2020 (UTC)[reply]
Proposer does say the proposal concerns wikis he has just become aware of (therefore, other than Meta).
I welcome a change to 45 or 60. I maintain, a programming reference site, but edit it only when an issue is called to my attention. It would be helpful to go back further to verify that no vandalism has occurred during an extended absence. Right now, 30 days is not just the default but the longest interval presented on the form (though you can request a longer interval by composing your own URL). Spıke (talk) 22:58 6-Oct-2020
@Spike: (and @RhinosF1: as well, really)...yes, I know that @Avengium: said this is in regards to "wikis he has just become aware of," but where would Avengium be learning of new wikis from a centralized feed other than on Meta? Thus, I believe changing this setting on Meta is all that's required at this point. Since, as a Consul on TestWiki, I can change this RC maximum setting in this section of ManageWiki, it holds that any bureaucrat should be able to make this change on the same page on their wiki, such as this section of ManageWiki on rfobasicwiki. I just think we should avoid changing something globally unless absolutely required, as I know local control over such things is important. Dmehus (talk) 23:08, 6 October 2020 (UTC)[reply]
Have just made the change on my wiki, which solves my particular problem. I agree with not changing global things, though local wiki bureaucrats retain ultimate local control. I continue to believe that what proposer was requesting is an easier way to gauge inactivity on wikis other than Meta. Spıke (talk) 23:42 6-Oct-2020
The question was because they wanted to be able to see how close a wiki was to meeting the inactivity policy and being closed from recent changes which you can't based on the default. Changing the default for what it's worth will not stop any wiki changing it back or to whatever value they want (up to 180 days but we can happily make that higher if I a wiki needed it. It just seemed a sensible number to set it to when I fixed a bug with a wiki having an invalid value). ~ RhinosF1 - (chat)· acc· c - (on) 06:35, 7 October 2020 (UTC)[reply]
My concern is with the default amount of days on personal wikis that are new to me. And is related with the dormancy policy and with the inactivity period of wikis before they obtain some inactivity banner that makes them available on a request for adoption. Avengium (talk) 09:32, 7 October 2020 (UTC)[reply]
What do you think about raising the default number of days in Recent Changes to ease checking wikis for adoption and wikis who are close to inactivity due to dormancy policy? This kind of wikis don't have local admins or are absent. So I can't count on the activity of a local admin to check the manage setting for RC on their side. Is best if sysadmins can view the amount of time left for adoption as global admins or if a common user can check the recent activity in the last 45-60 days. @Dmehus: , @Spike: , @RhinosF1:.
Avengium (talk) 23:46, 7 October 2020 (UTC)[reply]
@Avengium: It's a bit confusing on how you are monitoring inactive wikis. Are you monitoring RecentChanges on Meta at requests for adoption, or do you mean that you're monitoring wikis' Special:RecentChanges where the wikis have very low activity to see when they go inactive? If the former, I think we can change this setting on Meta only. If the latter, I'm okay with this as there's a valid use case, but my preference would be for the default maximum RC setting to be set to 60 days (the period by which non-exempt wikis would become closed and thus eligible for adoption, well public wikis that is). I would also like to invite @John, NDKilla, and Void: to comment on whether this is setting change is within system administrator or steward purview. Though somewhat technical in nature, in which I can see the former having jurisdiction here, it's also related to procedural setting within the purview of all wiki bureaucrats, so I can also see community-elected stewards having primary jurisdiction here. Dmehus (talk) 23:57, 7 October 2020 (UTC)[reply]
@Avengium: On the other hand, why not just check the wikis you monitor and patrol within the thirty day timespan to ensure they have activity within a 30 day timespan? After all, if you perform an edit or log action within that thirty day timeframe, you'll be a bit ahead of the game and prevent the wiki from becoming inactive anyway (i.e., the inactivity "clock" will be reset). Dmehus (talk) 00:01, 8 October 2020 (UTC)[reply]
Screenshot - Metawiki - Modified RecentChanges - 7 October 2020.png
A useful proposal is to change the default setting for $wgRCLinkDays, the options for number of days that the form in RecentChanges presents, as I did yesterday on rfobasic as instructed above (pictured). Avengium could get what he wants with one additional click, and local sysops would be less perturbed that their procedure was being upended. Spıke (talk) 00:03 8-Oct-2020
@Spike: Yeah, I tend to agree. I realize Avengium may not be a local bureaucrat on the wikis he monitors, and said wikis may not have active bureaucrats; however, in such cases, @Avengium: could also hold a local election requesting bureaucrat rights on said wikis, consistent with any local wiki policies as may exist (or global customs and conventions where none exist), and a steward would be able to assess the election after a reasonable period of in absence of an active bureaucrat. If we it's still desired to change this globally, I think this warrants a fuller community discussion, either a global RfC or, better yet, a full global community proposal on this noticeboard that articulates clearly both the need and rationale for the change. This would allow others to suggest potential workable alternative proposals for ideas which had not been brought to light. Dmehus (talk) 00:30, 8 October 2020 (UTC)[reply]
I think Spike's idea is probably quite good. I think the default max is 30 days but it's slightly less user experience wise intrusive. ~ RhinosF1 - (chat)· acc· c - (on) 06:42, 8 October 2020 (UTC)[reply]
@RhinosF1: Just to be clear, Spike's idea is very similar to the idea I expressed above, and involves making no global change to the default max RC age? To add to what Spike and I said above, Avengium can always request a steward change the default maximum RC age setting in any wiki(s) where the bureaucrats are inactive in responding to his request, as it's quite a minor change. So this would have the effect of allowing Avengium to still monitor RCs up to 45-60 days on wikis he monitors while at the same time not making any global change. Dmehus (talk) 14:24, 8 October 2020 (UTC)[reply]
@Dmehus, RhinosF1, and Spike: I love the idea Spike suggested. Putting another number allows people (not just me) to check other time frame, but keeping the same default as before. And local admins continue with their time frames. Is a win-win situation. I think we should keep the default the same and add another value to $wgRCLinkDays that is 180 days (like in the image Spike shared). I suggest putting that new number in all wikis that have $wgRCLinkDays as default. Avengium (talk) 19:07, 8 October 2020 (UTC)[reply]

──────────────────────────────────────────────────────────────────────────────────────────────────── As requested, now see Requests for Comment/Add a link on Special:RecentChanges to see last 180 days. Spıke (talk) 02:09 9-Oct-2020

@Spike: I have moved your good-faith RfC to this subpage of your userspace, as I feel that your proposal needs some clarification. As well, above, you said that you didn't feel changing the default RC value for all wikis was necessary in this case, since, as I said above, stewards could simply change the default RC value on any wikis @Avengium: monitored and where the local bureaucrats were inactive. Moreover, though global in nature, this is a relatively modest global change, so I'm not sure a full RfC is indeed needed. We could simply utilize this discussion and agree on a proposal to move forward with in a new sub-section of this discussion, on which we'd all vote. Thanks. Dmehus (talk) 02:19, 9 October 2020 (UTC)[reply]
An update for everyone (@Avengium, RhinosF1, and Spike:) in this discussion...I have followed up with Spike on his user talk page by way of this discussion, mainly to (a) seek clarification on his original proposal, (b) gain insight as to why 180 days was decided on, (c) obtain clarity on whether more than proposal (an RfC) might make sense, and (d) determine whether it makes the most sense to move forward with the one community proposal in a new sub-section of this community noticeboard discussion. Dmehus (talk) 03:28, 9 October 2020 (UTC)[reply]
Can't @Avengium: just go to their global preferences and change their default recent changes days just for themselves? I don't see why this would need a change to a global setting. K599 (talk) 14:40, 9 October 2020 (UTC)[reply]
I could do it @K599:, But I hadn't thought about it until now. About Spike's proposal, I think is useful for everyone, not just me. But I realize that there are several ways to achieve the same result. Part of this is because I am less involved in the wiki environment (and I use user friendly mechanics), and had not thought of the option that my global preferences could overlap and replace the default way of showing recent changes. Avengium (talk) 15:04, 9 October 2020 (UTC)[reply]
@K599: Yeah, as @Avengium: mentioned, that's exactly what ended up being suggested in our conversations on the Miraheze Discord server. While I'm not necessarily opposed to changing the default RC setting for everyone as I do agree with Avengium that MediaWiki is not all that intuitive, especially when it comes to one's preferences and global preferences, I think we should be cautious at changing settings globally for everyone, overriding local wikis' discretion and autonomy, where only one or a few users may not be aware of other workarounds. I think what this discussion elucidated for us is that we could do well to create a FAQ question for Avengium's problem described above, and then provide recommended solutions for both wiki users and wiki owners. Dmehus (talk) 20:32, 9 October 2020 (UTC)[reply]

Request for Interwiki

I need to show some page from to our visitors in helping page. And I find that the transclude function of the Interwiki can do it easily. So I request Interwiki administrators to:

  • add some Interwiki prefixes:zw and zhwiki. The url is the same as zhwikipedia.
  • add the transclude function to mw and mediawikiwiki.

Thank you.

-开炸弹车 (talk) 03:34, 7 October 2020 (UTC)[reply]

@开炸弹车: I have no problem with this, but just need which wiki(s) you want me to add those additional prefixes for Chinese Wikipedia and also add the transclude flag for On which wiki(s) do you want these changes/additions done? Thanks. Dmehus (talk) 13:48, 7 October 2020 (UTC)[reply]
@Dmehus: Both in -开炸弹车 (talk) 14:05, 7 October 2020 (UTC)[reply]
@开炸弹车: Thanks. This is now Yes check.svg Done. Note that in my local interwiki table log summaries, I missed adding the meta prefix to link to this diff on Meta, but suspect that's not too big of a deal. Also, I originally misread your request for the zw prefix as zh, which added it as the interlanguage prefix. This may have been what you wanted anyway, but if you still want zw added, let me know, provided, of course, that's not a valid language code for another language in which case, it probably won't work for being added to the local interwiki table versus the local interlanguage interwiki table. Hope that helps. Dmehus (talk) 14:26, 7 October 2020 (UTC)[reply]
@Dmehus: No problem. -开炸弹车 (talk) 23:45, 7 October 2020 (UTC)[reply]

Request A Wiki "WearYourDictionary"

I would like to create a wearable dictionary aggregator wiki. A competitive marketplace for artists to show of the designs of dictionary entries. — Preceding unsigned comment added by WearYourDictionary (talkcontribs) 18:35, 7 October 2020 (UTC)[reply]

@WearYourDictionary: Firstly, (Please sign your posts on talk pages by using four tildes like this: ~~~~.)
Secondly, please go back into your original wiki request by adding to your existing description, answering the information requested of your request. Thanks. Dmehus (talk) 18:39, 7 October 2020 (UTC)[reply]

Like Special:GlobalRenameRequest

I want to make my local wiki like Special:GlobalRenameRequest, Special namespace's request page. How to make? Thanks. Gomdoli4696 (talk) 01:49, 8 October 2020 (UTC)[reply]

@Gomdoli4696: I believe that special page can only be accessed on Meta. Can you clarify how you mean? You want to make a new separate special page? You could possibly try the PageForms extension, but not sure if that's what you're after. Dmehus (talk) 02:33, 8 October 2020 (UTC)[reply]
Yeah, I want to make a new separate special page. Gomdoli4696 (talk) 02:56, 8 October 2020 (UTC)[reply]
@Gomdoli4696: That involves some php coding expertise, and would then likely involve you submitting that special page to either Wikimedia's Phabricator or Miraheze's Phabricator, depending on which extension it's related to. This MediaWiki help page provides some instruction on the mechanics involved in creating a special page. Hope this helps. Dmehus (talk) 14:31, 8 October 2020 (UTC)[reply]
To add to (and perhaps clarify) what @Dmehus: said, you would have to create a MediaWiki extension in order to have your own kind of special page. This does indeed require PHP developing skills. In addition, the extension would have to be secure in order to pass our security review process which is mandatory for every new extension excluding ones used by the Wikimedia Foundation. Reception123 (talk) (C) 08:26, 10 October 2020 (UTC)[reply]

How do I change the theme of my wiki?

So, I want to turn Dream Fiction Wiki green, but how do I do it? — Preceding unsigned comment added by FlegSlaviraheze (talkcontribs) 08:30, 9 October 2020 (UTC)[reply]

@FlegSlaviraheze: First, welcome to Miraheze, and to Meta. Second, (Please sign your posts on talk pages by using four tildes like this: ~~~~.). Third, to answer your question, your wiki's style and apperance is done through Cascading Style Sheets, principally in your wiki's MediaWiki:Common.css interface file. You want to start with this very basic answer to this question at: FAQ#How do I give a distinctive style to my wiki?. Beyond that, you could use your Discord account to join our Discord server, where a number of CSS experts exist to provide one-on-one support. You can also ask on IRC, at #miraheze connect; however, I do recommend using IRCCloud as your IRC client, as they provide a complimentary IRCCloud IRC cloak upon registering for an account, as your IP address would otherwise be available in an unmasked format. Hope this helps. Dmehus (talk) 13:36, 9 October 2020 (UTC)[reply]

My miraheze

Can I get help I'm new here? Hrvcfr (talk) 01:35, 11 October 2020 (UTC)[reply]

@Hrvcfr: Firstly, welcome to Miraheze, and to Meta wiki. You're off to a great start by signing your posts with four tildes (~~~~). Second, what do you need help with? Dmehus (talk) 01:44, 11 October 2020 (UTC)[reply]
You can start at FAQ. If you have more questions that aren't covered there then you can ask. Тишина (talk) 01:45, 11 October 2020 (UTC)[reply]
I need ppl to help my miraheze Hrvcfr (talk) 01:46, 11 October 2020 (UTC)[reply]

My miraheze

Come join criminal world if you are interested in crime topics.

Hrvcfr (talk) 01:58, 11 October 2020 (UTC)[reply]

@Hrvcfr: You should wait until your wiki has been approved and created. Also, I note you've created two threads with the same section header. Your section header should concisely describe your topic on the noticeboard. Thanks. Dmehus (talk) 02:06, 11 October 2020 (UTC)[reply]
Sorry Hrvcfr (talk) 02:06, 11 October 2020 (UTC)[reply]
No problem. Dmehus (talk) 02:07, 11 October 2020 (UTC)[reply]

Scary transclusion is not working as expected

Hi altogether, in this topic I asked for an interwiki prefix. The prefix is working fine, but it seems to me that scary transclusion is ignoring all includeonly/onlyinclude/noinclude tags. Here is a template on my wiki: Transclusion, what it looks like in the same wiki and here an example of scary transclusion in an other wiki. Is this a bug or a feature? Am I missing something? Is there anybody out there who is using scary transclusion? Thank you for your support, Lily (Lilypond Wiki · talk and I will listen · my little garden ) 07:39, 11 October 2020 (UTC)[reply]

@Lily: I'll have to look into whether scary transclusion ignores the includeonly and noinclude tags. It's definitely possible this is either a known issue or a bug. In the mean time, you might try searching Wikimedia Phabricator as if it's a known issue or bug, that's where it would be tracked as it is a so-called upstream issue (outside of Miraheze's own maintained source code). In the mean time, what I might suggest instead is to essentially use it for very basic pages and templates. For example, you might create a "clean code" version as a subpage of the existing page, without such tags or a several levels deep of transcluded templates. As well, it is after all called scary transclusion for a reason. As just one example, see this example revision in my TestWiki sandbox in which I attempted to transclude the Special:GlobalUsers special page (note that this special page does not have local transclusion built into it, although I was able to transclude the page using scary transclusion, with, as you'll see, unexpected results). Hope this helps. Dmehus (talk) 23:10, 11 October 2020 (UTC)[reply]
@Lily: Indeed, it seems this is actually a long-standing, and still open, bug, as seen in this Wikimedia Phabricator ticket. Dmehus (talk) 23:17, 11 October 2020 (UTC)[reply]
@Dmehus: thank you so much for your support. I had already the idea of adding a subpage with clean code but this does make life not really easier. With this bug scary transclusion is more or less useless for my purposes, Lily (Lilypond Wiki · talk and I will listen · my little garden ) 06:27, 12 October 2020 (UTC)[reply]
@Dmehus: I have tried the method with clean code in a subpage of the template and performed some experiments. I could not find a way to pass parameters; compare "normal" transclusion with parameters with scary transclusion with parameters. This fact restricts the usability of scary transclusion to templates without parameters. Maybe there is a way and I just could not figure it out, Lily (Lilypond Wiki · talk and I will listen · my little garden ) 08:49, 12 October 2020 (UTC)[reply]
@Lily: Considering mw:Manual:$wgEnableScaryTranscluding, maybe {{raw:lily:template name}} might work with parameters. K599 (talk) 16:59, 12 October 2020 (UTC)[reply]
Also, having done some tests, it seems like using "raw:" works with "noinclude" and "includeonly" tags correctly. K599 (talk) 19:05, 12 October 2020 (UTC)[reply]
@K599: thank you so much, raw: does the trick! Lily (Lilypond Wiki · talk and I will listen · my little garden ) 07:13, 13 October 2020 (UTC)[reply]


You can test beta Twinkle! Thanks! Gomdoli4696 (talk) 09:17, 11 October 2020 (UTC)[reply]

@ChipWolf and Gomdoli4696: Thank you both for your work in importing that user script version of Twinkle on Miraheze. That will be helpful, and more streamlined, for users than setting up and installing the MediaWiki gadget version. I personally try and avoid the Twinkle templates, as I find them too formulaic and imperfect. However, Twinkle does have some very useful features, notably the pseudo-rollback feature "restore this revision." Dmehus (talk) 22:59, 11 October 2020 (UTC)[reply]

Cross-wiki contributions

We can view Wikimedia project's cross-wiki contributions, Then how to view miraheze's cross-wiki contributions? Thanks. --Gomdoli4696 (talk) 22:53, 11 October 2020 (UTC)[reply]

@Gomdoli4696: We would love to be able to offer the global user contributions tool on Miraheze; however, it's very resource intensive in that every query of a user's global contributions is a query of every database for every wiki to which the user has attached their account. Hopefully, we'll be able to offer it in the future, but there's no timeline for such an offering. Hope that helps. Dmehus (talk) 22:56, 11 October 2020 (UTC)[reply]
Ah, ok. --Gomdoli4696 (talk) 23:11, 11 October 2020 (UTC)[reply]


Could crimeworld be added to the list??? Ty Hrvcfr (talk) 06:58, 12 October 2020 (UTC)[reply]

@Hrvcfr: Hi, I have just reverted last time because your wiki was not created, but you can add it now ! HeartsDo (Talk || Global || Wiki Creator) 07:05, 12 October 2020 (UTC)[reply]
How?? And thank you. Hrvcfr (talk) 07:08, 12 October 2020 (UTC)[reply]
@Hrvcfr: You can add it when you did last time (depends of the category who are your wiki), and for create a link to your wiki, you can use the magic interwiki word [[mh:]] (for example for your wiki, this would be [[mh:criminals|Criminals World]]) HeartsDo (Talk || Global || Wiki Creator) 07:21, 12 October 2020 (UTC)[reply]
Ty Hrvcfr (talk) 07:26, 12 October 2020 (UTC)[reply]
@Hrvcfr: Np, you can maybe a little expand your description, but for the rest is OK :). HeartsDo (Talk || Global || Wiki Creator) 07:33, 12 October 2020 (UTC)[reply]

──────────────────────────────────────────────────────────────────────────────────────────────────── Could someone please get the word out for the wiki I created??? Ty Hrvcfr (talk) 00:19, 14 October 2020 (UTC)[reply]

Wiki community project script

I made a script that will display banners for wikis and provide a list of links at the bottom of the page for other wikis that have interesting topics or already have content on them.

Тишина (talk) 19:23, 12 October 2020 (UTC)[reply]


How to set? --Gomdoli4696 (talk) 23:21, 12 October 2020 (UTC)[reply]

@Gomdoli4696: Please use Special:GlobalPreferences. The first column represents whether to set that specific setting globally; the second column, to the first's immediate right, represents whether to enable that specific function or setting. In Special:Preferences, for settings you've set globally, those settings will now be greyed out unless you set a local exception on that wiki. Hope that helps. Dmehus (talk) 01:49, 13 October 2020 (UTC)[reply]
I was mistaken. Sorry. --Gomdoli4696 (talk) 04:59, 16 October 2020 (UTC)[reply]


Looking for more people to contribute to my wiki. Any ideas? It's -- Iron Sword 22 (talk) 01:18, 14 October 2020 (UTC)[reply]

Multilingual glossary ?

Hi, I started translating some pages of this Meta wiki into French.

Q: is there any multilingual glossary here that we could use to ensure homogoneous and consistent translations? Example: (en) e-mail address -> (fr) adresse e-mail or adresse courriel ? Gerdami (talk) 07:09, 14 October 2020 (UTC)[reply]

@Gerdami: That is an interesting idea, do you know how the Wikimedia Foundation (for example their Meta wiki) deals with this? Maybe we could also use their method. Reception123 (talk) (C) 08:22, 14 October 2020 (UTC)[reply]
I have no idea, sorry Gerdami (talk) 09:51, 14 October 2020 (UTC)[reply]
Actually there is one at mediawikiwiki:Manual:Glossary that is currently translated into 3 other languages. Gerdami (talk) 11:51, 14 October 2020 (UTC)[reply]
@Gerdami and Reception123: Thank you for suggesting this, Gerdami, with your question. That latest interwiki link is to the MediaWiki software manual, so wouldn't be a specific Wikimedia standard or practice. I would think the common sense way to handle this would be a Meta Wiki style guide (a Miraheze Meta Manual of Style, if you will), with a specific section focused on translations. Definitely not opposed to such an idea, but would be a rather large undertaking. As well, if it becomes too comprehensive in other areas of writing, it may encourage users to view that as a policy with little flexibility. I do like to follow stylistic conventions in some ways, but moreso for technical reasons than grammatical or vocabulary-type reasons. Even in English, we have some pages that no doubt use certain British or Canadian English spellings intermixed with U.S. English. Ideally, we should use a consistent English variation on a given page, but any WikiGnome can correct these as they see them. So, I would just say, go with whatever you prefer. Someone may prefer something else in the future, so it could get changed. If two French translators disagree on something, they can just discuss it on the talk page (though preferably not the /fr language subpage of the given talk page). Hope that helps a bit? Dmehus (talk) 14:48, 14 October 2020 (UTC)[reply]
@Dmehus and Reception123:, the interwiki link I provided was just an example. If you agree I could start making a Help:Glossary page (I think it would be a good location) in English with the terms I find relevant while translating some existing pages into French, for example from the FAQ page. These terms could link to existing pages. Gerdami (talk) 18:15, 16 October 2020 (UTC)[reply]
@Gerdami: I think that's not a bad location for the final page, but I'm not sure what this would look like, so I'd rather suggest using a subpage(s) of your Meta userspace for now, and we can always move the page into Help: namespace and/or history merge in the earlier revisions from your page(s) as required. Dmehus (talk) 18:19, 16 October 2020 (UTC)[reply]
@Dmehus: Good suggestion. I will start that way. Gerdami (talk) 07:45, 17 October 2020 (UTC)[reply]

Some problems about using out image

Oh, I wanted to show forum users' avatars in the main page automatically. It seems to be easy—all of forum users' avatars are in, so I only need to show the image of as a out image. Then I looked up and enabled $wgAllowImageTag. I have known the setting will be invalid in Mediawiki 1.35+ so I also enabled $wgAllowExternalImages.

After that, I used two forms – and <img src="" />.But to my surprise, there was only an icon of a damaged image and the avatar was not showed.

I also used widgets, but it was the same end as that two forums. I have tried other image urls, a few of them was success.

I seem to have found a problem - almost every out things such as out images, out js especially hosted in China things (for example China-cdn js) can not work on Miraheze. But in other wiki they can. The same code in zhmoegirlpediain my wiki(NMFWiki)

Why? If some settings are controlling it?

Thanks, --开炸弹车 (talk) 13:25, 17 October 2020 (UTC)[reply]

@开炸弹车: Inspecting the console shows CSP blocking "", so you would need to open a Phabricator task to add that to the CSP whitelist. K599 (talk) 19:41, 17 October 2020 (UTC)[reply]

Local interwiki request

I'm one of the admins at nssports and I'd like to request this as a local interwiki:

I'd do it myself but I don't think any of our admins has made 500 edits yet. Thanks for the help and I'm happy to address any questions. Kelssek (talk) 22:53, 17 October 2020 (UTC)[reply]

@Kelssek: The 500 edit requirement for local interwiki administrator, as far as I am aware, doesn't seem to be enforced. All that's required is that you be a local bureaucrat on your local wiki. Nevertheless, I'll add this for you. Not a problem. Do you need either the forward or transclude flags enabled? Dmehus (talk) 23:04, 17 October 2020 (UTC)[reply]
Yes check.svg Done without the forward and transclude flags, but can always be changed should the need change. Dmehus (talk) 23:08, 17 October 2020 (UTC)[reply]
This works, thanks! --Kelssek (talk) 23:49, 17 October 2020 (UTC)[reply]
No problem. Dmehus (talk) 00:08, 18 October 2020 (UTC)[reply]

Gadget Cat a lot

Is it possible to have this feature "Cat a lot" in my Wiki ?

AMITRAM (talk) 17:08, 18 October 2020 (UTC)[reply]

@AMITRAM: Yep. Gadgets, unlike extensions, don't require security reviews or approvals by system administrators to install. I'm not that familiar with that gadget's installation procedures, but speaking just generally, it involves importing the JS and CS files into your wiki's MediaWiki: namespace, then updating MediaWiki:Gadgets-definition to reference the gadget and its file, configuration variables, and the like. @Lakelimbo: recently installed it on his wiki, so may be able to offer some assistance. Dmehus (talk) 17:16, 18 October 2020 (UTC)[reply]
@Dmehus: Thanks, I'm gonna ask him.
Do you know where I can't get help for PDF files support ? I can't get thumbnails for this file format.
AMITRAM (talk) 17:50, 18 October 2020 (UTC)[reply]

My miraheze vanished

Travelguidesworld is gone. Plz fix. Hrvcfr (talk) 17:38, 19 October 2020 (UTC)[reply]

@Hrvcfr: It's not gone. @Reception123: just fixed the URL, as I told you in the wiki request. Additionally, I should also note that this was tracked on Phabricator as #T6324. You can now use travelguidesworld as your URL. Dmehus (talk) 17:46, 19 October 2020 (UTC)[reply]
ty doug. Hrvcfr (talk) 17:50, 19 October 2020 (UTC)[reply]
No problem. Dmehus (talk) 17:54, 19 October 2020 (UTC)[reply]

Local interwiki administrator request

Hi, I request local rights for interwiki admininstration for my wikis Lilypond Wiki · my little garden · Regionalbahn Weinviertel (although I said I would not need them, maybe this rights come in handy for some purposes), thank you very much Lily (Lilypond Wiki · talk and I will listen · my little garden ) 04:45, 21 October 2020 (UTC)[reply]