User talk:Pyrrhus

Welcome to Pyrrhus’s Talk page.
Feel free to talk with me here about MEpedia.

Just add a new comment to the end of this page, ideally using the "Add topic" tab.

You can reply to an existing comment by beginning your comment with the Horizontal Line button, or by indenting your reply using colons.

And please remember to end your comment with four tilde characters " ~ " on a line by itself, which signs your name to the comment.

Thanks!

Pyrrhus (talk) 19:13, 10 February 2019 (EST)

{{collapse|

Changes to Primers
Thanks for making clarity changes on the Primers. There are five Primers and if you could make the changes to all five, that would be helpful.

Primer for doctors and researchers

Primer for family, friends and care providers

Primer for journalists

Primer for patients

Primer for the public

--77.111.245.5 18:04, 15 February 2019 (EST)

Thanks for letting me know!

I'll go do that, and in the future I'll make changes to all 5 primers as appropriate.

Thanks.

Pyrrhus (talk) 18:45, 15 February 2019 (EST) }}

Persistent Infection Page
So great to see you here! I think it would be useful to create a page on persistent infection that has sections re: the ways (and evidence) for persistent infection in different families of viruses (and perhaps other pathogens) that also links to the main pages for those viruses. We could use this page: https://me-pedia.org/wiki/Persistent_infection_hypothesis or create a page on persistent infection that is a bit broader and not specifically about the evidence for/against its role in ME/CFS. I propose the latter. https://me-pedia.org/wiki/Persistent_infection --JenB (talk) 09:53, 20 February 2019 (EST)


 * Good to see you back! I'll take your suggestion and go with the latter page.  Please be patient, it may take me a while, but I'll get there eventually.
 * Pyrrhus (talk) 22:09, 20 February 2019 (EST)

Collapsing lists
Hey, I noticed your query about collapsing lists and thought I'd leave you some links with info about formatting those in source editor as well as Wikipedia guidance on using them or not. It's not my area of expertise but generally speaking, I believe WP recommends against using them in mainspace (unless the collapsed/hidden info is truly only supplementary rather than essential to the topic) because of some accessibility issues, and that instead it's best to split off pages when lists become unwieldy. So that would recommend for making the Contents page into a clean list of major overhead categories, and then each would have a subpage. But, like I say, not usually among the questions I deal with so, yes, in case the details here can be of any use: Hope that may be of help! Canele (talk) 19:25, 10 April 2019 (EDT)
 * https://en.wikipedia.org/wiki/Help:Collapsing
 * https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style#Scrolling_lists_and_collapsible_content
 * https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Accessibility
 * Wow, that’s incredibly helpful! Thanks!
 * Pyrrhus (talk) 19:38, 10 April 2019 (EDT)
 * My pleasure! (Truth is I have considerably more wiki than ME/CFS expertise so if I can help out at least on that score, in terms of tools for organizing information and starting up basic pages that people with more scientific expertise may be able to come along behind and fill in a little more easily, well I'm just glad I can make a contribution.) Canele (talk) 00:56, 11 April 2019 (EDT)
 * Hi. Some time ago I copied collapsible list templates from several other wikis. It was a total nightmare to get them working to be honest but there's an example here:
 * Common_symptoms_in_ME/CFS
 * If they look expanded rather than collapsed by default then check my user CSS - it needed a few extra styles adding, I requested these to be added to the site Common.css but I can't remember if they were done or not. There's a similar thing on Template:Read_more - I was hoping to use it to partially hide the Quote field in certain references. The quote field might well increase visits since some of them are pretty controversial. E.g. Wessely contradicting his previous work then reverting back depending on the audience.
 * A search for Templates created in the last year will come up with a lot of those recently copied from WikiMedia's Commons or Wikipedia if you are looking for extra features. notjusttired (talk) 19:16, 11 April 2019 (EDT)
 * Thanks, Njt! That's certainly helpful.  Sorry it was such a nightmare to get the collapsible lists working.  But you gave me some good sources to investigate! Thanks.
 * Pyrrhus (talk) 20:07, 11 April 2019 (EDT)

{{collapse|

Add topic re updates
I made the changes you requested. Let me know if everything is to your liking. The programming work you have been doing has been outstanding! Thanks so much Kmdenmark (talk) 18:02, 17 May 2019 (EDT)

Donate button and footer bleed
Can you copy these to your pivot.css and see if they work on desktop / larger screens? Donate seems fine to me, I'm less sure on the footer bleed issue. Thanks notjusttired (talk) 08:03, 20 May 2019 (EDT)
 * Thanks User:Notjusttired! For some reason, the MediaWiki software refuses to recognize my pivot.css page as CSS code.  Maybe I need the "editmycssjs" right given(?)  Did you ever receive this user right?  Or is the MediaWiki software just confused?
 * Pyrrhus (talk) 20:28, 20 May 2019 (EDT)
 * Never mind! I just went to Special:ChangeContentModel to specify that my pivot.css page is CSS code. Now I can see that the Donate button looks like a button again! Thanks!  (But the footer still bleeds left.)
 * Pyrrhus (talk) 20:32, 20 May 2019 (EDT)
 * Strange problem with the CSS! Does the footer bleed less than before? How many characters wide is the box that bleeds? notjusttired (talk) 04:38, 21 May 2019 (EDT)
 * I just edited the footer code below, which should hopefully fix the issue. The powered by mediawiki logo I'm going to hide too. notjusttired (talk) 13:28, 21 May 2019 (EDT)
 * Thanks User:Notjusttired! The change doesn’t seem to have affected the footer row, it still bleeds as before :(
 * I love the idea of hiding the second column in that footer row, the column containing “Powered by MediaWiki”. That should give the first column more space to expand.
 * The first column in that footer row uses unordered lists to display the lines, which makes the text vertically long. Do you know if there is any CSS hack to make the list items display with inline flow, so the list items stack horizontally?
 * Pyrrhus (talk) 15:22, 21 May 2019 (EDT)
 * I guess try using !important on the footer margins (as below). If that doesn't work I'm stumped... although removing the background color/setting to the same as the side bar would probably make it look ok. I haven't been able to remove the "poweredbyico" - I think it needs doing in LocalSettings.php - but I am not sure if the space will be freed up that way. It might be better to put the MEAction logo in that space. There is a "hlist" class we already have for horizontal lists. I think it's in MediaWiki:Common.css, but you really would want to adapt that to use something other than commas to space things out. This hlist template could be copied over, we don't use our existing hlist template. To be honest though, Wikipedia and mediawiki look messy even on small screens. notjusttired (talk) 15:54, 21 May 2019 (EDT)
 * Thanks User:Notjusttired! I'll try that.
 * Pyrrhus (talk) 16:15, 21 May 2019 (EDT)
 * Holy S**t, User:Notjusttired! That fixed it.  Just adding "!important" made the footer no longer bleed into the sidebar!  Great hack!
 * Pyrrhus (talk) 16:20, 21 May 2019 (EDT)

/* fix footer bleed by fixing negative padding  */ footer { margin-left: 0!important; margin-right: 0!important;}

/* make donate look like button */ margin-left: 0.25em; } display:inline-block; }
 * 1) n-donate {
 * 1) n-donate a {

Centering footer
Powered by was actually under the test of the footer and is finally hidden. Disclaimers and Cookie statement had both been given a line each, I've moved them to the same line. They don't seem to join with the previous line though. Adding some centering too. The footer always begins right of the sidebar too. notjusttired (talk) 17:33, 21 May 2019 (EDT)

padding-right: 2rem; display: inline; text-align: center; }  display: inline; text-align: center; } /* removed powered by mediawiki - which has several different names oddly */ .poweredby { display:none; } /* center block - won't overlap sidebar */ display: inline-block; width: 100%!important; text-align: center; padding-right:8px; }
 * 1) footer-developers,
 * 2) footer-cookiestatement {
 * 1) footer-left,
 * 2) footer-places,
 * 3) footer-disclaimers,
 * 4) footer-privacypolicy,
 * 5) footer-about {
 * 1) footer-poweredbyico,
 * 2) footer-poweredby,
 * 1) footer-left {


 * This looks great, User:Notjusttired! Could you take a look at the CSS I am testing? (Below). Maybe this can be merged with the code above? I’m still not sure if I like the footer text centered or not... Thanks!
 * Pyrrhus (talk) 19:38, 21 May 2019 (EDT)

/* UNTESTED CODE */

/* make donate look like button */ margin-left: 0.25em; } display:inline-block; }
 * 1) n-donate {
 * 1) n-donate a {

/* center donate button in sidebar */ text-align: center; }
 * 1) n-donate {

/* fix footer bleed by fixing negative padding  */ footer { margin-left: 0!important; margin-right: 0!important;}

/* expand footer-left and hide footer-right */ display: none; } width: 100%; }
 * 1) footer-right-icons {
 * 1) div-footer-left {

/* make text lines into a paragraph */ li#footer-lastmod, li#footer-viewcount { float: left; margin-right: 0.5em; }

/* make links all in a row */ li#footer-privacy, li#footer-about, li#footer-disclaimer, li#footer-developers, li#footer-cookiestatement { float: left; margin-right: 2em; }

/* center footer text */ ul#footer-left { text-align: center; }

/* END UNTESTED CODE */ }}

Disambiguation template and __DISAMBIG__
Hi. The disambiguation template already includes the magic word __DISAMBIG__ so there's no need to add it. A page containing means add the contents of the disambiguation page, including any magic words that are in it. (Three curly brackets around something pass a parameter value into any templates, in case you see that. notjusttired (talk) 09:03, 24 May 2019 (EDT)
 * Excellent, that’s good to know! I’ll go fix the documentation to make it clear that only the  is required.  Thanks for catching that!
 * Pyrrhus (talk) 12:39, May 24, 2019 (EDT)

-- notjusttired (talk) 21:08, June 2, 2019 (EDT)
Hi. Check out MediaWiki_talk:Vector.css - now with the "What is this page?" info put in a template. Any template can be added to a page using - just like you would if marking a page as a stub. The remaining bits are the parameters (values passed in that control what it does) eg  would use a template called "lowercase" and pass it the parameter  (1 - with 3 curly brackets) - which would have the value HELLO. Some templates to check out are Template:Tmbox and Template:imbox - of documentation is missing you can find it on the same pages at wikimedia Commons or Wikipedia. Anything in the "noinclude" tags is not displayed - so that's a great place to add categories or instructions. Advantages are less repeateding of the same info, so easier to update just one version, and easier to skip over the template description of you know what it does, and they can automatically be added to categories at the same time. Also - with CSS there is also the option to have user css. Hope this is helpful. notjusttired (talk) 21:08, June 2, 2019 (EDT)
 * I saw that! Very cool!  I read the doc on Imbox, it could come in very helpful.  Thanks for the great info!
 * Pyrrhus (talk) 23:36, June 2, 2019 (EDT)

Pivot code
If you have time can you give this a test. Should change small screens to call the website #MEPEDIA not MEPEDIA. Also a small layout change for main page too. Thanks for your last feedback on pivot. Many changes to follow yet on Timeless - mostly for editing tools and pages used by editors. Surprisingly timeless does not allow mobile users to edit on Wikipedia - lots of layout issues for mobiles. notjusttired (talk) 19:34, June 9, 2019 (EDT)
 * Done. The “#” is showing up correctly.  Haven’t noticed any changes on the main page, but I’m not sure what I should be looking for...
 * Pyrrhus (talk) 19:15, June 10, 2019 (EDT)

section#middle-nav .title a::before { content: "#"; font-family: Oswald, sans-serif; font-style: italic; font-variant: normal; margin-right: -0.15em; }

.mw-body li.gallerybox div.thumb { padding: 0; }

/* main page centering contents list in wikitable at top */

.wikitable > * th > p { text-align: center; }

Citoid version -- notjusttired (talk) 05:42, July 16, 2019 (EDT)
Hi. Can you explain how Citoid fixed work? Does the extension need updating to include them? How do we know which patches / fixes need a code update and which are for an external service? I noticed some fixed are labeled as waiting for deploy  notjusttired (talk) 05:42, July 16, 2019 (EDT)
 * I can share my understanding, but my understanding may be incomplete:


 * There is an external citoid server which performs the actual conversion from URL to citation.
 * The citoid extension mostly exists just to connect the VisualEditor to the external citoid server.
 * The default citoid server that the citoid extension connects to is probably https://en.wikipedia.org/api/rest_v1/#!/Citation/getCitation but I'm not sure about that. Thanks to the Wikimedia Foundation for providing this free service.
 * Zotero is a non-profit that develops citation management software that includes a "Translation server" to convert URL's to citations.
 * Wikimedia Foundation has adapted Zotero's "Translation server" as the code for the citoid server.
 * Although the non-profit Zotero frequently updates their "Translation server", Wikimedia Foundation doesn't implement the updates that frequently. More info: https://www.mediawiki.org/wiki/Citoid/Determining_if_a_URL_has_a_translator_in_Zotero
 * Wikimedia Foundation currently stores their citoid server code on Phabricator: https://phabricator.wikimedia.org/project/profile/62/
 * I assume that when a bug on Phabricator is moved from "Waiting for deploy" to "Resolved", it means that the fix has been deployed from Phabricator to the external citoid server.
 * The Citoid extension should only be updated when the MediaWiki software itself is updated, as each version of MediaWiki requires its own version of the citoid extension.
 * Hope this helps
 * Pyrrhus (talk) 23:34, July 17, 2019 (EDT)

out of date extensions -- notjusttired (talk) 07:06, July 16, 2019 (EDT)
Some particular ones that look worth upgrading: These seem worth doing before the upgrade of MediaWiki. Obviously there's an argument for updating every extension to the latest version rather than just these. Most include many translation or localization updates. Some are clearly going to be very low priority. Most date from September 2017 - Special:Version Thoughts? 07:06, July 16, 2019 (EDT)
 * citoid (possibly wait for next release)
 * codeeditor - icon changes that look relevant to the mobile improving I'm making on skins, use WikiEditor toggle tool
 * disambiguator - remove disambiguator pages from Special:AncientPages
 * scribunto - works the Lua modules, although I don't see any particular bug fix that's relevant
 * categorytree - fix categories with numeric names, this extension is key for searches etc although didn't see any important fix
 * parserfunctions - really key extension used in many templates
 * graph - icon changes and other fixes, I think this is worth doing
 * templatedata - don't see anything worth updating this for but obviously it's well used
 * hitcounter - number of views out if date
 * pagesimages - images not always showing
 * smitespam - couldn't see any particular change, User:Kmdenmark mentioned it often flags images but an upgrade may not fix this
 * dismissablesitnotice - use session storage instead of cookies
 * Any extension with a “compatibility policy” of “release branches” must be updated with any new version of MediaWiki. These include Echo, Scribunto, TemplateData, PageImages, Citoid, VisualEditor. So we can't update those extensions until we update the MediaWiki software.
 * Some of the others might be worth updating but since they released MediaWiki version 1.33 they are no longer offering downloads for our version of MediaWiki, so these will also have to wait until MEdiaWiki is updated. (I don't think codeeditor or smitespam are important enough to update.)  Hope this helps.
 * Pyrrhus (talk) 23:58, July 17, 2019 (EDT)

Pages in need - Articles needing an image
Articles needing an image is currently not helpful / too hard to see what's important or what to focus on. I thought it might be helpful to split this page into sections by main category (researchers, treatments etc) and have longest pages listed first.

I wondered if you wanted to update this, link to escape codes below. Perhaps the first 10 longest posts at the top of the page, then subheadings for researchers, potential treatments, etc, the contents would let people jump to the category they are interested in User:Notjusttired