TestWiki:Community portal

From TestWiki
Jump to navigation Jump to search

Welcome to our Community portal. Post your questions, issues or problems below by clicking Add topic. TestWiki:Community portal/Archive 1

Gadget description

I noticed the gadget description on MediaWiki:Gadget-UTCLiveClock includes the text "After adding please en:purge the page" and was wondering what the point of it is. After all, the page already says that the tool includes a purge link. wikipedia:en:purge (apparent intended target) is no help either. ping @Reception123: who added it. -- Void Discuss 20:43, 8 September 2016 (UTC)[reply]

I have not seen this when importing the template. Removed. Reception123 (talk) 04:41, 9 September 2016 (UTC)[reply]

Shall we remove the background color of the logo just like File:NewLogo2.png? --Gyakusyuu no Amanojaku (talk) 10:50, 8 March 2017 (UTC)[reply]

.........Already changed by Gyakusyuu no Amanojaku.--Tiger (talk) 07:31, 30 March 2017 (UTC)[reply]
Bit of advice, don't change the logo by css. I'll upload a new version of the File:NewLogo.png, and, if needed, do a pull request to change the logo. -- Void Whispers 01:14, 31 March 2017 (UTC)[reply]

Are bureaucrats allowed to grant administrator right?

I found that bureaucrats are able to grant administrator right to other users technically. Are bureaucrats allowed to grant administrator right when other users request it on TestWiki:Request_permissions? Are they allowed to revoke the right when it is inappropriately used?--Tiger (talk) 14:51, 29 March 2017 (UTC)[reply]

Bureaucrats are allowed to grant sysop and bureaucrat, and can revoke sysop. If you are granting admin/bureaucrat, just make sure that the request fulfills the requirements at the top of the page. If in doubt, let someone else handle it. -- Void Whispers 15:06, 29 March 2017 (UTC)[reply]

RFC: Puffin Web Browser global blocks


As some may know, the entire Puffin Web Browser has been globally blocked on Miraheze through 4 or 5 separate rangeblocks due to suspected and in some cases confirmed abuse. However, this massive block(s) have the serious potential to cause collateral damage. I have locally blocked the same ranges specifically here, anon. only and with account creation allowed. I would like to propose the following:

"Immediately following the closure of this RFC, all global blocks on Puffin Web Browser IP addresses are to be locally disabled. The local blocks made by Primeferac shall be left as is for the time being, but any admin has permission to harden the blocks if obvious abuse occurs."

I personally use Puffin when accessing the Internet from unsecure locations like restaurants and public transportation, and I'm sure I'm not the only one. Therefore, I would like to help reduce the potential for collateral damage, which is never a good thing. Primeferac (talk) 00:30, 1 April 2017 (UTC)[reply]





The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section


The community portal has been protected from anonymous editing for 24 hours due to excessive vandalism. Amanda (talk) 18:08, 21 April 2017 (UTC)[reply]

Userrights update

Just an FYI in a visible place.

  • After a bug was resolved in the config, sysops now have the ability to add Autopatrolled, confirmed, and rollbacker to accounts.
  • 'Crats may now assign the bot usergroup. However, please be aware to only assign the group for testing or to prevent flood, never run a full bot account without consul permission.
  • The exampleuser usergroup will be removed as the only accounts it was assigned to were locked for security concerns. It is no longer useful.

If I'm forgetting anything, remind me. If you have any questions, ask below. Cheers -- Void Whispers 21:19, 25 April 2017 (UTC)[reply]

I think we can set a special usergroup like "flood" on Chinese Wikipedia (can be added by admins and only to admins themselves) to divide test groups from non-test groups. However, I don't think it's necessary because there are no real bots now. --Amanojaku (talk) 13:58, 26 April 2017 (UTC)[reply]

Does the email notice work?

I can't receive emails when someone leaves messages, but I can receive emails when changing the email address in preferences. --Amanojaku (talk) 14:03, 26 April 2017 (UTC)[reply]

Already posted to phab:T1738 by Reception123. --Amanojaku (talk) 16:45, 30 April 2017 (UTC)[reply]

Spanish PublicTestWiki

Hello, I just wanted to announce that I have established the Spanish Version of PublicTestWiki for native speakers of Spanish and that they need to have more facilities to communicate with the rest of their peers, all Spanish speakers who want to participate can visit the wiki in https://es.publictestwiki.com and begin to be part of the community. Regards. —Alvaro Molina ( - ) 12:24, 7 May 2017 (UTC)[reply]

Que bueno, una versión en español :) Cyborg (talk) 17:04, 7 May 2017 (UTC)[reply]

Don't need to test any more

Please revoke my crat and admin flag. I don't need them any more.--Tiger (talk) 12:09, 29 May 2017 (UTC)[reply]

 Done; if you need the rights back at any time, just let me know. Cheers -- Void Whispers 17:22, 29 May 2017 (UTC)[reply]

Pywikibot official community approval

This is just something for more "formal" reasons, and so that the WMF sees that there is community support for having Pywikibot here (details. It would be nice to get Pywikibot working here so we can have that as a testing option. Reception123 (talk) 17:26, 28 July 2017 (UTC)[reply]


  1. Support Reception123 (talk) 17:26, 28 July 2017 (UTC)[reply]
  2. Support Videojeux4 (talk) 17:40, 28 July 2017 (UTC)[reply]
  3. SupportAlvaro Molina ( - ) 18:04, 28 July 2017 (UTC)[reply]
  4. Support Amanojaku (talk) 07:07, 29 July 2017 (UTC)[reply]
  5. Support PokestarFan (talk) 23:42, 4 August 2017 (UTC)[reply]

# Strong support Test user (talk) User is indefinitely blocked for disruption --Reception123

# Support 13Reasons (talk) 18:06, 3 August 2017 (UTC) User is indefinitely blocked for abusing multiple accounts --Reception123[reply]



The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section

Abuse filter

Please examine my (IP) edits to my named account's userpage, it shouldn't be disallowed even though it starts with an IP address. 10:11, 1 August 2017 (UTC)[reply]

Please see your talkpage. Reception123 (talk) 14:15, 1 August 2017 (UTC)[reply]

Recent vandalism

I restored pages deleted by User:Anniubbo but please note that translation pages are not restored yet because they can't be undeleted directly. --Amanojaku (talk) 15:18, 4 August 2017 (UTC)[reply]

AlvaroMolina for consul

AlvaroMolina is a trusted user on other wikis including miraheze test wiki (spanish edition) and the test wiki @ https://testwiki.wiki/ . If these users are the same person I hereby propose that the user AlvaroMolina be granted consul to bring the amount of consuls to 4 (1 user makes an action and the other 3 can review it/take action about the first action) which is good for confirming actions made by consuls. He is also very active and can efficiently deal with issues.

Sau226 (talk) 06:57, 9 September 2017 (UTC)[reply]

  • Oppose I don't think there is need of other consuls. Sherry J. Scott (talk)
  • Support As the founder of https://testwiki.wiki, I think they are doing a great job. MacFan4000 (talk) 23:35, 10 September 2017 (UTC)[reply]
  • Oppose Per Sherry. Cyborg (talk) 17:28, 11 September 2017 (UTC)[reply]
  • Pictogram voting comment.svg Comment Only recently have I heard of this, I would like to clarify that at no time was I made known this proposal nor accepted it. For my part I agree with the comments below that there is no need for more consuls since the existing ones for me are sufficient and I have not seen an urgent need of another user, in addition, consul's actions are quite scarce here. For this reason I ask that this be closed as not done. Regards. —Alvaro Molina ( - ) 17:32, 11 September 2017 (UTC)[reply]

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section

Temporary feature

Hi, yesterday I used the temporary feature on Special:Userrights and I'm wondering if that feature was created by Miraheze or it comes with MediaWiki. Thank you, Cyborg (talk) 20:52, 9 September 2017 (UTC)[reply]

Temporary userrights is a feature that was added in MediaWiki version 1.29. It is not specific to Miraheze. -- Void Whispers 00:03, 10 September 2017 (UTC)[reply]
Thank you. --Cyborg (talk) 00:17, 10 September 2017 (UTC)[reply]


I've added translation pages to the MediaWiki:Titleblacklist to prevent vandalism. Only autoconfirmed users can modify or create translations now. The translations of the main page are also protected. Please feel free to change it after it's safe. --Amanojaku (talk) 04:19, 16 September 2017 (UTC)[reply]

Good! Sherry J. Scott (talk)

Able to change protection levels

Even though deletion and move rights are consul only, I am able to change them. Why? PokestarFan (talk) 19:35, 23 September 2017 (UTC)[reply]

Because the protect action is not restricted. As a result, unless we decide to modify the configuration, the only way to prevent the modification of protection levels is to remove edit access as well. It would make sense if the software only allowed users to modify protection levels if they had the ability to perform the action with its current restriction level. (eg that an admin would not be able to modify consul level move/deletion restrictions). But, this is not the case. -- Void Whispers 19:45, 23 September 2017 (UTC)[reply]
This can be configured said way. That is how it’s done on https://testwiki.wiki . Config is here. MacFan4000 (talk) 20:13, 23 September 2017 (UTC)[reply]

Got fatal error

I made a test on how long can a user be blocked (except indefinite) and set a block till 31 Dec. 9999 23:59:59 on a wasted account (declared by its owner). Then I met "[cadbecb3fec4cc62aa74674e] 2017-11-29 12:16:46: Fatal exception of type "MWException"" on all the pages that involving the block log of that account.(Block log of that account, Block log of this site, Logs of me and so on.) Sorry for making this trouble and wish it not a big trouble for the consuls.--Tiger (talk) 12:22, 29 November 2017 (UTC)[reply]

Well, it's not a problem anymore (as far as I can tell), so no big deal. -- Void Whispers 20:50, 29 November 2017 (UTC)[reply]
how can I help you? Artix Kreiger (talk) 22:29, 29 November 2017 (UTC)[reply]
It seems that the problem doesn't affect anyone except me........-Tiger (talk) 10:51, 21 December 2017 (UTC)[reply]

Asdfugil for consul in here

Hi guys I'm to become consul in here to help or monitoring in here. how your opinions?--Asdfugil (talk) 10:28, 20 December 2017 (UTC)[reply]

Arguments in favour

Arguments against

  1. Oppose Maybe if you were more actively involved in the project. Plus, this wiki is not very active. MacFan4000 (talk) 12:06, 20 December 2017 (UTC)[reply]
  2. Oppose Currently there's no need for new consuls. Esteban (talk) 20:46, 20 December 2017 (UTC)[reply]
  3. Oppose Has a few test edits, but no real serious edits, or anything that shows a need for this user to be a consul, or that they would benefit from the extra rights. At the moment, I think that three consuls is enough. Reception123 (talk) 19:20, 21 December 2017 (UTC)[reply]
  4. Oppose Not in a snowballs chance in hell... Then again who are you? Consuls should be a person thats known in the community not just anyone Zppix (talk) 19:20, 21 December 2017 (UTC)[reply]


The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section

Enable protect lock

I think we need to enable protect lock. It should be defined in LocalSettings.php and will stop lower downs from changing protection levels e.g. Sysops removong consul protection. If the community consents to it very soon I can get that set up --Sau226 (talk) 02:54, 2 January 2018 (UTC)[reply]

Sysops cannot currently remove consul protection, if they could do that that would defeat the point of having it in the first place. Reception123 (talk) 09:01, 2 January 2018 (UTC)[reply]
@Reception123: In some cases only delete and move are protected, such as this page. As long as “edit” isn’t consul protected, any non consul can remove the move and delete protection. This would prevent that from happening. MacFan4000 (talk) 12:12, 2 January 2018 (UTC)[reply]
Ok, I didn't know. That is fine yes, we should have the protect lock. Reception123 (talk) 15:22, 2 January 2018 (UTC)[reply]

The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section

Allow bureaucrats to self resign

Dear community,

I believe bureaucrats should be allowed to resign. A little bit of code like '+testwiki' => array( 'bureaucrat' => array( 'bureaucrat', ), or similar should be added to wgGroupsRemoveFromSelf in LocalSettings.php .

This code would allow a bureaucrat to revoke their own access themselves immediately without letting a bureaucrat decrat another user. Consuls would still be able to remove such access from anyone as required. --Sau226 (talk) 12:02, 4 January 2018 (UTC)[reply]

Can someone else please comment on this? --Sau226 (talk) 10:21, 23 January 2018 (UTC)[reply]

Consul for MacFan4000

I would like to be a consul. I am currently a sysadmin, and I helped to fix this wiki from the incident. I am familiar with the permissions. I currently have them to work on cleanup.


  1. Support Cy (talk) 06:38, 1 May 2018 (UTC)[reply]
  2. Strong supportMore consuls can’t be bad.—08:47, 14 July 2018 (UTC)



Request for Consul - Kiko4564

I wish to be a consul and have experience with admin tools both on this wiki and here Kiko4564 (talk) 20:08, 22 May 2018 (UTC)[reply]



  1. Oppose We have enough consuls already, plus, on wikipedia you are blocked for sock puppetry. Maybe later. Cy / Talk 05:02, 23 May 2018 (UTC)[reply]
  2. Oppose We have 4 consuls, plus this wiki isn’t very active MacFan4000 (Talk Contribs) 22:15, 23 May 2018 (UTC)[reply]



Hi. What does Special:AggregateGroups do? Pkbwcgs (talk) 08:15, 3 June 2018 (UTC)[reply]