Community noticeboard

Archives:
 * Archive 1 (23 July 2017 - 25 November 2017)
 * Archive 2 (1 December 2017 - 3 March 2018)
 * Archive 3 (3 March 2018 ~ )

Infobox Differences from Wikia
I transferred my wiki from Wikia.com to Miraheze and imported the xml, but the infoboxes on the new wiki don't work. I don't know what changes I have to make to the infoboxes to make them work on miraheze, I thought they were the same for all mediawiki wikis. Can someone tell me the miraheze version of this wikia infobox source code:

Details  Combatants

--^Vitiate^ (talk) 04:57, 6 March 2018 (EST)


 * Wikia was energetically re-engineering Infoboxes and frequently nagging wiki administrators to adopt the new coding. Their criteria was smooth operation on mobile devices and rendering in stages to deliver quicker reaction for readers.  Stock MediaWiki, including wikitables, work fine on Miraheze.   22:18 6-Mar-2018


 * Without a visual example, that's rather hard to do. We do have general help for infoboxes (those from Wikipedia) here and a wiki dedicated to templates, which may prove useful. If that doesn't prove useful, then I would need to see a live example of the infobox. -- Void  Whispers 00:16, 7 March 2018 (UTC)

Install GlobalUserPage
I propose that we install the GlobalUserPage extension. It is used by the WMF and would be very useful on miraheze. Those who would not want a GlobalUserPage can use or __NOGLOBAL__ on their user page. MacFan4000 (Talk Contribs) 17:52, 3 February 2018 (UTC)

Votes

 * 1)  as proposer. MacFan4000 (Talk Contribs) 19:44, 3 February 2018 (UTC)
 * 2)  as long as abusefilters are setup to prevent global userpages to be used as an advertising place. Zppix (Meta | CVT Member | talk to me) 17:56, 3 February 2018 (UTC)
 * 3)  (as it is currently) My issue with this is the fact that you need to "opt-out" if you don't want it, not that you need to "opt-in" if you do. I would definitely support this if it's disabled by default, as then users decide whether they want a global userpage or not. Reception123  (talk) ('C' ) 18:03, 3 February 2018 (UTC)
 * 4)  See my previous comments on T1681. —AlvaroMolina (✉ -  ✔ ) 18:06, 3 February 2018 (UTC)
 * 5)  Esta función me parece perfecta. La he probado en Wikimedia y la veo útil. Así no tienes que actualizar cada wiki con nueva información o modificar el existente. Solo tienes que ir a Meta y actualizarlo. Wiki1776 (talk) 18:13, 3 February 2018 (UTC)
 * 6)  There is only one of me, and Mirahezians wanting to write to me ought not have to research which wiki has the busier talk page (though there is a hint in my signature).  If users want project-specific user pages, this is easily done and the global user page is an ideal directory of them.  Reception123 is right to be concerned about users getting opted-in involuntarily, but in this case, reacting to it is simple.  I support it with either opt-in or opt-out.   18:47 3-Feb-2018
 * 7)  Would change vote to support if it were opt-in and not opt-out. CoolieCoolster (talk) 19:44, 3 February 2018 (UTC)
 * 8)  I have no problem with this and the caveat isn't an issue for me either as I trust Miraheze admins.  20:28, 3 February 2018 (UTC)
 * 9) I also think this should be opt-in (  opposed to current NOGLOBAL opt-out). &mdash;  revi  03:07, 4 February 2018 (UTC)
 * 10) For the betterment of the community, I believe that it should be opt-in not opt-out. I thoroughly believe only people interested in using such a feature will actually use it, so there is no need to make it opt-out. I fully support this motion if it is opt-in. &#32;  Miraheze Logo.svg CnocBride | Talk | Contribs  12:20, 9 February 2018 (UTC)
 * 11)  It'd be very useful. -- 11:35, 9 March 2018 (UTC)

Comments/Questions

 * Making the feature opt-in can be achieved by setting wgDefaultUserOptions['globaluserpage'] = false; However, this requires the addition of the global preferences extension as well. -- Void  Whispers 20:47, 14 February 2018 (UTC)
 * Per https://phabricator.wikimedia.org/T184643 GlobalPreferences passed WMF security review. MacFan4000 (Talk Contribs) 22:02, 14 February 2018 (UTC)
 * If I remember correctly, wasn't there a performance issue related to GlobalPreferences, pointed out by Labster? Reception123 (talk) ('C' ) 19:43, 16 February 2018 (UTC)
 * I would imagine that was GlobalContribs, if only for the reason that WMF is adding GlobalPreferences, while a phab task on GlobalContribs hinted that the performance impact from GlobalContribs would make it impossible to use with more than several hundred wikis. -- Void  Whispers 20:04, 16 February 2018 (UTC)
 * So, today we installed both extensions, and discovered that GUP mo longer integrates with GlobalPreferences. We disabled GUP. We now have three options, if we still want it.
 * 1. Fork the repo and integrate the fork with GlobalPreferences
 * 2. Open a task on WMF phabricator asking to add this feature back
 * 3. Have it be Opt-Out
 * MacFan4000 (Talk Contribs) 22:00, 8 March 2018 (UTC)
 * As I have also said on IRC, I'd prefer number 1 (since number 2 is unlikely to happen). Reception123 (talk) ('C' ) 06:19, 9 March 2018 (UTC)
 * I dislike the idea of forking repos to make non breaking changes. I removed a few forked repos in favour of going back to upstream because it’s nice, cleaner, easier and puts the maintenance onus on someone else completely. The number of extensions declined because x or y which are easy fixes that we’ve never forked show it’s not something we should be doing. Plus we’ve never forked to fix performance issues, instead we work upstream. Why is this any different from everything else? John (talk) 09:23, 9 March 2018 (UTC)
 * I agree that option 1 would probobly be the best, since I am not sure that the devs would add a feature back that they just removed. MacFan4000 (Talk Contribs) 13:42, 9 March 2018 (UTC)
 * Seems like we are going with option 2. We will need somone who is willing to keep the extension updated. MacFan4000 (Talk Contribs) 15:47, 20 March 2018 (UTC)

Create a sitewide iw link to TME?
On Administrators' noticeboard, I requested that  (and  ) be added as an interwiki prefix for The Multilingual Encyclopedia (https://tme.miraheze.org) as a global interwiki. It got no response, so I assume it needs community consensus? Can it happen? -- 11:51, 9 March 2018 (UTC)
 * Yes, for creating a new global Interwiki, there should be consensus. Reception123 (talk) ('C' ) 08:02, 10 March 2018 (UTC)

Where are Miraheze's servers located?
Where? It doesn't say it in the FAQ. I need it for VandalismWiki's general disclaimer. -- 05:33, 17 March 2018 (UTC)
 * (Please ping me.) -- 05:37, 17 March 2018 (UTC)
 * The location for individual servers can be found by visiting the individual pages (see Category:Servers), but most of our servers are located in the Netherlands, with the exception of Tech:bacula1 and Tech:cp2 which are located in the United States. For your disclaimer, you can probably say "in the Netherlands and the United States". Reception123 (talk) ('C' ) 10:41, 17 March 2018 (UTC)
 * P.S.: Also added to the FAQ. Reception123 (talk) ('C' ) 10:45, 17 March 2018 (UTC)
 * There is a plan for CP3, but only thing we know for sure is it will be located in Asia Pacific. (No final decision about the location has been made) &mdash; revi  12:16, 17 March 2018 (UTC)

Does Miraheze have a counter to count the number of visitors to a page?
I'd like a counter on just a few pages of my wiki. Does Miraheze have a counter I could use? Or can I install a third party counter somehow? Thank you. Bulrush (talk) 11:37, 30 March 2018 (UTC)

Language errors
The UI language of my wiki is supposed to be Korean, but sometimes it's displayed as English. What's wrong with my wiki? --Glacial HCM (talk) 21:15, 9 April 2018 (UTC)