Community portal/Archive 26

From Miraheze Meta, Miraheze's central coordination wiki
Archive This page is an archive. Do not edit the contents of this page. Please direct any additional comments to the current talk page.

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

Prefix (iw_prefix):dw

Url (iw_url):$1


Prefix (iw_prefix):hs

Url (iw_url):$1.html


Prefix (iw_prefix):hsstudy

Url (iw_url):$1


Prefix (iw_prefix):dcm

Url (iw_url):$1


Prefix (iw_prefix):dcmeta

Url (iw_url):$1


Wiki to be (

Prefix (iw_prefix):hs

Url (iw_url):$1.html


Prefix (iw_prefix):hsstudy

Url (iw_url):$1


Prefix (iw_prefix):dcm

Url (iw_url):$1


Prefix (iw_prefix):dcmeta

Url (iw_url):$1


Thanks. @Diamochang - talk | email me - 01:19, 18 December 2021 (UTC)

@Diamochang: This is  Done at this time, you can visit diamodocswiki and diamowikiwiki for the logs. Ugochimobi (talk) 21:47, 18 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 & D (talk) 10:44, 19 December 2021 (UTC)

@Ora & D: What errors are you facing? Agent Isai Talk to me! 10:51, 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.
Fatal exception of type "LogicException".
2. Fatal exception of type "Wikimedia\Rdbms\DBTransactionError". Ora & 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 & 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 YellowFrogger (Talk Edits) 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)

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?  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.  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) YellowFrogger (Talk Edits) 19:32, 16 December 2021 (UTC)
Yes and Sure. I also like RandomPage on Wikis since start :-p
How can this proposal get picked up? --ZBlace (talk) 17:53, 24 December 2021 (UTC)
@ZBlace It's addicting to do that. And why are you wanting to change? The current one looks pretty good, and I don't know where you can make the proposal either, if it's on the Miraheze server on Discord, with RfC or on SN or Meta:AN (administrators noticeboard , interace admins can change MediaWiki:Sidebar), so it would be nice if you send there. --YellowFrogger (Talk) 19:50, 24 December 2021 (UTC)
Reasoning? Check my #2post in thread. --ZBlace (talk) 20:41, 24 December 2021 (UTC)
I like the spirit here, of using fewer words to convey the concepts. Especially in the noticeboards area, spelling out 'noticeboard' is not really necessary. I do think the 'adoption' wording should change, as it's no longer appropriate for what the page does (but that requires that the page is moved to a renamed version as well, an action that is still pending). I would pick bones with exact choices of words however, and would rather see it explored further if we can get confirmation that a Meta Admin would like to pursue this or raise this to a Meta RfC. Raidarr (talk) 00:48, 25 December 2021 (UTC)
@Raidarr thanks for positive feedback. I would also love to hear of any Meta admin now. --ZBlace (talk) 14:58, 25 December 2021 (UTC)
Raidarr, this is the shortcut. Good for lazy people looking for a shortcut like this and therefore redirection with these shouldn't be eliminated like Hose Keeping or maintenance, etc. And in response to the above user, admins (and even stewards) unfortunately get that way most of the time, but I don't think it needs to go to the point of a RfC --YellowFrogger (Talk) 15:15, 25 December 2021 (UTC)
I'm afraid I don't understand what you're referring to with this comment, except for the RfC bit. --Raidarr (talk) 15:49, 25 December 2021 (UTC)
I was quoting about what you talked about above (spirit of using abbreviated words), this is something from the template:shortcut --YellowFrogger (Talk) 02:19, 26 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 YellowFrogger (Talk Edits) 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 YellowFrogger (Talk Edits) 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 YellowFrogger (Talk Edits) 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 YellowFrogger (Talk Edits) 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 YellowFrogger (Talk Edits) 03:38, 22 December 2021 (UTC)


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:
  • 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 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:

  • 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

Source: --YellowFrogger (Talk) 22:44, 23 December 2021 (UTC)

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)
Please file a Phabricator task and we'll help you set it up after Christmas. All config files are public but we'll be happy to help you make the relevant changes and deploy it.
Side note: I'm not 100% sure why something that relies so heavily on setup by us is available for you to turn on. ~ RhinosF1 - (chat)· acc· c - (on) 09:35, 24 December 2021 (UTC)
I think the best way would be to let the bureaucrats configure this extension via ManageWiki or remove it from those available on ManageWiki. DecabristM (talk) 11:21, 25 December 2021 (UTC)
I fully agree that getting it in ManageWiki somehow needs to be done but we're unfortunately without our main developer at the moment and it's the middle of the festive season. ~ RhinosF1 - (chat)· acc· c - (on) 11:24, 25 December 2021 (UTC)
I sent a request to the phabricator. DecabristM (talk) 11:58, 25 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 : 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?  Anpang📨  11:49, 23 December 2021 (UTC)
Basically, yes. Darkrai18 (talk) 12:01, 23 December 2021 (UTC)
Something like this:
{| class="wikitable" style="margin-bottom:-1px"
! Header text !! Header text !! Header text
| Example || Example || Example
| Example || Example || Example
{| class="wikitable" style="margin-top:0px"
! Header text !! Header text !! Header text
| Example || Example || Example
| Example || Example || Example

Which is:

Header text Header text Header text
Example Example Example
Example Example Example
Header text Header text Header text
Example Example Example
Example Example Example
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.  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)

Hello, Darkrai18


{| class="wikitable" style="margin-bottom:-1px;"
! A partir de 2009!!
| '''''[[Fast and Furious (franchise)|Fast and Furious]]''''' || [[Gisèle Yashar]]

{| class="wikitable" style="margin-top:0;"
! A partir de 2016!!
| '''[[Univers étendu DC]]'''|| [[Wonder Woman (Univers étendu DC)|Wonder Woman]]

A partir de 2009
Fast and Furious Gisèle Yashar
A partir de 2016
Univers étendu DC Wonder Woman

Greetings. Hugo Ar (talk) 14:46, 24 December 2021 (UTC)

To add, if you want the width of the 2 tables to be matching, you can use 1 table:
{| class="wikitable"
! A partir de 2009!!
| '''''[[Fast and Furious (franchise)|Fast and Furious]]''''' || [[Gisèle Yashar]]
! A partir de 2016!!
| '''[[Univers étendu DC]]'''|| [[Wonder Woman (Univers étendu DC)|Wonder Woman]]

Which results in:

A partir de 2009
Fast and Furious Gisèle Yashar
A partir de 2016
Univers étendu DC Wonder Woman

Interwiki table

Could you please

  1. Add the prefix s to$1, and
  2. Delete the interlanguage prefix en,

In the Interwiki table of XComhghall Wiki?

Thank you very much. — XComhghall (talk) 22:35, 23 December 2021 (UTC)

@Ugochimobi: --YellowFrogger (Talk) 22:40, 23 December 2021 (UTC)
This is  Done, thanks. --  Joseph  TB  CT  CA  23:08, 23 December 2021 (UTC)


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 ( TalkAll 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)
@Bukkit: 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)

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 Raidarr and Agent Isai 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:

  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:
    1. 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):
      1. 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.
      2. 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.
      3. 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.
      4. 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.
      5. 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.
      6. If the user with the highest position disagrees, then again, try to have a full conversation with them.
      7. 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.
    2. 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:
      1. Creating pages on wikis that contain destructive criticism towards the wiki.
      2. Having any content on wikis that the wiki's staff members have stated that they do not want.
  3. 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:
    1. Negative pages about obscure users on the internet
    2. Pages about people who do not want a page about them (this does not apply to informative pages)

FatBurn0000 (talk) 02:28, 12 December 2021 (UTC)

"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. YellowFrogger (Talk Edits) 02:37, 12 December 2021 (UTC)
@YellowFrogger: 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 Tali64³ 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)
  1. Well, it should still be made more clear.
    1. This is why there are exceptions to this rule. Also this doesn't necessarily apply to just Fandom wikis.
    2. Fair enough.
  2. 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).

FatBurn0000 (talk) 22:03, 12 December 2021 (UTC)

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? YellowFrogger (Talk Edits) 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)
@Tali64³: 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 YellowFrogger (Talk Edits) 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)
  1. How is there "no issue" with it? There is no need for two versions of one wiki on the internet.
  2. What I am saying is, the pages should not suggest that due to the flaws, users should go against the wiki and possibly fork it.
  3. Fair enough.

FatBurn0000 (talk) 21:56, 25 December 2021 (UTC)

@FatBurn0000: There is no issue with it because while it's generally not a good thing, the community of editors around a particular topic isn't bound to a particular platform, and migration away from Fandom is a positive. Also, wikis don't have "owners", so you won't want to use that word in any proposals. — Arcversin (talk) 23:07, 25 December 2021 (UTC)
@Arcversin: There are exceptions in certain cases, but wikis should still not have duplicates anywhere unless it is truly necessary. If there is a fair enough reason to fork a wiki from another site, then again, exceptions can be made. FatBurn0000 (talk) 05:12, 26 December 2021 (UTC)
@FatBurn0000: Whether a wiki exists some other place on the internet isn't, apart from copyright, relevant to whether Miraheze will host a wiki. It might not be a good thing for communities to be split, but it's best for such situations to be sorted out by the communities themselves, via migration of community members, as opposed to external interference. For other Miraheze wikis, we have the fork provision of the Content policy, but for external wikis, we want to support communities getting out of places like Fandom. — Arcversin (talk) 16:08, 26 December 2021 (UTC)
@Arcversin: That still isn't a reason to duplicate a wiki. FatBurn0000 (talk) 21:38, 27 December 2021 (UTC)
@FatBurn0000: Then please explain your reasoning. — Arcversin (talk) 00:22, 28 December 2021 (UTC)
@Arcversin: My reason why I would like no wikis to be duplicated is because there is no need for more than one wiki about one topic. Most issues with wikis can be dealt with. FatBurn0000 (talk) 22:28, 28 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)

Request for overturn on Requests for Comment/Local IP Block Exemption

Problem with Tab

Hi there, I have created a "Tab" template for my pages. Problem, I would like the two ends to be rounded. However, this is only the case on one end. It is only rounded when my Tab has this shape:

|tab4=Capabilities and equipment

Either when it's staggered. My page link : My template link : Thanks in advance. Darkrai18 (talk) 11:35, 28 December 2021 (UTC)

The two ends are already rounded?
Or you mean all 4 corners to be rounded?
Then border-radius: (how much round)px should work <span style="display:inline-block;border:2px solid #bfff00;border-radius:8px;background-image:linear-gradient(to bottom right, #75ff75, #ffff80)"> Anpang📨  11:45, 28 December 2021 (UTC)
I'm talking about this : . I would like both ends to be rounded. Darkrai18 (talk) 11:58, 28 December 2021 (UTC)
Oh, then that I have no idea. Maybe an {{if: checking if the next one exists, if not set to rounded else not rounded and continue?
Like i have no idea....  Anpang📨  12:02, 28 December 2021 (UTC)
Thanks for trying. I'm waiting for more answers. Darkrai18 (talk) 12:32, 28 December 2021 (UTC)
This current theme of your wiki (mw:Skin:Monobook) is weird. But let's show the rounded borders preview CSS in the Vector theme:
border-top-left-radius: 2em; border-bottom-left-radius: 2em;
--YellowFrogger (Talk) 16:44, 28 December 2021 (UTC)
@Darkrai18: Your template is too complex for me to locate where to added Template:Border-radius in the other tabs. I have recreated it in a simpler design on the Test Wiki

Comments disabled

On 28 December 2021, we experienced severe performance issues globally which led to hours long downtime across all Miraheze wikis. While investigating the issue, we found that the commentlist API module (used by the Comments extension) was at fault as it used an excessive amount of resources whenever called and disabled it which seems to have put an end to the hours of downtime. However, as a result of the commentlist API module being disabled, the Comments extension cannot load comments. We apologize for the inconvenience and are actively working with the upstream developers of the extension to find a solution to this and to re-enable the API module as soon as possible.

In the meanwhile, we encourage you to consider alternatives to the Comments extension such as CommentStreams.

Please note that even though the API module is disabled, extensions that rely on Comments such as BlogPage are not affected and can be used as normal. Agent Isai Talk to me! 01:31, 30 December 2021 (UTC)

This here will have an impact mainly on Qualitipedia wikis, which often use these comments in their articles from what I see. --YellowFrogger (Talk) 01:37, 30 December 2021 (UTC)
This is correct; QP cannot reasonably just consider alternatives outright given the lengthy history of existing comments and the familiarity of their use, and losing history is indeed an impact. Then when switched a new history is made to wipe out the old one, or the plugin is switched back to result in a blind period for comment history since from what I understand the data is not compatible between them. I understand Miraheze is doing what it can, but in case of the above it does have an impact and it would be preferable to see a fix than to make an intermediate switch. --Raidarr (talk) 17:25, 30 December 2021 (UTC)
We migrated from CommentStreams... How difficult is to do a module that works and don't spent tons of resources? All the ones we have tried have performance issues or were difficult to comment... Thanks for resolving the downtime :) Jakeukalane (talk) 09:28, 30 December 2021 (UTC)
@Jakeukalane: Ultimately, it would depend on the upstream maintainer of the extension. A variety of factors come into play such as the complexity of the issue and whether the maintainer has the time to fix the issue. Because of that, we can't give you an ETA unfortunately, sorry! Disabling an API module isn't something we take lightly, it was an emergency measure taken to combat the hours of downtime we suffered yesterday. We are actively working with the maintainer to hopefully find a fix and restore functionality of the Comments extension. However, in the meanwhile, have you tried revisiting CommentStreams? The latest update gave it a facelift and it acts snappier, perhaps you may like that as a temporary alternative. Agent Isai Talk to me! 09:51, 30 December 2021 (UTC)
@Agent Isai: There was some confusion on my part. We migrated to CommentStreams but it is not working right now. That lead me to believe that we had the problematic comment extension. Greetings. Jakeukalane (talk) 12:55, 30 December 2021 (UTC)
I still have Miraheze taking 7 seconds to boot. DecabristM (talk) 16:49, 30 December 2021 (UTC)
@DecabristM: We still aren't perfect, but the actions taken did resolve the major downtime and improved things. User:Universal Omega/Sig  16:55, 30 December 2021 (UTC) |

A few concerns:

  1. When will this be back?
  2. What is CommentStreams exactly? Can I perhaps see a picture of what it looks like, since the MediaWiki page does not have one. I also would not recommend the Commentbox extension as it just edits the page which is quite annoying.
  3. I wonder if this is why it would not let me use the reply button to reply here, so I had to actually edit the page. Blubabluba9990 (talk) 17:42, 31 December 2021 (UTC)
I figured out what CommentStreams is, since I enabled it on my wiki. Blubabluba9990 (talk) 19:35, 31 December 2021 (UTC)

Bug with the article counter

Hey! I am using the article counter on the main page for readers. But despite the fact that there are already three articles on my wiki, the article counter has been displaying zero for several days. What could be the problem? DecabristM (talk) 13:02, 30 December 2021 (UTC)

@DecabristM: Please note that MediaWiki only counts pages with links to them so if a page doesn't have any other pages linking to it, it won't show up in Special:Statistics. Additionally, Statistics gets stuck every so often but gets manually refreshed every 2 weeks so if all your pages have links to each other than Statistics should show them once they get refreshed. Agent Isai Talk to me! 14:14, 30 December 2021 (UTC)
Yes, the problem was missing links. Thanks! DecabristM (talk) 16:45, 30 December 2021 (UTC)
As Agent Isai said above (even if the page is large and has the main namespace, if it doesn't have links, it doesn't count as articles). And, very small pages in the main namespace don't count as articles, but as pages. --YellowFrogger (Talk) 17:41, 30 December 2021 (UTC)

Problem with Tab, part 2

Hey there. The tab works very well, I'm very happy with it and I thank you all. I made some modifications but a problem persists: The text appears in white when I'm not on the main page, while I would like it to appear in black when I'm not on the said page. For example, here it appears in white and it's fine : But here it stays white : I would like it to be black. Do you have a solution? Thanks in advance. Darkrai18 (talk) 14:03, 30 December 2021 (UTC) Darkrai18 (talk) 14:03, 30 December 2021 (UTC)

Thank you very much, @PercyUK:. Darkrai18 (talk) 16:31, 30 December 2021 (UTC)

Issue with our wikis

Hi, I am one of the admins at the music reception wikis. Today we turned on video functionality for the best music wiki, and it appears it allows us to import videos properly. However, there is an issue. When the video is in, it says "Click to load content" which I do not know why, do you know why it appears this way and how we could fix it? FullInterTurn (talk) 22:33, 30 December 2021 (UTC)

I would expect an admin to talk about this first, but as I write this review no response. With that, I advise you then, as it is an error of an extension, to open a ticket in the phabricator so they will probably check if there is an error in the extension that is preventing such thing. And if you want, you can invite me to review the wiki. --YellowFrogger (Talk) 01:34, 31 December 2021 (UTC)

A bit of a problem

So I went to reply to the notice about the Comments extension being (hopefully temporarily) disabled, but when I clicked the reply button it took a few seconds to load and then displayed an error screen. I had to end up editing the actual page itself in order to reply. I do hope all of this is fixed soon because Miraheze is the last good wiki-hosting platform: Fandom has multiple problems, ShoutWiki is broken and inactive, Wikisite and EditThis run on ancient MediaWiki software and are inactive, and all of the other wiki hosts and wiki farms use other software and are pay-to-use. Blubabluba9990 (talk) 17:54, 31 December 2021 (UTC)

Oh and that isn't the only issue. When you click Save Changes, it takes like 30 seconds to save the changes. Blubabluba9990 (talk) 17:55, 31 December 2021 (UTC)
@Blubabluba9990: See the section above. Current comments extension is currently disabled due to a problem. --YellowFrogger (Talk) 22:36, 31 December 2021 (UTC)
I thought that was talking about the comments that can be created with the "comments" tag, not the thing that lets you reply to talk pages without editing the page. Or is it both. I'm confused. Blubabluba9990 (talk) 20:14, 1 January 2022 (UTC)
Specify what you are saying, you yourself stated that you are "confused". --YellowFrogger (Talk) 23:31, 1 January 2022 (UTC)
Which comment extension are you referring to? I assumed you were referring to the one that allows the <comments/> tag, but you are saying it is also that creates the reply button that allows you to reply to talk pages here, which means it is both extensions. Or are they part of the same extension. Blubabluba9990 (talk) 15:21, 2 January 2022 (UTC)
There is also the fact that for some reason it takes a minute to save edits. I do not know why that is. Blubabluba9990 (talk) 15:27, 2 January 2022 (UTC)

How do I post a template multiple times to the same page without "Pages using duplicate arguments in template calls"?

Is there a way around this? I want my user to fill out a form that selects some values and then have those values displayed simultaneously in two different spots within the page. Thanks for your help! ParentRatings (talk) 21:43, 31 December 2021 (UTC)

@ParentRatings: This is happening because you are using two parameters with the same name (duplicated). To avoid this, you should set the parameter and remove the duplicate, and leave only one. What is your wiki? Could you invite me to analyze the error? --YellowFrogger (Talk) 22:32, 31 December 2021 (UTC)

Interwiki changes for planetariumwiki

Please edit the following Interwiki prefixes.

Prefix: wikitroid
Metroid Wiki
Prefix: metroidwiki

No need for transclusion or forwarding on either. dross (tcg) 07:22, 1 January 2022 (UTC)

@Dross:  Done. Consult your local Special:Log/interwiki for more information. Agent Isai Talk to me! 07:31, 1 January 2022 (UTC)

Request for Feedback: Adding new default extensions

Fixing collapsible lists for the Sidebar template

Hello. I'm currently having issues with templating on my wiki. My current iteration of the Sidebar with collapsible lists template has the appearance of a normal Sidebar, but the collapsible lists function of the template doesn't seem to work, making it so that only the name of the list is shown without giving the option of expanding its contents. See this if you want a direct example of the issue, this for the template in question.

As far as I know, every template and module that is used by the Sidebar with collapsible lists template is a direct copy from Wikipedia or other wiki templates, so I'm stumped as to what could be causing the issue here. Sylepieus (talk) 16:33, 1 January 2022 (UTC)

Sylepieus, it seems that the wiki is private. Only members and administrators can view the pages. Greetings. Hugo Ar (talk) 16:01, 2 January 2022 (UTC)
Hugo Ar My bad, it should be fixed now. Appreciate the heads up. Sylepieus (talk) 20:11, 2 January 2022 (UTC)
Hola Sylepieus. La plantilla llama al módulo: Sidebar. Lo que veo en el resumen de edición del módulo es que al módulo lo importaste desde la Wikipedia en inglés. Pero, sin embargo, el código no es igual.
¿Puede ser esta la causa de que no funcione como lo deseas? ¿O puede ser que aun haya que incorporar otros módulos?
Translate by Google traductor
Hello Sylepieus. The template calls the module: Sidebar. What I see in the module edit summary is that you imported the module from the English Wikipedia. But nevertheless, the code is not the same.
Could this be the cause of it not working the way you want it to? Or could it be that other modules still have to be incorporated? Best regards and good start to 2022. Hugo Ar (talk) 20:50, 2 January 2022 (UTC)
Hugo Ar, changing over the Sidebar module seems to have fixed the collapsible lists part of the issue, though another issue seems to have cropped up as a result. Looking at this template for reference, it's trying to transclude Module:Sidebar/styles.css. It seems that the issue here now is that Module:Sidebar/styles.css is stuck in plaintext and doesn't function as code, even if it's directly copied from en Wikipedia. Do you know how I could fix this? Thanks in advance. Sylepieus (talk) 07:04, 3 January 2022 (UTC)
Sylepieus, You must activate Template Styles. To do this go to y and activate:       TemplateStyles and       TemplateStylesExtender. Greetings. Hugo Ar (talk) 12:09, 3 January 2022 (UTC)
Hugo Ar, I've turned on both the extensions as you've advised. There's some progress since the sample template now shows an error message in editing previews, but the issue with the code in Module:Sidebar/styles.css being in plaintext still persists. If it helps, the error message from the sample template says Page Module:Sidebar/styles.css must have content model "Sanitized CSS" for TemplateStyles (current model is "plain text"). Sylepieus (talk) 16:29, 3 January 2022 (UTC)
Sylepieus, Try activating the CSS extension:       CSS. Greetings. Hugo Ar (talk) 16:57, 3 January 2022 (UTC)
Hugo Ar, I've already activated the CSS extension in advance. The issue still persists. Sylepieus (talk) 17:07, 3 January 2022 (UTC)
Sylepieus, te falta configurar algo más porque veo que ocurre lo mismo en otras páginas similares como, por ejemplo, esta:
En la wiki que administro no tengo módulos ni plantillas con hojas de estilo CSS. Todo los estilos los agrego en MediaWiki:Common.css
Mi sugerencia: crea una cuenta en Phabricator, describe la situación y solicita que te indiquen el cambio de configuración para que todo funcione correctamente:
Saludos cordiales. Hugo Ar (talk) 17:54, 3 January 2022 (UTC)
Translated by Google Translator
Sylepieus, you need to configure something else because I see the same thing happening on other similar pages, such as this one:
In the wiki that I manage I do not have modules or templates with CSS stylesheets. All the styles I add in MediaWiki: Common.css
My suggestion: create an account in Phabricator, describe the situation and request that they tell you the configuration change so that everything works correctly:
Kind regards. Hugo Ar (talk) 17:54, 3 January 2022 (UTC)
@Sylepieus To fix the issue, you'll need to change the content model of Module:Sidebar/styles.css to Sanitized CSS. To do this, follow these steps:
  1. On the page, Module:Sidebar/styles.css, click "Page information" in the sidebar under "Tools" to get to its page info.
  2. Click the link "change" in the row "Page content model" to bring up a form for changing content models.
  3. Select "Sanitized CSS" and change the content model to that.
Hopefully this helps solve the error. K599 (talk) 21:02, 4 January 2022 (UTC)

Miraheze's relationship to Orain

I have been wondering this for a while, but what exactly is Miraheze's relationship to Orain. I have seen many conflicting answers about it: Some have said it is a direct predecessor, others have said that it is a spiritual predecessor, I have seen people that Miraheze was founded by former Orain staff, but it seems like the exact relationship (or if there even is one) remains ambiguous. In addition, the Orain Meta home page redirects to the Miraheze Meta home page, which implies that Miraheze is at least partially a successor to Miraheze. In addition, this says that Miraheze was originally Orain. Despite all of this, Orain doesn't seem to be mentioned much, and wasn't mentioned in Miraheze's five-year anniversary celebration. Blubabluba9990 (talk) 16:28, 2 January 2022 (UTC)

Miraheze and Orain are often linked together because both John and Southparkfan were volunteers on Orain for a long time. In July 2015, they left Orain to make Miraheze but Orain continued to exist as its own independent wiki farm. In September 2015 however, Orain was compromised and all of it's server data deleted. Many wikis on Orain moved over to Miraheze as a result which is why Orain and Miraheze have a sort of link together, Miraheze is a bit like Orain's de facto successor as many Orain wikis moved over to Miraheze and so did a lot of the volunteers and users but in a technical sense, Orain and Miraheze are completely unrelated. Since Orain was no more after 2015, I'm guessing Miraheze bought to redirect users who thought Orain was still in existence to us as we held a nice portion of Orain's user base. Because we're not technically related to Orain, there's really no need to mention it as it's just a thing of the past. Agent Isai Talk to me! 16:37, 2 January 2022 (UTC)
Blubabluba9990, officially, Miraheze and Orain have no direct relationship. Both were/are volunteer run and funded wiki farms, but with different purposes and visions. If trying to quantify the relationship, you could say was inspired by, for better or for worse, Orain. When Orain collapsed, the domain name expired, and Miraheze purchased the domain name and redirected it to Miraheze. Some volunteers also had Orain accounts, but other than those points, that's about the extent of the connection. Dmehus (talk) 16:39, 2 January 2022 (UTC)
Ok, that makes sense. I had figured that Miraheze could somewhat be considered Orain's spiritual successor. Blubabluba9990 (talk) 17:07, 2 January 2022 (UTC)
@Blubabluba9990: Orain was founded in 2013 by Wikipedians and was attacked in 2015 and do not have relationship with Miraheze. And as you can see in this archive page, some Orain users are the same as Miraheze users today. --YellowFrogger (Talk) 23:02, 2 January 2022 (UTC)

Math editor

Hello, it seems math equations editor is missing on this wiki. How can I get it? RedFox (talk) 17:43, 2 January 2022 (UTC)

@RedFox: Could you elaborate? Do you mean on this wiki (Miraheze Meta) or your wiki? Agent Isai Talk to me! 17:46, 2 January 2022 (UTC)
Agent Isai, I mean my own wiki called mathzadachi. It was created today. Thanks for your quick answer. — Preceding unsigned comment added by RedFox (talkcontribs)
You can enable it in your Special:ManageWiki/extensions interface under 'Parser hooks'. --Raidarr (talk) 20:30, 2 January 2022 (UTC)

Miraheze hit 5,000 wikis!

I was looking at the main page and saw that Miraheze is now hosting over 5,000 wikis! That's a great achievement for a wiki farm funded solely by donations. How should we celebrate this accomplishment? Tali64³ (talk) 01:13, 3 January 2022 (UTC)

Tali64³, yep, that's right. We have hit 5,000 wikis before, back in early 2020, but that was largely because the wiki closure was broken, so long dormant wikis weren't being appropriately marked as deleted. Dmehus (talk) 01:19, 3 January 2022 (UTC)
Congrats!  Anpang📨  01:26, 3 January 2022 (UTC)
Milestones usually don't matter that much, especially when it's about the number of wikis (soon the number will go down by a huge number for deleted wikis, currently there are too many inactive or closed wikis). --YellowFrogger (Talk) 01:27, 3 January 2022 (UTC)
Well, I was thinking about what you said, and I decided to start the Save the Inactive Wikis coalition to save inactive wikis. Would you like to join? Tali64³ (talk) 03:32, 3 January 2022 (UTC)
However, there are more interesting things to do. An inactive wiki means the owner is sick of it. --YellowFrogger (Talk) 17:14, 3 January 2022 (UTC)
Or that they gave up maintaining/editing it, or forgot (all) about it. --Routhwick (talk) 08:50, 4 January 2022 (UTC)