User talk:Electron

Free texts and images.
Jump to: navigation, search

Polski Jeśli chcesz zostawić dla mnie wiadomość proszę pisać w języku polskim, angielskim lub rosyjskim.

English If you want to leave me a message, please write in Polish, English or Russian.

русский Если хочешь оставить мне весточкy пиши на польском, английском или русском языкaх.

Deutsch Wenn Du eine Nachricht hinterlassen, willst Du bitte sie in polnisch, englisch oder russisch schreiben.

Español Si quieres dejarme un mensaje, por favor escribe en polaco, inglés o ruso.

Potugal Se quiseres deixar-me uma mensagem, escreve-a por favor em polaco, inglês ou russo.

Italiano Se vuoi lasciarmi un messaggio, per favore scrivi in polacco, inglese o russo.

Nederlands Als je een berichtje voor me wilt achterlaten, schrijf dan alsjeblieft in het Pools, Engels of Russisch.

Suomea Jos haluat lähettää minulle ilmoitus, voitko, ole hyvä, kirioita se puolaksi, englanniksi tai venäjäksi.

Francais Si vous voulez me laisser un message, ne l'écrivez qu'en polonais, anglais ou russe, s'il vous plaît.

Picard Pou m'foaire un messache, écrire in poloné, inglé o bin in russe, mérchi.

Svenska Om du vil lämna mig ett meddelande, var så god, skriv det på polska, engelska eller ryska.

Also you can contact me on my Polish Wikipedia discussion page. Thank you!

User talk Archive: 2012-2016

Restore Feedback

Hi Electron, Welcome. I'm helping get the server restored. If you see anything that is missing or not working as expected, please let me know. Thanks! --Jeffmcneill (talk) 23:51, 31 March 2017 (JST)

Wikilivres Status Update

Hi Electron. There is a new status update available. It includes info on the restore, and the domain name. --Jeffmcneill (talk) 01:36, 2 April 2017 (UTC)

Autoconfirm Status Configuration

Hi Electron, I see that autoconfirm status was enabled and gave new users limited rights on Wikilivres. Do you recommend we do that, and what kind of rights should non-autoconfirmed users have/not have? Also how soon should accounts be autoconfirmed? Please advise. --Jeffmcneill (talk) 07:25, 8 April 2017 (UTC)

Multilingual Interwiki Configuration Option

Hi Electron,

The current use of /xy after a page to denote a language is a way of working around the problem of not wanting to set up a database for each language, and other related problems. However, it has deficiencies such as pages needing the same name in order to have related language siblings. Example: PageNameInEnglish/en, PageNameInEnglish/pl, etc.

The more complicated, but more functional approach is to have an interwiki with each wiki its own language, as in, This need not be subdomains, as this could bełówna,

We can see both designs in Wikisource:

Wikisource used to use the full /LanguageName, at least for the Main_page, see:

Because a Wiki Family (Wikifarm) can use tools such as translate and others to help more easily build links between pages in various languages.

More info here:

Note, this would be a big project, as it would move files from a single namespace in one wiki to multiple other wikis. In addition, there would be a commons wiki for file uploads (so that these would be shared via interwiki as well, instead of each namespace wiki having its own file upload area). This would be something to do only after all other technical requrests were completed, and the site back to the functionality it had before the server move.

Thoughts? --Jeffmcneill (talk) 04:30, 13 April 2017 (UTC)

@Jeffmcneill: OK. I've tried other way of lokalization of Main Page and MediaWiki:Recentchangestext-lang. They transcluded other pages in local language. It's working properly now , so I see Strona główna (Polish main page) and MediaWiki:Recentchangestext-lang/pl on default if I set Polish language in my Prefences. And it works for others our main language, now. Electron   09:44, 13 April 2017 (UTC)

BASEPAGENAME is deprecated

Hi Electron. BASEPAGENAME is deprecated. Please use PAGENAME instead. --Jeffmcneill (talk) 14:48, 17 April 2017 (UTC)

@Jeffmcneill:: Thanks for the info but it seem it still works -> [1] This info is from 2011, and there was discussion -> [2]. It doesn't work only with some specific parameters. Without parameters it still works. I used it with no parameters only or with the parser function: {{#titleparts:}}, as it is recomended. Electron   08:37, 18 April 2017 (UTC)
Hi @Electron:, it is still deprecated, which means it cannot be relied on for future use. Deprecated parts of MediaWiki should be removed so that some extensions and upgrades don't break the system in the future. Tracking down deprected parts of the system that cause problems in the future is difficult to do, so it is important to upgrade to supported (non-deprecated) syntax. Perhaps your bot can go through and replace uses of the magic word with supported magic words? --Jeffmcneill (talk) 12:32, 18 April 2017 (UTC)
@Jeffmcneill: To say the truth I'm not sure. There -> [3] is no info about this and this is official site of So I think that there is no intension to deprecat this magic word or if there was in the past they have change their mind. Every depricated words they marked with red frames, but this word is not marked with red but with green, as others... And there is not any warning. Btw. {{PAGENAME}} in not the same than {{BASEPAGENAME}}, they work slightly in different way, so if we change they without others additional changing the magic can't work properly... I do not suppose there is many pages that are put in. Electron   22:45, 18 April 2017 (UTC)
Ok @Electron: I looked in Phabricator and elsewhere and I think you are right. This looks to only be deprecated on Wikipedia, not MediaWiki. I no longer see problems with using it on Wikilivres. Here is a list of pagename magic words, but {{BASEPAGENAME}} does look to provide a unique function that is easier to use (for some cases). Carry on. --Jeffmcneill (talk) 04:49, 19 April 2017 (UTC)

Template:Title three breaks (assistance request)

Hi @Electron: I see you've edited Template:Title. I've used it on Alcoholics_Anonymous_(Original_Manuscript)_1938 and all the chapters. But I get three paragraphs each with a break, so there is a big amount of space after the header, and before the text begins. I've looked at the template but it includes so many others, perhaps you would know where to look closer? --Jeffmcneill (talk) 16:38, 18 April 2017 (UTC)

@Jeffmcneill: OK. Now it should work withtout the space. Electron   23:10, 18 April 2017 (UTC)
Perfect, thanks! --Jeffmcneill (talk) 04:26, 19 April 2017 (UTC)


I've made you the fifth Bureaucrat. Let me know if you don't want to be. It gives you some rights over admins. I appreciate your help around here. --Jeffmcneill (talk) 04:28, 19 April 2017 (UTC)

@Jeffmcneill: Thank you, it can be useful :) Electron   09:29, 19 April 2017 (UTC)
welcome among bureaucrats!

Welcome, Electron, and congratulations. Here are some paper and pen :-) --Zephyrus (talk) 23:37, 19 April 2017 (UTC)
@Zephyrus: Thanks for the greetings and the office supplies :) Electron   09:22, 20 April 2017 (UTC)
somebody took the pen though? ;p & congrats :) Lx 121 (talk) 09:37, 20 April 2017 (UTC)
 ;-) Electron   09:50, 20 April 2017 (UTC)

Main_page formatting breaks MediaWiki mobile

Hi @Electron:. I've implemented Extension:MobileFrontend which is how Wikipedia serves mobile pages (works ok out of the box), however the home pages /Main_page are formatted in a way that breaks the mobile experience. I think it might be fixed width in the CSS or something. I can take a look at this, or if you want to, let me know which you prefer. There is now a link at the bottom of the page to mobile/deskop for testing. --Jeffmcneill (talk) 16:53, 22 April 2017 (UTC)

@Electron: To say the truth I'm rather an old-fashioned man and I do not use the mobile to look through the internet... so I can't help you in this metter, sorry. Electron   22:34, 22 April 2017 (UTC)
@Electron: No worries, thought I'd give you first crack if you were interested, but I can do the CSS wrangling. Format may shift a bit, but it will be as usable. --Jeffmcneill (talk) 13:42, 23 April 2017 (UTC)

categories for works by year


please do not delete categories for "works by year".

at some point, we are most certainly going to have more works from 1932, 1933, & 1935,

so there is no reason to remove the categories, just because they are empty "right now".

when you do this, it just makes more work for people later, when they have to re-create the categories you have erased.

it also makes the categorization "untidy", when certain years are missing from the list.


Lx 121 (talk) 08:34, 23 April 2017 (UTC)

my apologies -- i have just noticed the capitalisation. however, i still think it is more useful to keep the redirects; given that our mediawiki has no decent tools to correct capitalisation errors (or any other common errors) in categorising. at least with proper redirects, items will still end up in the correct category. rspectfully, Lx 121 (talk) 08:40, 23 April 2017 (UTC)

@Lx 121: See here -> Category:Works by year, what is the purpose to keep doubled categories? You added categories that are doubled, some not categoriezed, that are empty (but is not the main point) and don't fit the others. If the categories are don't fit the others because of capitalisation, they should be delated and there should be made new instade with proper capitalisation. The admin's role is to organize and not make more mess than was before. Electron   09:45, 23 April 2017 (UTC)
yes, they are set up as category redirects; so that if somebody makes a common typo/error, the item still goes to the correct category. this does not "make more mess than before". it helps to organise material correctly; BECAUSE we do not have good tools to auto-correct such typos. Lx 121 (talk) 12:35, 23 April 2017 (UTC)
@Lx 121: It makes sense only if it works... I can't see that at the moment. Electron   12:40, 23 April 2017 (UTC)
yes, i have just noticed that; i have posted a request @ "technical" to fix or install the "category redirect" template. Lx 121 (talk) 12:42, 23 April 2017 (UTC)
we don't need any category redirects; if somebody makes a typo so he should recognize it and make a new cat; simple isn't it? -jkb- (talk) 12:49, 23 April 2017 (UTC)

Case-Sensitivity in MediaWiki

This gets at a bigger issue which is a design problem in MediaWiki, which is case-sensitivity. This can actually be fixed in Search (with a different API), which I've logged as a new task. However, the case-sensitivity in things like pages and categories is a pain. I will look more into this, as I am sure there is some way to get this going better, if only some regular bots that can auto-correct capitalization errors. I've logged this also as a separate task to look into. --Jeffmcneill (talk) 13:38, 23 April 2017 (UTC)