User talk:Evad37/Archive 6

Happy New Year, Evad37!


Happy New Year! Evad37, Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.

– Davey 2010 Merry Xmas / Happy New Year 13:02, 1 January 2017 (UTC)

Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.

Please create documentation pages for your scripts
Hello, could you please create documentation pages for your scripts? That would be really helpful. They don't have to be long - they just need to state what the script is doing (it doesn't matter if that's already in a comment in the script or not). E.g. for User:Evad37/WikidataWatchlistLabels.js.

--Fixuture (talk) 19:25, 14 January 2017 (UTC)
 * ✅. Thanks for the prompt/reminder, all the ones in my new navbox User:Evad37/Scripts navbox now have doc pages. Any other .js pages in my userspace either aren't finished, are tests, or are sandboxes. - Evad37 &#91;talk] 05:45, 15 January 2017 (UTC)
 * Great - thank you! --Fixuture (talk) 11:52, 15 January 2017 (UTC)

My Watchlist-openUnread tweak
Hi Evad37. Sorry if I was overreaching with this edit - I just couldn't resist tweaking it. :) — Mr. Stradivarius  ♪ talk ♪ 04:46, 23 January 2017 (UTC)
 * Thanks, no problem! - Evad37 &#91;talk] 05:56, 23 January 2017 (UTC)

Watchlist-openUnread
Hello Evad37. I tried out Watchlist-openUnread. Unless I define openUnread_maxnum, I get the below in my console using Vector skin running Chrome 55.0.2883.87 m (64-bit): Uncaught ReferenceError: openUnread_maxnum is not defined index.php?title=User:Evad37/Watchlist-openUnread.js&action=raw&ctype=text/javascript:16 at HTMLDocument. (index.php?title=User:Evad37/Watchlist-openUnread.js&action=raw&ctype=text/javascript:16) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1rfuz0b:45) at Object.add [as done] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1rfuz0b:45) at jQuery.fn.init.jQuery.fn.ready (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki&only=scripts&skin=vector&version=1rfuz0b:49) at index.php?title=User:Evad37/Watchlist-openUnread.js&action=raw&ctype=text/javascript:8 This prevents the script from working since the UI elements don't show up. —&thinsp;JJMC89&thinsp; (T·C) 04:40, 23 January 2017 (UTC)
 * Also, I think oldif on line 50 should be oldid. —&thinsp;JJMC89&thinsp; (T·C) 04:43, 23 January 2017 (UTC)
 * yes, fixed - Evad37 &#91;talk] 06:10, 23 January 2017 (UTC)
 * I think this is because the script had  on line 16, when it should be   or  . (Same for the other config variables.) — Mr. Stradivarius  ♪ talk ♪ 05:01, 23 January 2017 (UTC)
 * thanks... sometimes I make silly mistakes with syntax (but usually I'm better on picking up on it) - Evad37 &#91;talk] 06:10, 23 January 2017 (UTC)

January 2017
Hello, I'm 331dot. An edit that you recently made to Talk:Main Page seemed to be a test and has been removed. If you want more practice editing, please use the sandbox. If you think a mistake was made, or if you have any questions, you can leave me a message on my talk page. Thanks! 331dot (talk) 10:11, 28 January 2017 (UTC)
 * Thanks, I forgot that Special:ApiSandbox can make edits even though it is a sandbox - Evad37 &#91;talk] 10:12, 28 January 2017 (UTC)
 * In that case I apologize for the disturbance. You seem to know what is going on.  Best wishes 331dot (talk) 10:18, 28 January 2017 (UTC)

Turkeys and idiots out and roaming
But I fear not, Evad is editing... HNY JarrahTree 01:01, 2 January 2017 (UTC)
 * Bring em on! the more the merrier JarrahTree 01:07, 2 January 2017 (UTC)
 * your choice of where the money was being wasted on fireworks is conditionally ok - there is no known threat to our safety and sanity from that particular country, as for the rest... - well chosen JarrahTree 01:25, 2 January 2017 (UTC)
 * amazing what happens when you take a day or two off... JarrahTree 03:32, 14 January 2017 (UTC)
 * Yeah... and it takes more time to figure out what to do (revert, partial revert, or fix up) when they have good intentions, or at least seemingly good intentions. At least "pure vandalism" might be reverted by a recent changes patroller, or a bot. - Evad37 &#91;talk] 03:44, 14 January 2017 (UTC)
 * Can you keep an eye out for more odd changes to road articles? Similar things have started happening again... - Evad37 &#91;talk] 08:51, 30 January 2017 (UTC)
 * Yup its everywhere on the planet at the moment - blame the c--- - its probably the karma from their new year celebrations JarrahTree 08:56, 30 January 2017 (UTC)

self identified turkey
Have been creating more Freo street stubs - and havent yet got a handle on the magic you used to do for the older stubs - is there one that is best to use as a model/reverse engineer... ? East, Burt, Elder, Beach, Ord, Norfolk is a bit of a 'thing', plan to get more up soon, but thought I should seek guidance re the magic tweaks you used to do with the road things, if you get my drift. Please dont do my work for me - just a point, link or clue is all that is asked for - and no rush either JarrahTree 00:44, 17 January 2017 (UTC)
 * High Street, Fremantle is probably the best one to try to emulate. Even though its more of a "road" than a "street", it has all the right elements – sections for:
 * Lead (summary of details which are also covered elsewhere in the article)
 * History (whatever info you can find from Trove or elsewhere)
 * Route description (where it starts, goes, and finishes, referenced with maps)
 * Heritage places/streetscape
 * List of (major) intersections
 * Plus an infobox with the basic details (which are also covered elsewhere in the article), portal link, categories, etc.
 * I hope that's what you after (otherwise I might have to add, , and/or into your message above...  (I saw your interaction with Mitch this morning) ) - Evad37 &#91;talk] 01:38, 17 January 2017 (UTC)
 * aw shucks I live in sheer terror of mitches in text templates JarrahTree 09:19, 17 January 2017 (UTC)


 * thanks for your reply, thinking about it further. I suppose I was also interested in the kml stuff you get up to - JarrahTree 00:33, 18 January 2017 (UTC)
 * I use Google Earth to creates KML files, following the tutorial at WikiProject_U.S._Roads/Maps_task_force/Tutorial. Which will work for now, though probably isn't the best format going forward. The "next generation" of interactive mapping will be to tag roads in OpenStreetMap so that we can just reuse their data, like this: . I've been meaning to investigate this further, but just haven't gotten around to it yet (there's some further details on my commons talk page) - Evad37 &#91;talk] 00:47, 18 January 2017 (UTC)


 * can see why, my scatterbrain style editing (thanks of course to mitch to cleanup after me :) would probably require a close look, as stiff drink, a sit down and think about that one :) JarrahTree 00:57, 18 January 2017 (UTC)


 * thanks for the late night fixups - meant to ping the others as well, still time to do so - thank you JarrahTree 22:55, 1 February 2017 (UTC)
 * it is complicated - not yet determined JarrahTree 04:57, 6 February 2017 (UTC)

CSS styling in templates
Hello everyone, and sincere apologies if you're getting this message more than once. Just a heads-up that there is currently work on an extension in order to enable CSS styling in templates. Please check the document on mediawiki.org to discuss best storage methods and what we need to avoid with implementation. Thanks, m:User:Melamrawy (WMF), 09:11, 6 February 2017 (UTC)

Thank you
Hi Evad37, thanks very much for cleaning up that table at History_of_Smooth_Island_(Tasmania). This page as well as Smooth_Island_(Tasmania) would really benefit from an additional editorial perspective. I've spent several years working on these two pages but sometimes it's easy to lose the forest for the trees. Would appreciate any other contributions you feel inclined to make. Kind regards, Jkokavec (talk) 04:43, 12 February 2017 (UTC)

Category:Pages using duplicate arguments in template calls
I made [//en.wikipedia.org/w/index.php?title=User%3AEvad37%2FXFDcloser%2Fsandbox.js&type=revision&diff=765173622&oldid=764988231 this change] to remove your sandbox script from Category:Pages using duplicate arguments in template calls. It would be great if you could do the same, or something else, for the main script. Thanks! Plastikspork ―Œ (talk) 23:57, 12 February 2017 (UTC)
 * ✅, thanks - Evad37 &#91;talk] 00:06, 13 February 2017 (UTC)

NHs in India
Hi Evad37, I am trying to get all the mapping and linked national highways in India. Can you please help ? About 15 primary nh (nh no below 100) are mapped and linked. --naveenpf (talk) 11:29, 15 February 2017 (UTC)
 * https://en.wikipedia.org/wiki/User:Naveenpf/sandbox <=== It giving a syntax error.
 * The syntax error was using double quotes inside the query. I fixed the syntax with, but the link doesn't actually show anything – I'm not sure why - Evad37 &#91;talk] 12:48, 15 February 2017 (UTC)
 * Figured it out using some trial and error and mw:Help:Extension:Kartographer, maplink should work now - Evad37 &#91;talk] 13:12, 15 February 2017 (UTC)
 * Thanks Evad37 -- naveenpf (talk) 14:29, 15 February 2017 (UTC)

RSS feed not updating
Hello. The Signpost feed is bombing out for some reason. :-( I'm getting "Bad title "Category%253AWikipedia_Signpost_RSS_feed"". Am investigating now. Sam Wilson 03:26, 28 February 2017 (UTC)
 * Thanks for looking into to this. It seems like the title's getting encoded twice, as  percent-encoded becomes , which when encoded again becomes   - Evad37 &#91;talk] 03:31, 28 February 2017 (UTC)
 * Well, this was a weird one.... the problem just disappeared. :-( Anyway, I've updated mediawiki-feeds to use the better category traverser from the addwiki library (which has meant switching to dev-master branches, but I'll keep an eye on things). So now things should be working! Nice work on adding the descriptions to everything; looks good. Sam Wilson 07:50, 28 February 2017 (UTC)

signpost and all
great to see the oz quotient on signpost - looks good! JarrahTree 23:33, 28 February 2017 (UTC)

Pacific Highway
I can understand what you were trying to do here, but the the infobox was setup with a split route because there is now, officially at least, a hole in the middle in Newcastle. It's only a 6.7km gap, but it's a split route nonetheless. And, of course, there's the Wyoming to Kariong section. -- Aussie Legend  ( ✉ ) 18:00, 14 March 2017 (UTC)
 * Yeah, you have a point there. I restored the split endpoints in the infobox, but still left out the other junctions I removed earlier. - Evad37 &#91;talk] 23:26, 14 March 2017 (UTC)

Watchlist-openUnread: apiCallback_getRevId
Hi Evad37. Could you adjust apiCallback_getRevId in Watchlist-openUnread to be wiki agnostic. I would like to use the script globally without having to fork it. —&thinsp;JJMC89&thinsp; (T·C) 01:03, 21 March 2017 (UTC)
 * ✅ - Evad37 &#91;talk] 01:36, 21 March 2017 (UTC)
 * Much appreciated! Thank you. —&thinsp;JJMC89&thinsp; (T·C) 01:46, 21 March 2017 (UTC)

Disambiguation link notification for March 29
Hi. Thank you for your recent edits. Wikipedia appreciates your help. We noticed though that when you edited Stuart Highway, you added a link pointing to the disambiguation page Observer. Such links are almost always unintended, since a disambiguation page is merely a list of "Did you mean..." article titles. Read the FAQ* Join us at the DPL WikiProject.

It's OK to remove this message. Also, to stop receiving these messages, follow these opt-out instructions. Thanks, DPL bot (talk) 10:08, 29 March 2017 (UTC)
 * - Evad37 &#91;talk] 10:35, 29 March 2017 (UTC)

just a thought
any chance of https://en.wikipedia.org/wiki/Wikipedia:Meetup/Perth/35 ?? JarrahTree 00:07, 6 April 2017 (UTC)
 * Not sure... I've been feeling a bit off, think i might be coming down with a bug or cold – so it depends how I'm feeling tomorrow afternoon/evening - Evad37 &#91;talk] 02:26, 6 April 2017 (UTC)
 * I understand - a friend who is very interested does have a full blown flu at moment - not able to go JarrahTree 00:43, 7 April 2017 (UTC)

Nomination for deletion of Template:Traffic volume bottom/TemplateData
Template:Traffic volume bottom/TemplateData has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. P p p er y 21:47, 8 April 2017 (UTC)

The Center Line: Spring 2017
  Volume 9, Issue 1 • Spring 2017 • About the Newsletter

1=
 * Departments

• Assessment roundup

• Portal selected articles and pictures 1=
 * Features

• Commons and Wikidata revamp

• Route logs for junction lists

• Finding friends at the DOT

• This space for rent 1=
 * State and national updates

• State updates

• In other project news...

 Archives • Newsroom • Full Issue • Shortcut: WP:USRD/NEWS
 * —delivered by MediaWiki message delivery (talk) on behalf of on 01:03, 14 April 2017 (UTC)

Tool for moving to draftspace
Hey Evad, with your API experience with the XFD closer, I thought I'd run a different problem past you. Every week, a batch of new articles is posted at WT:VG and I try to help patrol it. Many of these articles belong in draftspace or need further incubation. I end up wasting a lot of time with the same routine after whatever cleanup I can do myself: Since this is always the same repetitive action, it would be great if I could do this with one click. Would this be easy to put together? And if you aren't able to help, would you suggest any skeleton for getting me started? czar 18:13, 18 April 2017 (UTC)
 * 1) Move article to draftspace (reason: "undersourced, incubate in draftspace"), leave no redirect behind
 * 2) Since it's in draftspace, manually hide categories and fair use images, add   with the page creator's username
 * 3) At the page creator's talk page, make a section explaining why the page was moved (I have a template for this)
 * 4) (Optional?) Update article's WikiProject banners, if set
 * That does seem easy enough for the most part... detecting wikiproject banners can be a bit tricky, but can probably be done by just removing anything and anything parameters from all templates, and letting the banners auto-set those. I can help you if you're interested in coding it yourself, or else I can look at doing it later this week or next week. - Evad37 &#91;talk] 03:20, 19 April 2017 (UTC)
 * Thanks, Evad! It would be a big project for me since I haven't written a gadget that does more than text-processing JavaScript, so if it's easy for you, I'd appreciate if you can take a look. Otherwise, it's on my list for the future. I think it would be helpful to page patrollers too. The WikiProject banner solution sounds good to me, especially since I consider changing the banners only a courtesy to the projects in the first place  czar  03:27, 19 April 2017 (UTC)

RfA?
It's somewhat ironic how you created many scripts for the use of admins, yet are not an admin yourself and are unable to use them for deleting pages. With your experience and article creation, you would easily pass a WP:RFA. Or if you don't trust me, try starting a poll at WP:ORCP. Wikipedia needs help. f e  minist  10:35, 18 May 2017 (UTC)
 * Thank you for your confidence, but (at the moment anyway) there isn't actually anything I want to do with the mop. . - Evad37 &#91;talk] 00:37, 19 May 2017 (UTC)
 * If, after you finish my move-to-draft tool, you're interested in finding some admin areas, let me know if I can return the favor czar  01:17, 19 May 2017 (UTC)
 * I think you'd be fine Evad37. One thing that is of value is that if you are like me you'll have a significant watchlist. I have semiprotected many articles that I have found get hit a lot and eroded before someone posts a request at WP:RPP. Most of the time folks are pretty prompt there but sometimes there can be a lull. Being familiar with how easy or difficult an article is to keep in good nick is helpful there. Also there is always buildup of speedy deletion candidates and expired PRODs. And being a content editor can be helpful and pausing and maybe noting which articles are potentially salvageable. Anyway just my 2c worth. Cas Liber (talk · contribs) 05:50, 19 May 2017 (UTC)

Welcome to WikiProject JavaScript
Thank you for joining up!

If you haven't already, please add WikiProject JavaScript to your watchlist, so you can spot activity on the WikiProject's talk page.

(By the way, there's a new message there now, about jsfiddle). The Transhumanist 21:50, 21 May 2017 (UTC)

XFDcloser
Hi Evad37: XFDcloser is a nice tool, and smooth in operation, so thanks for creating it. I was wondering if it's possible to have the script update the AfD log date when relisting discussions. I had to update the log date manually after I used the script to relist an AfD discussion (diff). North America1000 02:15, 21 May 2017 (UTC)

Page mover granted
Hello, Evad37. Your account has been [//en.wikipedia.org/w/index.php?title=Special%3ALog&type=rights&user=&page=User%3AEvad37 granted] the "extendedmover" user right, either following a request for it or demonstrating familiarity with working with article names and moving pages. You are now able to rename pages without leaving behind a redirect, and move subpages when moving the parent page(s).

Please take a moment to review Page mover for more information on this user right, especially the criteria for moving pages without leaving redirect. Please remember to follow post-move cleanup procedures and make link corrections where necessary, including broken double-redirects when  is used. This can be done using Special:WhatLinksHere. It is also very important that no one else be allowed to access your account, so you should consider taking a few moments to secure your password. As with all user rights, be aware that if abused, or used in controversial ways without consensus, your page mover status can be revoked.

Useful links:
 * Requested moves
 * Category:Articles to be moved, for article renaming requests awaiting action.

If you do not want the page mover right anymore, just let me know, and I'll remove it. Thank you, and happy editing! S warm  ♠  05:25, 1 June 2017 (UTC)

Addition to News and Notes
Hi. Given that it just went out, do you think we could add one more bulletpoint to the Wikipedia Signpost/2017-06-09/News and notes saying: Just to reach anyone who missed the other notices. Thanks! Quiddity (WMF) (talk) 03:20, 9 June 2017 (UTC)
 * Wikimedia Movement Strategy: Join the Cycle 2 of the Wikimedia Movement Strategy discussions (ending 12 June), or Cycle 3 (starting 28 June), and debate about the themes of our strategic directions. More information at Strategy/Wikimedia movement/2017.
 * ✅ - Evad37 &#91;talk] 03:55, 9 June 2017 (UTC)

strategy
At this stage I am in process of writing a report about discussions in Australia about https://meta.wikimedia.org/wiki/Strategy/Wikimedia_movement/2017 the cycle 2 of the broader wikimedia strategy -

You have already been to the Perth meetup about this - but if you at all interested in adding any further insights at this stage - - please feel free to contact on or off wiki - thanks JarrahTree 04:35, 11 June 2017 (UTC)

Thanks for restarting The Signpost
Pardon me if I'm thanking the wrong guy but it looks like you revived The Signpost. Just wanted to say I appreciate the effort it took. Bri (talk) 06:22, 9 June 2017 (UTC)


 * Additional Cheers! for all the "magic" to publish the newest Signpost! Regards, — JoeHebda • (talk) 13:45, 13 June 2017 (UTC)

A barnstar for you!

 * Thanks . For any WP:TPSs out there, this is referring to User:Evad37/MoveToDraft. - Evad37 &#91;talk] 08:39, 21 June 2017 (UTC)

Creating a new script for RFPP similar to XFDCloser?
Hi there. Your XFDCloser script is a great tool for anyone patrolling XFD, helping to do so many things easier. When clerking WP:RFPP just now, I was wondering whether a similar script could be created for RFPP. Currently admins have to edit sections to add a template and then use Twinkle to protect the page and place a protection template. I think all that could be handled by AJAX/JS/API in the background, making it easier to clerk this area. Do you think you could create such a script (and would be willing to do so)? I'd be happy to test it of course. Regards  So Why  14:58, 23 June 2017 (UTC)
 * It should be possible, but might take some time to code up something viable. How multiple page requests should be handled also requires some thought. - Evad37 &#91;talk] 04:59, 24 June 2017 (UTC)
 * Thanks for taking the time. Multiple requests are probably rare enough that the script can ignore them for now. Most requests are made using Twinkle and Twinkle does not allow multiple requests. Regards  So Why  06:52, 24 June 2017 (UTC)

Please check lead section at JavaScript
I heavily revised it. If you have time, please check it for accuracy and flow. Thank you. The Transhumanist 20:34, 26 June 2017 (UTC)

Unlink on Twinkle
You wouldn't happen to contribute to Twinkle too, would you? I miss your upgrades to the unlink function (full removal from navboxes and dab pages) whenever I have to unlink (with Twinkle) outside of your XfD helper... Perhaps there's some way of letting the Twinkle devs know? czar 02:13, 29 June 2017 (UTC)
 * Nah, sorry, I'm not a Twinkle contributor... just a user, and occasionally a re-user of small parts of their code. If you want to ask Twinkle devs about it (WT:TW or their github page), my implementation in the latest version of XFDcloser is lines 1799 to 1918 – more specifically, navbox removal is lines 1874 to 1893, dab removal is lines 1894 to 1899, See also removal is lines 1900 to 1914. - Evad37 &#91;talk] 03:20, 29 June 2017 (UTC)

Is JavaScript untyped, or is it weakly typed?
The article now says it is weakly typed, and I was wondering if that is accurate.

Yes, I know, I'm still a newb. :) The Transhumanist 20:15, 3 July 2017 (UTC)
 * Seems basically right, though it does depend on what you mean by weakly and typed. Programming language has an overview of typed/untyped, static/dynamic, and weak/strong. - Evad37 &#91;talk] 02:41, 4 July 2017 (UTC)

Signpost help - article formatting
Am I supposed to add standard article templates manually to User:22mikpau/Signpost/John Rocco edit-a-thon, or is it done automatically when you publish? Or maybe something else? - Bri (talk) 05:02, 7 July 2017 (UTC)
 * It has to be done manually. Though there probably should be an easier way, maybe ing templates at the top and bottom of the page. - Evad37 &#91;talk] 10:19, 7 July 2017 (UTC)
 * Okay, I manually copied what was generated for this issue's ITM section and made a few tweaks to authors and dates. Let's hope it works when everything is integrated. - Bri (talk) 22:45, 7 July 2017 (UTC)

I tried the source code you provided, but ran into a...
User talk:The Transhumanist/anno.js

I added the ping after I wrote that message, so I don't know if it pinged you or not. The Transhumanist 18:57, 8 July 2017 (UTC)

The menu item being placed on the sidebar menu was messing with the viewport position (the view would jump to there everytime the user pressed the hotkey), so I moved that to one of the tab menus. Your code works approximately - it returns the screen to the relative neighborhood (on the Outline of forestry).

I'll be testing it further over the next few days.

I'll keep you posted. The Transhumanist 17:03, 9 July 2017 (UTC)

Hemisphere specific phrase?
Hey, where I live we call movies released around this time of year "summer blockbusters" which I refrained from using in the Signpost Traffic Report. Is this necessary? Bri (talk) 05:37, 14 July 2017 (UTC)
 * I think it is generally better not to use region-specific phrasing where possible, or otherwise make sure the context is clear... we do cater to a global audience (and its definitely not summer where I am). But with these sorts of questions, you can mostly just follow the MOS – in this case, MOS:SEASON. Thanks, - Evad37 &#91;talk] 02:32, 15 July 2017 (UTC)

Irregular article
I've read the guidelines for submitting an irregular article and got the impression that since I have been writing humorous content then I should not also write irregular content. I have a suggestion OR I can write about Hatnote I use it as a page patrolling tool and sleeping aid.
 * Best Regards,
 * Barbara (WVS) ✐   ✉  11:08, 26 July 2017 (UTC)
 * Um... I'm not entirely sure what you mean. If you want to write humorous content, then it's best to have it in a clearly-labelled section – but just because you have written humorous content (or any 'regular section' content) doesn't mean you can't suggest/write a more 'serious' op-ed or other irregular article. I hope that helps (otherwise I might need some clarification) - Evad37 &#91;talk] 12:46, 26 July 2017 (UTC)
 * That is the answer I was looking for. Are you looking to have what is called an 'irregular' article for the upcoming signpost? Has that writing task been assigned to someone else? I can easily adopt a more serious tone without any problem. I have little extra bit of time this week to put into writing and I thought I would offer to help out by creating content for another article. I can't do it all the time.
 * Best Regards,
 * Barbara (WVS) ✐   ✉  13:02, 26 July 2017 (UTC)

Greetings
I would like to help with the Traffic Report. Where do you get the stats? Best Regards, Barbara (WVS) ✐   ✉  06:10, 16 August 2017 (UTC)
 * Thanks, see the WP:Top 25 Report, which is itself derived from WP:5000. Since the Signpost isn't weekly anymore, perhaps we should be doing do the top ten of each week since the last issue, rather than than the top 25 of one of the weeks. - Evad37 &#91;talk] 00:04, 17 August 2017 (UTC)
 * Hello again. Does this mean that the traffic report should have two tables; or should I combine the top stats from the two week period?
 * Don't want to step on any toes. Barbara (WVS) ✐   ✉  07:58, 17 August 2017 (UTC)
 * Whatever works for you. In the past we've had separate tables, but its okay if you want to combine them. - Evad37 &#91;talk] 09:56, 17 August 2017 (UTC)

Signpost
Hi Evad! I hate to bug you, and understand you are probably aware of this, but there are two (maybe three) submissions at the Signpost submissions desk that are just waiting for someone who has the experience to tell them what the next step is. (also, I will be done with FC, but I don't know what to else do for ITN.) Eddie891 Talk Work 11:16, 24 August 2017 (UTC)
 * I'll have a look over the next few days, or maybe or  can help with feedback and/or copyediting. As for ITM, there's some links at Wikipedia Signpost/Newsroom/Resources that may be of use, and you can check out Press coverage 2017. - Evad37 &#91;talk] 13:08, 24 August 2017 (UTC)
 * Is that the procdure? Ask the folks who have submitted their ideas to write an article? Barbara (WVS) ✐   ✉  17:00, 24 August 2017 (UTC)
 * Maybe just a friendly reminder, if it's been a while since the idea was pitched and there's no submission yet (or not content there). Once its finished being drafted, then the submission should be reviewed for suitability (i.e. 'news'-type items should be relatively neutral and factual, 'opinion'-type items should have a coherent argument and not be antagonistic or overly controversial), clarity, and relevance, and feedback given to the author if there's anything to be improved; also, it should be copyedited, and formatted with Signpost style templates/conventions. - Evad37 &#91;talk] 00:58, 25 August 2017 (UTC)
 * Sounds good. Thanks for being patient with me and my learning curve. I will see what I can do to help. Barbara (WVS) ✐   ✉  01:00, 25 August 2017 (UTC)

The contribution by Eddie891 will take some work but the editor doing it will need some leeway. It's got to be publication-ready without destroying the original intent and tone. I've actually started a couple times then chickened out before hitting Save. ☆ Bri (talk) 18:56, 27 August 2017 (UTC)

MoveToDraft
I am a big fan of your User:Evad37/MoveToDraft script, and have found it very useful. I also made my own version with a modification to the author notification message, as I thought yours was a bit too WP:CRYPTIC for my personal taste.

However, I am messaging you because I am trying to figure out how to create a version which also logs each instance of draftification in a user log (i.e. User:Insertcleverphrasehere/Draftify log) similarly to how twinkle logs CSDs in a CSD log. You can see my very crude efforts at User:Insertcleverphrasehere/gadgets/MoveToDraftTEST.js. For some reason, which will probably be abundantly clear to you, it isn't loading in the 'more' menu at all. I am not a coder really, but have been trying to figure out how to make this work as having a log of Draftifications would be extremely useful to go be able to go back through and check on them later on and see what happens to all of them and to see if the articles got recreated later, etc. Any help you could offer would be invaluable. Thanks. —  InsertCleverPhraseHere (or here)  04:46, 27 August 2017 (UTC)
 * you've got some syntax errors: missing a semicolon at the end of line 28:
 * and missing a comma at the end of line 370:
 * But even if you weren't, you would be literally adding the section header plus wikitext, since you haven't got the  s being replaced with anything, and  is just a template transclusion, so it will always be showing the current date (as of last purge/edit).
 * I can look at adding such a feature to the main script so you don't have to maintain your own fork (unless you want to). And I did code in a way to customise customise the message, but its a bit complicated: you need to add the line  to your common.js, but within your message you need to use   instead of the page title, prevent wikitext transformations on the common.js page itself (i.e.   instead of ,   instead of   for any template substitution), and escape any  s as   to avoid syntax errors. – i.e.
 * before the article title) where you can work on the article with minimal disruption from other users while you improve it. When you feel the article meets Wikipedia's general notability guideline and thus is ready to be published, you can move it back to the article space yourself. However, I recommend that instead of moving it yourself that you follow the prompts on the Articles for Creation template that I have added to the page. This submits the article to be reviewed by experienced editors that specialize in helping new editors write their first articles. \\";
 * - Evad37 &#91;talk] 10:13, 27 August 2017 (UTC)
 * before the article title) where you can work on the article with minimal disruption from other users while you improve it. When you feel the article meets Wikipedia's general notability guideline and thus is ready to be published, you can move it back to the article space yourself. However, I recommend that instead of moving it yourself that you follow the prompts on the Articles for Creation template that I have added to the page. This submits the article to be reviewed by experienced editors that specialize in helping new editors write their first articles. \\";
 * - Evad37 &#91;talk] 10:13, 27 August 2017 (UTC)


 * On the text, I don't see the "at least two" and "move it yourself" clauses being helpful to new users. The point is to direct them towards some help (via AfC) before submitting to mainspace, not to accelerate them into a mess of technicality and policy. If any added length is needed, it should be in suggesting venues where users can request help with sourcing/submitting. czar  17:12, 27 August 2017 (UTC)
 * @Evad, thank you very much for your reply. Thanks for pointing out where I made mistakes with my rather limited coding ability. I would definitely support adding this functionality to the main script for the aforementioned reasons. Perhaps you could add the functionality so that it doesn't log unless a log page is manually created at User/Username/Draftify log, then add a note on the script page stating that to 'opt in' to the draftify log users should create such a page themselves. Either that, or just have the script create the page if it doesn't exist and have it toggleable in some other way so that existing users can opt out if they wish. Thanks for the info about how I can change the display message with var, this is very useful, and I would suggest that info about how to do this be added to the main script page so that users know about it.
 * @, perhaps I could remove the 'at least two' bit, or clarify that it should be "at least two very high quality sources", but I think it helps indicate the level that is necessary to new users. Otherwise you get cases where new users end up scouring for sources and end up including a bunch on inappropriate junk sources in an effort to find as many sources as possible (i.e. I'd prefer a few good sources to a few good sources + a bunch of crap sources). This overlinking of crap sources is a major problem at AfC, where articles often get bogged down with a giant list of facebook and twitter 'sources', which just serve to obfuscate the few good ones and waste other editor's time removing them.
 * The other issue, about "moving it themselves", is intended to give full information to new users as to the options available to them. While AfC is useful, it can also be fairly obstructionist at times, takes quite a while, and new users should not be forced to use it if they don't want to (for example; if they have had a bad experience with it in the past). Personally I don't think it is fair to move a mainspace contribution to draft without informing the user that they have the option to revert my move (If I am allowed to WP:BOLDly move it to draft, they should be informed of their right to WP:BOLDly revert my action). —  InsertCleverPhraseHere (or here)  20:26, 27 August 2017 (UTC)

✅ - Evad37 &#91;talk] 04:38, 28 August 2017 (UTC)
 * Thanks! All works perfectly. Note that you wrote 'var m2d_rationale', but it should be 'var m2d_notification' to insert a change to the author notification (I fixed it above in case any one else uses this thread to do something similar). —  InsertCleverPhraseHere (or here)  06:40, 28 August 2017 (UTC)

Your draft article, Draft:Noongarpedia


Hello, Evad37. It has been over six months since you last edited the Articles for Creation submission or Draft page you started, "Noongarpedia".

In accordance with our policy that Wikipedia is not for the indefinite hosting of material deemed unsuitable for the encyclopedia mainspace, the draft has been nominated for deletion. If you plan on working on it further, or editing it to address the issues raised if it was declined, simply and remove the, , or  code.

If your submission has already been deleted by the time you get there, and you wish to retrieve it, you can request its undeletion by following the instructions at this link. An administrator will, in most cases, restore the submission so you can continue to work on it.

Thanks for your submission to Wikipedia, and happy editing. SwisterTwister  talk  20:48, 9 September 2017 (UTC)

Images
Is there a way to line up images of different sizes? For instance, when someone puts images of different sizes and heights, they line up differently, leaving lots of white space in between. Is that avoidable?Eddie891 Talk Work 14:18, 21 September 2017 (UTC)


 * , not sure of your use case but for most articles, multiple images works well and you can enter the image dimensions to have the template scale to fit automatically czar  03:34, 22 September 2017 (UTC)

Precious four years!
--Gerda Arendt (talk) 05:42, 22 September 2017 (UTC)

Impedehim reversions
Hi - I notice that you recently reverted some edits by User:Impedehim to some Signpost-related pages. Can you please look at this user's projectspace creation (Wikipedia Signpost/Archives/Lacaidonian, duplicated at Dahomean Articles and on his userpage) and do something about them? I'm not too sure if this is G2, G6, or if it must be taken to MFD. – Train2104 (t • c) 03:42, 23 September 2017 (UTC)
 * I've U5'ed the user page, G6'ed the project-basepage as a duplicate, and will leave the Signpost subpage up to you. – Train2104 (t • c) 03:56, 23 September 2017 (UTC)
 * Thanks, all seems to have been dealt with now - Evad37 &#91;talk] 01:48, 24 September 2017 (UTC)

A goat for you!
Great ongoing work with the Signpost.

Ed [talk] [majestic titan] 04:57, 29 September 2017 (UTC) 

Script to format search results as a list of page names with bullet list wikicode provided
I've written a script called StripSearch.js that unclutters search results to make them bare lists of page names.

Now I'm writing a sequel to it called StripSearchInWikicode.js.

I would like the output of search results to look like this:

* [[Benjamin Franklin ]] * [[Larry Page ]] * [[Carl Sagan ]] * [[Hillary Clinton ]] * [[Warren Oates ]]

...for easy copying and pasting into articles.

I'm having trouble manipulating the elements of class "mw-search-result-heading".

I gather that you put them into an array like this:

I'd like to subject the items in that array to a regex, using the jQuery .each method, or the .each function, but I don't know how. The documentation is confusing as hell.

I think the search string  and replacement string   ought to work.

Any pointers would be most appreciated.

Sincerely, The Transhumanist 12:58, 29 September 2017 (UTC)
 * You don't really need anything that complicated – you can just insert content before and after each element with class "mw-search-result-heading" using jQuery's prepend and append methods:
 * just about does the trick. - Evad37 &#91;talk] 13:51, 29 September 2017 (UTC)
 * Or even better
 * (this avoids leaving a space before the ) - Evad37 &#91;talk] 13:53, 29 September 2017 (UTC)
 * (this avoids leaving a space before the ) - Evad37 &#91;talk] 13:53, 29 September 2017 (UTC)
 * (this avoids leaving a space before the ) - Evad37 &#91;talk] 13:53, 29 September 2017 (UTC)


 * You are right, the first method would be perfect if it didn't insert an extraneous space.


 * The second method inserts * unexpectedly on the same line after various entries, like this (searched for "genre"):


 * * Genre
 * * Genre art
 * * Rapping *
 * * Pop music *
 * * Trap music *


 * Is there a way to apply regex, to avoid both problems?


 * Another feature I would love the script to have is to strip redirected entries out of the search results. Those are the  entries that include   inside their divs.  I would like to remove just those instances of.


 * Adding that feature would probably also solve the bug in the second method you presented above.


 * Would  work for this, to hide divs with the class   except for those that do not contain  ?


 * Unfortunately, I don't know how to apply regex to facilitate matches for this type of thing. I can construct regex strings, I just don't know how to put them into play.


 * Forgoing jQuery, I think a for loop could be set up like this:




 * But I don't know how to write the guts.


 * By the way, the script failed when I ran it with that empty for loop, and it failed when I tried sorting the array, like this:




 * It's enough to make one's head spin. :) The Transhumanist 20:50, 29 September 2017 (UTC)


 * Loops and regex aren't always the best tools, especially when working with collections of elements. jQuery has several ways to filter and refine results. One way would be to only apply * to the first-child elements within .mw-search-result-heading like so:
 * Another way, like you alluded to above, is to first remove the searchalttitle elements, and then the * can be added safely:
 * Or to remove instances of mw-search-result-heading which contain searchalttitle you can use :
 * Which can also be written slightly more succinctly like so:
 * Note that you can use  instead of   if you want to be able to show those elements again at some point. - Evad37 &#91;talk] 02:52, 30 September 2017 (UTC)
 * Which can also be written slightly more succinctly like so:
 * Note that you can use  instead of   if you want to be able to show those elements again at some point. - Evad37 &#91;talk] 02:52, 30 September 2017 (UTC)
 * Note that you can use  instead of   if you want to be able to show those elements again at some point. - Evad37 &#91;talk] 02:52, 30 September 2017 (UTC)
 * Note that you can use  instead of   if you want to be able to show those elements again at some point. - Evad37 &#91;talk] 02:52, 30 September 2017 (UTC)

Wow. You make it looks so easy. So, you chain methods to a selector. Nice. That sure is convenient. jQuery is simpler than I thought. When you chain methods to a class, they work on all the elements of that class. I was doing that with hide, but was just copying the examples and didn't really grasp the underlying structure. Thank you. And on retrospect, with loops and regex, it looks like I was trying to conduct surgery with an icecream scoop. :)

I try to follow along in the documentation during these discussions, so that I can grasp the jargon. While doing so, I noticed this:

can be refactored to this:

It seems to work!

The script is now operational, thanks to you. But, I came across an unforeseen obstacle. The results look great on the search results page, but when you copy and paste them into an edit page, there is a blank line between all the entries. That requires that the user regex them all out in WikEd. I'd like to eliminate that manual operation by removing the blank lines in the search results.

Also, when we remove the .mw-search-result-heading entries that contain .searchalttitle, additional blank lines are left behind. Is that a clue that can help us track those newlines (\n) down?

It is not apparent where the newlines are inserted in the page source for the search results page. So, I assume they are specified on a style sheet somewhere. What is the most effective way to hunt down the style sheet which defines a particular class used on a Wikipedia page? The Transhumanist 21:24, 30 September 2017 (UTC)
 * It all seems to be very much browser dependent. Chrome gives me the expected result:

There is a page named "Genre" on Wikipedia
 * Genre
 * Yuri (genre)
 * Film genre
 * Literary genre
 * Harem (genre)
 * Genre studies
 * Music genre
 * Western (genre)
 * Bara (genre)
 * Genre fiction
 * Biblical genre
 * Epic (genre)
 * Genre art
 * Thriller (genre)


 * Firefox adds spaces at the start of each line:

There is a page named "Genre" on Wikipedia

* Genre * Yuri (genre) * Film genre * Literary genre * Harem (genre) * Genre studies * Music genre * Bara (genre) * Western (genre) * Genre fiction * Biblical genre * Epic (genre) * Genre art * Thriller (genre)


 * IE adds several newlines between each item:

There is a page named "Genre" on Wikipedia


 * Genre


 * Yuri (genre)


 * Film genre


 * Harem (genre)


 * Literary genre


 * Genre studies


 * Music genre


 * Bara (genre)


 * Western (genre)


 * Genre fiction


 * Biblical genre


 * Epic (genre)


 * Thriller (genre)


 * Genre art


 * That's all on windows 7. And you're presumably using some other browser/OS combination. Not really sure what the solution is though. - Evad37 &#91;talk] 03:28, 1 October 2017 (UTC)

Arbitrary beak

 * Since the removed items each leave behind a newline, my guess is that it's one newline per div. But what div? There is other formatting there, including alternating background colors, and a solid border between entries. If I can remove the divs that the removed entries were in, that might get rid of some of the extraneous new lines. The rest I won't know until I get a look at the style sheets.  But I can't find the style sheets.  Is there a way to trace a class back to the style sheet it is defined on? The Transhumanist 04:54, 1 October 2017 (UTC)
 * I got rid of the blank lines for the removed items by changing one of your lines of code to this:
 * I'm wondering why the double spacing (extra newline) between list items doesn't show up in the page source. In WikEd, newline characters ("\n") are invisible, but its regex feature finds/replaces them anyways. Maybe the same concept can be applied. The Transhumanist 05:40, 1 October 2017 (UTC)
 * I'm wondering why the double spacing (extra newline) between list items doesn't show up in the page source. In WikEd, newline characters ("\n") are invisible, but its regex feature finds/replaces them anyways. Maybe the same concept can be applied. The Transhumanist 05:40, 1 October 2017 (UTC)
 * I'm wondering why the double spacing (extra newline) between list items doesn't show up in the page source. In WikEd, newline characters ("\n") are invisible, but its regex feature finds/replaces them anyways. Maybe the same concept can be applied. The Transhumanist 05:40, 1 October 2017 (UTC)


 * I tried this to get rid of each \n, and it didn't work:




 * But then I tried it on \s instead, and it got rid of the extra linefeeds (along with all other white space, turning the entries to mush -- separated list items of mush! This shows that the extraneous linefeeds are potentially specifically accessible.).


 * Any ideas? The Transhumanist 11:59, 4 October 2017 (UTC)
 * Tracing styles: A lot of browsers have Web development tools ("dev tools" or "inspectors" or similar) that can show what styles an element currently has, and where they come from (e.g. in Chrome you can right-click on an area you're interested in and select Inspect).
 * Regex:  is equivalent to , so one of those should work. There are various regex-testing website you could use to test, analyse, explain, and experiment with regex patterns – I use https://regex101.com/ (just need to make sure the 'flavor' is javascript), but there are others out there.
 * – Since I didn't have the problem with Chrome on Win 7, and FF/IE had different problems to what you're describing, I think its basically down to either browser bugs (or "features") – possibly MediaWiki is serving up (or the JavaScript modification is making) non-standard/non-compliant code, and the browsers have to decide for themselves how to handle it (thus some insert phantom spaces, others don't). - Evad37 &#91;talk] 13:21, 4 October 2017 (UTC)

Itty bitty little question
Hey Evad, just had a quick script question. I know my js fairly well, but finding the wiki-specific syntax for some things is troublesome. Basically, I cannot figure out the particular syntax for allowing a user to edit a page without being on the edit screen. Just as an example, on User:Primefac/Qwikify.js, what would I need to change to make the edit happen "by itself" so to speak? Thanks! Primefac (talk) 22:19, 8 October 2017 (UTC)
 * To do that you need to use the API, specifically mw:API:Edit. The easiest way I've found is using mediawiki.api resource loader module. So your first line needs to specify the dependency, i.e.


 * Then create an mw.api object, and identify your script/contact details. The same object can be used for multiple requests.


 * Then for your doQwikify function, you use the API to prepend text to the current page:


 * You can do something similar to append, overwrite, or add a new section, and you can specify a section number to work on. For other types of editing, it's a bit more complicated – you have to retrieve the current wikitext first, make your changes, and then send it back. - Evad37 &#91;talk] 00:54, 9 October 2017 (UTC)
 * Mostly looking at pre/appending, so that should work. Thanks! Primefac (talk) 00:56, 9 October 2017 (UTC)

Signpost and the Visual Editor
Just FYI, someone is asking about this VisualEditor/Feedback here Kerry (talk) 00:42, 9 October 2017 (UTC)
 * Thanks for the pointer Kerry - Evad37 &#91;talk] 03:03, 9 October 2017 (UTC)

WP Military history
Greetings Evad, I am a coordinator of WikiProject Military history. Recently, the project reached a milestone of 1000 Featured articles in the project's scope, of the approx. 5300 FAs on en Wiki. So in this context, we're hoping to take this news to the Signpost. Looking forward for you help in this, in the sense, how it can be done? Regards, Krishna Chaitanya Velaga (talk &bull;&#32;mail) 03:52, 8 October 2017 (UTC)
 * If you are okay with a brief mention, we can put something in the News and notes section. - Evad37 &#91;talk] 02:45, 9 October 2017 (UTC)
 * Sure Evad, please let me know if in case any information is required. Regards, Krishna Chaitanya Velaga (talk &bull;&#32;mail) 11:50, 9 October 2017 (UTC)

Problem with your edit to Template:Mapbox
Hi. Your recent edit to Template:Mapbox introduced a problem with some articles. The template no longer automatically retrieves the Wikidata ID for the current page and thus fails to generate a map. North Shore railway line is an example of an article affected by this. Gareth (talk) 10:12, 20 October 2017 (UTC)
 * . - Evad37 &#91;talk] 07:59, 21 October 2017 (UTC)

Signpost script
It looks like Wikipedia Signpost/2017-10-23 is created before the others, because when I browsed to it there were broken red links. Maybe you could have the script purge that page after everything is created? Just letting you know! :) &mdash; MusikAnimal  talk  03:21, 23 October 2017 (UTC)
 * The script does purge a whole lot of pages, but apparently I missed that one out – will fix for next time. Thanks, Evad37 &#91;talk] 03:29, 23 October 2017 (UTC)

first try of rater

 * put into common js
 * re-jigged
 * opened at https://en.wikipedia.org/wiki/Category_talk:Philemon_(genus)
 * drop down box showed (nice box)
 * added birds project as in
 * saved change
 * didnt show on talk as an edit
 * had to apply again manually
 * very exciting when it gets to work properly !!!!

JarrahTree 06:16, 7 November 2017 (UTC)


 * was on main space side and not open to edit


 * however got it to work in edit mode on talk page side with


 * https://en.wikipedia.org/w/index.php?title=Talk:1954_Asian_Baseball_Championship&action=edit

JarrahTree 06:31, 7 November 2017 (UTC)


 * Not sure what happened the first time. I thought it might have to do with the talk page not existing, but I was able to tag the sandbox Category:X1 (which at the time didn't have a talk page). The script should work regardless of whether you're on a subject-space page or talk-space page, and regardless of whether you're in read, edit, or history mode. - Evad37 &#91;talk] 07:13, 7 November 2017 (UTC)


 * https://en.wikipedia.org/wiki/Category_talk:Lichmera
 * at main space and tried to add wikiproject birds in curly brackets (might that be the problem?)
 * registered an edit - but nothing there ? JarrahTree 07:45, 7 November 2017 (UTC)
 * it was doesnt want curlies - working fine now- JarrahTree 07:47, 7 November 2017 (UTC)

my recent contribs as a good example of project tagging from the main page - very impressed JarrahTree 07:54, 7 November 2017 (UTC)
 * well done!

Future of outlines
Hi Evad,

Here's a summary/update on my script writing efforts, in case you would like to provide insight of any kind...

I'm in the process of building scripts for viewing outlines and for outline development.

So far, there is:
 * User:The Transhumanist/OutlineViewAnnotationToggler.js – this one provides a menu item to turn annotations on/off, so you can view lists bare when you want to (without annotations). When done, it will work on (the embedded lists of) all pages, not just outlines. Currently it is limited to outlines only, for development and testing purposes. It supports hotkey activation/deactivation of annotations, but that feature currently lacks an accurate viewport location reset for retaining the location on screen that the user was looking at. (The solution you provided gets it in the general vicinity). The program also needs an indicator that tells the user it is still on. Otherwise, you might wonder why a bare list has annotations in edit mode, when you go in to add some. :) Though it is functional as is. Check it out. After installing it, look at Outline of cell biology, and press . And again.
 * User:The Transhumanist/RedlinksRemover.js – strips out entries in outlines that are nothing but a redlink. It removes them right out of the tree structure. But only end nodes (i.e., not parent nodes, which we need to keep). It delinks redlinks that have non-redlink offspring, or that have or are embedded in an annotation. It does not yet recognize entries that lack a bullet (it treats those as embedded).

It is my objective to build a set of scripts that fully automate the process of creating outlines. This end goal is a long way off (AI-complete?). In the meantime, I hope to increase editor productivity as much as I can. Fifty percent automation would double an editor's productivity. I think I could reach 80% automation (a five-fold increase in productivity) within a couple years. Comments and suggestions are welcome.

Then there's the recent script you helped me on (above). It's working pretty good:
 * User:The Transhumanist/StripSearchInWikicode.js – another script, which strips WP search results down to a bare list of links, and inserts wikilink formatting for ease of insertion of those links into lists. This is useful for gathering links for outlines. It still has the interlaced CR/LFs problem.  Aside from that, I'd like this script to sort its results. So, if you know how, or know someone who knows how, please let me know.

Script and script feature requests (for outlines) are welcome. The Transhumanist 10:51, 26 October 2017 (UTC)
 * I've had a thought on how to fix the stripsearch script: What it should do is make an array containing the search result titles - which can be sorted and otherwise manipulated using standard array methods - and then remove all the search result stuff, and rebuild the links from the array in the format you want. jQuery's .map or .get functions should be able to make the array. - Evad37 &#91;talk] 00:34, 27 October 2017 (UTC)
 * Thank you for the guidance. How would you "rebuld the links from the array"? The Transhumanist 02:19, 27 October 2017 (UTC)
 * You can make links from page titles using code like I've got in User:Evad37/extra.js's makeLink function. But in your case you need to also surround the link with  and , and have the whole thing within a block tag like &lt;div> or &lt;p>. Do that for each item in the array, and then you can add them all to (or next to) an element on the page using a jQuery method like .before, .after, .prepend, or .append, each of which can take an array as the input. - Evad37 &#91;talk] 02:40, 27 October 2017 (UTC)
 * I'll try it. But first, I've encountered a glitch in the seemingly straight forward approach of getting elements into an array by wrapping them in a jQuery object as described at https://learn.jquery.com/using-jquery-core/jquery-object/#getting-elements-into-the-jquery-object. I immediately discovered that the elements I want are, but that there is more than one set of li's on the page. How do I fetch just the set of li's that are within the element  ? The Transhumanist 07:01, 28 October 2017 (UTC)
 * You can select that ul, and then use  to get the li's within it, i.e.   - Evad37 &#91;talk] 07:12, 28 October 2017 (UTC)


 * Okay, so I tried this to see what was in the array:



var results = $('ul.mw-search-results').children; alert( results );


 * And all that it showed was "[object Object]". The Transhumanist 07:56, 28 October 2017 (UTC)
 * alert is only good for strings. For arrays and objects, you have to log them to the browser console using e.g.  (and have the console open, see ). Plus the   in this case would be a jQuery object, not an array – to get an array from a jQuery object you need to use .map  (or something similar) - Evad37 &#91;talk] 08:09, 28 October 2017 (UTC)


 * Shows this in the console:
 * I have no idea how to use .map to display the actual array. I can't write code to work on the array if I can't even see it. Please excuse my newbness. :) The Transhumanist 08:48, 28 October 2017 (UTC)
 * I have no idea how to use .map to display the actual array. I can't write code to work on the array if I can't even see it. Please excuse my newbness. :) The Transhumanist 08:48, 28 October 2017 (UTC)

Thats okay. Here's my solution, I'll walk you through it below: - Evad37 &#91;talk] 02:54, 29 October 2017 (UTC)
 * 1) The  selects the &lt;ul&gt; with the class "mw-search-results".
 * 2)  then selects the children elements of that &lt;ul&gt;, which we know will be the &lt;li&gt; elements. If instead of continuing, you logged to console at this point, you should get a similar result to what you had above, but with li's that can expanded to see what's inside them.
 * 3)  takes a function as an input, and applies it to every element in that's selected.
 * 4) *Within the function, the context (i.e. the  keyword) refers to the element that is being worked on – in our case, each &lt;li&gt; element.
 * 5) *To be able to use jQuery methods, we select the element using
 * 6) * selects the &lt;a&gt; element within the &lt;li&gt; element
 * 7) * retrieves the text between the  tags
 * 8) *The function is repeated for each element within the jQuery object (the li's from )
 * 9)  transforms the jQuery object into a plain javascript array. Depending on what you want to do, this step isn't always neccessary - the data is stored with incremental numeric keys, so can be accessed like an array, and there is a   property, so you can do a for loop like   But available methods will be jQuery methods, not native array methods like
 * I had some time, so I did the whole thing for you: User:Evad37/StripSearchSorted.js - Evad37 &#91;talk] 03:29, 2 November 2017 (UTC)
 * Wow. That is sleek! Solves many problems. And you've paved the way for the next round of search scripts and features. For example, I plan to adapt your use of an array to filter out WP search's "intitle:" bug. I'll keep you posted. The Transhumanist 00:06, 6 November 2017 (UTC)

Giving an id to .after
Evad,

You used .after to add modified results for the search. I need a way to remove those results later so I can restore the original results...

I'm utilizing your code in User:The_Transhumanist/StripSearch.js (the unsorted version), in a toggle to turn stripping on and off.

To make it work, I need a way to .remove the stuff you added with .after.

Assuming an id of "Stripped", I'd like to do this:

How would you assign the id of "Stripped" to the contents of the .after chain so that it can be removed in this way? The Transhumanist 21:06, 7 November 2017 (UTC)


 * I figured it out (created a jQuery object, stuck that on with .after, and then appended the stripped search results to the jQuery object):




 * The script as a whole is very cludgy, and desperately needs refactoring, but it seems to be working!


 * The version discussed above is https://en.wikipedia.org/w/index.php?title=User:The_Transhumanist/StripSearch.js&oldid=809253595 The Transhumanist 23:06, 7 November 2017 (UTC)

Request for advice...
What I'd like to do is fork StripSearch.js to create User:The Transhumanist/SearchSuite.js and add some more toggles (as menu items).

The first one I would like to add is a menu item for turning the sorting of search results on/off. It will sort the results whether or not they've been stripped yet.

Another one will insert/remove wikilink formatting. (Not everyone will want the link delimiters displaying all the time).

And more.

My question for you is this: what do I need to think about in approaching the writing of this script, with its various menu item features (that are intended to work together)?

I look forward to reading your thoughts on this matter.

Sincerely, The Transhumanist 22:51, 8 November 2017 (UTC)


 * I think the basic approach to this would be to set classes for elements you want to show/hide, because then the code for the menu items themselves becomes really easy: when clicked, you just hide/show the relevant classes, i.e.   and   for elements that should be shown/hidden when foo is activated (and then reversed when foo is turned off). Sorting is going to more tricky to do/undo, but basically you would store data about the original order, then write functions like sortAlpha and sortOrig that would operate on the containing element, replacing it's contents with sorted contents. For a simpler example, to sort the links in the toolbox, you could do   (which does half the job – sorting alphabetically, but not returning to the original order)  - Evad37 &#91;talk] 03:28, 9 November 2017 (UTC)
 * Thank you. What about saving the unsorted version to a variable, and swapping it out when the user wants to undo the sort? The Transhumanist 04:14, 9 November 2017 (UTC)
 * I think setting a data-* attribute (e.g. data-origsort) for each element makes more sense, which would allow you to do something like  (sticking with the example of the toolbox links) - Evad37 &#91;talk] 17:09, 9 November 2017 (UTC)
 * What should I be wary of in designing features that work together and operate on each others' results? The Transhumanist 15:14, 9 November 2017 (UTC)
 * I'm not really sure, just be aware anything one feature might change has to be accounted for when coding the other features. - Evad37 &#91;talk] 17:09, 9 November 2017 (UTC)

Another request for advice (on menu item chaos)
Development of SearchSuite.js is underway.

The function guts are temporary, for testing of menu items.

I'm trying to get the menu items placed correctly on the sidebar, but they keep jumping around when you click them. I'd like to place them relative to each other, but they don't seem to be recognizing each other's IDs. But they do recognize #t-print (Printable version). As a test, I currently have them all set to position themselves relative to #t-print. They can see that ID just fine.

For some reason, the new menu items don't show up on the page source. Maybe that has something to do with it?

Another challenge is that I want the "SR wikify" menu items to be displayed only when the "SR detail (turn off)" menu item is displayed. But I can't hide them by referencing their ID. just doesn't work. Nothing happens.

I look forward to your reply. The Transhumanist 11:35, 11 November 2017 (UTC)
 * Easy things first:  doesn't work because the end brackets are missing – ie, it should be.
 * For menu item positioning, are you sure the IDs are actually present in the page at the time each  is executed?
 * Additionally, what you are currently doing is adding and removing menu items (and re-adding them and re-removing them) each time one of the functions runs. Which means that you have to get the positing (i.e. the last argument passed to  right every time, without knowing what that should be (or not easily knowing, as it depends on which other menu items are currently there). What I would do instead is, in the setup phase, add all the menu items that might be needed at some stage, in the order that you want them, and  –ing ones that shouldn't be displayed just yet. Then, in the functions, instead of removing or menu items you just   or   them as needed. - Evad37 &#91;talk] 13:39, 11 November 2017 (UTC)
 * I was using hide/show to remove a menu item in a couple of the subroutines, but there was a typo in the id calls. That is fixed now, and the "SR wikify" menu item disappears/reappears as it should based on which "SR detail" menu item is present.
 * Though initial placement of menu items still isn't working right. I'm not sure placing menu items in the set up and hiding them later (as you suggested above) will work, because there are 2 functions and 2 menu items (toggled) for each feature provided by the script. When a menu item that says (turn on) is clicked, it is replaced by a menu item that says (turn off). The script doesn't have to discern between the menu items of a pair, as they each have the same id (those shouldn't conflict, because only one or the other is present at any given time).
 * It's probably another typo. :)
 * Besides all of that, one particularly pernicious problem that I have is that I can't figure out what 'e' is or how preventDefault works (even after googling the hell out of them). This makes the workings of the menu items very mysterious. I'll track down intelligible explanations eventually, or it may at some point just *click*. :) The Transhumanist 20:11, 12 November 2017 (UTC)
 * P.S: Okay, I found the problem(s). The order in which the subroutines were called affected the placement, and one of the anchors had to be changed. Initial placement works! Menu item chaos solved. Talking it out with you helped immensely. The Transhumanist 20:27, 12 November 2017 (UTC)
 * P.P.S.: You were right, two of the menu items kept leap frogging each other, even after the above fixes. So, I've placed an if/else construct. Problem solved. Though it feels very clunky. Not sure how your show/hide approach above would be implemented. Though once I figure it out, I'll give it a try. The Transhumanist 20:52, 12 November 2017 (UTC)
 * I can't figure out what 'e' is or how preventDefault works 'e' is a jQuery event object, which is basically a wrapper for a DOM event that has cross-browser compatible methods. preventDefault stops the default action from occurring: e.g. for a link that is clicked, the default action is to load the specified url. By using e.preventDefault it means we can safely do whatever we want to do when the link is clicked. Though it is not always necessary, e.g. if you're sure there is no default action (like clicking on a plain text element), or if you don't mind the default action occurring (like clicking on a same-page section link, where the default action just scrolls the page and adds/changes the # part of the url) - Evad37 &#91;talk] 00:54, 13 November 2017 (UTC)

Status report
StripSearchSorted.js is now on a switch. The Transhumanist 08:00, 10 November 2017 (UTC)

Signpost ready
Hi Evad37,

I have updated the signpost draft. I think it should be ready to review. Could you take a look at it, and let me know anything that I need to work on? Thank you! Bobo.03 (talk) 03:05, 8 November 2017 (UTC)
 * Thanks Bobo, will have a look later today - Evad37 &#91;talk] 05:04, 8 November 2017 (UTC)
 * Great, thank you! Any update on this? Bobo.03 (talk) 00:48, 14 November 2017 (UTC)
 * Hi sorry for not getting back to you sooner. It looks pretty good, will just need some Signpost templates/formatting (I can take care of that), and maybe some minor style editing or copyedits. Will keep you posted if there's anything else that needs your attention. Thanks, - Evad37 &#91;talk] 01:49, 14 November 2017 (UTC)
 * Sounds good. Thank you! I wonder when the next Signpost would be published? Looping in the update. Bobo.03 (talk) 02:54, 14 November 2017 (UTC)
 * Thanks ! :) Megalibrarygirl (talk) 17:34, 14 November 2017 (UTC)
 * I like it, especially seeing as there are so many superheroes using the new resource. ;) Megalibrarygirl (talk) 17:35, 14 November 2017 (UTC)
 * I noticed you made it to the Signpost format. Thank you, Evad37! I just had another pass on it for copyedit. if you have a chance, could you help on copyedits? Thank you!
 * As the draft seems in a good shape, I want to make sure it published in the next Signpost issue.. Thank you! Bobo.03 (talk) 02:39, 17 November 2017 (UTC)
 * Thanks Bobo.03 and Megalibrarygirl; and yes, it will go out with the next issue - Evad37 &#91;talk] 02:24, 19 November 2017 (UTC)
 * That's great. Thank you! Bobo.03 (talk) 21:02, 19 November 2017 (UTC)

Old rater vs new rater.
There are no two ways about it, your new rater is just better in pretty much every way than the old, discontinued one. There are actually not that many people who still have Kephir's rater installed, at least among those that have included a backlink as suggested (I'm not sure how to check how many people have it installed without a backlink). I suggest sending personal messages to each of these folks. —  Insertcleverphrasehere (or here)  03:12, 23 November 2017 (UTC)
 * Actually, there are quite a few more at (including me :), perhaps we should ask someone with mass message sending privileges to send out a small template? —  Insertcleverphrasehere (or here)  03:16, 23 November 2017 (UTC)
 * With a search I get about 300 results. Once the Rater is further developed/stable, we can propose redirecting the old script, like how closeAFD was redirected to XFDcloser - Evad37 &#91;talk] 03:20, 23 November 2017 (UTC)

My edit and query
Hi, Evad: I did worry momentarily about calling him a "sleazeball"—I guess no one's going to sue under the circumstances. Please check my edit of the wording aside from that ("could" seemed a little ambiguous to me). Thx. Tony  (talk)  02:52, 24 November 2017 (UTC)
 * Your edits look good, thanks - Evad37 &#91;talk] 02:57, 24 November 2017 (UTC)

a drum roll for you

 * richer than a gold stealers clearing house pub, the rater is the best thing in 10 years for project tagging ever, thank you for your efforts and labour to help make project tagging great again!!!

JarrahTree 05:23, 24 November 2017 (UTC)

New Page Reviewing
If only to test out the rater tool 'in the wild'. (sorry the above template is a bit boilerplate but it has all the links) —  Insertcleverphrasehere (or here)  09:22, 28 November 2017 (UTC)

New Page Reviewer granted
Hello Evad37. Your account has been added to the " " user group, allowing you to review new pages and mark them as patrolled, tag them for maintenance issues, or in some cases, tag them for deletion. The list of articles awaiting review is located at the New Pages Feed. New page reviewing is a vital function for policing the quality of the encylopedia, if you have not already done so, you must read the new tutorial at New Pages Review, the linked guides and essays, and fully understand the various deletion criteria. If you need more help or wish to discuss the process, please join or start a thread at page reviewer talk. The reviewer right does not change your status or how you can edit articles. If you no longer want this user right, you may ask any administrator to remove it for you at any time. In case of abuse or persistent inaccuracy of reviewing, the right can be revoked at any time by an administrator. Alex Shih (talk) 17:26, 28 November 2017 (UTC)
 * Please consider helping get the huge backlog down to a manageable number of pages as soon as possible.
 * Be nice to new users - they are often not aware of doing anything wrong.
 * You will frequently be asked by users to explain why their page is being deleted - be formal and polite in your approach to them too, even if they are not.
 * Don't review a page if you are not sure what to do. Just leave it for another reviewer.
 * Remember that quality is quintessential to good patrolling. Take your time to patrol each article, there is no rush. Use the message feature and offer basic advice.

Script to convert headings to list items (and back again) in outlines
Outlines (e.g., Outline of Japan) are essentially big long bullet lists broken up by headings.

I'd like a viewing script (that does not edit the page's saved wikicode), that does the following to viewed outlines:

On "Outline of" pages only, I'd like a menu item toggle that converts the headings so that they are integrated into the overall bullet list on the page, as list items. Clicking the menu item again would turn the page back to normal (to heading format). Like my other scripts, the status should be remembered between pages (so that all outlines get viewed the same way).

When turned on, the page's content will be one long indented bullet list. H2 headings would be converted to list items with one bullet, H3 with two bullets, etc. The subsection edit link should be retained.

Any bullet item trees beneath a converted heading would have to also be adjusted to start out with one more bullet than the heading they belong to, otherwise, the level indications will be off.

I started picking away at this project in User:The Transhumanist/OutlineViewConventional.js, but have realized it is way beyond my skill level. The Transhumanist 23:34, 3 December 2017 (UTC)
 * That does seem a bit complicated. If I understand correctly, you want to do the following sort of transformation to the page html:


 * If so, then the basic approach would be to get all the content between heading tags of the same level, and wrap it inside list tags like  and   (doing the same for all headings on the page). Going back would be a matter of moving the heading text back into appropriate heading tags, and removing the added   and   tags (but not the original content). Does that give you some ideas? - Evad37 &#91;talk] 08:52, 5 December 2017 (UTC)
 * I missed the li part. Thank you. By the way, what about the rest of the bullets? Will their indents be adjusted automatically? The Transhumanist 05:04, 6 December 2017 (UTC)
 * Yes, indentation is automatic - Evad37 &#91;talk] 05:52, 6 December 2017 (UTC)
 * Thank you. The Transhumanist 12:05, 7 December 2017 (UTC)

Adding a filter to StripSearchSorted.js
There's a really annoying design flaw in WP's search's intitle feature. Common words like "of" are ignored, even though they are included within a quoted phrase. So, intitle:"of Boston" is interpreted as just intitle:Boston. And the search results are filled with non-matching results. To make matters worse, the search results include matches of the phrase in the contents of pages, watering the results down even more to inlcude pages that don't even have "Boston" in the title. What I need is for results to strictly match the term provided after "intitle:".

For StripSearchSorted.js, you wrote a long sequence of chained methods (which I modified ever so slightly):

Is it possible to continue adding to this chain in order to filter the array down to elements that only include the intitle search string?

Assume we've put the search string into a variable, say

After the closing parenthesis (included below), the .filter chain continuation might look something like this:

The problem is, I don't know what to put after "this." to match intitleString. I know regex generally speaking, but I don't know how to include it in a chain, or how to match a variable with it.

By the way, would this nuke the array if intitle wasn't specified in the search? Can an if control structure be put in a chain? (Like: If "intitle" is in the title, do this). The Transhumanist 12:05, 7 December 2017 (UTC)
 * Filtering is possible, but it's easier to do the filtering before the .map, because at that stage you have a plain array of strings (each of which is a title), rather than an array of jQuery objects (which you have to drill down into to get the title string). When filtering on a plain javascript array, don't use  (that only works with jQuery objects) – the basic syntax is


 * To check if a string contains a test string, you can do, which returns -1 if not found, or a number of where it is found. To convert to a true/false value; you just do  . That's for case-sensitive results, and dosen't care about word boundaries. To do more advanced matching, you have to make a regex object, and then test for a match using  , which returns true or false accordingly.
 * So putting it all together, elswehere in your code you make your regex pattern, then


 * To stop things blowing up, you just have to make sure everything passes the filter when there's no intitle: in the search, i.e. set  or   for that case. You can't really have control structures in a chain – you would have to store the intermediate value of the chain in a variable, then put in the control structure, and resume the chain from the intermediate variable. Like


 * - Evad37 &#91;talk] 02:34, 8 December 2017 (UTC)


 * So, let me see if I got this straight...


 * You store the search's intitle value in a variable, and if there isn't one, the variable's value would just be null.


 * Then, in the chain, filter out non-matching entries. If the variable has a null value, meaning that intitle wasn't included in the search, all entries would match.


 * Is that correct? The Transhumanist 21:50, 10 December 2017 (UTC)
 * Not quite...  doesn't match anything, so no entries would match. To get all entries to match, you either have to set the variable to something that does actually match any entry (  or   depending on whether you use indexOf or regex matching inside the filter); or else have an explicit check inside the filter which will just return true if the variable is null. - Evad37 &#91;talk] 03:02, 11 December 2017 (UTC)
 * So, there is no way to match null in regex? So you can't match null or whatever the string is, using the pipe character? The Transhumanist 04:26, 11 December 2017 (UTC)
 * If you want to check if a variable is null or undefined, just do  (gives true if someVar is null/undefined, false otherwise). You can combine this with other logical tests using  ,   ,   as usual. - Evad37 &#91;talk] 04:37, 11 December 2017 (UTC)

New Page Reviewer Newsletter
Hello, thank you for your efforts reviewing new pages!

Backlog update: Outreach and Invitations:
 * The new page backlog is currently at 12713 pages. Please consider reviewing even just a few pages each day! If everyone helps out, it will really put a dent in the backlog.
 * Currently the backlog stretches back to March and some pages in the backlog have passed the 90 day Google index point. Please consider reviewing some of them!
 * If you know other editors with a good understanding of Wikipedia policy, invite them to join NPP by dropping the invitation template on their talk page with: . Adding more qualified reviewers will help with keeping the backlog manageable.

New Year New Page Review Drive
 * A backlog drive is planned for the start of the year, beginning on January 1st and running until the end of the month. Unique prizes will be given in tiers for both the total number of reviews made, as well as the longest 'streak' maintained.
 * Note: quality reviewing is extremely important, please do not sacrifice quality for quantity.

General project update: If you wish to opt-out of future mailings, go here. —  TonyBallioni (talk) 20:27, 12 December 2017 (UTC) 
 * ACTRIAL has resulted in a significant increase in the quality of new submissions, with noticeably fewer CSD, PROD, and BLPPROD candidates in the new page feed. However, the majority of the backlog still dates back to before ACTRIAL started, so consider reviewing articles from the middle or back of the backlog.
 * The NPP Browser can help you quickly find articles with topics that you prefer to review from within the backlog.
 * To keep up with the latest conversation on New Pages Patrol or to ask questions, you can go to Wikipedia talk:New pages patrol/Reviewers and add it to your watchlist.

Wiki Loves Monuments
I tried but couldn't find information on this contest to put into the gallery article. Best regards, Barbara (WVS) ✐ ✉ 01:12, 16 December 2017 (UTC)

Update from Signpost newsroom
The next issue of The Signpost is pretty much wrapped up except for News and Notes which you were working on last. I'm available for about 2-3 hours then will be out of pocket for the rest of the day (Pacific Time). ☆ Bri (talk) 19:30, 16 December 2017 (UTC)
 * Oops, Technology Report is also incomplete. But everything else is ready. ☆ Bri (talk) 19:55, 16 December 2017 (UTC)

ITM glitch?
There may have been some newsroom notes left in ITM:The "Wikipedia Seagull". The four bullets at the end of the text look out of place. ☆ Bri (talk) 07:06, 18 December 2017 (UTC)
 * Thanks; I've taken them out now - Evad37 &#91;talk] 07:09, 18 December 2017 (UTC)
 * One other glitch in ITM, a redlink to next issue/Blog appears to be an artifact of publication. ☆ Bri (talk) 07:14, 18 December 2017 (UTC)
 * - Evad37 &#91;talk] 07:16, 18 December 2017 (UTC)

Extra newlines mystery partially solved and partially fixed
When copying search results from the various StripSearch scripts, or the new CatTree script mentioned above, I was running into a problem in which an extraneous newline was being added after every entry.

I've discovered that it doesn't happen in the regular editor, or in off-line editors.

It only happens in WikEd. But, when you click on undo, the extra newlines disappear!

That's weird. Any idea why it is happening? The Transhumanist 05:22, 19 December 2017 (UTC)

Merry Christmas!
 Merry Christmas !!

Hi, I wish you and your family a very Merry Christmas and a very Happy New Year,

Thanks for all your help and contributions on the 'pedia! ,

– Davey 2010 Merry Xmas / Happy New Year 13:38, 23 December 2017 (UTC)

Happy holidays
I'm having a merry Christmas and I hope you have a good day today and a happy new year. Thanks for working with me over the past year on the Signpost. Keep up the good work. SchreiberBike &#124; ⌨  23:06, 25 December 2017 (UTC)

New Years new page backlog drive
Hello, thank you for your efforts reviewing new pages!

Announcing the NPP New Year Backlog Drive!

We have done amazing work so far in December to reduce the New Pages Feed backlog by over 3000 articles! Now is the time to capitalise on our momentum and help eliminate the backlog!

The backlog drive will begin on January 1st and run until January 29th. Prize tiers and other info can be found HERE.

Awards will be given in tiers in two categories:


 * The total number of reviews completed for the month.
 * The minimum weekly total maintained for all four weeks of the backlog drive.

NOTE: It is extremely important that we focus on quality reviewing. Despite our goal of reducing the backlog as much as possible, please do not rush while reviewing.

If you wish to opt-out of future mailings, go here. — TonyBallioni (talk) 20:24, 30 December 2017 (UTC)