This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Evad37,
Have a prosperous, productive and enjoyable
New Year, and thanks for your contributions to Wikipedia.
Eddie891
Talk
Work 00:00, 1 January 2018 (UTC)
Send New Year cheer by adding {{ subst:Happy New Year fireworks}} to user talk pages.
In StripSearchSorted.js we added bullets and double square brackets for copying linked items straight off the page for pasting into an editor.
Now I've started ViewAsOutline-CategoryTree.js to do that in the Special:CategoryTree utility. But, the display starts out collapsed, with very few article names showing. Clicking on each category to expand them is very tedious, so I included a menu item to expand all of the categories at the same time (one level at a time) and another to collapse them (so far, all at once). There is also a menu item for adding wikilink formatting, and another to hide it.
The problem I've run into is, once you click on the Wikicodify menu item, further expanding and collapsing do not work. If you get the categories you want showing before you Wikicodify, you're fine. But if you don't, you have to reload the page and start all over again.
I think it has something to do with the "Brackets" class I added in this version. I stuck that class in there so that Wikicodify wouldn't match the entries that it already inserted link formatting into, so that it wouldn't insert it again. I was expecting to be able to further expand the category tree after the insert operation, but unexpectedly nothing happens when you click on the expand or collapse menu items after that.
When you have time, please take a look under the hood, and let me know what you make of it.
To help get the gist of the program, user instructions are posted at User_talk:The_Transhumanist/ViewAsOutline-CategoryTree.js#Description_/_instruction_manual
The Transhumanist 17:40, 16 December 2017 (UTC)
cont.outerHTML = cont.outerHTML.replace
... line. Rewriting the <a> tags is definitely not something the categoryTree.js expects. You might want to try only modifying the text within the <a> tags, and not the tags themselves. Or only adding stuff before and after the tags (i.e. with jQuery methods) and not rewriting the tags using regex. -
Evad37 [
talk 15:07, 1 January 2018 (UTC)Hi Evad,
Given your position as editor-in-chief over at Signpost, and the time pressure regarding the specific item which I have nominated (the annual version of the Top 25 Report), I felt that it might be a good idea to alert you directly to the submission, as it diminishes in interest as the days go by.
Happy new year! - Stormy clouds ( talk) 00:25, 4 January 2018 (UTC)
By the way, do I need to load any dependencies for the following code?
// ============== activation filters ==============
// Only activate on Vector skin
if ( mw.config.get( 'skin' ) === 'vector' ) {
Do all "mw." lines have dependencies? The Transhumanist 13:40, 1 January 2018 (UTC)
mw.config
is always available, and contains lots of other useful stuff – see
mw:mw.config. Other mw modules, detailed at
mw:ResourceLoader/Core modules, aren't necessarily available unless you load them – see
mw:ResourceLoader/Migration_guide_(users)#mw.loader for further details. -
Evad37 [
talk 14:10, 1 January 2018 (UTC)
Hi Evad, I want to thank you for your diff viewer, and for being so kind to create it when someone asked. That was very nice of you. All the best, SarahSV (talk) 04:49, 6 January 2018 (UTC)
User talk:The Transhumanist/ViewAsOutline-AllPagesWithPrefix.js
This script disappears the bullets from the "All pages with prefix" page, and inserts wikicode formatting for list items for easy copying and pasting into a wiki-editor. Useful for building lists and outlines. The Transhumanist 05:31, 5 January 2018 (UTC)
Created 2 more scripts, that make similar conversions to 2 other types of pages:
Made possible by your generous instructions. Thank you. The Transhumanist 08:05, 6 January 2018 (UTC)
P.S.: I was pleasantly surprised that .find
creates an array.
There were two outspoken commentators at the Mister Wiki workshop with what looks to me like incompatible points of view. I'd like to ask each of them for a 250 word response/op-ed to include in the article (the article is about 500 words now). Is that kosher? ☆ Bri ( talk) 20:40, 11 January 2018 (UTC)
Salvidrim! asked if he can contribute as well. I'm inclined to say "no" as it was just an invitation to two opposing views from the workshop participants, to make it digestible and not a re-litigation of the case. But I'd like to hear what you think of that request. ☆ Bri ( talk) 20:58, 11 January 2018 (UTC)
For example, the
Glossary of architecture has a newline between all the dt and dd elements (in the rendered output). More specifically, between "</dt>
" and "<dd
" in each glossary entry.
How do you get rid of just those newlines? (And no others).
I tried this, to replace the newline (and anything else between the elements) with " – ", and it didn't work:
// Strip out the newlines after dt elements
var mwContentLtr = document.getElementsByClassName( "mw-content-ltr" );
mwContentLtr0].outerHTML = mwContentLtr0].outerHTML.replace(/(<\/dt>).*?(<dd)/g,'$1 – $2');
Note that there is only one mw-content-ltr on the page. The Transhumanist 14:30, 6 January 2018 (UTC)
$('dd, dt').css('display','inline');
gets rid of all the visual newlines... but that makes everything go onto one line, effectively. But you can add linebreaks after each dd: $('dd').after('<br>');
. And to get the ndashes after each dt: $('dt').after(' – ');
. And to remove the spacing before the dd elements: $('dd').css('margin-left','0');
. So putting it all together into just two lines of code:$('dt').css('display','inline').after(' – ');
$('dd').css({'display':'inline', 'margin-left':'0'}).after('<br>');
Dear Evad,
Happy Hollidays! I hope yours went well.
I've been spending mine banging my head against some new scripts. And I've run into an enigma...
I'd like to remove the bullets from unordered lists, and the following code doesn't have any effect:
// Make the bullets go bye bye
$( ".navbox").find( "ul" ).css( "list-style-type", "none" );
I also tried this:
// Make the bullets go bye bye
$( "ul" ).css( "list-style-type", "none" );
And it didn't work either.
Do you have any idea what I'm doing wrong? The Transhumanist 14:47, 30 December 2017 (UTC)
::after
CSS pseudo element
[2]. Which means that to override it, you have to add more CSS rules to the page. There is a handy function mw.util.addCSS()
that you can use:// Make the bullets go bye bye
mw.util.addCSS('.hlist dd:after, .hlist li:after { content: ""; }');
mw.util
is available, so you need to surround your script with:// Load dependencies
mw.loader.using( 'mediawiki.util'], function () {
// ... your script goes here ...
});
mw.loader.using
line after the $(function() {
line -
Evad37 [
talk 03:17, 31 December 2017 (UTC)$( ".navbox").find( "*" ).removeClass( "hlist" );
// Make the ul's targettable by adding a class to them
$( ".navbox").find( "ul" ).addClass( "navbox-ul" ); //this part worked
// Make the bullets go bye bye, by altering the elements' style
var elements = document.getElementsByClassName('navbox-ul');
elements.style.listStyleType="none";
// Make the bullets go bye bye
mw.util.addCSS('.navbox-list dd:after, .navbox-list li:after { content: ""; }');
// Make the bullets go bye bye
$( ".navbox-ul" ).css( "list-style-type", "none" );
list-style-image: none;
to override the image of a bullet that Vector uses by default. So that line should actually be// Make the bullets go bye bye
$( ".navbox-ul" ).css( {"list-style-type":"none", "list-style-image":"none"} );
// Make the bullets go bye bye
$( ".navbox-ul" ).css( "list-style-type", "none" );
$( ".navbox-ul" ).css( "list-style-image", "none" );
// Make the bullets go bye bye, by altering the elements' style
var elements = document.getElementsByClassName('navbox-ul');
elements.style.listStyleType="none";
elements.style.listStyleImage="none";
In the script above, I'd like to force all the navigation footers on the page to be uncollapsed. I've also run into this obstacle on another script, for working on pages like this, where I need the boxes expanded. How is that done in a script? The Transhumanist 07:51, 6 January 2018 (UTC)
I went back and looked at the HTML source more closely, after studying the .css method, and found "display: none". So I checked what was there when the boxes were displaying, and invoked that with this line of code:
// Force the navboxes to show
$('tr').css('display', 'table-row');
I'm guessing the .find method may allow this to be restricted to occurrences of tr within navboxes only. I'll keep you posted. The Transhumanist 07:09, 13 January 2018 (UTC)
I've learned that looking at page source is a tricky business - it doesn't show the current state. Just looking at the page source isn't good enough; it turns out that other scripts (like NavFrame in mw:common.js) change the source after that picture is taken, requiring that you view selected source to see its current state.
So, while in "view page source" NavContent in a series box showed no indication of being collapsed (and so no code available to change), looking at the current page source (via "View Selection Source" in drop-down menu on right-click) reveals that some JavaScript came along afterward and added some styling (display: none). When expanded, that changes (to display: block).
So, I added a few "display; block"s of my own. :) Now I have a script, that among other things, forces all the content in sidebar and series boxes to be displayed, which is very useful for someone inspecting and collecting list components. Still needs refining of the formatting though. The script is ViewAsOutline-Sidebar.js.
This (acquiring JavaScript) is a grueling learning curve!
Do you have any suggestions that might make this journey easier? :) The Transhumanist 06:47, 18 January 2018 (UTC)
console.log()
, and also evaluate snippets of Javascript you type into it. -
Evad37 [
talk 04:42, 19 January 2018 (UTC)Hello, I'm Lingzhi. The regular FAC reviewers have some toilsome tasks that a script could make much easier. Would you be willing/available to make one? It would be greatly appreciated. Plus I was a Pick Basic and Python programmer, still hobbyist in latter, and I would like to help/learn with javascript. The request is on Mike Christie's page, check your pings... Thanks! Lingzhi ♦ (talk) 02:51, 20 January 2018 (UTC)
I'm in the process of trying to fix the intitle bug in Wikipedia's search, by providing the solution as a function within StripSearchSorted.js.
The intitle bug is that when you enter a search phrase in WP's search box with a common word (like this: intitle:"in Germany"), the titles in the search results don't match.
I'm almost done, but I can't figure out how to get :contains to accept a variable:
function TrueMatch() {
// The purpose of this function is to filter out non-matches
// Activation filter:
// Run this function only if 'intitle:"' is in the page title
// Notice the lone " after intitle:
if (document.title.indexOf('intitle:"') != -1) {
// Body of function
// Create variable with page title
var docTitle = document.title;
// Display on screen for checking
//alert ( docTitle );
// Extract the intitle search string from the html page title
// We want the part between the quotation marks
var regexIntitle = new RegExp('intitle:"(.+?)(")(.*)','i');
var intitle;
intitle = docTitle.replace(regexIntitle,"$1");
//alert ( intitle );
// Filter out search results that do not match
$( "li" ).not( 'li:contains(" + intitle + ")' ).remove();
}
}
It works fine up until that last line. I want to remove all li elements that do not contain the text in the intitle variable. The Transhumanist 07:51, 19 January 2018 (UTC)
$( "li" ).not( 'li:contains("' + intitle + '")' ).remove();
'li:contains("' + intitle + '")'
gets processed first, and the result is passed through to .not()
. Or if you wanted to be a bit more explicit, you could do something likevar intitle_selector = 'li:contains("' + intitle + '")';
$( "li" ).not( intitle_selector ).remove();
$( "li" ).remove();
, it removes all results.
The Transhumanist 02:16, 20 January 2018 (UTC)$( "li").not('li:contains( "of" )').remove();
resulted in blank results (ie, none).$( "li").not('li:contains( of )').remove();
resulted in no matches (ie results unaffected).
// First, strip out the searchmatch class elements (they match).
$( 'li').find( '.searchmatch').remove();
$( "li" ).not( 'li:contains("' + intitle + '")' ).remove();
$( 'li:contains("' + intitle + '")').remove();
intitle
will be somewhere within the li
, just not neccesarily in the title. Plus we can limit the searching of li
s to just the search results, rather than the whole page:// Mark true results with a class
$('.mw-search-results').find('li').has( 'div > a:contains("' + intitle + '")' ).addClass('truematch');
// Remove other results
$('.mw-search-results').find('li').not('.truematch').remove();
mw-search-results
, find the li
s which have a div
that itself has (as a direct child element) an a
that contains the text intitle
, and add the class truematch
to those li
s. Then, in the mw-search-results
, find the li
s which do not have the class truematch
, and remove them. -
Evad37 [
talk 09:25, 20 January 2018 (UTC)This is very exciting. That's one more step in one of the city outline building approaches that gets sped up...
Steps 3, 4, and 5 are currently done manually, but 3 (copy/paste) isn't as tedious, so 4 and 5 have priority.
Since deduping is more complicated after links are placed, developing this first, makes the most sense.
The Outline of Chicago is currently being drafted, using the above steps...
Step 1: See all the redlinks? Those are from the Template:Outline city. Many of the links in the template do not apply to Chicago, and so they turn red, but you never know what all is going to turn red when you first start a city outline, and they are time consuming to remove by hand. So, what we do is populate the outline with all the topics we can find, and then strip out the redlinks in step 6. The RedlinksRemover doesn't remove red entries that have children, it just delinks them. But, when the outline first starts out, most of the redlinks don't have children. If we strip them out too soon, we'll wind up having to type many of them back in when we find children topics for them.
Step 2: Here's where StripSearchSorted with TrueMatch comes in. You do some intitle searches, such as "in Chicago". Increase the limit in the url to 5,000 to get the maximum results you can at once. That produces the results here: https://en.wikipedia.org/?title=Special:Search&limit=5000&offset=0&profile=default&search=intitle%3A%22of+Chicago%22&searchToken=bvc5dp6q7ldd4ayxph2a6ixg
Step 3: We copy and paste them to the "Place these" section in the outline (under See also). We repeat step 2 with further intitle searches (such as "of Chicago") and other gathering methods and send them all to "Place these" until we have all the topics we can find.
Step 4: The problem we have now is that many of the links in the "Place these" section are already in the body of the outline, like Culture of Chicago, Demographics of Chicago, and so on. And links may be duplicated in the "Place these" section itself. Therefore, we need to dedupe (remove the duplicates from) this section. That for each link in "Place these" that is found in the body of the outline (not navigation templates), or elsewhere in "Place these", gets removed.
Step 5: In this step, you take each of the topics one-by-one from the "Place these" section, after the duplicates have been removed, and put them into the body of the outline. Currently done by hand.
Step 6: Clean it all up with the RedlinksRemover. This tool is quick and painless – just click on the menu item. Without this tool, it is mind-numbingly tedious.
Which brings us to the design of OutlineDedupeHolding.js.
Eventually, this will dedupe more than one section, but its initial version will just process entries in the "Place these" section.
For each item, it needs to check the rest of the outline, excluding templates, and including the rest of "Place these", for a matching entry. If a match is found, that item is deleted from "Place these". If no match, go on to the next item.
I think this one may be within my ability level to write. I just need a little guidance...
How would you go about programming it? The Transhumanist 07:37, 22 January 2018 (UTC)
<li>
) with a duplicate link in them.no big deal JarrahTree 13:45, 26 January 2018 (UTC)
Here's one that's beyond my current abilities...
I came across a script called User:The Evil IP address/hdedit.js (heading editor). It allows you to edit headings without opening the page or section editor.
I'd like this concept applied to editing list item annotations. List items are ubiquitous on outlines, stand-alone lists, and embedded lists, and their annotations typically follow the list items, on the same lines, starting with an en-dash, like this:
If a list item has an annotation, it should appear in the annotation editor for modification by the user. If a list item has no annotation, the script should pull in the first 2 sentences of the lead of the corresponding article, if the list item is an embedded link. Then the user can edit them (the 2 sentences) in the annotation editor for context and polishing. If there is no link, then an empty annotation editor should appear, ready for user input.
I was very excited when I found hdedit, figuring it could be easily tweaked to perform the function I desired, until I looked at the source. Even though it is in JavaScript, I couldn't understand hardly a byte of it. I don't even recognize the syntax being used.
Then I started hoping that this would be just the type of script writing challenge you could sink your teeth into.
Sincerely, The Transhumanist 11:52, 15 January 2018 (UTC)
hdedit
is an object, and it is placed on the native window
object – but it probably could have also been declared with var hdedit =
instead of window.hdedit
.What is being chained?
hdedit
is an object, the syntax follows that of javascript objects – i.e. var foo = { 'key': 'value', 'key 2': 'value 2' }
. But in this case, functions are used as the values rather than strings (and if the keys don't contain special characters like spaces, then the quotes can be omitted). Functions within objects are sometimes called methods.foo[key]
, or dot notation if there's no special characters: foo.key
.hdedit.wikitext.replace(/^(=+)(\s*).+?(\s*)\1(\s*)$/m, '$1$2' + hdedit.newheading + '$3$1$4')
). You can't do something that simple with list items, because regex like /^(\*+)(\s*).+?$/m
would always match the first list item, not the one that needs to be changed. So then you need to find some other way of working out which list items in the wikitext match up with which list items rendered in the page HTML, which is where it starts getting complicated. -
Evad37 [
talk 04:34, 19 January 2018 (UTC)
What about counting?
Would the 55th list item in the html view always be the 55th list item in the wikitext view? The Transhumanist 08:03, 23 January 2018 (UTC)
<li>...</li>
tags directly in the wikitext. Which would completely blow things up if you're just counting li tags in the html and lines begining with * in the wikitext. -
Evad37 [
talk 02:45, 25 January 2018 (UTC)
Hi. I've only been working with javascript for a couple days now (sorry, n00b alert). I am rather at my wits' end. I have no idea why User:Lingzhi/reviewsourcecheck.js (a fork of Ucucha's HarvErrors script, which I am also using concurrently) seems to work correctly on the Notes section for all articles, but on the References section it works for some articles but not others. I have spent literally hours and hours trying to walk through the history to see where the bug began... I can't ask you to comb through the whole thing, but... do you have any general thoughts? A million thanks... Oh and occasionally the error messages in the Notes section (generated by Ucucha's script) are duplicated, but if I clear the browser's cache, they usually but not always fix themselves... Lingzhi ♦ (talk) 00:17, 25 January 2018 (UTC)
srctxt
, but then you're trying to using srctext
on line 119, which is undefined. Secondly, you are missing a semicolon at the end of line 109. Thirdly, variables are scoped to functions, not other block structures like for
. This means that in the second check, the variables 'i', 'srctxt', 'spline', and 'k' have already been defined from the first check.Harv error: link to #CITEREFTrigger1980 doesn't point to any citation. Harv error: link to #CITEREFGreen1981 doesn't point to any citation. P/PP error: Green 1981, pp. 123; P/PP error: Champion 2009, pp. 121. Harv error: link to #CITEREFTrigger1980 doesn't point to any citation. Harv error: link to #CITEREFGreen1981 doesn't point to any citation.;
P/PP error: Green 1981, pp. 123; P/PP error: Champion 2009, pp. 121. Harv error: link to #CITEREFTrigger1980 doesn't point to any citation. Harv error: link to #CITEREFGreen1981 doesn't point to any citation.;
Lingzhi ♦ (talk) 02:35, 25 January 2018 (UTC)
So I've been working on User:Lingzhi/reviewsourcecheck.js and made huge progress. I'm sure it could be made much much more elegant, but that's a task for another day. My question is this: There are no "red box with white x" errors, which I assume means "fatal errors". There are no little italic letter i warnings (information). There is only one yellow warning triangle with an exclamation point (what is the correct terminology for all these?)..
But alas, the fatal problem is this: the tooltip text (or whatever the correct term would be) for that one little yellow triangle says "Too many errors. (96% scanned)." And every section of the script works fairly well except for that section with the yellow warning, which is the lowest section of the script. When I debug, the logic all seems to work fine and I get into the place where I want to be, holding the information that I want to hold. But alas again, there is no output, even tho the "innerHTML" worked in earlier sections.
(Update: I made some edits and added a little more code; the yellow "Too many errors." triangle now appears higher up, at line 222sortedCites.sort();
, but it is still the only error warning.)
I have tried tweaking that section in every way I can imagine.
How can there be only one error, but that error says "Too many errors"?
As a note, I used to have many more yellow caution triangles, because I was re-declaring variables again and again... so I kept the "var" for the first instance (forex var i = 0
), and for all later points I deleted the "var" (forex i = 0
). Is that the wrench in the works? Or something else?
Thanks Lingzhi ♦ (talk) 05:15, 28 January 2018 (UTC)
Hello, I am trying to figure out how to use {{ maplink}} with a GeoJSON data file. I was looking at documentation and testcases and still cannot figure out where exactly to put the data file.
Can you tell me the exact location of 'St Georges Terrace.map
'? I'm quite confused in trying to locate this file to help me understand where to put my file.
{{Maplink||type=data|from=Sandbox/Evad37/St Georges Terrace.map}}
Here is a file I would like to map, but I don't even know how to test if it works on Wikipedia. c:High Point High School/Data:Boundary_Map.map I appreciate any help you can provide.~ Mellis ( talk) 04:33, 29 January 2018 (UTC)
Would it be possible to create a script similar to your HIDEAWB thing, but that would work for specific, user-defined edit summaries? AKA, something like
function setupHideBotTask() {
// Add a class to list items with edit summaries containing specific strings/regex matches/whatever
// Replace EXAMPLETEXT1/2/3 with your own strings/regex
$( "a[title='EXAMPLETEXT1']" ).closest("li, tr").addClass("watchlist-bot-task-edit");
$( "a[title='EXAMPLETEXT2']" ).closest("li, tr").addClass("watchlist-bot-task-edit");
$( "a[title='EXAMPLETEXT3']" ).closest("li, tr").addClass("watchlist-bot-task-edit");
// 'Hidden by default' option
if ( window.BotTaskHiddenByDefault ) {
$(".watchlist-bot-task-edit").hide();
$('#ca-BotTask').hide();
} else {
$('#ca-BotTask').hide();
}
$('#ca-BotTask').on('click', function() {
$(".watchlist-bot-task-edit").hide();
$('#ca-BotTask').show();
$('#ca-BotTask').hide();
return false;
});
$('#ca-BotTask').on('click', function() {
$(".watchlist-bot-task-edit").show();
$('#ca-BotTask').hide();
$('#ca-BotTask').show();
return false;
});
}
if( mw.config.get('wgNamespaceNumber') === -1 ) {
// Only operate in Special: namespace
$.when( mw.loader.using( 'mediawiki.util' ), $.ready).done( setupHideBotTask );
}
And maybe 'function setupHideBotTask()' is something that could be externalized to make things less intimidating for newbies / the main script being easily maintainable? Headbomb { t · c · p · b} 14:27, 28 August 2017 (UTC)
\[\[User:JCW-CleanerBot#What is the bot approved for\?\|Task \dSA\]\]
" would match
Tasks 1SA/2SA/3SA/4SA, but not Tasks 1A/2A/3A/4A), and add the "watchlist-bot-task-edit" class to the corresponding item. Part 2) Make the item hideable in the same way
WP:HIDEAWB does it.@
Headbomb: I've got a basic version working at
User:Evad37/Watchlist-hideCustom.js. The filters live in your userspace in a /WatchlistFilters.js subpage (e.g. mine is
User:Evad37/WatchlistFilters.js), and at the moment need to be entered manually, between the lines window.watchlistFilters = [
and ];
– one per line, with a comma at the end of each line except the last (i.e. a javascript array). Each filter can either be a regular expression, or plain text inside quote marks. Let me know if you need any help. -
Evad37 [
talk 09:02, 4 October 2017 (UTC)
Backlog update:
New Year Backlog Drive results:
General project update:
If you wish to opt-out of future mailings, go here. 20:32, 7 February 2018 (UTC)
To do that you need to use the mw:API, specifically mw:API:Edit. The easiest way I've found is using the mediawiki.api resource loader module. So you need to specify the dependency, i.e.
mw.loader.using( 'mediawiki.api'], function () {
// ...
// ... the rest of your script goes here ...
// ...
});
(see
mw:ResourceLoader/Migration_guide_(users)#mw.loader for further details).
Then create an mw.api object, and
identify your script/contact details. The same object can be used for multiple requests.
var API = new mw.Api( {
ajax: {
headers: {
'Api-User-Agent': 'Scriptname/version ( /info/en/?search=User:.../Script )'
}
}
} );
function doEdit() {
API.postWithToken( "edit", {
action: "edit",
title: "Wikipedia talk:Sandbox" // for example. You can use ` mw.config.get( "wgPageName" ) ` to get the current page name.
appendtext: "This text will be appended to the page.",
summary: "Edit summary goes here"
} ).done( function() {
// Code to execute if saved successfully
// Maybe notify the user.
// Or maybe reload the page:
location.reload();
} ).fail( function( code, jqxhr ) {
// Edit failed. The reason will be in the code and/or jqxhr parameters...
// (though you probably want to notify the user, rather than just logging to console)
if ( code === "http" && jqxhr.textStatus === "error" ) {
console.log( "HTTP error " + jqxhr.xhr.status );
} else if ( code === "http" ) {
console.log( "HTTP error: " + jqxhr.textStatus );
} else if ( code === "ok-but-empty" ) {
console.log( "Error: Got an empty response from the server" );
} else {
console.log( "API error: " + code );
}
} );
}
On some of my scripts, I use an activation filter that checks the title and runs only if the namespace up there matches:
// Run this script only if "Book:" is in the page title
if (document.title.indexOf( "Book:") != -1) {
// (Body of script goes here)
};
Now I need to do this with articles in the main namespace, but there is no prefix up there in the title to work off of.
What to do? The Transhumanist 13:02, 11 February 2018 (UTC)
mw.config.get( 'wgNamespaceNumber' ) === 0
. —
JJMC89 (
T·
C) 17:17, 11 February 2018 (UTC)
// Run this script only for main namespace
if (mw.config.get('wgNamespaceNumber') !== 0) {
return;
};
// (Body of script goes here)
return
statement only works within functions, but that's generally not a problem – you're whole script is usually wrapped inside a function, assuming you need to wait for the document ready and/or wait for resource loader modules to be loaded. -
Evad37 [
talk 00:44, 12 February 2018 (UTC)
$( function($) {
...});
there's nothing more left to execute, and so the script ends. It doesn't matter if the "return" is within any number of "if"/"if-else" statements, "for" loops, "while" loops, etc – only having another (sub)function will change the scope it applies to. One thing to watch for, at deeper levels within your programs, is that when you are assigning a variable to a function call (var foo = someFunction(bar);
), the variable is set to the return value, which is specified with "return someValue;"
inside the function. Since we haven't explicitly set a return value, it would be undefined
– but that doesn't matter for our purpose, since the function is just there to make the script wait before executing, and is not assigning a value to a variable. -
Evad37 [
talk 02:09, 13 February 2018 (UTC)Based on your explanations above, I've written the following deactivation filters using return statements:
// ============== deactivation filters ==============
// End the script if Vector skin is not the user's skin
if ( mw.config.get( 'skin' ) !== 'vector' ) {
// use a return statement to end the local function and hence the program's body
// important: this approach does not work outside of a function
return;
}
// End the script if " - Search results - Wikipedia" is not in the page title
if (document.title.indexOf(" - Search results - Wikipedia") == -1) {
// use a return statement to end the local function and hence the program's body
// important: this approach does not work outside of a function
return;
}
Are these correct?
And am I using the correct terminology in my comments?
What is the common name for the above technique? The Transhumanist 10:39, 15 February 2018 (UTC)
What about doing the same thing for more than one namespace? Such as "run script if the page is in the article namespace or the template namespace"? The Transhumanist 18:03, 13 February 2018 (UTC)
return
. NOT( isArticle OR isTemplate ) is equivalent to isNotArticle AND isNotTemplate. So in script (and putting the actual namespace number into a variable to avoid duplication), you get something like: // Run this script only for main and template namespaces
var namespaceNumber = mw.config.get('wgNamespaceNumber');
if ( namespaceNumber !== 0 && namespaceNumber !== 10 ) {
return;
};
// (Body of script goes here)
!
operator: // Run this script only for main and template namespaces
var namespaceNumber = mw.config.get('wgNamespaceNumber');
var isArticleOrTemplate = (namespaceNumber === 0 || namespaceNumber === 10);
if ( !isArticleOrTemplate ) {
return;
};
// (Body of script goes here)
// Run this script only for main and template namespaces
var namespaceNumber = mw.config.get('wgNamespaceNumber');
var allowedNamespaces = 0, 2, 10, 828]; // main, user, template, module
var isInAllowedNamespace = (allowedNamespaces.indexOf(namespaceNumber) !== -1);
if ( !isInAllowedNamespace ) {
return;
};
// (Body of script goes here)
the meltham station was created by the blocked sockpuppet /info/en/?search=Wikipedia:Sockpuppet_investigations/D47817 enough to delete with no hesitation or compunction, to say the least JarrahTree 02:44, 21 February 2018 (UTC)
the editors who used to help me with setting up project maintenance and so on have gone...
could you lead me to something or somebody who has the capacity to even get /info/en/?search=Wikipedia:WikiProject_Ageing_and_culture to square one? you can see on the project page that it started and more or less died without the requisite pages to even have a sense of what it is about I have tagged for many different projects - but have no idea who to ask or how to ask for the basics (some redlinked_)
any thoughts on or off wiki would be appreciated, thanks JarrahTree 23:47, 19 February 2018 (UTC)
I assume by "square one" you mean set up the project for class/importance assessments. To do this, you need to:
{{
Grading scheme|Project=Ageing and culture}}
and {{
Importance scheme|topic=Ageing and culture}}
(or similar listings and explanations of classes and importances).{{
Articles by Quality|topic=Ageing and culture}}
(or similar links to the other classes) and [[
Category:WikiProject Ageing and culture articles by quality]]
{{
Articles by Importance|topic=Ageing and culture}}
(or similar links to the other importances) and [[
Category:WikiProject Ageing and culture articles by importance]]
- Category:WikiProject Ageing and culture - Category:WikiProject Ageing and culture articles - Category:WikiProject Ageing and culture articles by quality - Category:WikiProject Ageing and culture articles by importance
- Evad37 [ talk 09:44, 20 February 2018 (UTC)
Dear Evad,
I was wondering if you would, for the sake of helping a relative newb get up to speed, mind answering some questions about the sources of your JavaScript know-how, the practices you follow, and the tools you use...
Which JavaScript books have you studied that you recommend?
Which are your go-to JavaScript-related websites?
What tools do you use for script development?
What does a script/gadget developer for WP need to know about MediaWiki?
What is your approach for writing scripts?
How do you go about fixing bugs?
What were your hardest learned lessons?
If you were to start all over again, what would you do differently?
What other pointers can you provide?
What important questions did I not ask?
I look forward to your replies.
Sincerely, The Transhumanist 14:37, 2 February 2018 (UTC)
var someTemplate = new Template('name', {'para1':'value1', 'para2':'value2'});
and then later someTemplate.setParamValue('para1', 'foo');
to change the value set for 'para1'. And later someTemplate.makeWikitext();
to produce the string {{name|para1=foo|para2=value2}}
.var newWikitext = someTemplate.makeWikitext() + currentWikitext;
is adding the wikitext representation of the template to the start of the current wikitext (without concern as to how the template object is turned into wikitext).function foo (whatever) {
if ( condition1 ) {
if ( condition2 ) {
if ( condition 3 ) {
//code if everything is okay
} else {
//code if #3 fails
}
} else {
//code if #2 fails
}
} else {
//code if #1 fails
}
}
function foo (whatever) {
if ( !condition1 ) {
//code if #1 fails. The return below stops any further code being processed.
return;
}
if ( !condition2 ) {
//code if #2 fails
return;
}
if ( !condition3 ) {
//code if #3 fails
return;
}
//code if everything is okay
}
var foo;
if ( condition ) {
foo = 'isTrue';
} else {
foo = 'isFalse';
}
var foo = ( condition ) ? 'isTrue' : 'isFalse';
var x = a || b // evaluates to a if a is truthy, or b if a is falsey - ie IF (a) { x=a; } ELSE { x=b; }
var y = a && b // evaluates to b if a is truthy, or b if a is falsey - ie IF (a) { y=b; } ELSE { y=a; }
return;
implementation.Hey, would you have any tips on debugging what is slowing down my page loads? I've tried to isolate individual gadgets and common.js scripts but I'm going in circles. (Or would you know if there's something up with WP's sitewide JS?) I tried Chrome's dev tools "Sources" (edit: ah, meant "Network") tab but the userscripts all run the same length
czar 01:33, 26 February 2018 (UTC)
An error message as shown in the screenshot popped up when I pressed the button. Please look into it — Frc Rdl 07:36, 4 March 2018 (UTC)
I removed the deactivation filter for vector skin from SearchSuite.js, and loaded it in common.js. It works on all skins, with the following quirk in MinervaNeue:
In the MinervaNeue skin, the features are stuck in whatever state they are in when the skin is selected. Unless there is a way to access the sidebar menu in this skin – if there is, please let me know.
By the way, is there a faster way to change skins than in "preferences"? — The Transhumanist 11:58, 9 March 2018 (UTC)
I'm just checking in. Seems you haven't been well lately. If you are indeed sick, I hope you will be in good health soon. I'll see you around. Eddie891 Talk Work 16:13, 11 March 2018 (UTC)
...is now operational.
Thanks for your contributions and advice. The development of the script would have been substantially delayed without your support.
I did the best I could, though it is far from optimized.
What needs to be, or should be, done to it? The Transhumanist 18:26, 24 February 2018 (UTC)
try {
// Code that might generate an error goes here
// The script will execute up until an error occurs, at which point it moves to the catch block,
// or until the end of the try block, at which point it skips the catch block
} catch(e) {
// Code to execute if there is an error – i.e. if you can't read a value from localStorage, just assume a default value
// The error details are in the `e` parameter, which you can output the browser console like this:
console.warn(e);
}
// Script continues here, even if there was an error encountered in the try block
TrueMatch
, you could have something like removeResultsWithoutIntitleString()
So, the program is just hanging in the breeze, waiting to crash?
I applied your code to variable assignments, like this:
try {
var SRSisterStatus = localStorage.getItem( 'SRSisterStatus' );
} catch(e) {
console.warn(e);
var SRSisterStatus = "off" ;
}
try {
var SRRedirectedStatus = localStorage.getItem( 'SRRedirectedStatus' );
} catch(e) {
console.warn(e);
var SRRedirectedStatus = "off" ;
}
try {
var SRDetailStatus = localStorage.getItem( 'SRDetailStatus' );
} catch(e) {
console.warn(e);
var SRDetailStatus = "off" ;
}
try {
var SRWikifyStatus = localStorage.getItem( 'SRWikifyStatus' );
} catch(e) {
console.warn(e);
var SRWikifyStatus = "off" ;
}
try {
var SRSortStatus = localStorage.getItem( ' SRSortStatus ' );
} catch(e) {
console.warn(e);
var SRDetailStatus = "on" ;
}
What is "e"?
What do I do with "e"?
That's a lot of repetition, how do you shrink that down?
Is try catch needed for instances of localStorage.setItem also? — The Transhumanist 08:20, 12 March 2018 (UTC)
This is a feature I would like to add, to let the user further hone down the search results. I think TrueMatch could be cloned and adapted to do this, but in order to parse an additional search string, the program will need an input form. I've never done one of those before. Any guidance would be most helpful. The Transhumanist 20:06, 24 February 2018 (UTC)
prompt()
method to request user input. W3Schools has a couple of good examples:
[5] -
Evad37 [
talk 04:36, 25 February 2018 (UTC)
The search results have links at the bottom for setting the number of items to be displayed to 20, 50, and so on, up to 500. But the API allows setting at any number up to 5,000, with &limit=5000
.
I'd like a menu item that allows the user to choose their own limit. Then the program would need to pass the &limit command to the API. I don't know how to do that.
Any pointers would certainly help. The Transhumanist 20:06, 24 February 2018 (UTC)
Hi Evad37 , I would like to participate to the JS project. Could you please help me with process? Tools, documenattiosn and how task are organized? Thnaks for your help. -- Mah3110 ( talk) 10:45, 14 March 2018 (UTC)
Hey there! So
phab:T32750 is going to be deployed next Thursday. With this, any edit summary that links to someone else's userpage will ping them. Looking at the code, I can't actually tell if your MoveToDraft script will be affected, but I wanted to give you a heads up just in case. Can the script be used to move userpage drafts to the Draft namespace? Anyhoo, disabling the pings is as easy as prefixing with a colon, like [[:User:MusikAnimal]]
, so you could safely put this before any wikilink in the edit summary and there will be no unwanted pings. If you have any questions don't hesitate to ask. Regards —
MusikAnimal
talk 00:37, 9 March 2018 (UTC)
I understand you may not be doing well in real life :/ I'm sorry to hear this and you have my sympathies. Since I haven't heard back from you, I've gone ahead and made the above change with Special:Diff/830585089. I doubt we needed to add a colon for all of those links, but I did anyway just to be safe. Hope this OK. Get well soon!! :) — MusikAnimal talk 18:55, 15 March 2018 (UTC)
Just want your quick opinion on a Signpost matter. Would it be kosher to review a Wikipedian's article that they wrote for a real-world history newsletter? Would this be topical for In The Media? The subject is coverage of specific historical content on Wikipedia. ☆ Bri ( talk) 01:38, 16 March 2018 (UTC)
Chicken Soup for a Programmer's Soul | |
Hey, I have glimpsed a couple mentions of the fact that you be or might have been under the weather. I hope you're doing well. Have a nice warm bowl of chicken soup. Lingzhi ♦ (talk) 07:10, 18 March 2018 (UTC) |
I apologise for making what might have been a disparaging remark posted on here. Do you think the message template could be shortened and made more clear? Kudpung กุดผึ้ง ( talk) 01:07, 18 March 2018 (UTC)
Kudpung กุดผึ้ง ( talk) 04:20, 27 March 2018 (UTC)
Is it possible to use todo script on other sister and language projects? I added it on m:User:Titodutta/global.js and kn:ಸದಸ್ಯ:Titodutta/common.js. -- Titodutta ( talk) 22:20, 28 March 2018 (UTC)
ACTRIAL:
Paid editing
Subject-specific notability guidelines
Nominate competent users for Autopatrolled
News
A proposal has been made to delete Portal:Australian roads, which you have made significant contributions to, as well as all other portals on English Wikipedia. You are welcome to contribute to the discussion if you'd like, which is located at Wikipedia:Village pump (proposals)#RfC: Ending the system of portals. Thank you for your contributions to Wikipedia. North America 1000 11:21, 12 April 2018 (UTC)
Evad, I set next issue dates to 4/25 for writing deadline and 4/28 for publication. Thought you would want to know in case you didn't see the Newsroom update. Also, having published the March issue manually, am planning plan to use the publishing script this time, since now I know what to expect it to do.
Do you plan to be involved in the April issue? ☆ Bri ( talk) 14:48, 12 April 2018 (UTC)
I'm working on a study of political motivations and how they affect editing. I'd like to ask you to take a survey. The survey should take no more than 1-2 minutes. Your survey responses will be kept private. Our project is documented at https://meta.wikimedia.org/wiki/Research:Wikipedia_%2B_Politics.
Your survey Link: https://uchicago.co1.qualtrics.com/jfe/form/SV_9S3JByWf57fXEkR?Q_DL=56np5HpEZWkMlr7_9S3JByWf57fXEkR_MLRP_cJbCbj99tqmYbTD&Q_CHL=gl
I am asking you to participate in this study because you are a frequent editor of pages on Wikipedia that are of political interest. We would like to learn about your experiences in dealing with editors of different political orientations.
Sincere thanks for your help! Porteclefs ( talk) 12:38, 16 April 2018 (UTC)
Hello,
There will be some changes to the way wikitext is parsed during the next few weeks. It will affect all namespaces. You can see a list of pages that may display incorrectly at Special:LintErrors. Since most of the easy problems have already been solved at the English Wikipedia, I am specifically contacting tech-savvy editors such as yourself with this one-time message, in the hope that you will be able to investigate the remaining high-priority pages during the next month.
There are approximately 10,000 articles (and many more non-article pages) with high-priority errors. The most important ones are the articles with misnested tags and table problems. Some of these involve templates, such as infoboxes, or the way the template is used in the article. In some cases, the "error" is a minor, unimportant difference in the visual appearance. In other cases, the results are undesirable. You can see a before-and-after comparison of any article by adding ?action=parsermigration-edit to the end of a link, like this: /info/en/?search=Arthur_Foss?action=parsermigration-edit (which shows a difference in how {{ infobox ship}} is parsed).
If you are interested in helping with this project, please see Wikipedia:Linter. There are also some basic instructions (and links to even more information) at https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-April/001836.html You can also leave a note at WT:Linter if you have questions.
Thank you for all the good things you do for the English Wikipedia. Whatamidoing (WMF) ( talk) 21:18, 19 April 2018 (UTC)
This geezer was born at the age of 117 - /info/en/?search=Kenneth_Slessor - which parameter has been completely -'ed up ? JarrahTree
Requesting to be added as user of the Signpost publishing script ☆ Bri ( talk) 03:03, 23 April 2018 (UTC)
Wikipedia:Wikipedia Signpost/Next issue/
<noinclude> ... </noinclude>
section and following couple of lines) as the pages created from the newsroom "start article" button (i.e. traffic report or news and notes){{Wikipedia:Wikipedia Signpost/Templates/Signpost-block-end-v2}} {{Wikipedia:Wikipedia Signpost/Templates/Signpost-article-end-v2}} <noinclude>{{Wikipedia:Signpost/Template:Signpost-article-comments-end|||}}</noinclude>
Wikipedia:Wikipedia Signpost/Next issue/
– equivalently, everything listed at
Wikipedia:Wikipedia_Signpost/Next_issue – will become part of the published issue, and nothing else. Correct? ☆
Bri (
talk) 04:16, 23 April 2018 (UTC)
Signpost draft
parameter ready
be set to "Yes"? ☆
Bri (
talk) 18:03, 23 April 2018 (UTC)
Everything seemed to work. Hoorah! The script cut down publishing to about 1 hour, which is nice. One request: could you look at the formatting at Wikipedia:Wikipedia_Signpost/Archives/2018-04-26 to see if the script did something funky there? ☆ Bri ( talk) 02:18, 26 April 2018 (UTC)
so no need? re project tags on signpost talk pages? ok JarrahTree 03:40, 26 April 2018 (UTC)
apologies - every now and then some project space shows up a total disinterest in project maintenance - but I see your issue and will not touch again - sorry about that JarrahTree 03:53, 26 April 2018 (UTC)
Is there a spot you go to to find the going ons in Wikipedia ? Eddie891 Talk Work 22:26, 27 April 2018 (UTC)
Once again I misread a situation - thanks for the revert JarrahTree 12:43, 27 April 2018 (UTC)
Hello Evad37,
I'm a contributor of the German Wikipedia and tried to transfer the Maplink template into our Wiki but I encountered a problem: The template you use for coordinates ({{ Coord}}) is quite different in our German version. It seems to use a different coordinates format. Could you help me there? I don't have any LUA knowledge and I don't know how to fix it myself. -- Doktorpixel14 ( talk) 08:56, 13 May 2018 (UTC)
are primaily conducted as wiki club west events - which is the western australian branch of wikimedia australia chapter - which in effect makes them wmau events - JarrahTree 11:53, 13 May 2018 (UTC)
Hi does multi qid works ? /info/en/?search=User:Naveenpf/Sandbox/map#Multi -- naveenpf ( talk) 01:25, 7 May 2018 (UTC)
|type=shape-inverse
only works with data from OSM). So to show an inverse of a Commons map, you would need to create a new one on Commons. Also if you are using |from=
for the first feature, then the next feature to be mapped should be using |type2=
, not |type=
. -
Evad37 [
talk 02:59, 13 May 2018 (UTC)Hello! I'm currently getting desparate after trying to modify the Signpost article table. I've copied both /Tasks/Set and /Tasks/Task over to my userspace in order to play around with them, and am currently trying to change the default setup to what I have manually hacked into the table in my userspace overhaul of the Newsroom, so something like:
Name of the Feature, link to Next issue page if present
Status: |
Checklist:
Discussion: |
---|
But I have absolutely no idea how on earth I could get this into the template. Got any help? Zarasophos ( talk) 13:09, 16 May 2018 (UTC)
The Signpost Barnstar | ||
For everything you continue to do for The Signpost. Stepping in as Editor in Chief during a period of turmoil was gutsy and I appreciate it, also appreciate your onboarding me and others and helping the effort to get closer to self-sustaining. I just realized you haven't really been thanked before. ☆ Bri ( talk) 17:04, 17 May 2018 (UTC) |
Strong support Zarasophos ( talk) 21:48, 17 May 2018 (UTC)
I did a dry run of the publication script and got this error, and appeared to hang after the first screen.
index.php?title=User:Evad37/SPS.js&action=raw&ctype=text/javascript:123 Uncaught TypeError: Cannot read property '1' of null at apiCallback_getInfo (index.php?title=User:Evad37/SPS.js&action=raw&ctype=text/javascript:123) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:46) at Object.fireWith [as resolveWith] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:47) at Object.deferred.(anonymous function) [as resolve] (https://en.wikipedia.org/w/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:51:337) at Object.<anonymous> (<anonymous>:15:410) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:46) at Object.fireWith [as resolveWith] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:47) at done (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:126) at XMLHttpRequest.<anonymous> (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:129)
It seems to be repeatable. @ Chris troutman: you may want to follow this conversation ☆ Bri ( talk) 18:35, 22 May 2018 (UTC)
just tinkling around with things - please revert if wrong JarrahTree 04:29, 21 May 2018 (UTC)
Just thought I'd let you know the mapframe doesn't show up in the Technology report for me, using Chrome running on an 8.4" Android tablet. There's just a blank space there with the open square "expand" icon. The access URL is https://en.m.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2018-05-24/Technology_report ☆ Bri ( talk) 15:58, 24 May 2018 (UTC) ☆ Bri ( talk) 15:58, 24 May 2018 (UTC)
ACTRIAL:
Deletion tags
Backlog drive:
Editathons
Paid editing - new policy
Subject-specific notability guidelines
Not English
News
...in the latest edition of the Portals newsletter, I've posted you a copy below. — The Transhumanist 00:50, 25 May 2018 (UTC)
We have grown to 79 members.
Please provide a warm welcome to our latest additions, Wpgbrown, Cactus.man, JLJ001, and Wumbolo.
A lot is going on, much of it on the WikiProject's talk page, so be sure to go there and join in on any of the many discussions taking place there.
Elsewhere around the portal project, or related to portals, the following is happening...
Evad37 has created a new template, with supporting lua module, to handle news in portals...
{{ Transclude selected current events}} is ready to be tested in some actual portals. Let Evad37 know if you need help with the search patterns.
Noyster commented that "This is the best portal innovation since sliced bread!"
See the relevant discussion at Wikipedia talk:WikiProject Portals#Alternative to Wikinews.
Thank you, Evad.
Our WikiProject is now subscribed to the bot that makes automatic article alerts, but the subpage where they are posted has not been added to our WikiProject page yet because of a weird problem...
Featured portal nominations from two years ago keep popping up on there.
Please check Wikipedia:WikiProject Portals/Article alerts to see if you can figure out how to fix this.
Once that is remedied, it will be posted on our WikiProject page.
Thank you.
Note that, this will only track base pages, because to track the rest, we'd have to create over 140,000 talk pages for the subpages, and that just isn't worthwhile (as we're trying to remove the subpages anyways). Therefore, any alerts for subpages will still need to be posted manually.
Your input/editing is welcome on the draft-in-progress of a new guideline for portals.
See or work on the draft at User:Cesdeva/sandbox11.
See also the discussion at: Wikipedia talk:Portal guidelines#RfC on new portal guidelines
There is a proposal to change the look of the table of contents at Portal:Contents/Portals.
See: Portal talk:Contents/Portals#RFC on layout update.
Thank you to those who have participated in portal deletion discussions. There are still some editors out there who despise portals, and this comes across in their argumentation style. Wow. Such negativity. But, there is some good news...
Current deletion discussions are posted on our WikiProject page.
While portal detractors are trying to get rid of portals via MfD, we have deleted many of them via speedy deletion (per {{ Db-p1}} or {{ Db-p2}}). Essentially, they were bare skeletons, with maybe a little meat on them. The plus here is that speedy deletion is without prejudice to re-creating the portals. They can easily be restarted from scratch without getting approval, or be undeleted by request by someone willing to work on them. We have kept track of these, for when someone wants to rebuild them. They are listed at Portal talk:Contents/Portals#These are not listed yet.
We are also removing subpages, the functions of which have been migrated to portal base pages. To see which ones have been removed, look for the redlinks in our watchlist.
There is also an MfD concerning some of these at Wikipedia:Miscellany for deletion/Redundant subpages of the Cornwall portal.
For subpages that need to be deleted, you can conveniently place this speedy deletion template at the top of each of them:
{{Db-g6|rationale=of subpage clean up – this subpage's function has been migrated to the portal base page and is no longer needed}}
Then an admin will come along and delete them.
There are still 100 existing portals not yet presented on the main portal list at Portal:Contents/Portals. There were 400, so we've come a long way. Thank you! But we are not done yet...
Please list a couple of them. Every little bit helps. If each member of this project listed one more, it would almost all be done. Many hands make light work.
The list of missings, and instructions, are to be found at Portal talk:Contents/Portals#These are not listed yet.
I hope to see you there!
These developments make up just the tip of the iceberg. I'll have more to report in the next update, soon. — The Transhumanist 00:50, 25 May 2018 (UTC)
I think everyone would enjoy it if you officially joined the Portals WikiProject.
Though morale is high, you joining would certainly boost it higher. ;)
And, you would receive a complementary subscription to our oddly irregular newsletter. — The Transhumanist 00:50, 25 May 2018 (UTC)
Hi Evad37: The Transclude Selected Current Event was an excellent work. You are super awsome. One quaestion about the template - it looks like the template returns only current month news (or correct me if I am mistaken on this). Is it possible to parameterize how much old news the template will return? Some portals may one to show last 3 months for example. Arman ( Talk) 05:44, 27 May 2018 (UTC)
|max=
and |days=
parameters. There is a technical limit on how high the number can be, but such errors should only appear for very high values, like more than one or two years. -
Evad37 [
talk 08:37, 27 May 2018 (UTC)I'm contacting you because you indicated on the Portals WikiProject's members list that you use AWB.
We are now working on a task that requires your help.
Please see Wikipedia talk:WikiProject Portals#AWB team please tackle maintenance run on intro sections.
Thank you. — The Transhumanist 22:35, 28 May 2018 (UTC)
Wikipedia:Wikipedia Signpost/2018-05-24/From the editor is having trouble linking to Wikipedia:Wikipedia Signpost/2018-04-26/From the editorss, probably becuase of the different SUBPAGENAME. Is there an elegant solution to this? ☆ Bri ( talk) 16:49, 30 May 2018 (UTC)
you look like you are saving the world.... just a query about whether I could get some help re-creating the SLWA project space into a new MoP space - see User:JarrahTree/MoP - any thoughts? I seem to be stuck on the header... JarrahTree 15:02, 29 May 2018 (UTC)
[11] in the page layout of course - it is the contents that will change... JarrahTree 15:21, 29 May 2018 (UTC)
{{:Wikipedia:GLAM/Museum of Perth/Tab header/Tab|full page name|text to display on tab}}
templates (next to the existing ones on that page) -
Evad37 [
talk 01:07, 30 May 2018 (UTC)Thank you very much for that advice - is there any chance of you being able to get to the Museum of Perth on a Tuesday, Wednesday or Thursday between 9 and 4 - in the near future ?? JarrahTree 03:03, 31 May 2018 (UTC)
got it - sorry about that JarrahTree
We have grown to 89 members.
This is the seventh issue of this newsletter. For previous issues, see our newsletter archive.
A warm welcome to our nearly one dozen new members...
Our new members include:
Be sure to say "hi" and welcome them to the team.
There were 1515 portals, but now we have 1475, because we speedy deleted a bunch of incompleted portals that had been sitting around for ages, that were empty shells or had very little content. Because they were speedied, they can be rebuilt from scratch without acquiring approval from WP:DRV.
This is what we have been gearing up for: upgrading the portals en masse, using AWB.
More than half of the Associated Wikimedia sections have been converted to no longer use a subpage. This chore will probably be completed over the next week or two. Many thanks to the WikiGnome Squad, who have added an Associated Wikimedia section to the many geography-related portals that lacked one. The rest of the subjects await. :)
The next maintenance drive will be on the intro sections. Notices have gone out to the WikiProjects for which one or more portals fall within their subject scope. Once enough time has elapsed for them to respond (1 week), AWB processing of intro sections will begin.
I'd like to take this opportunity to thank you all for your part in the RfC. I went back and reread much of it. I believe your enthusiasm played a major part in turning the tide on there. I'm proud of all of you.
Why reread that mess, you ask?
To harvest ideas, and to keep the problems that need to be fixed firmly in mind. But, also to keep in touch. See below...
I've contacted all of the other opposers of the RfC proposal to delete portals, to thank them for their support, and to assure them that their decision was not made in vain. I updated them on our activities, provided the link to the interviews about this project in the Signpost, pointed out our newsletter archive so they can keep up-to-date with what we are doing, and I invited them all to come and have a look-see at our operations (on our talk page).
It so happened that one of our members was a sockpuppet: JLJ001. According to the admin who blocked him, he was a particularly tricky long term abuser. This is a weird situation, since the user was quite helpful. He will be missed.
This has been somewhat disruptive, because admins are doing routine deletions of the pages (portals, templates, etc.) he created, and reversion of his edits (I don't know if they will be reverting all of them). Please bear with them, as they are only doing what is best in the long run.
The following pages have been deleted by the admins so far, that I know of:
{{Wikimedia for portals|species=no|voy=no}}
{{#tag:categorytree|{{PAGENAME}}}}
Automatic article alerts are now featured on the project page.
Some super out-of-date entries kept showing up on there, so posting it on the Project page was delayed. Thanks to Evad37 and AfroThundr for providing solutions on this one. Evad37 adjusted the workflow settings per Wikipedia:Article alerts/Subscribing#Choosing workflows, to make sure only the appropriate page types show up. AfroThundr removed the tags from the old entries that caused them to keep showing up in the article alerts.
Noyster pointed out that it would be nice to automate the updating of the portals section at the Community bulletin board.
Another major component of the portal system is the main list of portals, at Portal:Contents/Portals. How would we go about automating the updating of that?
Please post your ideas on the WikiProject's talk page. Thank you.
Keep in mind that we have already speedy deleted almost all of the nearly empty portals, which can be rebuilt without approval whenever it is convenient to do so. Other portals should be completed if at all possible rather than delete them through MfD (which requires approval from Deletion review to rebuild).
(Current deletion discussions are posted on our WikiProject page).
There's still more, but it will have to wait until next issue.
Until then, see ya around the project. — The Transhumanist 12:01, 31 May 2018 (UTC)
The Barnstar of Diplomacy | ||
Thank you for withdrawing your proposal when you found it lacked support, and taking criticism seriously. Your willingness to improve your work in response to others' suggestions, where many would become upset at criticism, is truly admirable, and something I wish more Wikipedians would adopt. Tamwin ( talk) 04:21, 1 June 2018 (UTC) |
For fixing portal project project pages (hahah I like that) JarrahTree 09:25, 3 June 2018 (UTC)
Thanks for making one of those, it's been on my to-do list for a while now. Do you think you can also do one for the cat importance template? This would eliminate the need for the category redirects completely. Also the FPo button doesn't have a color. Perhaps it should match the old FA button? — AfroThundr ( u · t · c) 17:01, 3 June 2018 (UTC)
I'd like to post a sample portal box in the newsletter, which will go on user talk pages, but this template appears to be turning off section editing for the entire page. Could you see if it is feasible to alter this without adversely affecting portals? — The Transhumanist 22:57, 6 June 2018 (UTC)
|EDIT=yes
in {{
Box-header}}
. (Other variations of the template might need to adjusted to pass that parameter through.) -
Evad37 [
talk 00:20, 7 June 2018 (UTC)The WikiProject now has 92 participants, including 16 admins.
A warm welcome to the newest members of the team:
Be sure to say hi.
Pbsouthwood has just gotten through the grueling RfA process to become a Wikipedia administrator. Be sure to congratulate him.
The reason he went for it was: "For some time I expect to be busy with subpage deletion for Wikipedia:WikiProject Portals as mentioned above. The amount of work is expected to keep me busy for some time. I am primarly a content creator and contributor to policy discussions, but would be willing to consider other admin work on request, providing that I feel that my involvement would be appropriate and not too far outside my comfort zone."
Evad37 has figured out a way to let the user flip through pictures without purging the page. Purging is awkward because there is an intermediary confirmation screen that you have to click on "yes". In the new picture slideshow section, all you have to do is click on the >
to go to the next picture or <
to instantly show the previous feature. The feature also shuffles the pictures when the page is initiated, so that they are shown in a different order each time the user visits the page (or purges it).
It is featured in Portal:Sacramento, California. Check it out to the right.
Keep in mind that the feature is a beta version. Please share your comments on how to refine this feature, at Wikipedia talk:WikiProject Portals#Refining the Picture slideshow.
We now have a one-page portal design. It isn't fully automated, nor is it even fully semi-automated, as there are still some manually filled-in areas. But it no longer requires any subpages in portal space, and that is a huge improvement. For example, Portal:Sacramento, California utilizes the one-page design concept. While is employs heavy use of templates, it does not have any subpages of its own.
This is the most cooperative team I've ever seen. With a strong spirit of working together to get an important job done. Kudos to you.
There's more. A lot more. But it will have to wait until next issue, but you don't have to wait. See what's going on at the WikiProject's talk page. — The Transhumanist 02:09, 7 June 2018 (UTC)
1) Replace the intro box sections on portals with an upgrade. See details at Wikipedia talk:WikiProject Portals/Tasks#AWB task: converting/upgrading intro sections.
2) Replace categories box sections on portals with an upgrade. See details at Wikipedia talk:WikiProject Portals/Tasks#AWB task: Converting category sections.
Enjoy. — The Transhumanist 08:08, 13 June 2018 (UTC)
VIP - heaps of questions. JarrahTree 01:30, 8 June 2018 (UTC)
Hello Evad37, thank you for your work reviewing New Pages!
We can see the light at the end of the tunnel: there are currently 2900 unreviewed articles, and 4000 unreviewed redirects.
Announcing the Backlog Elimination Drive!
Go here to remove your name if you wish to opt-out of future mailings. — Insertcleverphrasehere ( or here) 06:57, 16 June 2018 (UTC)
Don't mind that box to the right. We'll be talking about that later, below.
With the portals upgrades?
No. :)
What is almost done is the updating of the main list of portals!
There are 23 portals left to be listed.
Kudos to the WikiGnome Squadron, for spearheading this.
Once it is fully updated, we need to keep it up to date. When you complete a portal, remember to add it to Portal:Contents/Portals.
Concerning portal upgrades, we are working on those section-by-section...
The Associated Wikimedia sections of the entire set of portals have been upgraded. These are now handled on each portal base page (bypassing the previously used corresponding subpages), using the {{ Wikimedia for portals}} template rather than reiterated copied/pasted code.
So, to be more accurate on reporting upgrade progress, that's one section down (for the whole set of portals), with (about) nine sections to go. (Skipping curated portals, regarding custom content sections, of course).
Work is underway on converting Portals' introduction sections, and the categories sections.
If you would like to help, see Wikipedia:WikiProject Portals#Upgrade introduction sections and Wikipedia:WikiProject Portals#AWB task: Convert category sections
Work has also started with converting selected picture sections to picture slideshow sections. See Wikipedia:WikiProject Portals#Install picture slideshows.
Currently, there is no quality rating for portals: in the Portals WikiProject box on each portals' talk page, it just says "Portal". But times are a changin'. Quality assessment is on the way, and you can help. See the discussion.
Evad37 has figured out a way to apply the picture slideshow feature to displaying article excerpts (now you can check out the provided box above). :) This allows us to bypass page purging to see the next selection, and you can even click through them rather quickly. Currently, the wikicode for doing this for article excerpts is a bit eye-boggling, and so we are looking into simplifying it. A streamlined version may be just around the corner.
Note that this is a prototype, not ready for widespread use. Click on the box in between the lesser than and greater than signs, to see what I mean. It was meant for pictures, and so the thumbnail feature doesn't apply to article prose very well. I've presented it even though it isn't ready, to show the direction portal development is heading. See the discussion.
I'm amazed at how rapidly portals are evolving. And we're still within a single generation of portal technological evolution. Imagine what they might be in 2 or 3 more generations of developments. Pretty soon, portals will be able to shake your hand. :) — The Transhumanist 11:03, 16 June 2018 (UTC)
Can you help me fix the spelling error of "heroes" at Wikipedia:Wikipedia Signpost/Archives/2018-05-24? I can't quite figure out where it's coming from. ☆ Bri ( talk) 00:15, 21 June 2018 (UTC)
avon terrace york - good, for the centre point is it possible to resurrect the red bit... ? I was in town tonight trying to work out the config for lord street, perth - any clues? - not the centre point.. but the red line? JarrahTree 14:02, 21 June 2018 (UTC)
|location=
rather than using the infobox's automated code (like what was previously at the Avon Terrrace article, except with the recognised data type on OSM) -
Evad37 [
talk 14:42, 21 June 2018 (UTC)Just to warn you that I made a small edit to Module:Excerpt without noticing that you'd just synced the sandbox. It's easily repeated in your new version if you choose to promote the sandbox to the live module. Certes ( talk) 01:49, 22 June 2018 (UTC)
https://commons.wikimedia.org/wiki/Category:Wheatbelt_region_of_Western_Australia - is where the blue blob centrepoint system makes me see red. JarrahTree 00:24, 23 June 2018 (UTC)
You've got mail. ~ Amory ( u • t • c) 20:40, 24 June 2018 (UTC)
Interesting that "You will be able to move local wiki files to Commons..." just appeared in the tech report; I did a file move for the first time yesterday using one of the five listed tools for doing this. So I'm wondering if this feature will replace the existing modes? Or coexist? ☆ Bri ( talk) 19:22, 27 June 2018 (UTC)
Sorry, mate, lost track of what page I was on. My bad. Cheers, · · · Peter (Southwood) (talk): 09:03, 30 June 2018 (UTC)
We've grown to 94 participants.
A warm welcome to dcljr and Kpgjhpjm.
We are in the process of developing a rating system specifically for portals, as the quality assessment scheme for articles does not apply to portals. It is coming along nicely. Your input would be very helpful. See the discussion at Wikipedia talk:WikiProject Portals/General#Proposed new quality class assessments.
One of our participants got involved with this WikiProject through interest in how the new generation of portals would be handled in WP's MOS (Manual of Style). It didn't take long before he got sucked in deeper. This has given him an opportunity to look around, and so, he has made an assessment of this WikiProject's operations:
I'm quite frankly really impressed and inspired by what's happening here. If you'd asked me a year ago if I thought portals should just be scrapped as a failed, dragged-out experiment, I would have said "yes". This planning and the progress toward making it all practical is exemplary of the wiki spirit, in particular of a happy service-to-readers puppy properly wagging its technological and editorial tail instead of the other way around, and without "drama". It's also one of the few examples I've seen in a long time of a new wikiproject actually doing something useful and fomenting constructive activity (instead of acting as a barrier to participation, and a canvassing/ownership farm for PoV pushers). Kudos all around. — SMcCandlish
Congratulations, everyone. Keep up the great work.
We've run into a glitch with slideshows: they don't work on mobile devices.
Initially, we will need to explore options that allow portals to have slideshows without adversely affecting mobile viewers. See Wikipedia talk:WikiProject Portals/Design#Mobile view support.
Eventually, we may need another way to do slideshows. If we do go this route, and I don't see why we wouldn't, then (user configurable) automatic slideshows also become a possibility.
Once implemented, this will allow editors to create and edit cascading style sheets for use with templates. This will expand what we can do with portals. For more detail, see mw:Extension:TemplateStyles and Wikipedia:TemplateStyles.
We've run into an obstacle using Lua-based selective transclusion: Lua is incapable (on Wikipedia) of reading in article names from categories. Because of this, we'll need to seek other approaches for fully automating the Selected article section. We are exploring sources other than categories, and other technologies besides Lua.
Speaking of using other sources, the template {{ Transclude list item excerpt}} collects list items from a specified page, or from a section of that page, and transcludes the lead from a randomly selected link from that list. Courtesy of Certes. So, if you use this in a portal, and if the template specifies a page or section serviced by JL-Bot, you've now got yourself an automatically updated section in the portal. JL-Bot provides links to featured content and good articles, by subject.
What is "fully automated"? When you create a portal using a creation template, and the portal works thereafter without editor intervention, the portal is fully automated. That is, the portal is supported by features that fetch new content. If you have to add new article names every so often for it to display new content, then it is only semi-automated.
Currently, the Selected article section is semi-automated, because it requires that an editor supplies the names of the various articles for which excerpts are (automatically) displayed. For examples, look at the wikisource code of Portal:Reptiles, Portal:Ancient Tamil civilization, and Portal:Reference works.
So far, 3 sections are fully automatable: the introduction section, the categories section, and the Associated Wikimedia section.
Henry.
Or some other name.
Eventually, the portal department will be a software program. And we won't have to do anything (unless we want to). Not even tell it what portals to create (unless we want to). It will just do it all (plus whatever else we want it to do). And we will of course give it good manners, and a name.
But, that is a few years off.
Until then, building portals is still (partially) up to us. — The Transhumanist 13:31, 30 June 2018 (UTC)
We now have 97 participants.
Be sure to welcome our newest members, BrantleyIzMe, Coffeeandcrumbs, and Nolan Perry, with warm regards.
Work is proceeding apace. We have 2 major thrusts right now: converting the intro sections of portals, and building the components of the one-page automated model...
We need everybody, except those building software components, to work on converting intros. If you have AWB, definitely use that. If not, then work on them manually. Even one a day, or as often as you can muster, will help a lot. There are only about 1,000 of them left to go, so if everyone chips in, it will go pretty quickly. Remember, there are 97 of us!
The intros for most of the portals starting with A through F have already been converted to use the {{ Transclude lead excerpt}} template.
The standard wikicode for the automated intro that we want to put into place looks like this:
{{/box-header|Introduction|noedit=yes|}}
{{Transclude lead excerpt | {{PAGENAME}} | paragraphs=1-2 | files=1}}
{{Box-footer|[[{{PAGENAME}}|Read more...]]}}
That works for most portals, but not all. For some portals it requires some tweaking, and for others, we may have to use a different or more customized approach. Remember to visually inspect each portal you work on and make sure that it works before moving on to the next one.
Be sure to skip user-maintained portals. They are listed at Wikipedia:WikiProject_Portals#Specific_portal_maintainers.
I've started an AWB tips page, for those of you feeling a bit overwhelmed by that power user tool. Feel free to add to it and/or improve it.
We have some very talented Lua programmers, who are pushing the limits of what we can do in gathering data from Wikipedia's various namespaces and presenting it in portals. Due to their efforts, Lua is powering the selective transclusion core of our emerging automated portal design, in the form of selected article sections that rotate content, and slideshows.
To go beyond Lua's limits, to take full advantage of Mediawiki's API, we are in the midst of adding another programming language to the resources we shall be making use of: JavaScript. The ways that JavaScript can help us edit portals to boost the power of our Lua solutions, are being explored, which will likely make the two languages synergistic if not symbiotic. Research is under way on how we can use JavaScript to make some of the portal semi-automated features fully automatically self-updating, in ways that Lua cannot. Like gathering random members from a category and inserting them into a portal's templates as parameters. Once the parameters are in place, Lua does the rest.
If you would like to get involved with design efforts, or just keep up on them, see Wikipedia talk:WikiProject Portals/Design.
Well, not at the present time, because building portals is quite time consuming. The good news is that we are working on a design that will be fully automated, or as close to that as we can get. And the new design is being implemented in the portal department's main portal creation template. This means, that not only will portals update themselves, their creation will be highly automated as well. That's the nature of templates. You put them in place, and they just... work.
What I'm getting at here, is that it would be better to wait to build lots of new portals until after the new design is completed. Because with it, instead of taking hours to create a new portal, it will likely take minutes.
That does not mean we should be idle in the meantime. The main reason most of us are here is because it became apparent that portals were largely unmaintained and had grown out-of-date. This had become so apparent that a proposal was made to delete all the portals and the portal namespace to boot. That makes our main objective in the short term to improve all the existing portals so that the community will want to keep them—forever.
Building lots of new portals comes later. Let's fix up the ones we have first. ;)
And on that note, I bid you adieu. Until next newsletter, see ya 'round the WikiProject. — The Transhumanist 12:30, 10 July 2018 (UTC)
/info/en/?search=Wikipedia:Meetup/Perth/50 - apologies for late notice - hope you are able to make it!! JarrahTree 04:28, 14 July 2018 (UTC)
We have 97 participants.
Automation makes things go faster, even portal creation. One of the components Certes made was {{ Transclude list item excerpt}}. I became curious about its possible applications.
So I worked out a portal design using it, the initial prototypes being Portal:Kyoto (without a "Selected pictures" section), and Portal:Dubai (with a "Selected pictures" section). Then I used Portal:Dubai as the basis for further portals of this type...
Why?
To see, and to show, what may become feasible via automation.
It now looks highly feasible that we could get portal construction time down to a few minutes, or maybe even down to a few seconds.
The singularity is just around the corner. :)
When using the {{ Random slideshow}} template to display pictures, be sure to use the plural tense in the section title: "Selected pictures". That's because slideshows don't show up on many mobile devices. Instead the whole set of pictures is shown, hence the section title "Selected pictures", as it fits both situations.
In case you are curious, here is a list of the portals so far that have a slideshow:
|
The intros for most of the portals up through the letter "O" have been converted, using this wikicode:
{{/box-header|Introduction|noedit=yes|}}
{{Transclude lead excerpt | {{PAGENAME}} | paragraphs=1-2 | files=1}}
{{Box-footer|[[{{PAGENAME}}|Read more...]]}}
Where the pagename didn't match the article title for the subject, the title was typed in.
Most of the portals that do not contain {{/intro}}
or {{{{FULLPGENAME}}/Intro}}
have not yet been processed.
About a thousand portals use the method of selective transclusion for the intro section. That's about two-thirds. That means we have one-third of the way to go on the intro section conversions.
So much has been happening with portals that I can't keep up with it. (That's good). Which means, more in the upcoming issue. Until then, see ya 'round the project. Sincerely, — The Transhumanist 08:45, 15 July 2018 (UTC)
I got overwhelmed IRL (in real life) during the production of issue #12. So, here is a catch-up issue, to help bring you (and me) up to speed on what is happening with portals...
By the way, we still have 97 participants. (Tell all your friends about this WikiProject, and have them join!)
One cool feature of some of the geographical portals is a panoramic picture at the top of the intro section.
Check these out:
The Portals WikiGnome squadron is busy adding panoramas to geographical portals that don't yet have one. Feel free to join in on the fun. See task details at Wikipedia:WikiProject Portals#Add a panorama or skyline to a geographic portal.
Caveat: avoid super-huge pics, as they can cause portal scripts to time-out. Please try to keep picture size down below 2 megabytes. Thank you.
Speaking of pictures...
We now have two slideshow templates. You may be familiar with {{ Random slideshow}}, in which the editor types in (or copies/pastes) a list of pictures he or she wants it to display.
Well, now we have another template, courtesy of Evad37, which accepts one or more page names instead, and displays a random image off of the listed pages. So instead of listing dozens of files by hand, you can include a title or three to be scanned automatically. It even lets you specify particular sections.
The new slideshow template is {{ Transclude files as random slideshow}}.
Here's a sample, that grabs images from a single page:
Speaking of new templates, here's another one!
Also from Evad37, we have a new component for starting section boxes, that is color configurable, and that bypasses the need for box-header subpages altogether. It is {{ Box-header colour}}.
For color support, see Web colors.
For the discussion in which this was inspired, see Wikipedia talk:WikiProject Portals/Tasks#Colour combinations for accessibility.
(In case you didn't notice, the slideshow box above uses this new template).
BTW, don't forget to close your box with {{ Box-footer}}.
The answer to this question is quite involved, and would fill this page to overflowing. Therefore, this subject, including a complete update on where we are at and where we are going with portal design, is covered at Wikipedia talk:WikiProject Portals/Design.
An AWB pass to convert intros on the portals has been completed. The pass couldn't convert them all (due to various formatting configurations, etc.).
All but about 170 portals now have introductions selectively transcluded on the base page. Not counting manually maintained portals, that leaves about 70 portals that either need their intros converted, or they need an intro.
Next, we'll be converting the categories sections!
The course of action we have been taking goes something like this, with all steps being pursued simultaeneously...
1) Design a one-page automated portal model
2) Convert existing portals to that design (except those being manually maintained)
3) Remove subpages no longer needed
4) Develop further tools to empower editors working on portals
Later, when the tools are up to the task, filling in the gaps in coverage (with new portals) will also become practical.
Probably not.
Who knows what our programmers and editors have dreamed up while I was writing this.
See ya again soon, — The Transhumanist 11:06, 18 July 2018 (UTC)
real life keeps interrupting a smooth work flow on that lot - thanks JarrahTree 03:11, 19 July 2018 (UTC)
Development of design continues, full speed ahead...
Can you say " paradigm shift"?
Now, in addition to picture slideshows, we have slideshows that can display excerpts. Portals are not just for topic tasting anymore. Now they can be made useful for surveying Wikipedia's coverage of entire subjects. This gives a deeper meaning to their name. Hmmm. "Portals"... Doorways to knowledge.
Portal:Lithuania was redesigned using excerpt slideshows. Check it out.
For those of you who cannot wait to test out these new toys...
We have not one, but three excerpt slideshow components to pick from:
{{ Transclude excerpts as random slideshow}}
{{ Transclude list item excerpts as random slideshow}}
{{ Transclude linked excerpts as random slideshow}}
{{ Portal image banner}} displays a panoramic picture the width of the page, and adjusts its size, so it stays that way even if the user changes page view size. And it accepts multiple file names, so that the picture displayed randomizes between them each time the page is visited/purged.
Give resizing the page a try:
Before:
After:
Notice how the box bottoms line up. That readjusts even if you click the slideshow buttons.
The template used for this is {{ Flex columns}}.
By the way, when you include more than one box in a column, any left over whitespace in that column is divided between them.
You may have noticed the new {{ Box-header colour}} template used above. It lets you pick the color locally (right on the same page). Before, this was handled on a subpage somewhere.
Now that we have lots of toys to play with for making cool portals...
Don't forget, that the majority of views of Wikipedia these days are from mobile devices. We need to make certain that portals display well on those. So, remember to check your work on portals in mobile view mode...
To see a portal in mobile view mode, insert a ".m" into a portal's url, after "en", like this:
https://en.m.wikipedia.org/wiki/Portal:Reptile
If you discover problems in a portal you can't fix, report them on Wikipedia talk:WikiProject Portals/Design.
Have fun. — The Transhumanist 00:58, 27 July 2018 (UTC)
Someone asked me for a reference on this.
You wouldn't happen to know the link to this statistic, would you?
Thank you, — The Transhumanist 00:39, 28 July 2018 (UTC)
|
Hello Evad37, thank you for your work reviewing New Pages!
Overall the June backlog drive was a success, reducing the last 3,000 or so to below 500. However, as expected, 90% of the patrolling was done by less than 10% of reviewers.
Since the drive closed, the backlog has begun to rise sharply again and is back up to nearly 1,400 already. Please help reduce this total and keep it from raising further by reviewing some articles each day.
Go here to remove your name if you wish to opt-out of future mailings. — Insertcleverphrasehere ( or here) 00:00, 30 July 2018 (UTC)
Template:Uses TemplateStyles/sandbox/example.css has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. {{3x|p}}ery ( talk) 00:13, 30 July 2018 (UTC)
Now that we have lots of toys to play with, it's play time!
Here are some fun activities to use our new toys on...
Would you like to travel around the world? Well, this may be the next best thing...
Here's another fun toy to play with: {{ Portal image banner}}
To see what it looks like, check out the panoramas at the tops of the following portals:
The task: There are many geography portals that lack panoramas. Please add some. Please keep the file size down below 2 megabytes, and keep in mind that you may find quality banners at commons: at less than 200K (.2 megabytes). Good search terms to include with the place name are "banner", "cityscape", "skyline", "panorama", "landscape", etc.
Related task: There are also lots of geography portals that have panoramas used as gaudy banners (with print or icons splattered across them) or that display them in some random location on the page. In many cases, those pages would be improved by displaying the panorama as a clean picture at the top of the intro section, like on the examples above. This works best with banner-like panoramas. Please fix such pages when you come across them, if you believe it would improve the look of the page.
Taller images might be better suited displayed further down the page, or in the "Selected images" section.
Note that {{ Portal image banner}} supports multiple images, and displays one at random upon the first visit, and each time the page is purged.
That is, image slideshows!
Over 200 have been installed so far. Just 1200 to go. (Be sure not to install them on portals with active maintainers, unless they want you to).
The title "Selected images" reflects the fact that not all images on Wikipedia are pictures, and encompasses maps, graphs, diagrams, sketches, paintings, pictures, and so on.
The toys we have to work with for this are:
{{ Random slideshow}}
and
{{ Transclude files as random slideshow}}
The task: Using one of the above templates directly on a portal's base page, replace static "Selected picture" sections, with a section like one of these:
The one on the left uses {{ Random slideshow}} (which accepts file names), and the one on the right uses {{ Transclude files as random slideshow}} (which accepts source pages from which the filenames are gathered).
The above section formatting is used on many of the pages you will come across, but not all. In those cases, use whatever section formatting matches the rest of the page.
Note that you may come across "Selected picture" sections done with {{ Random portal component}} templates. That template call is the entire section. Replace it with a section that matches the other sections on the page, and put the new slideshow inside that.
For example, in Portal:California, this code:
{{Random portal component|max=21|seed=27|header=Selected picture|subpage=Selected picture}}
was replaced with this code:
{{/box-header|Selected images|noedit=yes}}
{{Transclude files as random slideshow
| {{PAGENAME}}
| Culture of {{PAGENAME}}
}}
{{Box-footer}}
And the new section blended right in with the formatting of the rest of the page. Note the use of the {{PAGENAME}}
magic word. Plain article titles also work. Don't feel limited to one or two page names. But be sure to test each slideshow before installing the next one. (Or if you prefer, in batches - just don't leave them hanging). Report technical problems at the
Portal design talk page.
These sections, where unmaintained, have gone stale. That's because 1) the excerpts are static, having been manually copied and pasted, and 2) because they lack automatic addition of new entries.
They can be upgraded with:
{{ Transclude random excerpt}}
or
{{ Transclude list item excerpt}}
or
{{ Transclude linked excerpt}}
All three of these will provide excerpts that won't go stale. The latter two can provide excerpt collections that won't go stale, by providing new entries over time. The key is to select source pages or source sections that are frequently updated, such as root article sections, mainstream lists, or navigation templates.
When the above tasks are completed for the entire collection of portals (except the ones with specific maintainers), we'll be more than half-way done with the portal system upgrade.
Keep up the great work. — The Transhumanist 19:10, 30 July 2018 (UTC)
I wonder why [13] was necessary? ☆ Bri ( talk) 02:08, 1 August 2018 (UTC)
{{Wikipedia:Wikipedia Signpost/Templates/RSS description|1=Title}}
, and it was still there when it was published. If there's an existing value in the RSS description, the script won't override it. -
Evad37 [
talk 02:17, 1 August 2018 (UTC)
The Technical Barnstar | |
Thank you for all of your contributions to skin-related bugs, including the patches you've submitted! I haven't seen a patch that closed as many bugs as gerrit:442021 in quite a while :) Legoktm ( talk) 04:17, 3 August 2018 (UTC) |
Hello, may you please add the dynamic wikimap parameter into those two templates, your edits on {{ Infobox building}} are very useful and better than use location map. angys ( Talk Talk) 15:10, 12 August 2018 (UTC)
/info/en/?search=Template_talk:WikiProject_Australia - I think the default should be nla but... JarrahTree 04:44, 15 August 2018 (UTC)
Discussions are underway on the design of a portal tool (user script) that will hopefully have features for modifying portals at the click of a menu item, to make editing them easier. It might do things like change the color for you, add to a selection, add a new section, move a section, and so on.
If you'd like to be involved and suggest features for the tool, please join us at Wikipedia talk:WikiProject Portals/Design#What would you want a portal tool to be able to do?.
As new portal components are built by our Lua gurus, those components are being used to upgrade portals. Each component automates a section of a portal in a particular way.
The sections that are mostly upgraded so far are the Intro, and the Associated Wikimedia section.
The sections currently undergoing upgrade are: Selected image, Categories, and the Intro.
The Intro? Isn't that done already?
Yes, and no.
The upgrade of the excerpt in intros is mostly complete (there are about 70 non-standard portals that still need it).
Now we are doing another upgrade of intros in the form of adding a panoramic picture at the top of the intro, on portals for which such a picture is available on Commons:. Dozens of panoramas have been added so far, and they are really starting to affect the look of portals — the portals that have them look really good.
Regions are the most likely subjects to have panoramas, but a surprising number of other subjects have banner-shaped pictures too. Some examples of non-geographic portals that they have been added to are:
Speaking of pictures, several hundred Selected image sections have been upgraded to include image slideshows.
The push for automation continues, with new components under continuous testing in the field. As problems are spotted, they are reported to our programmers, who have done a fantastic job of keeping up with bug reports and fixing the relevant Lua modules fast. I am highly impressed.
Construction time on new portals is now down to as little as a minute or less. Though not in general. If you are lucky enough to spot portals that fit the profile of the new tools (their strengths), then a portal can be complete almost as soon as it is created, with the added time it takes to find and add a panorama. Source page titles are not generally standardized, and so it source pages in many cases must be entered manually. Where source page titles follow a standard naming convention, portal creation for those subjects goes quickly.
So, we still have some hurdles, but the outlook on portals is very good. New features, and many improvements to features are on the horizon. I'll be sure to report them when they become available.
What will the portal of the future look like? That is up to you!
See you on the project's talk pages.
Sincerely, — The Transhumanist 21:04, 15 August 2018 (UTC)
This issue is about portal creation...
Myself and others have been testing and experimenting with the new components in upgrading existing portals and in building new portals. They have now been applied in hundreds of portals.
The templates are ready for general use for portal creation.
They are still a bit buggy, but the only way we are going to work the rest of the bugs out is by using them and reporting the bugs as we come across them.
I look forward to seeing what new portals you create!
Be sure to report bugs at WT:WPPORTD.
The main portal creation template is {{ box portal skeleton}}.
After starting a portal using {{ box portal skeleton}}...
Check out the Did you know? section on Portal:Determinism. — The Transhumanist 02:21, 22 August 2018 (UTC)
Hello Evad37! Thank you for the magic you did at {{ Infobox building}}. :-) A quick question, if you edit a random page which uses Infobox building, you will notice that in the edit mode, when clicking preview, the map has additional zoom-in/zoom-out buttons, and also zooms in/out when scrolling over the map. Would you know if this functionality could be made available in the viewing mode as well? Maybe at least the zoom buttons? Best regards, Reh man 10:48, 24 August 2018 (UTC)
code will insert a simple interactive map ... with the ability to maximize it by either double-clicking the map or clicking the icon in the right corner. Which might mean the documentation is outdated, e.g. static maps might be needed for performance reasons... except that on test2wiki (a test site running the latest version of the software) dynamic thumbnails are shown when viewing a page, e.g. [15]. I've asked for clarification on Phabricator; See also mw:Help talk:Extension:Kartographer § Map maximizing on single click? - Evad37 [ talk 03:35, 25 August 2018 (UTC)
Regarding the upcoming tech report. Do you think the visibility of the server switch should be higher? I'm not sure if the "up to" one hour editing outage is realistic or a worst-case scenario. ☆ Bri ( talk) 16:11, 25 August 2018 (UTC)
The second issue of the Timeless newsletter is out.
The news: Themes are coming to Timeless! Your infobox and navbox templates in particular are probably going to look absolutely horrible in the new built-in night mode.
For more information, background, plans and progress updates, please see the
full issue on Meta, complete with a ridiculous list of phabricator task links, gratuitous mention of other skins, and me complaining about the current state of MediaWiki skinning in general.
If you want to move my DateCountdown widget to shared space go ahead. It could be a community tool. ☆ Bri ( talk) 04:17, 30 August 2018 (UTC)
As you know, portals are now supported by a number of new templates, which are in turn supported by some new Lua modules.
Those templates and modules are being put to the test, in the new portals that have been created since this WikiProject rebooted, plus a number of existing portals that have been revamped.
The new portals, and revamped ones, can be found at Category:Single-page portals.
Please browse the new portals at your leisure, and report any and all problems that you spot. Post bug and other portal problem reports at WT:WPPORTD. Please report bugs, quirks, awkward aspects, or anything weird or off that you notice. Compliments and suggestions are also welcome. :)
When you report a bug, please indicate the portal's name, the section that the problem appeared in, and the name of the article appearing (first) in the section with the problem. Most problems will likely be encountered in the Selected general articles" section, due to quirks in a displayed article's wikicode that the lua modules don't handle yet. Your help in spotting those is of utmost value. Thank you.
For portals that have been converted to the single-page design, we are not deleting their subpages at this time, because we are working on ways to harvest the data from those pages. For example, the Selected picture subpages include filenames and captions that would be valuable for the image slideshows. Please don't delete portal subpages, for now. They'll be slated for d-batch speedy deletion after harvesting. Thank you.
We are currently testing a feature added to {{ Transclude files as random slideshow}} that allows it to accept both sourcepages and filenames. Courtesy of Evad37. This will pave the way for harvesting files and their captions from portal subpages, for use in image slideshows.
The bulk of the work is being done by a handful of editors. But we can't do it all. We need help with spotting bugs, refining the search parameters in new/revamped portals (in the "Did you know..." and "In the news" sections), adding images to slideshows for a broader selection (they default to showing the images on the root article page but are capable of showing so much more), adding panoramic pictures at the top of the intro section of region portals (cities, counties, states, provinces, countries, continents, and other regions), to name but a few task types.
It is rewarding to be a part of the growing portal phenomenon. And you get to see its expansion and refinement up close.
Feel free to join in on the fun. ;)
Thank you, — The Transhumanist 06:50, 4 September 2018 (UTC)
Hi! I patrol Category:Templates with missing files and just wanted to quick let you know that your template is currently showing up in there due to a missing file(s) somewhere. I attempted to fix it myself, though I'm not finding what's causing the error. No worries and you're welcome to just leave it the way it is if you like, just thought I'd let you know in case it would help with testing process in some way. All the best, Katniss May the odds be ever in your favor ♥ 21:08, 3 September 2018 (UTC)
|thumb
from transcluded images, but did not take account of |thumbnail
also being a valid syntax. So [[File:Cat_playing_with_a_lizard.jpg|thumbnail|alt=Cat playing with a lizard|Cat playing with a lizard]]from Cat#Play got turned into
File:Cat_playing_with_a_lizard.jpgnail|alt=Cat playing with a lizard|Cat playing with a lizardinstead of
File:Cat_playing_with_a_lizard.jpg|alt=Cat playing with a lizard|Cat playing with a lizardThanks for letting me know, so I could investigate and fix this error. - Evad37 [ talk 02:47, 4 September 2018 (UTC)
frame
and framed
. Not sure if that applies here too.
Certes (
talk) 07:49, 4 September 2018 (UTC)
Hello, I noticed you assessed Imaqtpie as Start class. It is one of my first articles I have created, so I was wondering if you would please give me some advice on how to improve it to C class or better? I have already taken a look at Wikipedia:WikiProject_Video_games/Assessment#Quality_scale but I am still confused. Thank you. Derek M ( talk) 17:26, 6 September 2018 (UTC)
The Technical Barnstar | |
XFDcloser is just brilliant. Nothing more to say.. Galobtter ( pingó mió) 05:17, 7 September 2018 (UTC) |
I'm writing a user script.
I need to preview a page rather than save (submit).
How do you do that?
(More importantly, how do you find that information? I couldn't find it in the API) ( https://en.wikipedia.org/w/api.php)
I look forward to your replies. — The Transhumanist 23:33, 26 August 2018 (UTC)
document.editform.submit();
$('#wpPreviewWidget > input').click();
. Which then causes the page to reload, so you can't do anything with the script after that point (or at least not easily) -
Evad37 [
talk 07:04, 6 September 2018 (UTC)
<title>
that starts with "Creating", and the page has an empty edit window on it. When you Ctrl+click on that redlink, you get a tab; then, when you go to that tab, there's the same page I just described. So, there appears to be a page that exists as soon as you go there. It looks like a perfectly viable html page to me. The thing I don't understand is, why the script runs in the first instance of that page, and not the second. —
The Transhumanist 07:56, 6 September 2018 (UTC)
After I added your line for previewing the page, it worked, but each tab went into an endless loop, because the script ran again each time a new edit page was presented (which is what happens with preview). So I added a conditional so it would only continue if the page was empty, and a weird thing happened. The tabs went into an endless loop until I looked at them. Meaning they were empty until I actually went there. Bizarre. I have no idea why it is behaving that way. But, on the bright side, I'm further along with this thing than I was. Thank you.
I'll tinker around with it some more, and will let you know how far I get. — The Transhumanist 05:12, 7 September 2018 (UTC)
The problem went away after turning wikEd off. Works like a charm. Thank you for your help. — The Transhumanist 05:38, 7 September 2018 (UTC)
Hi Evad37, How difficult would it be to write a template that transcludes the short description of an article as an annotation?
The usage would be something like {{
Transclude short description|Foo}}
and should return A metasyntactic variable commonly used in template discussions
. It would mainly be useful to annotate a list of article links, so {{
Annotated link|Foo}}
would return [[Foo]] – A metasyntactic variable commonly used in template discussions
which would be useful in list articles like indexes. Part of it should be easy, as manually edited short descriptions are generally near the top of the article and use a consistent and straightforward syntax, {{short description|A metasyntactic variable commonly used in template discussions}}
, but some are embedded in infoboxes and disambiguation notice templates. Even just working with the standard short description template would be useful. Cheers, · · ·
Peter (Southwood)
(talk): 10:05, 6 September 2018 (UTC)
{{Template parameter value|Achilles|short description|1|1}}
→ Greek mythological hero -
Evad37 [
talk 05:34, 13 September 2018 (UTC)
Hey...
If you have AWB laying around, please dust it off and crank it up! ;)
We have a growing backlog!
There are now 539 portals. Of those, 51 are of the new design.
Many of the new portals are orphaned or near orphaned, and need links pointing to them:
To make a list of corresponding templates, you can use AWB's make list feature to make a list of the pages in
Category:Single-page portals. Then you copy that list to a sandbox, and replace \nPortal:
with ]]\n* [[Template:
, using
WP:wikEd. That will give you a list of templates to work on. Then you set skip in AWB to skip the ones that already have the portal link.
To make a list of corresponding root articles, make a list of portal links, and then remove "Portal:" from the links.
To make a list of category links to process, make sure you use a leading colon (:) in the category links, like this: [[:Category:Blue Öyster Cult]]
.
All new and revamped portals can be found at Category:Single-page portals.
Thank you. — The Transhumanist 20:44, 17 September 2018 (UTC)
Hello Evad37, thank you for your work reviewing New Pages!
The New Page Feed currently has 2700 unreviewed articles, up from just 500 at the start of July. For a while we were falling behind by an average of about 40 articles per day, but we have stabilised more recently. Please review some articles from the back of the queue if you can (Sort by: 'Oldest' at Special:NewPagesFeed), as we are very close to having articles older than one month.
List of other useful scripts for New Page Reviewing
|
---|
|
Go here to remove your name if you wish to opt-out of future mailings. MediaWiki message delivery ( talk) 23:11, 17 September 2018 (UTC)
The publication date for the Signpost is fast approaching, and your section seems to need some amount of work until it's publishable. Please continue working! Eddie891 Talk Work 15:10, 19 September 2018 (UTC)
next meetup thingoes for next event in perth are a real mess - and you are so good at fixing it up - 16th cancelled till following week - any chance to have a once over of all the points of mistakes etc? if you are able much appreciated. thanks JarrahTree 23:49, 19 September 2018 (UTC)
Five years! |
---|
-- Gerda Arendt ( talk) 06:53, 22 September 2018 (UTC)
Don't blink. You might miss something.
As of a few days ago, portals had doubled in about a month and a half.
Also, there were 98 incompleted portals in Category:Portals under construction. Now there are just 43.
The goals, plans, and task sections have all been updated.
Many new portals are still orphans, and need links pointing to them:
All new and revamped portals can be found at Category:Single-page portals.
This is the main list of portals.
Nearly 2,000 of the new portals need to be listed here.
They can be found at Portal talk:Contents/Portals#These are not listed yet. Instructions are included there.
Portals now have a new rating system of their own designed specifically to support portal evaluation! We were trying to use the standard assessment system for articles, but that doesn't fit portals very well.
Many thanks to Evad37, Waggers, AfroThundr3007730, SMcCandlish, Tom, BrendonTheWizard, and Pbsouthwood for their work and input on this.
The new system can be found at the top of all portal talk pages, in the WikiProject portals box. Those with "???" ratings need to be assessed, which makes up most of the older portals.
Most of the new portals were started out with an initial "Low" level of importance when their talk pages were created. Those deserving higher importance should be promoted as you come across them.
The starting point for new portals included minimal parameters and content, in the form of default values in the template(s) used for their creation.
So, for the search strings in the "Did you know..." and "In the news" sections, this was the magic word {{PAGENAME}}
, which represents the portal's name. Unfortunately, the resulting term is alway capitalized, which limits its effectiveness as a search string for anything but proper nouns. Results for those two sections can be improved, by replacing the "PAGENAME" magic word with multiple search strings, and search strings that begin with lower case letters. There is no inherent limit as to how many search parameters may be included. Lua search notation is used. The more general the subject, the more subtopic search terms you may want to include. For example, on
Portal:Avengers (comics), {{PAGENAME}}
turned up nothing. But, when more parameters were added, as in the wikicode below...
{{Transclude selected recent additions | {{PAGENAME}} | Iron Man | Spiderman | Antman | Hawkeye | The Hulk | Incredible Hulk | David Banner | Captain America | Scarlet Witch | Black Widow | Tony Stark | Nick Fury | Age of Ultron | Infinity War | months=36 | header={{Box-header colour|Did you know... }}|max=6}}
... that returned several results in the portal's DYK section.
Be sure you make the improvements to both the DYK section and the "In the news" section, as they both require the search strings.
The default starting selection for the image slideshow in most new portals is whatever images happen to be in the corresponding root article (via the PAGENAME magic word). You can improve image slideshows by adding more sourcepages and filenames as parameters in the "Selected images" section of portals.
See Template:Transclude files as random slideshow/doc for instructions.
Portals used to take about 6 hours or more to create. Now, for subjects that have particular navigation support, we've got that down to about one minute each, with even more content displayed than ever. True, that means the new portals pick you, rather than the other way around. Creating a specific portal that doesn't happen to have the requisite navigation support is still pretty time consuming. But, we are working on extending our reach beyond the low-hanging fruit.
And efforts are ongoing to keep shaving time off of the creation process. Eventually, we may get it down to seconds each.
In addition to improving automation, we're always looking for new features and improvements that we can add to portals, and there is plenty of potential to expand on the standard design so that new portals are even better right out of the starting gate. Additional designs are also possible.
On the horizon, there are many more portals waiting to be created. And we can expect to see at least a few more section types emerge. I never expected slideshows, for example, especially not for excerpts. Who knows where innovation will take us next?
Keep up the great work everyone.
Sincerely, — The Transhumanist 07:06, 23 September 2018 (UTC)
Hi Evad. Saw that you started a Technology report for September issue. Will it be possible to make it ready for copyedit soon? Say in next 24-48 hours? I'd like to publish in month of September. ☆ Bri ( talk) 14:27, 28 September 2018 (UTC)
The SPS does not appear in my pull-down menu. I had no issue last month. I jumped on another computer (different OS/ different browser) and it still doesn't appear. I had no problem last month and I cannot figure out what changed. Chris Troutman ( talk) 23:04, 30 September 2018 (UTC)
importScript('User:Evad37/SPS.js');
from your common.js and then see if it's there when you go to the newsroom, in case one of the other scripts you are using is interfering. -
Evad37 [
talk 23:53, 30 September 2018 (UTC)
Hi there. I raised an idea at Wikipedia talk:WikiProject Video games#Semi-automating cover upload? and would need someone very skilled (like you!) to implement it. Basically, it would be a upload- and edit-script that works like this:
Do you think you can create such a script? And more importantly, would you be willing to? Regards So Why 09:40, 27 September 2018 (UTC)
The Technical Barnstar | |
For your tool User:Evad37/rater.js Dreamy Jazz 🎷 talk to me | my contributions 21:16, 7 October 2018 (UTC) |
The Technical Barnstar | |
For the genius creation that is User:Evad37/Covery and the help you provide all the time. If you ever reconsider RFA, I'd be happy to nominate you. Regards So Why 12:23, 9 October 2018 (UTC) |
Whew, a lot has been happening.
A bit of defending of the portals has been needed. But, most activity recently has been directed upon maintenance and development of existing portals.
The majority of portals now use the new design, about 2400 of them, leaving around 1200 portals that still employ the old style.
Please inspect these portals, and report problems or suggest improvements at WT:WPPORTD. Thank you.
Since the last issue of this newsletter, Nineteen portals were nominated for deletion. All posted by the same person.
Two portals were deleted.
One resolved as "no consensus".
Sixteen resolved as "keep".
Links to the archived discussions are provided below:
Many thanks to those who participated in the discussions.
To watch for future MfD's, keep in mind that the Portals WikiProject is supported by automatic alerts. You can see them at: Wikipedia:WikiProject Portals#Article alerts: portals for deletion at MfD
There was also some discussion of creation criteria for portals. The result was that one of the participants in the discussion reverted the portal guidelines to the old version, which has the minimum number of articles for a portal included in there: "about 20 articles", a guideline that was in place since 2009.
Many of the portals that existed prior to April 2018 do not have that many (being limited to however many subpages the portal creator created), and therefore, these portals need to be upgraded to the new design (which automatically provides many articles for display). Using the new design, exceeding 20 articles for display is very easy.
Efforts have been underway to place links to new portals (all 2200 of them created since April).
Your help is needed. It is easy to access the page mentioned in #1, #2, & #3 from the portals themselves.
AWBers could do these tasks even faster (that's how the category pages were done), except #4...
Item #4 above pretty much has to be done by hand. (If you can find a way to speed that up, I would be very impressed). The links needing placement can be found at Portal talk:Contents/Portals#These are not listed yet. Instructions are included there.
There are still around 1200 old-style portals that have only undergone partial conversion to the new design concepts, still relying on subpages with copied/pasted excerpts that have been going stale for years, out of date (manually posted) news entries, etc.
The section currently being tackled on these is news. You can help by deleting any news section on the old-style portals that has news entries that are years old (that is the dead giveaway to a manual news section). Be sure not to delete the news sections of portals that have up-to-date news, or active maintainers. For maintainers, look at the portal's categories, and/or check the participants list at WP:WPPORT.
Eventually, conditional news sections (that appear only when news items are available for display) will be added using AWB to all portals without a news section.
News items (and even the news sections themselves) are automatically generated for portals that were created using the Basic portal start page. On those portals, there is a hidden comment at the top of the page (that you can see in the edit window), that says this:
<!-- This portal was created using subst:Basic portal start page -->
Presently, we are in the process of implementing the new design features, creating new portals with them, and installing them in existing portals.
But, what about development of new new design features?
We have a wish department.
Post your wishes at Wikipedia talk:WikiProject Portals/Design#Discussions about possible cool new features, and they might come true. Many have already, and for many of those, this is where they were posted.
A resource that has been elusive so far will be obtained eventually: categories. That is, the ability to pull category member links to populate a page.
Rather than populate portals directly with such links, it may be more beneficial to the encyclopedia to utilize them in navigation footers, because portals already have the ability to generate themselves based on those.
So, this would create a cascade effect: auto-gathering entries from categories, would enable the construction of new navigation footers, that would in turn support the development of new portals.
The cascade effect would also be felt by existing portals, as existing navigation footers could be expanded using the category harvesting methods, which would in turn expand the coverage of portals that access those navigation footers.
You can help by providing leads about any potential category harvesting methods. Please report anything you know about harvesting categories at WT:WPPORTD. Thank you.
One idea that has been floating around is the concept of a pageless portal. That is, a portal that isn't stored anywhere, instead being generated when you click on a menu item or button.
Many of the new portals were generated by a single click, and then saved via a second click.
Therefore, it seems likely that the portals of the future will employ the one-click concept.
Because of the need for customization by users, this concept would need to be augmented with a way to integrate user contributions. This could be done in at least two ways: posting an existing portal, autogenerating one from scratch if such does not yet exist, or have a special data page for user contributions that is folded into the auto-generated portal.
How soon? That is up to you. All that is needed are persons to implement it.
Keep up the good work on portals. They are improving daily. Thank you. — The Transhumanist 04:18, 12 October 2018 (UTC)
Kaya, I trying to create a template that can be used to identify each of the Noongar origins for the different spellings. that way we put a template say in quenda and show each of the regional variants in spelling names. or if there is no known word not include that group in the list. I know it'll be a quick one for you to do, I have created User:Gnangarra/sandbox/nys help with what I'd like to see. thanks in advance Gnan garra 13:30, 13 October 2018 (UTC)
Hi Evad37,
Are you perhaps interested in working on a new stub-tagging script or on a new automatic copyvio checking script? I put two requests in over at the
script requests page with some details. Feel free to decline if busy or if you think them too tedious. The copyvio one especially would be of huge benefit to the wiki. —
Insertcleverphrasehere (
or here) 22:37, 19 October 2018 (UTC)
Hi Evad37, hope all is well with you. Just wondering if you were planning to contribute to the issue 11 Technology report? ☆ Bri ( talk) 20:17, 20 October 2018 (UTC)
|
Hello Evad37, thank you for your work reviewing New Pages!
As of 21 October 2018 [update], there are 3650 unreviewed articles and the backlog now stretches back 51 days.
Go here to remove your name if you wish to opt-out of future mailings. — Insertcleverphrasehere ( or here) 20:49, 21 October 2018 (UTC)
Portals have passed the 4,000 mark.
Here's a list of portals created since the last issue
Please inspect these portals, report problems or suggest improvements at WT:WPPORTD, or develop them further (see below). Thank you.
There is still lots to do...
There are many subject gaps that need to be filled. This can be done by creating new portals, or by adding Selected article sections to existing portals. To create a new portal, simply place {{subst:Basic portal start page}}
on an empty portal page, and click "Preview". If the portal is complete, click "Save". After you try it, come share your experience and excitement at
WT:WPPORTD.
Each new portal is just a starting point. Each portal of the new design can be further developed by:
Besides the new portals, there are still about 1200 portals of the old design that need to be converted to the new design.
Many portals need to be de-orphaned, by placing links to them (in the See also section of the corresponding root articles, at the bottom of the corresponding navigation footer templates, and on the corresponding category pages).
Many of the new portals still need to be listed at Portal:Contents/Portals.
Bugs keep popping up in portals. These need to be tracked down and reported at WT:WPPORTD.
Tools are needed to make developing and maintaining portals quicker and easier.
Dreaming up new features and capabilities. Innovation needs to continue, to design the portal of tomorrow, and the portal development-maintenance-system of the future. Automation!
So, if you find yourself with a little (or a lot) of free time, pick an area (or more) above and...
...dive in! — The Transhumanist 07:04, 25 October 2018 (UTC)
P.S.: Evad, there's a bunch of new feature idea posts at WT:WPPORTD.
I see from the page history that you created Template:Maplink. I have tried a number of times to get this feature to work but have only managed to get a single point to work. I have copied one of my attempts below and would appreciate an indication of where I am doing it wrong. I do understand basic template and lua syntax but not these geodata concepts. — Frayæ ( Talk/ Spjall) 12:18, 25 October 2018 (UTC)
|frame-lat=
and |frame-long=
.
Galobtter (
pingó mió) 12:26, 25 October 2018 (UTC)|frame-width=
and |frame-height=
is something you also may want to change too.
Galobtter (
pingó mió) 12:28, 25 October 2018 (UTC)
Hi,
Do you know why some hospitals have a red boundary around their main buildings on the mapframe maps (in the infobox) wheras others do not?
ClippednPinned ( talk) 11:22, 2 November 2018 (UTC)
Give a hearty welcome to AmericanAir88, who has adopted working on portals as one of his main purposes on Wikipedia. So far, he has created the following portals:
Way to go!
Evad disappeared from Wikipedia on October 18.
He has been, and will continue to be, sorely missed.
Hopefully, he is okay, on a Caribbean cruise or something.
Portals of the old design, are slowly but surely being converted to the new single-page design.
One factor that has slowed things down is that for many sections, the section header call and section contents call are integrated into a template and buried in a lua module, locking them in on each portal. They have been that way for years.
This means that these sections can't be directly edited like the other sections on the same portal. So, search/replaces affect all the sections except those. So, upgrading headers on these portals, for example, misses the integrated sections and inadvertently results in 2 different header colors.
Before we can continue with the upgrade of these portals, the headers and section contents calls need to be restored to each portal, so that those can be edited in concert with the other sections on the portal, and worked on independently of each other.
This is underway, with a solution implemented on about 1/4 of the affected portals so far. Around 300 of them. The remaining 900 should be done within a couple weeks or so.
We now have banner-shaped pictures included in the introduction sections of 180 portals. The rarity of such pictures has made it difficult to find suitably narrow images for display across the tops of portals.
We have a solution for this, courtesy of FR30799386...
Most pictures are not banner-shaped. But, you can still use them as banners. Here's how:
{{Portal image banner|File:Blueberries .jpg |maxheight=120px |overflow=Hidden }}
Using both maxheight=120px
and overflow=Hidden
produces this:
There are now 4,140 portals, with more being created almost daily. Prior to this project's reboot, portals were created at about the rate of 80 per year. Since April of this year, we've created about 2,600 new portals, or 32.5 years' worth at the old rate.
Of those new portals, about 3/4 of them need links leading to them. Almost all of them are linked to from the category system, but they still need links in article see also sections, at the bottom of navigation templates, and on the main portals list at Portal:Contents/Portals.
Of the 1500 portals created before the reboot, about 300 have been completely converted to the new design so far. About 1100 more have been partially converted, with intros, image slideshows, and associated wikimedia sections getting the most attention.
Discussion has resumed on the portal guidelines.
See ya round the portal system! — The Transhumanist 11:42, 11 November 2018 (UTC)
Hi, this worked great but then it stopped so I deleted it and readded it later but now it wont load at all and am getting the following javascript error: index.php?title=User:Evad37/XFDcloser/v3.js&action=raw&ctype=text/javascript at line 1772: SyntaxError: Unexpected token ')'
Please advise, thanks Atlantic306 ( talk) 13:17, 8 November 2018 (UTC)
Dear Evad37, can you please see page User:Nitobus/test, and research why map number 6 (from6=moscowborders.ru/Crd/50-G.Dolgoprudny.map) does not displayed. Thank you in advance. Nitobus ( talk) 19:09, 14 November 2018 (UTC)
Chart of the New Pages Patrol backlog for the past 6 months. |
Hello Evad37,
Go here to remove your name if you wish to opt-out of future mailings. — Insertcleverphrasehere ( or here)18:37, 16 November 2018 (UTC)
Hello, Evad37. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery ( talk) 18:42, 19 November 2018 (UTC)
It's been a month since the last logon. If anyone knows, please let the rest of us know. — The Transhumanist 00:43, 20 November 2018 (UTC)
Hi Evad37, I hope that you're well! I was wondering if you would have time to help create a script for us over at peer review to help close reviews. It's not a particularly cumbersome process but can get quite time consuming if there are lots of reviews, and a script would be very helpful. I posted a description of what I think could happen at Wikipedia_talk:Twinkle#Feature_request_-_Peer_review and was wondering if this is something you could help out with? We'd be very thankful! -- Tom (LT) ( talk) 00:19, 19 November 2018 (UTC)
you are missed, trust all is ok - happy christmas at least!!! JarrahTree 00:13, 12 December 2018 (UTC)
Hello,
I have noticed that you marked the portal Australian roads for manual maintenance in June 2018, but this notice has not been updated in 6 months. This notice needs to be kept up to date to reflect the current status of the portal in December 2018. You can:
If you don't respond by updating the date in the notice in 2 weeks, then your name will be removed from the notice and the portal marked for automatic maintenance.
Thanks for your dedication to Portal:Australian roads. If you have questions about this message please {{ ping}} me about it. Thanks and happy editing, Dreamy Jazz 🎷 talk to me | my contributions 23:44, 13 December 2018 (UTC)
Hello Evad37,
This year's award for the Reviewer of the Year goes to Onel5969. Around on Wikipedia since 2011, their staggering number of 26,554 reviews over the past twelve months makes them, together with an additional total of 275,285 edits, one of Wikipedia's most prolific users.
See also the list of top 100 reviewers.
The backlog is now approaching 5,000, and still rising. There are around 640 holders of the NPR flag, most of whom appear to be inactive. The 10% of the reviewers who do 90% of the work could do with some support especially as some of them are now taking a well deserved break.
At #1 position, the Community Wishlist poll closed on 3 December with a resounding success for NPP, reminding the WMF and the volunteer communities just how critical NPP is to maintaining a clean encyclopedia and the need for improved tools to do it. A big 'thank you' to everyone who supported the NPP proposals. See the results.
Due to a number of changes having been made to the feed since this three-minute video was created, we have been asked by the WMF for feedback on the video with a view to getting it brought up to date to reflect the new features of the system. Please leave your comments here, particularly mentioning how helpful you find it for new reviewers.
If you wish to opt-out of future mailings, go here.
MediaWiki message delivery ( talk) 21:14, 14 December 2018 (UTC)
Welcome to the third issue of the Timeless newsletter, complete with a somewhat dubious explanation of where I've been all this time.
Somewhat dubious explanation of where I've been all this time:
I suffered a rather bad concussion in October, which knocked me pretty much completely out of commission through November, and I'm still recovering even now. One person = bus factor of one, even though it wasn't actually a bus but a very short flight of stairs.
Updates:
Comments on the RfC ( MediaWiki wiki RfC page, task) or bugs, or further reports, are always appreciated.
Until next time, hopefully with no further injuries,
Hi there all TPSs. I'm back after a longer than expected wikibreak. I'll be catching up with what I've missed over the next couple of weeks, but feel free to let me know if there's anything in particular you want me to look at. Cheers, - Evad37 [ talk 05:32, 21 December 2018 (UTC)
Hi. Recently, I discovered a passion for created and understanding user scripts on wikipedia, and am planning to create a monthly newsletter about new scripts and related projects (created by anyone, not for simply promoting my own), as well as currently pending user script requests, Wikipedia-related JavaScript tips/tricks, and other related information. This message was sent to you because you are listed as a member of the user script developers category. If you would like to subscribe to this upcoming newsletter, please go to User:DannyS712/subscribe to scripts and add yourself. If you have any questions, please reach out and talk to me。 -- DannyS712 ( talk) 05:22, 23 December 2018 (UTC)
Last issue, I mentioned there would be a flood, and so, here it is...
We now have 4,620 portals.
And the race to pass 5,000 by year's end is on...
Can we make it?
The New Year, and the 5,001st portal, await.
( New portals are created with {{subst:Basic portal start page}}
or
{{subst:bpsp}}
)
After disappearing in mid-thread, Evad37 has returned from a longer than expected wikibreak.
Be sure to welcome him back.
User:FR30799386 is working on making {{ Portal image banner}} even better by enabling it to chop the top off an image as well as the bottom.
Many pictures aren't suitable for banners because they are too tall. Therefor, User:FR30799386 added cropping to this template, so that an editor could specify part of a picture to be used rather than the whole thing.
Work has begun on upgrading Wikipedia's flagship portals (those listed at the top of the Main page).
So far, Portal:Geography, Portal:History, and Portal:Technology have been revamped. Of course, you are welcome to improve them further.
Work continues on the other five. Feel free to join in on the fun.
In place of many missing portals, there is a redirect that leads to "the next best topic", such as a parent topic.
Most of these were created before we had the tools to easily create portals (they used to take 6 hours or more to create, because it was all done manually). Rather than leave a portal link red, some editors thought it was best that those titles led somewhere.
The subjects that have sufficient coverage should have their own portals rather than a redirect to some other subject.
Unfortunately, being blue like all other live links, redirects are harder to spot than redlinks.
To spot redirects easily, you can make them all appear green.
And I'll see you next issue.
Sincerely, — The Transhumanist 08:08, 26 December 2018 (UTC)
It is now faster to build a portal than to place the links leading to it. So, I've been trying to write a link placer.
P-link stands for "portal link".
When completed, it will place links in 3 locations leading to a portal: on the corresponding category page, in the See also section of the corresponding article, and at the bottom of the corresponding navbox footer template. This will save loads of time, and should bring portal creation including link placement, down to under a minute for each portal.
I've got the "P link on category" menu item for placing the category page link working, sort of, but I had to resort to programming it to click the menu item up to 3 times instead of once, depending where you start from. I'd like it to work with one click from all of the allowed starting locations. It's a puzzle that has me stumped - working through the problem in my head or on paper with locally stored variables, I keep running into ambiguities discerning page types that I can't figure out. Once that problem is solved, I can move on to the other 2 menu items. — The Transhumanist 02:59, 26 December 2018 (UTC)
P.S.:pinging @ Certes and FR30799386:
?action=edit&plink=yes
. Then, for category edit pages, you check if the plink=yes
is in the URL: If so, you skip to the code that inserts the portal; if not, you add the menu item that when clicked will do that.mw.config.get('wgAction')
will result in "edit" for the initial edit page, and "submit" for the preview edit page -
Evad37 [
talk 08:17, 27 December 2018 (UTC)hope you had a good christmas, and will have a good new year
Dear Evad37, can you please see page User:Nitobus/test, and research why map number 6 (from6=moscowborders.ru/Crd/50-G.Dolgoprudny.map) does not displayed. Thank you in advance. Nitobus ( talk) 18:45, 26 December 2018 (UTC)
from
number
[21], but doesn't work when just in |from6=
. Which is quite weird, because there's nothing in the module code that would make |from6=
behave differently to the other positions. -
Evad37 [
talk 02:47, 27 December 2018 (UTC)
Before, we could only cut off the bottom of pics.
User:FR30799386 has pulled it off, and made the upgrade to {{ Portal image banner}}...
So, this:
Becomes this:
Here's the code for the above banner:
{{Portal image banner|File:American Falls from Canadian side in winter.jpg | [[Niagara falls]], from the Canadian side |maxheight=175px |overflow=Hidden|croptop=10}}
To see it employed in a portal, check out Portal:Niagara Falls.
We were racing against time to create 5,000 portals by the end of the year (just for the heck of it).
We made it. We've passed the 5,000 portals mark, with time to spare!
And the 5,000th portal is Portal:Major League Baseball, by Happypillsjr.
Congratulations!
The 10,000th portal mark. But...
...there is plenty else to do in addition to building new portals:
And whatever else you can dream up.
But most of all, have a...
Evad37, thank you for your contributions to the Portals Project, and have a prosperous, productive and enjoyable New Year.
Sincerely, — The Transhumanist 11:54, 30 December 2018 (UTC)
News and updates associated with user scripts from the past month (December 2018).
Hello everyone and welcome to the brand new Wikipedia Scripts++ Newsletter:
Scripts Submit your new/improved script here
|
|
Wishing you a happy new year, -- DannyS712 ( talk) 20:01, 31 December 2018 (UTC) |
This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Evad37,
Have a prosperous, productive and enjoyable
New Year, and thanks for your contributions to Wikipedia.
Eddie891
Talk
Work 00:00, 1 January 2018 (UTC)
Send New Year cheer by adding {{ subst:Happy New Year fireworks}} to user talk pages.
In StripSearchSorted.js we added bullets and double square brackets for copying linked items straight off the page for pasting into an editor.
Now I've started ViewAsOutline-CategoryTree.js to do that in the Special:CategoryTree utility. But, the display starts out collapsed, with very few article names showing. Clicking on each category to expand them is very tedious, so I included a menu item to expand all of the categories at the same time (one level at a time) and another to collapse them (so far, all at once). There is also a menu item for adding wikilink formatting, and another to hide it.
The problem I've run into is, once you click on the Wikicodify menu item, further expanding and collapsing do not work. If you get the categories you want showing before you Wikicodify, you're fine. But if you don't, you have to reload the page and start all over again.
I think it has something to do with the "Brackets" class I added in this version. I stuck that class in there so that Wikicodify wouldn't match the entries that it already inserted link formatting into, so that it wouldn't insert it again. I was expecting to be able to further expand the category tree after the insert operation, but unexpectedly nothing happens when you click on the expand or collapse menu items after that.
When you have time, please take a look under the hood, and let me know what you make of it.
To help get the gist of the program, user instructions are posted at User_talk:The_Transhumanist/ViewAsOutline-CategoryTree.js#Description_/_instruction_manual
The Transhumanist 17:40, 16 December 2017 (UTC)
cont.outerHTML = cont.outerHTML.replace
... line. Rewriting the <a> tags is definitely not something the categoryTree.js expects. You might want to try only modifying the text within the <a> tags, and not the tags themselves. Or only adding stuff before and after the tags (i.e. with jQuery methods) and not rewriting the tags using regex. -
Evad37 [
talk 15:07, 1 January 2018 (UTC)Hi Evad,
Given your position as editor-in-chief over at Signpost, and the time pressure regarding the specific item which I have nominated (the annual version of the Top 25 Report), I felt that it might be a good idea to alert you directly to the submission, as it diminishes in interest as the days go by.
Happy new year! - Stormy clouds ( talk) 00:25, 4 January 2018 (UTC)
By the way, do I need to load any dependencies for the following code?
// ============== activation filters ==============
// Only activate on Vector skin
if ( mw.config.get( 'skin' ) === 'vector' ) {
Do all "mw." lines have dependencies? The Transhumanist 13:40, 1 January 2018 (UTC)
mw.config
is always available, and contains lots of other useful stuff – see
mw:mw.config. Other mw modules, detailed at
mw:ResourceLoader/Core modules, aren't necessarily available unless you load them – see
mw:ResourceLoader/Migration_guide_(users)#mw.loader for further details. -
Evad37 [
talk 14:10, 1 January 2018 (UTC)
Hi Evad, I want to thank you for your diff viewer, and for being so kind to create it when someone asked. That was very nice of you. All the best, SarahSV (talk) 04:49, 6 January 2018 (UTC)
User talk:The Transhumanist/ViewAsOutline-AllPagesWithPrefix.js
This script disappears the bullets from the "All pages with prefix" page, and inserts wikicode formatting for list items for easy copying and pasting into a wiki-editor. Useful for building lists and outlines. The Transhumanist 05:31, 5 January 2018 (UTC)
Created 2 more scripts, that make similar conversions to 2 other types of pages:
Made possible by your generous instructions. Thank you. The Transhumanist 08:05, 6 January 2018 (UTC)
P.S.: I was pleasantly surprised that .find
creates an array.
There were two outspoken commentators at the Mister Wiki workshop with what looks to me like incompatible points of view. I'd like to ask each of them for a 250 word response/op-ed to include in the article (the article is about 500 words now). Is that kosher? ☆ Bri ( talk) 20:40, 11 January 2018 (UTC)
Salvidrim! asked if he can contribute as well. I'm inclined to say "no" as it was just an invitation to two opposing views from the workshop participants, to make it digestible and not a re-litigation of the case. But I'd like to hear what you think of that request. ☆ Bri ( talk) 20:58, 11 January 2018 (UTC)
For example, the
Glossary of architecture has a newline between all the dt and dd elements (in the rendered output). More specifically, between "</dt>
" and "<dd
" in each glossary entry.
How do you get rid of just those newlines? (And no others).
I tried this, to replace the newline (and anything else between the elements) with " – ", and it didn't work:
// Strip out the newlines after dt elements
var mwContentLtr = document.getElementsByClassName( "mw-content-ltr" );
mwContentLtr0].outerHTML = mwContentLtr0].outerHTML.replace(/(<\/dt>).*?(<dd)/g,'$1 – $2');
Note that there is only one mw-content-ltr on the page. The Transhumanist 14:30, 6 January 2018 (UTC)
$('dd, dt').css('display','inline');
gets rid of all the visual newlines... but that makes everything go onto one line, effectively. But you can add linebreaks after each dd: $('dd').after('<br>');
. And to get the ndashes after each dt: $('dt').after(' – ');
. And to remove the spacing before the dd elements: $('dd').css('margin-left','0');
. So putting it all together into just two lines of code:$('dt').css('display','inline').after(' – ');
$('dd').css({'display':'inline', 'margin-left':'0'}).after('<br>');
Dear Evad,
Happy Hollidays! I hope yours went well.
I've been spending mine banging my head against some new scripts. And I've run into an enigma...
I'd like to remove the bullets from unordered lists, and the following code doesn't have any effect:
// Make the bullets go bye bye
$( ".navbox").find( "ul" ).css( "list-style-type", "none" );
I also tried this:
// Make the bullets go bye bye
$( "ul" ).css( "list-style-type", "none" );
And it didn't work either.
Do you have any idea what I'm doing wrong? The Transhumanist 14:47, 30 December 2017 (UTC)
::after
CSS pseudo element
[2]. Which means that to override it, you have to add more CSS rules to the page. There is a handy function mw.util.addCSS()
that you can use:// Make the bullets go bye bye
mw.util.addCSS('.hlist dd:after, .hlist li:after { content: ""; }');
mw.util
is available, so you need to surround your script with:// Load dependencies
mw.loader.using( 'mediawiki.util'], function () {
// ... your script goes here ...
});
mw.loader.using
line after the $(function() {
line -
Evad37 [
talk 03:17, 31 December 2017 (UTC)$( ".navbox").find( "*" ).removeClass( "hlist" );
// Make the ul's targettable by adding a class to them
$( ".navbox").find( "ul" ).addClass( "navbox-ul" ); //this part worked
// Make the bullets go bye bye, by altering the elements' style
var elements = document.getElementsByClassName('navbox-ul');
elements.style.listStyleType="none";
// Make the bullets go bye bye
mw.util.addCSS('.navbox-list dd:after, .navbox-list li:after { content: ""; }');
// Make the bullets go bye bye
$( ".navbox-ul" ).css( "list-style-type", "none" );
list-style-image: none;
to override the image of a bullet that Vector uses by default. So that line should actually be// Make the bullets go bye bye
$( ".navbox-ul" ).css( {"list-style-type":"none", "list-style-image":"none"} );
// Make the bullets go bye bye
$( ".navbox-ul" ).css( "list-style-type", "none" );
$( ".navbox-ul" ).css( "list-style-image", "none" );
// Make the bullets go bye bye, by altering the elements' style
var elements = document.getElementsByClassName('navbox-ul');
elements.style.listStyleType="none";
elements.style.listStyleImage="none";
In the script above, I'd like to force all the navigation footers on the page to be uncollapsed. I've also run into this obstacle on another script, for working on pages like this, where I need the boxes expanded. How is that done in a script? The Transhumanist 07:51, 6 January 2018 (UTC)
I went back and looked at the HTML source more closely, after studying the .css method, and found "display: none". So I checked what was there when the boxes were displaying, and invoked that with this line of code:
// Force the navboxes to show
$('tr').css('display', 'table-row');
I'm guessing the .find method may allow this to be restricted to occurrences of tr within navboxes only. I'll keep you posted. The Transhumanist 07:09, 13 January 2018 (UTC)
I've learned that looking at page source is a tricky business - it doesn't show the current state. Just looking at the page source isn't good enough; it turns out that other scripts (like NavFrame in mw:common.js) change the source after that picture is taken, requiring that you view selected source to see its current state.
So, while in "view page source" NavContent in a series box showed no indication of being collapsed (and so no code available to change), looking at the current page source (via "View Selection Source" in drop-down menu on right-click) reveals that some JavaScript came along afterward and added some styling (display: none). When expanded, that changes (to display: block).
So, I added a few "display; block"s of my own. :) Now I have a script, that among other things, forces all the content in sidebar and series boxes to be displayed, which is very useful for someone inspecting and collecting list components. Still needs refining of the formatting though. The script is ViewAsOutline-Sidebar.js.
This (acquiring JavaScript) is a grueling learning curve!
Do you have any suggestions that might make this journey easier? :) The Transhumanist 06:47, 18 January 2018 (UTC)
console.log()
, and also evaluate snippets of Javascript you type into it. -
Evad37 [
talk 04:42, 19 January 2018 (UTC)Hello, I'm Lingzhi. The regular FAC reviewers have some toilsome tasks that a script could make much easier. Would you be willing/available to make one? It would be greatly appreciated. Plus I was a Pick Basic and Python programmer, still hobbyist in latter, and I would like to help/learn with javascript. The request is on Mike Christie's page, check your pings... Thanks! Lingzhi ♦ (talk) 02:51, 20 January 2018 (UTC)
I'm in the process of trying to fix the intitle bug in Wikipedia's search, by providing the solution as a function within StripSearchSorted.js.
The intitle bug is that when you enter a search phrase in WP's search box with a common word (like this: intitle:"in Germany"), the titles in the search results don't match.
I'm almost done, but I can't figure out how to get :contains to accept a variable:
function TrueMatch() {
// The purpose of this function is to filter out non-matches
// Activation filter:
// Run this function only if 'intitle:"' is in the page title
// Notice the lone " after intitle:
if (document.title.indexOf('intitle:"') != -1) {
// Body of function
// Create variable with page title
var docTitle = document.title;
// Display on screen for checking
//alert ( docTitle );
// Extract the intitle search string from the html page title
// We want the part between the quotation marks
var regexIntitle = new RegExp('intitle:"(.+?)(")(.*)','i');
var intitle;
intitle = docTitle.replace(regexIntitle,"$1");
//alert ( intitle );
// Filter out search results that do not match
$( "li" ).not( 'li:contains(" + intitle + ")' ).remove();
}
}
It works fine up until that last line. I want to remove all li elements that do not contain the text in the intitle variable. The Transhumanist 07:51, 19 January 2018 (UTC)
$( "li" ).not( 'li:contains("' + intitle + '")' ).remove();
'li:contains("' + intitle + '")'
gets processed first, and the result is passed through to .not()
. Or if you wanted to be a bit more explicit, you could do something likevar intitle_selector = 'li:contains("' + intitle + '")';
$( "li" ).not( intitle_selector ).remove();
$( "li" ).remove();
, it removes all results.
The Transhumanist 02:16, 20 January 2018 (UTC)$( "li").not('li:contains( "of" )').remove();
resulted in blank results (ie, none).$( "li").not('li:contains( of )').remove();
resulted in no matches (ie results unaffected).
// First, strip out the searchmatch class elements (they match).
$( 'li').find( '.searchmatch').remove();
$( "li" ).not( 'li:contains("' + intitle + '")' ).remove();
$( 'li:contains("' + intitle + '")').remove();
intitle
will be somewhere within the li
, just not neccesarily in the title. Plus we can limit the searching of li
s to just the search results, rather than the whole page:// Mark true results with a class
$('.mw-search-results').find('li').has( 'div > a:contains("' + intitle + '")' ).addClass('truematch');
// Remove other results
$('.mw-search-results').find('li').not('.truematch').remove();
mw-search-results
, find the li
s which have a div
that itself has (as a direct child element) an a
that contains the text intitle
, and add the class truematch
to those li
s. Then, in the mw-search-results
, find the li
s which do not have the class truematch
, and remove them. -
Evad37 [
talk 09:25, 20 January 2018 (UTC)This is very exciting. That's one more step in one of the city outline building approaches that gets sped up...
Steps 3, 4, and 5 are currently done manually, but 3 (copy/paste) isn't as tedious, so 4 and 5 have priority.
Since deduping is more complicated after links are placed, developing this first, makes the most sense.
The Outline of Chicago is currently being drafted, using the above steps...
Step 1: See all the redlinks? Those are from the Template:Outline city. Many of the links in the template do not apply to Chicago, and so they turn red, but you never know what all is going to turn red when you first start a city outline, and they are time consuming to remove by hand. So, what we do is populate the outline with all the topics we can find, and then strip out the redlinks in step 6. The RedlinksRemover doesn't remove red entries that have children, it just delinks them. But, when the outline first starts out, most of the redlinks don't have children. If we strip them out too soon, we'll wind up having to type many of them back in when we find children topics for them.
Step 2: Here's where StripSearchSorted with TrueMatch comes in. You do some intitle searches, such as "in Chicago". Increase the limit in the url to 5,000 to get the maximum results you can at once. That produces the results here: https://en.wikipedia.org/?title=Special:Search&limit=5000&offset=0&profile=default&search=intitle%3A%22of+Chicago%22&searchToken=bvc5dp6q7ldd4ayxph2a6ixg
Step 3: We copy and paste them to the "Place these" section in the outline (under See also). We repeat step 2 with further intitle searches (such as "of Chicago") and other gathering methods and send them all to "Place these" until we have all the topics we can find.
Step 4: The problem we have now is that many of the links in the "Place these" section are already in the body of the outline, like Culture of Chicago, Demographics of Chicago, and so on. And links may be duplicated in the "Place these" section itself. Therefore, we need to dedupe (remove the duplicates from) this section. That for each link in "Place these" that is found in the body of the outline (not navigation templates), or elsewhere in "Place these", gets removed.
Step 5: In this step, you take each of the topics one-by-one from the "Place these" section, after the duplicates have been removed, and put them into the body of the outline. Currently done by hand.
Step 6: Clean it all up with the RedlinksRemover. This tool is quick and painless – just click on the menu item. Without this tool, it is mind-numbingly tedious.
Which brings us to the design of OutlineDedupeHolding.js.
Eventually, this will dedupe more than one section, but its initial version will just process entries in the "Place these" section.
For each item, it needs to check the rest of the outline, excluding templates, and including the rest of "Place these", for a matching entry. If a match is found, that item is deleted from "Place these". If no match, go on to the next item.
I think this one may be within my ability level to write. I just need a little guidance...
How would you go about programming it? The Transhumanist 07:37, 22 January 2018 (UTC)
<li>
) with a duplicate link in them.no big deal JarrahTree 13:45, 26 January 2018 (UTC)
Here's one that's beyond my current abilities...
I came across a script called User:The Evil IP address/hdedit.js (heading editor). It allows you to edit headings without opening the page or section editor.
I'd like this concept applied to editing list item annotations. List items are ubiquitous on outlines, stand-alone lists, and embedded lists, and their annotations typically follow the list items, on the same lines, starting with an en-dash, like this:
If a list item has an annotation, it should appear in the annotation editor for modification by the user. If a list item has no annotation, the script should pull in the first 2 sentences of the lead of the corresponding article, if the list item is an embedded link. Then the user can edit them (the 2 sentences) in the annotation editor for context and polishing. If there is no link, then an empty annotation editor should appear, ready for user input.
I was very excited when I found hdedit, figuring it could be easily tweaked to perform the function I desired, until I looked at the source. Even though it is in JavaScript, I couldn't understand hardly a byte of it. I don't even recognize the syntax being used.
Then I started hoping that this would be just the type of script writing challenge you could sink your teeth into.
Sincerely, The Transhumanist 11:52, 15 January 2018 (UTC)
hdedit
is an object, and it is placed on the native window
object – but it probably could have also been declared with var hdedit =
instead of window.hdedit
.What is being chained?
hdedit
is an object, the syntax follows that of javascript objects – i.e. var foo = { 'key': 'value', 'key 2': 'value 2' }
. But in this case, functions are used as the values rather than strings (and if the keys don't contain special characters like spaces, then the quotes can be omitted). Functions within objects are sometimes called methods.foo[key]
, or dot notation if there's no special characters: foo.key
.hdedit.wikitext.replace(/^(=+)(\s*).+?(\s*)\1(\s*)$/m, '$1$2' + hdedit.newheading + '$3$1$4')
). You can't do something that simple with list items, because regex like /^(\*+)(\s*).+?$/m
would always match the first list item, not the one that needs to be changed. So then you need to find some other way of working out which list items in the wikitext match up with which list items rendered in the page HTML, which is where it starts getting complicated. -
Evad37 [
talk 04:34, 19 January 2018 (UTC)
What about counting?
Would the 55th list item in the html view always be the 55th list item in the wikitext view? The Transhumanist 08:03, 23 January 2018 (UTC)
<li>...</li>
tags directly in the wikitext. Which would completely blow things up if you're just counting li tags in the html and lines begining with * in the wikitext. -
Evad37 [
talk 02:45, 25 January 2018 (UTC)
Hi. I've only been working with javascript for a couple days now (sorry, n00b alert). I am rather at my wits' end. I have no idea why User:Lingzhi/reviewsourcecheck.js (a fork of Ucucha's HarvErrors script, which I am also using concurrently) seems to work correctly on the Notes section for all articles, but on the References section it works for some articles but not others. I have spent literally hours and hours trying to walk through the history to see where the bug began... I can't ask you to comb through the whole thing, but... do you have any general thoughts? A million thanks... Oh and occasionally the error messages in the Notes section (generated by Ucucha's script) are duplicated, but if I clear the browser's cache, they usually but not always fix themselves... Lingzhi ♦ (talk) 00:17, 25 January 2018 (UTC)
srctxt
, but then you're trying to using srctext
on line 119, which is undefined. Secondly, you are missing a semicolon at the end of line 109. Thirdly, variables are scoped to functions, not other block structures like for
. This means that in the second check, the variables 'i', 'srctxt', 'spline', and 'k' have already been defined from the first check.Harv error: link to #CITEREFTrigger1980 doesn't point to any citation. Harv error: link to #CITEREFGreen1981 doesn't point to any citation. P/PP error: Green 1981, pp. 123; P/PP error: Champion 2009, pp. 121. Harv error: link to #CITEREFTrigger1980 doesn't point to any citation. Harv error: link to #CITEREFGreen1981 doesn't point to any citation.;
P/PP error: Green 1981, pp. 123; P/PP error: Champion 2009, pp. 121. Harv error: link to #CITEREFTrigger1980 doesn't point to any citation. Harv error: link to #CITEREFGreen1981 doesn't point to any citation.;
Lingzhi ♦ (talk) 02:35, 25 January 2018 (UTC)
So I've been working on User:Lingzhi/reviewsourcecheck.js and made huge progress. I'm sure it could be made much much more elegant, but that's a task for another day. My question is this: There are no "red box with white x" errors, which I assume means "fatal errors". There are no little italic letter i warnings (information). There is only one yellow warning triangle with an exclamation point (what is the correct terminology for all these?)..
But alas, the fatal problem is this: the tooltip text (or whatever the correct term would be) for that one little yellow triangle says "Too many errors. (96% scanned)." And every section of the script works fairly well except for that section with the yellow warning, which is the lowest section of the script. When I debug, the logic all seems to work fine and I get into the place where I want to be, holding the information that I want to hold. But alas again, there is no output, even tho the "innerHTML" worked in earlier sections.
(Update: I made some edits and added a little more code; the yellow "Too many errors." triangle now appears higher up, at line 222sortedCites.sort();
, but it is still the only error warning.)
I have tried tweaking that section in every way I can imagine.
How can there be only one error, but that error says "Too many errors"?
As a note, I used to have many more yellow caution triangles, because I was re-declaring variables again and again... so I kept the "var" for the first instance (forex var i = 0
), and for all later points I deleted the "var" (forex i = 0
). Is that the wrench in the works? Or something else?
Thanks Lingzhi ♦ (talk) 05:15, 28 January 2018 (UTC)
Hello, I am trying to figure out how to use {{ maplink}} with a GeoJSON data file. I was looking at documentation and testcases and still cannot figure out where exactly to put the data file.
Can you tell me the exact location of 'St Georges Terrace.map
'? I'm quite confused in trying to locate this file to help me understand where to put my file.
{{Maplink||type=data|from=Sandbox/Evad37/St Georges Terrace.map}}
Here is a file I would like to map, but I don't even know how to test if it works on Wikipedia. c:High Point High School/Data:Boundary_Map.map I appreciate any help you can provide.~ Mellis ( talk) 04:33, 29 January 2018 (UTC)
Would it be possible to create a script similar to your HIDEAWB thing, but that would work for specific, user-defined edit summaries? AKA, something like
function setupHideBotTask() {
// Add a class to list items with edit summaries containing specific strings/regex matches/whatever
// Replace EXAMPLETEXT1/2/3 with your own strings/regex
$( "a[title='EXAMPLETEXT1']" ).closest("li, tr").addClass("watchlist-bot-task-edit");
$( "a[title='EXAMPLETEXT2']" ).closest("li, tr").addClass("watchlist-bot-task-edit");
$( "a[title='EXAMPLETEXT3']" ).closest("li, tr").addClass("watchlist-bot-task-edit");
// 'Hidden by default' option
if ( window.BotTaskHiddenByDefault ) {
$(".watchlist-bot-task-edit").hide();
$('#ca-BotTask').hide();
} else {
$('#ca-BotTask').hide();
}
$('#ca-BotTask').on('click', function() {
$(".watchlist-bot-task-edit").hide();
$('#ca-BotTask').show();
$('#ca-BotTask').hide();
return false;
});
$('#ca-BotTask').on('click', function() {
$(".watchlist-bot-task-edit").show();
$('#ca-BotTask').hide();
$('#ca-BotTask').show();
return false;
});
}
if( mw.config.get('wgNamespaceNumber') === -1 ) {
// Only operate in Special: namespace
$.when( mw.loader.using( 'mediawiki.util' ), $.ready).done( setupHideBotTask );
}
And maybe 'function setupHideBotTask()' is something that could be externalized to make things less intimidating for newbies / the main script being easily maintainable? Headbomb { t · c · p · b} 14:27, 28 August 2017 (UTC)
\[\[User:JCW-CleanerBot#What is the bot approved for\?\|Task \dSA\]\]
" would match
Tasks 1SA/2SA/3SA/4SA, but not Tasks 1A/2A/3A/4A), and add the "watchlist-bot-task-edit" class to the corresponding item. Part 2) Make the item hideable in the same way
WP:HIDEAWB does it.@
Headbomb: I've got a basic version working at
User:Evad37/Watchlist-hideCustom.js. The filters live in your userspace in a /WatchlistFilters.js subpage (e.g. mine is
User:Evad37/WatchlistFilters.js), and at the moment need to be entered manually, between the lines window.watchlistFilters = [
and ];
– one per line, with a comma at the end of each line except the last (i.e. a javascript array). Each filter can either be a regular expression, or plain text inside quote marks. Let me know if you need any help. -
Evad37 [
talk 09:02, 4 October 2017 (UTC)
Backlog update:
New Year Backlog Drive results:
General project update:
If you wish to opt-out of future mailings, go here. 20:32, 7 February 2018 (UTC)
To do that you need to use the mw:API, specifically mw:API:Edit. The easiest way I've found is using the mediawiki.api resource loader module. So you need to specify the dependency, i.e.
mw.loader.using( 'mediawiki.api'], function () {
// ...
// ... the rest of your script goes here ...
// ...
});
(see
mw:ResourceLoader/Migration_guide_(users)#mw.loader for further details).
Then create an mw.api object, and
identify your script/contact details. The same object can be used for multiple requests.
var API = new mw.Api( {
ajax: {
headers: {
'Api-User-Agent': 'Scriptname/version ( /info/en/?search=User:.../Script )'
}
}
} );
function doEdit() {
API.postWithToken( "edit", {
action: "edit",
title: "Wikipedia talk:Sandbox" // for example. You can use ` mw.config.get( "wgPageName" ) ` to get the current page name.
appendtext: "This text will be appended to the page.",
summary: "Edit summary goes here"
} ).done( function() {
// Code to execute if saved successfully
// Maybe notify the user.
// Or maybe reload the page:
location.reload();
} ).fail( function( code, jqxhr ) {
// Edit failed. The reason will be in the code and/or jqxhr parameters...
// (though you probably want to notify the user, rather than just logging to console)
if ( code === "http" && jqxhr.textStatus === "error" ) {
console.log( "HTTP error " + jqxhr.xhr.status );
} else if ( code === "http" ) {
console.log( "HTTP error: " + jqxhr.textStatus );
} else if ( code === "ok-but-empty" ) {
console.log( "Error: Got an empty response from the server" );
} else {
console.log( "API error: " + code );
}
} );
}
On some of my scripts, I use an activation filter that checks the title and runs only if the namespace up there matches:
// Run this script only if "Book:" is in the page title
if (document.title.indexOf( "Book:") != -1) {
// (Body of script goes here)
};
Now I need to do this with articles in the main namespace, but there is no prefix up there in the title to work off of.
What to do? The Transhumanist 13:02, 11 February 2018 (UTC)
mw.config.get( 'wgNamespaceNumber' ) === 0
. —
JJMC89 (
T·
C) 17:17, 11 February 2018 (UTC)
// Run this script only for main namespace
if (mw.config.get('wgNamespaceNumber') !== 0) {
return;
};
// (Body of script goes here)
return
statement only works within functions, but that's generally not a problem – you're whole script is usually wrapped inside a function, assuming you need to wait for the document ready and/or wait for resource loader modules to be loaded. -
Evad37 [
talk 00:44, 12 February 2018 (UTC)
$( function($) {
...});
there's nothing more left to execute, and so the script ends. It doesn't matter if the "return" is within any number of "if"/"if-else" statements, "for" loops, "while" loops, etc – only having another (sub)function will change the scope it applies to. One thing to watch for, at deeper levels within your programs, is that when you are assigning a variable to a function call (var foo = someFunction(bar);
), the variable is set to the return value, which is specified with "return someValue;"
inside the function. Since we haven't explicitly set a return value, it would be undefined
– but that doesn't matter for our purpose, since the function is just there to make the script wait before executing, and is not assigning a value to a variable. -
Evad37 [
talk 02:09, 13 February 2018 (UTC)Based on your explanations above, I've written the following deactivation filters using return statements:
// ============== deactivation filters ==============
// End the script if Vector skin is not the user's skin
if ( mw.config.get( 'skin' ) !== 'vector' ) {
// use a return statement to end the local function and hence the program's body
// important: this approach does not work outside of a function
return;
}
// End the script if " - Search results - Wikipedia" is not in the page title
if (document.title.indexOf(" - Search results - Wikipedia") == -1) {
// use a return statement to end the local function and hence the program's body
// important: this approach does not work outside of a function
return;
}
Are these correct?
And am I using the correct terminology in my comments?
What is the common name for the above technique? The Transhumanist 10:39, 15 February 2018 (UTC)
What about doing the same thing for more than one namespace? Such as "run script if the page is in the article namespace or the template namespace"? The Transhumanist 18:03, 13 February 2018 (UTC)
return
. NOT( isArticle OR isTemplate ) is equivalent to isNotArticle AND isNotTemplate. So in script (and putting the actual namespace number into a variable to avoid duplication), you get something like: // Run this script only for main and template namespaces
var namespaceNumber = mw.config.get('wgNamespaceNumber');
if ( namespaceNumber !== 0 && namespaceNumber !== 10 ) {
return;
};
// (Body of script goes here)
!
operator: // Run this script only for main and template namespaces
var namespaceNumber = mw.config.get('wgNamespaceNumber');
var isArticleOrTemplate = (namespaceNumber === 0 || namespaceNumber === 10);
if ( !isArticleOrTemplate ) {
return;
};
// (Body of script goes here)
// Run this script only for main and template namespaces
var namespaceNumber = mw.config.get('wgNamespaceNumber');
var allowedNamespaces = 0, 2, 10, 828]; // main, user, template, module
var isInAllowedNamespace = (allowedNamespaces.indexOf(namespaceNumber) !== -1);
if ( !isInAllowedNamespace ) {
return;
};
// (Body of script goes here)
the meltham station was created by the blocked sockpuppet /info/en/?search=Wikipedia:Sockpuppet_investigations/D47817 enough to delete with no hesitation or compunction, to say the least JarrahTree 02:44, 21 February 2018 (UTC)
the editors who used to help me with setting up project maintenance and so on have gone...
could you lead me to something or somebody who has the capacity to even get /info/en/?search=Wikipedia:WikiProject_Ageing_and_culture to square one? you can see on the project page that it started and more or less died without the requisite pages to even have a sense of what it is about I have tagged for many different projects - but have no idea who to ask or how to ask for the basics (some redlinked_)
any thoughts on or off wiki would be appreciated, thanks JarrahTree 23:47, 19 February 2018 (UTC)
I assume by "square one" you mean set up the project for class/importance assessments. To do this, you need to:
{{
Grading scheme|Project=Ageing and culture}}
and {{
Importance scheme|topic=Ageing and culture}}
(or similar listings and explanations of classes and importances).{{
Articles by Quality|topic=Ageing and culture}}
(or similar links to the other classes) and [[
Category:WikiProject Ageing and culture articles by quality]]
{{
Articles by Importance|topic=Ageing and culture}}
(or similar links to the other importances) and [[
Category:WikiProject Ageing and culture articles by importance]]
- Category:WikiProject Ageing and culture - Category:WikiProject Ageing and culture articles - Category:WikiProject Ageing and culture articles by quality - Category:WikiProject Ageing and culture articles by importance
- Evad37 [ talk 09:44, 20 February 2018 (UTC)
Dear Evad,
I was wondering if you would, for the sake of helping a relative newb get up to speed, mind answering some questions about the sources of your JavaScript know-how, the practices you follow, and the tools you use...
Which JavaScript books have you studied that you recommend?
Which are your go-to JavaScript-related websites?
What tools do you use for script development?
What does a script/gadget developer for WP need to know about MediaWiki?
What is your approach for writing scripts?
How do you go about fixing bugs?
What were your hardest learned lessons?
If you were to start all over again, what would you do differently?
What other pointers can you provide?
What important questions did I not ask?
I look forward to your replies.
Sincerely, The Transhumanist 14:37, 2 February 2018 (UTC)
var someTemplate = new Template('name', {'para1':'value1', 'para2':'value2'});
and then later someTemplate.setParamValue('para1', 'foo');
to change the value set for 'para1'. And later someTemplate.makeWikitext();
to produce the string {{name|para1=foo|para2=value2}}
.var newWikitext = someTemplate.makeWikitext() + currentWikitext;
is adding the wikitext representation of the template to the start of the current wikitext (without concern as to how the template object is turned into wikitext).function foo (whatever) {
if ( condition1 ) {
if ( condition2 ) {
if ( condition 3 ) {
//code if everything is okay
} else {
//code if #3 fails
}
} else {
//code if #2 fails
}
} else {
//code if #1 fails
}
}
function foo (whatever) {
if ( !condition1 ) {
//code if #1 fails. The return below stops any further code being processed.
return;
}
if ( !condition2 ) {
//code if #2 fails
return;
}
if ( !condition3 ) {
//code if #3 fails
return;
}
//code if everything is okay
}
var foo;
if ( condition ) {
foo = 'isTrue';
} else {
foo = 'isFalse';
}
var foo = ( condition ) ? 'isTrue' : 'isFalse';
var x = a || b // evaluates to a if a is truthy, or b if a is falsey - ie IF (a) { x=a; } ELSE { x=b; }
var y = a && b // evaluates to b if a is truthy, or b if a is falsey - ie IF (a) { y=b; } ELSE { y=a; }
return;
implementation.Hey, would you have any tips on debugging what is slowing down my page loads? I've tried to isolate individual gadgets and common.js scripts but I'm going in circles. (Or would you know if there's something up with WP's sitewide JS?) I tried Chrome's dev tools "Sources" (edit: ah, meant "Network") tab but the userscripts all run the same length
czar 01:33, 26 February 2018 (UTC)
An error message as shown in the screenshot popped up when I pressed the button. Please look into it — Frc Rdl 07:36, 4 March 2018 (UTC)
I removed the deactivation filter for vector skin from SearchSuite.js, and loaded it in common.js. It works on all skins, with the following quirk in MinervaNeue:
In the MinervaNeue skin, the features are stuck in whatever state they are in when the skin is selected. Unless there is a way to access the sidebar menu in this skin – if there is, please let me know.
By the way, is there a faster way to change skins than in "preferences"? — The Transhumanist 11:58, 9 March 2018 (UTC)
I'm just checking in. Seems you haven't been well lately. If you are indeed sick, I hope you will be in good health soon. I'll see you around. Eddie891 Talk Work 16:13, 11 March 2018 (UTC)
...is now operational.
Thanks for your contributions and advice. The development of the script would have been substantially delayed without your support.
I did the best I could, though it is far from optimized.
What needs to be, or should be, done to it? The Transhumanist 18:26, 24 February 2018 (UTC)
try {
// Code that might generate an error goes here
// The script will execute up until an error occurs, at which point it moves to the catch block,
// or until the end of the try block, at which point it skips the catch block
} catch(e) {
// Code to execute if there is an error – i.e. if you can't read a value from localStorage, just assume a default value
// The error details are in the `e` parameter, which you can output the browser console like this:
console.warn(e);
}
// Script continues here, even if there was an error encountered in the try block
TrueMatch
, you could have something like removeResultsWithoutIntitleString()
So, the program is just hanging in the breeze, waiting to crash?
I applied your code to variable assignments, like this:
try {
var SRSisterStatus = localStorage.getItem( 'SRSisterStatus' );
} catch(e) {
console.warn(e);
var SRSisterStatus = "off" ;
}
try {
var SRRedirectedStatus = localStorage.getItem( 'SRRedirectedStatus' );
} catch(e) {
console.warn(e);
var SRRedirectedStatus = "off" ;
}
try {
var SRDetailStatus = localStorage.getItem( 'SRDetailStatus' );
} catch(e) {
console.warn(e);
var SRDetailStatus = "off" ;
}
try {
var SRWikifyStatus = localStorage.getItem( 'SRWikifyStatus' );
} catch(e) {
console.warn(e);
var SRWikifyStatus = "off" ;
}
try {
var SRSortStatus = localStorage.getItem( ' SRSortStatus ' );
} catch(e) {
console.warn(e);
var SRDetailStatus = "on" ;
}
What is "e"?
What do I do with "e"?
That's a lot of repetition, how do you shrink that down?
Is try catch needed for instances of localStorage.setItem also? — The Transhumanist 08:20, 12 March 2018 (UTC)
This is a feature I would like to add, to let the user further hone down the search results. I think TrueMatch could be cloned and adapted to do this, but in order to parse an additional search string, the program will need an input form. I've never done one of those before. Any guidance would be most helpful. The Transhumanist 20:06, 24 February 2018 (UTC)
prompt()
method to request user input. W3Schools has a couple of good examples:
[5] -
Evad37 [
talk 04:36, 25 February 2018 (UTC)
The search results have links at the bottom for setting the number of items to be displayed to 20, 50, and so on, up to 500. But the API allows setting at any number up to 5,000, with &limit=5000
.
I'd like a menu item that allows the user to choose their own limit. Then the program would need to pass the &limit command to the API. I don't know how to do that.
Any pointers would certainly help. The Transhumanist 20:06, 24 February 2018 (UTC)
Hi Evad37 , I would like to participate to the JS project. Could you please help me with process? Tools, documenattiosn and how task are organized? Thnaks for your help. -- Mah3110 ( talk) 10:45, 14 March 2018 (UTC)
Hey there! So
phab:T32750 is going to be deployed next Thursday. With this, any edit summary that links to someone else's userpage will ping them. Looking at the code, I can't actually tell if your MoveToDraft script will be affected, but I wanted to give you a heads up just in case. Can the script be used to move userpage drafts to the Draft namespace? Anyhoo, disabling the pings is as easy as prefixing with a colon, like [[:User:MusikAnimal]]
, so you could safely put this before any wikilink in the edit summary and there will be no unwanted pings. If you have any questions don't hesitate to ask. Regards —
MusikAnimal
talk 00:37, 9 March 2018 (UTC)
I understand you may not be doing well in real life :/ I'm sorry to hear this and you have my sympathies. Since I haven't heard back from you, I've gone ahead and made the above change with Special:Diff/830585089. I doubt we needed to add a colon for all of those links, but I did anyway just to be safe. Hope this OK. Get well soon!! :) — MusikAnimal talk 18:55, 15 March 2018 (UTC)
Just want your quick opinion on a Signpost matter. Would it be kosher to review a Wikipedian's article that they wrote for a real-world history newsletter? Would this be topical for In The Media? The subject is coverage of specific historical content on Wikipedia. ☆ Bri ( talk) 01:38, 16 March 2018 (UTC)
Chicken Soup for a Programmer's Soul | |
Hey, I have glimpsed a couple mentions of the fact that you be or might have been under the weather. I hope you're doing well. Have a nice warm bowl of chicken soup. Lingzhi ♦ (talk) 07:10, 18 March 2018 (UTC) |
I apologise for making what might have been a disparaging remark posted on here. Do you think the message template could be shortened and made more clear? Kudpung กุดผึ้ง ( talk) 01:07, 18 March 2018 (UTC)
Kudpung กุดผึ้ง ( talk) 04:20, 27 March 2018 (UTC)
Is it possible to use todo script on other sister and language projects? I added it on m:User:Titodutta/global.js and kn:ಸದಸ್ಯ:Titodutta/common.js. -- Titodutta ( talk) 22:20, 28 March 2018 (UTC)
ACTRIAL:
Paid editing
Subject-specific notability guidelines
Nominate competent users for Autopatrolled
News
A proposal has been made to delete Portal:Australian roads, which you have made significant contributions to, as well as all other portals on English Wikipedia. You are welcome to contribute to the discussion if you'd like, which is located at Wikipedia:Village pump (proposals)#RfC: Ending the system of portals. Thank you for your contributions to Wikipedia. North America 1000 11:21, 12 April 2018 (UTC)
Evad, I set next issue dates to 4/25 for writing deadline and 4/28 for publication. Thought you would want to know in case you didn't see the Newsroom update. Also, having published the March issue manually, am planning plan to use the publishing script this time, since now I know what to expect it to do.
Do you plan to be involved in the April issue? ☆ Bri ( talk) 14:48, 12 April 2018 (UTC)
I'm working on a study of political motivations and how they affect editing. I'd like to ask you to take a survey. The survey should take no more than 1-2 minutes. Your survey responses will be kept private. Our project is documented at https://meta.wikimedia.org/wiki/Research:Wikipedia_%2B_Politics.
Your survey Link: https://uchicago.co1.qualtrics.com/jfe/form/SV_9S3JByWf57fXEkR?Q_DL=56np5HpEZWkMlr7_9S3JByWf57fXEkR_MLRP_cJbCbj99tqmYbTD&Q_CHL=gl
I am asking you to participate in this study because you are a frequent editor of pages on Wikipedia that are of political interest. We would like to learn about your experiences in dealing with editors of different political orientations.
Sincere thanks for your help! Porteclefs ( talk) 12:38, 16 April 2018 (UTC)
Hello,
There will be some changes to the way wikitext is parsed during the next few weeks. It will affect all namespaces. You can see a list of pages that may display incorrectly at Special:LintErrors. Since most of the easy problems have already been solved at the English Wikipedia, I am specifically contacting tech-savvy editors such as yourself with this one-time message, in the hope that you will be able to investigate the remaining high-priority pages during the next month.
There are approximately 10,000 articles (and many more non-article pages) with high-priority errors. The most important ones are the articles with misnested tags and table problems. Some of these involve templates, such as infoboxes, or the way the template is used in the article. In some cases, the "error" is a minor, unimportant difference in the visual appearance. In other cases, the results are undesirable. You can see a before-and-after comparison of any article by adding ?action=parsermigration-edit to the end of a link, like this: /info/en/?search=Arthur_Foss?action=parsermigration-edit (which shows a difference in how {{ infobox ship}} is parsed).
If you are interested in helping with this project, please see Wikipedia:Linter. There are also some basic instructions (and links to even more information) at https://lists.wikimedia.org/pipermail/wikitech-ambassadors/2018-April/001836.html You can also leave a note at WT:Linter if you have questions.
Thank you for all the good things you do for the English Wikipedia. Whatamidoing (WMF) ( talk) 21:18, 19 April 2018 (UTC)
This geezer was born at the age of 117 - /info/en/?search=Kenneth_Slessor - which parameter has been completely -'ed up ? JarrahTree
Requesting to be added as user of the Signpost publishing script ☆ Bri ( talk) 03:03, 23 April 2018 (UTC)
Wikipedia:Wikipedia Signpost/Next issue/
<noinclude> ... </noinclude>
section and following couple of lines) as the pages created from the newsroom "start article" button (i.e. traffic report or news and notes){{Wikipedia:Wikipedia Signpost/Templates/Signpost-block-end-v2}} {{Wikipedia:Wikipedia Signpost/Templates/Signpost-article-end-v2}} <noinclude>{{Wikipedia:Signpost/Template:Signpost-article-comments-end|||}}</noinclude>
Wikipedia:Wikipedia Signpost/Next issue/
– equivalently, everything listed at
Wikipedia:Wikipedia_Signpost/Next_issue – will become part of the published issue, and nothing else. Correct? ☆
Bri (
talk) 04:16, 23 April 2018 (UTC)
Signpost draft
parameter ready
be set to "Yes"? ☆
Bri (
talk) 18:03, 23 April 2018 (UTC)
Everything seemed to work. Hoorah! The script cut down publishing to about 1 hour, which is nice. One request: could you look at the formatting at Wikipedia:Wikipedia_Signpost/Archives/2018-04-26 to see if the script did something funky there? ☆ Bri ( talk) 02:18, 26 April 2018 (UTC)
so no need? re project tags on signpost talk pages? ok JarrahTree 03:40, 26 April 2018 (UTC)
apologies - every now and then some project space shows up a total disinterest in project maintenance - but I see your issue and will not touch again - sorry about that JarrahTree 03:53, 26 April 2018 (UTC)
Is there a spot you go to to find the going ons in Wikipedia ? Eddie891 Talk Work 22:26, 27 April 2018 (UTC)
Once again I misread a situation - thanks for the revert JarrahTree 12:43, 27 April 2018 (UTC)
Hello Evad37,
I'm a contributor of the German Wikipedia and tried to transfer the Maplink template into our Wiki but I encountered a problem: The template you use for coordinates ({{ Coord}}) is quite different in our German version. It seems to use a different coordinates format. Could you help me there? I don't have any LUA knowledge and I don't know how to fix it myself. -- Doktorpixel14 ( talk) 08:56, 13 May 2018 (UTC)
are primaily conducted as wiki club west events - which is the western australian branch of wikimedia australia chapter - which in effect makes them wmau events - JarrahTree 11:53, 13 May 2018 (UTC)
Hi does multi qid works ? /info/en/?search=User:Naveenpf/Sandbox/map#Multi -- naveenpf ( talk) 01:25, 7 May 2018 (UTC)
|type=shape-inverse
only works with data from OSM). So to show an inverse of a Commons map, you would need to create a new one on Commons. Also if you are using |from=
for the first feature, then the next feature to be mapped should be using |type2=
, not |type=
. -
Evad37 [
talk 02:59, 13 May 2018 (UTC)Hello! I'm currently getting desparate after trying to modify the Signpost article table. I've copied both /Tasks/Set and /Tasks/Task over to my userspace in order to play around with them, and am currently trying to change the default setup to what I have manually hacked into the table in my userspace overhaul of the Newsroom, so something like:
Name of the Feature, link to Next issue page if present
Status: |
Checklist:
Discussion: |
---|
But I have absolutely no idea how on earth I could get this into the template. Got any help? Zarasophos ( talk) 13:09, 16 May 2018 (UTC)
The Signpost Barnstar | ||
For everything you continue to do for The Signpost. Stepping in as Editor in Chief during a period of turmoil was gutsy and I appreciate it, also appreciate your onboarding me and others and helping the effort to get closer to self-sustaining. I just realized you haven't really been thanked before. ☆ Bri ( talk) 17:04, 17 May 2018 (UTC) |
Strong support Zarasophos ( talk) 21:48, 17 May 2018 (UTC)
I did a dry run of the publication script and got this error, and appeared to hang after the first screen.
index.php?title=User:Evad37/SPS.js&action=raw&ctype=text/javascript:123 Uncaught TypeError: Cannot read property '1' of null at apiCallback_getInfo (index.php?title=User:Evad37/SPS.js&action=raw&ctype=text/javascript:123) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:46) at Object.fireWith [as resolveWith] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:47) at Object.deferred.(anonymous function) [as resolve] (https://en.wikipedia.org/w/load.php?debug=false&lang=en&modules=jquery%2Cmediawiki%7Cmediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:51:337) at Object.<anonymous> (<anonymous>:15:410) at fire (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:46) at Object.fireWith [as resolveWith] (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:47) at done (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:126) at XMLHttpRequest.<anonymous> (load.php?debug=false&lang=en&modules=jquery%2Cmediawiki|mediawiki.legacy.wikibits&only=scripts&skin=modern&version=0upuj5q:129)
It seems to be repeatable. @ Chris troutman: you may want to follow this conversation ☆ Bri ( talk) 18:35, 22 May 2018 (UTC)
just tinkling around with things - please revert if wrong JarrahTree 04:29, 21 May 2018 (UTC)
Just thought I'd let you know the mapframe doesn't show up in the Technology report for me, using Chrome running on an 8.4" Android tablet. There's just a blank space there with the open square "expand" icon. The access URL is https://en.m.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2018-05-24/Technology_report ☆ Bri ( talk) 15:58, 24 May 2018 (UTC) ☆ Bri ( talk) 15:58, 24 May 2018 (UTC)
ACTRIAL:
Deletion tags
Backlog drive:
Editathons
Paid editing - new policy
Subject-specific notability guidelines
Not English
News
...in the latest edition of the Portals newsletter, I've posted you a copy below. — The Transhumanist 00:50, 25 May 2018 (UTC)
We have grown to 79 members.
Please provide a warm welcome to our latest additions, Wpgbrown, Cactus.man, JLJ001, and Wumbolo.
A lot is going on, much of it on the WikiProject's talk page, so be sure to go there and join in on any of the many discussions taking place there.
Elsewhere around the portal project, or related to portals, the following is happening...
Evad37 has created a new template, with supporting lua module, to handle news in portals...
{{ Transclude selected current events}} is ready to be tested in some actual portals. Let Evad37 know if you need help with the search patterns.
Noyster commented that "This is the best portal innovation since sliced bread!"
See the relevant discussion at Wikipedia talk:WikiProject Portals#Alternative to Wikinews.
Thank you, Evad.
Our WikiProject is now subscribed to the bot that makes automatic article alerts, but the subpage where they are posted has not been added to our WikiProject page yet because of a weird problem...
Featured portal nominations from two years ago keep popping up on there.
Please check Wikipedia:WikiProject Portals/Article alerts to see if you can figure out how to fix this.
Once that is remedied, it will be posted on our WikiProject page.
Thank you.
Note that, this will only track base pages, because to track the rest, we'd have to create over 140,000 talk pages for the subpages, and that just isn't worthwhile (as we're trying to remove the subpages anyways). Therefore, any alerts for subpages will still need to be posted manually.
Your input/editing is welcome on the draft-in-progress of a new guideline for portals.
See or work on the draft at User:Cesdeva/sandbox11.
See also the discussion at: Wikipedia talk:Portal guidelines#RfC on new portal guidelines
There is a proposal to change the look of the table of contents at Portal:Contents/Portals.
See: Portal talk:Contents/Portals#RFC on layout update.
Thank you to those who have participated in portal deletion discussions. There are still some editors out there who despise portals, and this comes across in their argumentation style. Wow. Such negativity. But, there is some good news...
Current deletion discussions are posted on our WikiProject page.
While portal detractors are trying to get rid of portals via MfD, we have deleted many of them via speedy deletion (per {{ Db-p1}} or {{ Db-p2}}). Essentially, they were bare skeletons, with maybe a little meat on them. The plus here is that speedy deletion is without prejudice to re-creating the portals. They can easily be restarted from scratch without getting approval, or be undeleted by request by someone willing to work on them. We have kept track of these, for when someone wants to rebuild them. They are listed at Portal talk:Contents/Portals#These are not listed yet.
We are also removing subpages, the functions of which have been migrated to portal base pages. To see which ones have been removed, look for the redlinks in our watchlist.
There is also an MfD concerning some of these at Wikipedia:Miscellany for deletion/Redundant subpages of the Cornwall portal.
For subpages that need to be deleted, you can conveniently place this speedy deletion template at the top of each of them:
{{Db-g6|rationale=of subpage clean up – this subpage's function has been migrated to the portal base page and is no longer needed}}
Then an admin will come along and delete them.
There are still 100 existing portals not yet presented on the main portal list at Portal:Contents/Portals. There were 400, so we've come a long way. Thank you! But we are not done yet...
Please list a couple of them. Every little bit helps. If each member of this project listed one more, it would almost all be done. Many hands make light work.
The list of missings, and instructions, are to be found at Portal talk:Contents/Portals#These are not listed yet.
I hope to see you there!
These developments make up just the tip of the iceberg. I'll have more to report in the next update, soon. — The Transhumanist 00:50, 25 May 2018 (UTC)
I think everyone would enjoy it if you officially joined the Portals WikiProject.
Though morale is high, you joining would certainly boost it higher. ;)
And, you would receive a complementary subscription to our oddly irregular newsletter. — The Transhumanist 00:50, 25 May 2018 (UTC)
Hi Evad37: The Transclude Selected Current Event was an excellent work. You are super awsome. One quaestion about the template - it looks like the template returns only current month news (or correct me if I am mistaken on this). Is it possible to parameterize how much old news the template will return? Some portals may one to show last 3 months for example. Arman ( Talk) 05:44, 27 May 2018 (UTC)
|max=
and |days=
parameters. There is a technical limit on how high the number can be, but such errors should only appear for very high values, like more than one or two years. -
Evad37 [
talk 08:37, 27 May 2018 (UTC)I'm contacting you because you indicated on the Portals WikiProject's members list that you use AWB.
We are now working on a task that requires your help.
Please see Wikipedia talk:WikiProject Portals#AWB team please tackle maintenance run on intro sections.
Thank you. — The Transhumanist 22:35, 28 May 2018 (UTC)
Wikipedia:Wikipedia Signpost/2018-05-24/From the editor is having trouble linking to Wikipedia:Wikipedia Signpost/2018-04-26/From the editorss, probably becuase of the different SUBPAGENAME. Is there an elegant solution to this? ☆ Bri ( talk) 16:49, 30 May 2018 (UTC)
you look like you are saving the world.... just a query about whether I could get some help re-creating the SLWA project space into a new MoP space - see User:JarrahTree/MoP - any thoughts? I seem to be stuck on the header... JarrahTree 15:02, 29 May 2018 (UTC)
[11] in the page layout of course - it is the contents that will change... JarrahTree 15:21, 29 May 2018 (UTC)
{{:Wikipedia:GLAM/Museum of Perth/Tab header/Tab|full page name|text to display on tab}}
templates (next to the existing ones on that page) -
Evad37 [
talk 01:07, 30 May 2018 (UTC)Thank you very much for that advice - is there any chance of you being able to get to the Museum of Perth on a Tuesday, Wednesday or Thursday between 9 and 4 - in the near future ?? JarrahTree 03:03, 31 May 2018 (UTC)
got it - sorry about that JarrahTree
We have grown to 89 members.
This is the seventh issue of this newsletter. For previous issues, see our newsletter archive.
A warm welcome to our nearly one dozen new members...
Our new members include:
Be sure to say "hi" and welcome them to the team.
There were 1515 portals, but now we have 1475, because we speedy deleted a bunch of incompleted portals that had been sitting around for ages, that were empty shells or had very little content. Because they were speedied, they can be rebuilt from scratch without acquiring approval from WP:DRV.
This is what we have been gearing up for: upgrading the portals en masse, using AWB.
More than half of the Associated Wikimedia sections have been converted to no longer use a subpage. This chore will probably be completed over the next week or two. Many thanks to the WikiGnome Squad, who have added an Associated Wikimedia section to the many geography-related portals that lacked one. The rest of the subjects await. :)
The next maintenance drive will be on the intro sections. Notices have gone out to the WikiProjects for which one or more portals fall within their subject scope. Once enough time has elapsed for them to respond (1 week), AWB processing of intro sections will begin.
I'd like to take this opportunity to thank you all for your part in the RfC. I went back and reread much of it. I believe your enthusiasm played a major part in turning the tide on there. I'm proud of all of you.
Why reread that mess, you ask?
To harvest ideas, and to keep the problems that need to be fixed firmly in mind. But, also to keep in touch. See below...
I've contacted all of the other opposers of the RfC proposal to delete portals, to thank them for their support, and to assure them that their decision was not made in vain. I updated them on our activities, provided the link to the interviews about this project in the Signpost, pointed out our newsletter archive so they can keep up-to-date with what we are doing, and I invited them all to come and have a look-see at our operations (on our talk page).
It so happened that one of our members was a sockpuppet: JLJ001. According to the admin who blocked him, he was a particularly tricky long term abuser. This is a weird situation, since the user was quite helpful. He will be missed.
This has been somewhat disruptive, because admins are doing routine deletions of the pages (portals, templates, etc.) he created, and reversion of his edits (I don't know if they will be reverting all of them). Please bear with them, as they are only doing what is best in the long run.
The following pages have been deleted by the admins so far, that I know of:
{{Wikimedia for portals|species=no|voy=no}}
{{#tag:categorytree|{{PAGENAME}}}}
Automatic article alerts are now featured on the project page.
Some super out-of-date entries kept showing up on there, so posting it on the Project page was delayed. Thanks to Evad37 and AfroThundr for providing solutions on this one. Evad37 adjusted the workflow settings per Wikipedia:Article alerts/Subscribing#Choosing workflows, to make sure only the appropriate page types show up. AfroThundr removed the tags from the old entries that caused them to keep showing up in the article alerts.
Noyster pointed out that it would be nice to automate the updating of the portals section at the Community bulletin board.
Another major component of the portal system is the main list of portals, at Portal:Contents/Portals. How would we go about automating the updating of that?
Please post your ideas on the WikiProject's talk page. Thank you.
Keep in mind that we have already speedy deleted almost all of the nearly empty portals, which can be rebuilt without approval whenever it is convenient to do so. Other portals should be completed if at all possible rather than delete them through MfD (which requires approval from Deletion review to rebuild).
(Current deletion discussions are posted on our WikiProject page).
There's still more, but it will have to wait until next issue.
Until then, see ya around the project. — The Transhumanist 12:01, 31 May 2018 (UTC)
The Barnstar of Diplomacy | ||
Thank you for withdrawing your proposal when you found it lacked support, and taking criticism seriously. Your willingness to improve your work in response to others' suggestions, where many would become upset at criticism, is truly admirable, and something I wish more Wikipedians would adopt. Tamwin ( talk) 04:21, 1 June 2018 (UTC) |
For fixing portal project project pages (hahah I like that) JarrahTree 09:25, 3 June 2018 (UTC)
Thanks for making one of those, it's been on my to-do list for a while now. Do you think you can also do one for the cat importance template? This would eliminate the need for the category redirects completely. Also the FPo button doesn't have a color. Perhaps it should match the old FA button? — AfroThundr ( u · t · c) 17:01, 3 June 2018 (UTC)
I'd like to post a sample portal box in the newsletter, which will go on user talk pages, but this template appears to be turning off section editing for the entire page. Could you see if it is feasible to alter this without adversely affecting portals? — The Transhumanist 22:57, 6 June 2018 (UTC)
|EDIT=yes
in {{
Box-header}}
. (Other variations of the template might need to adjusted to pass that parameter through.) -
Evad37 [
talk 00:20, 7 June 2018 (UTC)The WikiProject now has 92 participants, including 16 admins.
A warm welcome to the newest members of the team:
Be sure to say hi.
Pbsouthwood has just gotten through the grueling RfA process to become a Wikipedia administrator. Be sure to congratulate him.
The reason he went for it was: "For some time I expect to be busy with subpage deletion for Wikipedia:WikiProject Portals as mentioned above. The amount of work is expected to keep me busy for some time. I am primarly a content creator and contributor to policy discussions, but would be willing to consider other admin work on request, providing that I feel that my involvement would be appropriate and not too far outside my comfort zone."
Evad37 has figured out a way to let the user flip through pictures without purging the page. Purging is awkward because there is an intermediary confirmation screen that you have to click on "yes". In the new picture slideshow section, all you have to do is click on the >
to go to the next picture or <
to instantly show the previous feature. The feature also shuffles the pictures when the page is initiated, so that they are shown in a different order each time the user visits the page (or purges it).
It is featured in Portal:Sacramento, California. Check it out to the right.
Keep in mind that the feature is a beta version. Please share your comments on how to refine this feature, at Wikipedia talk:WikiProject Portals#Refining the Picture slideshow.
We now have a one-page portal design. It isn't fully automated, nor is it even fully semi-automated, as there are still some manually filled-in areas. But it no longer requires any subpages in portal space, and that is a huge improvement. For example, Portal:Sacramento, California utilizes the one-page design concept. While is employs heavy use of templates, it does not have any subpages of its own.
This is the most cooperative team I've ever seen. With a strong spirit of working together to get an important job done. Kudos to you.
There's more. A lot more. But it will have to wait until next issue, but you don't have to wait. See what's going on at the WikiProject's talk page. — The Transhumanist 02:09, 7 June 2018 (UTC)
1) Replace the intro box sections on portals with an upgrade. See details at Wikipedia talk:WikiProject Portals/Tasks#AWB task: converting/upgrading intro sections.
2) Replace categories box sections on portals with an upgrade. See details at Wikipedia talk:WikiProject Portals/Tasks#AWB task: Converting category sections.
Enjoy. — The Transhumanist 08:08, 13 June 2018 (UTC)
VIP - heaps of questions. JarrahTree 01:30, 8 June 2018 (UTC)
Hello Evad37, thank you for your work reviewing New Pages!
We can see the light at the end of the tunnel: there are currently 2900 unreviewed articles, and 4000 unreviewed redirects.
Announcing the Backlog Elimination Drive!
Go here to remove your name if you wish to opt-out of future mailings. — Insertcleverphrasehere ( or here) 06:57, 16 June 2018 (UTC)
Don't mind that box to the right. We'll be talking about that later, below.
With the portals upgrades?
No. :)
What is almost done is the updating of the main list of portals!
There are 23 portals left to be listed.
Kudos to the WikiGnome Squadron, for spearheading this.
Once it is fully updated, we need to keep it up to date. When you complete a portal, remember to add it to Portal:Contents/Portals.
Concerning portal upgrades, we are working on those section-by-section...
The Associated Wikimedia sections of the entire set of portals have been upgraded. These are now handled on each portal base page (bypassing the previously used corresponding subpages), using the {{ Wikimedia for portals}} template rather than reiterated copied/pasted code.
So, to be more accurate on reporting upgrade progress, that's one section down (for the whole set of portals), with (about) nine sections to go. (Skipping curated portals, regarding custom content sections, of course).
Work is underway on converting Portals' introduction sections, and the categories sections.
If you would like to help, see Wikipedia:WikiProject Portals#Upgrade introduction sections and Wikipedia:WikiProject Portals#AWB task: Convert category sections
Work has also started with converting selected picture sections to picture slideshow sections. See Wikipedia:WikiProject Portals#Install picture slideshows.
Currently, there is no quality rating for portals: in the Portals WikiProject box on each portals' talk page, it just says "Portal". But times are a changin'. Quality assessment is on the way, and you can help. See the discussion.
Evad37 has figured out a way to apply the picture slideshow feature to displaying article excerpts (now you can check out the provided box above). :) This allows us to bypass page purging to see the next selection, and you can even click through them rather quickly. Currently, the wikicode for doing this for article excerpts is a bit eye-boggling, and so we are looking into simplifying it. A streamlined version may be just around the corner.
Note that this is a prototype, not ready for widespread use. Click on the box in between the lesser than and greater than signs, to see what I mean. It was meant for pictures, and so the thumbnail feature doesn't apply to article prose very well. I've presented it even though it isn't ready, to show the direction portal development is heading. See the discussion.
I'm amazed at how rapidly portals are evolving. And we're still within a single generation of portal technological evolution. Imagine what they might be in 2 or 3 more generations of developments. Pretty soon, portals will be able to shake your hand. :) — The Transhumanist 11:03, 16 June 2018 (UTC)
Can you help me fix the spelling error of "heroes" at Wikipedia:Wikipedia Signpost/Archives/2018-05-24? I can't quite figure out where it's coming from. ☆ Bri ( talk) 00:15, 21 June 2018 (UTC)
avon terrace york - good, for the centre point is it possible to resurrect the red bit... ? I was in town tonight trying to work out the config for lord street, perth - any clues? - not the centre point.. but the red line? JarrahTree 14:02, 21 June 2018 (UTC)
|location=
rather than using the infobox's automated code (like what was previously at the Avon Terrrace article, except with the recognised data type on OSM) -
Evad37 [
talk 14:42, 21 June 2018 (UTC)Just to warn you that I made a small edit to Module:Excerpt without noticing that you'd just synced the sandbox. It's easily repeated in your new version if you choose to promote the sandbox to the live module. Certes ( talk) 01:49, 22 June 2018 (UTC)
https://commons.wikimedia.org/wiki/Category:Wheatbelt_region_of_Western_Australia - is where the blue blob centrepoint system makes me see red. JarrahTree 00:24, 23 June 2018 (UTC)
You've got mail. ~ Amory ( u • t • c) 20:40, 24 June 2018 (UTC)
Interesting that "You will be able to move local wiki files to Commons..." just appeared in the tech report; I did a file move for the first time yesterday using one of the five listed tools for doing this. So I'm wondering if this feature will replace the existing modes? Or coexist? ☆ Bri ( talk) 19:22, 27 June 2018 (UTC)
Sorry, mate, lost track of what page I was on. My bad. Cheers, · · · Peter (Southwood) (talk): 09:03, 30 June 2018 (UTC)
We've grown to 94 participants.
A warm welcome to dcljr and Kpgjhpjm.
We are in the process of developing a rating system specifically for portals, as the quality assessment scheme for articles does not apply to portals. It is coming along nicely. Your input would be very helpful. See the discussion at Wikipedia talk:WikiProject Portals/General#Proposed new quality class assessments.
One of our participants got involved with this WikiProject through interest in how the new generation of portals would be handled in WP's MOS (Manual of Style). It didn't take long before he got sucked in deeper. This has given him an opportunity to look around, and so, he has made an assessment of this WikiProject's operations:
I'm quite frankly really impressed and inspired by what's happening here. If you'd asked me a year ago if I thought portals should just be scrapped as a failed, dragged-out experiment, I would have said "yes". This planning and the progress toward making it all practical is exemplary of the wiki spirit, in particular of a happy service-to-readers puppy properly wagging its technological and editorial tail instead of the other way around, and without "drama". It's also one of the few examples I've seen in a long time of a new wikiproject actually doing something useful and fomenting constructive activity (instead of acting as a barrier to participation, and a canvassing/ownership farm for PoV pushers). Kudos all around. — SMcCandlish
Congratulations, everyone. Keep up the great work.
We've run into a glitch with slideshows: they don't work on mobile devices.
Initially, we will need to explore options that allow portals to have slideshows without adversely affecting mobile viewers. See Wikipedia talk:WikiProject Portals/Design#Mobile view support.
Eventually, we may need another way to do slideshows. If we do go this route, and I don't see why we wouldn't, then (user configurable) automatic slideshows also become a possibility.
Once implemented, this will allow editors to create and edit cascading style sheets for use with templates. This will expand what we can do with portals. For more detail, see mw:Extension:TemplateStyles and Wikipedia:TemplateStyles.
We've run into an obstacle using Lua-based selective transclusion: Lua is incapable (on Wikipedia) of reading in article names from categories. Because of this, we'll need to seek other approaches for fully automating the Selected article section. We are exploring sources other than categories, and other technologies besides Lua.
Speaking of using other sources, the template {{ Transclude list item excerpt}} collects list items from a specified page, or from a section of that page, and transcludes the lead from a randomly selected link from that list. Courtesy of Certes. So, if you use this in a portal, and if the template specifies a page or section serviced by JL-Bot, you've now got yourself an automatically updated section in the portal. JL-Bot provides links to featured content and good articles, by subject.
What is "fully automated"? When you create a portal using a creation template, and the portal works thereafter without editor intervention, the portal is fully automated. That is, the portal is supported by features that fetch new content. If you have to add new article names every so often for it to display new content, then it is only semi-automated.
Currently, the Selected article section is semi-automated, because it requires that an editor supplies the names of the various articles for which excerpts are (automatically) displayed. For examples, look at the wikisource code of Portal:Reptiles, Portal:Ancient Tamil civilization, and Portal:Reference works.
So far, 3 sections are fully automatable: the introduction section, the categories section, and the Associated Wikimedia section.
Henry.
Or some other name.
Eventually, the portal department will be a software program. And we won't have to do anything (unless we want to). Not even tell it what portals to create (unless we want to). It will just do it all (plus whatever else we want it to do). And we will of course give it good manners, and a name.
But, that is a few years off.
Until then, building portals is still (partially) up to us. — The Transhumanist 13:31, 30 June 2018 (UTC)
We now have 97 participants.
Be sure to welcome our newest members, BrantleyIzMe, Coffeeandcrumbs, and Nolan Perry, with warm regards.
Work is proceeding apace. We have 2 major thrusts right now: converting the intro sections of portals, and building the components of the one-page automated model...
We need everybody, except those building software components, to work on converting intros. If you have AWB, definitely use that. If not, then work on them manually. Even one a day, or as often as you can muster, will help a lot. There are only about 1,000 of them left to go, so if everyone chips in, it will go pretty quickly. Remember, there are 97 of us!
The intros for most of the portals starting with A through F have already been converted to use the {{ Transclude lead excerpt}} template.
The standard wikicode for the automated intro that we want to put into place looks like this:
{{/box-header|Introduction|noedit=yes|}}
{{Transclude lead excerpt | {{PAGENAME}} | paragraphs=1-2 | files=1}}
{{Box-footer|[[{{PAGENAME}}|Read more...]]}}
That works for most portals, but not all. For some portals it requires some tweaking, and for others, we may have to use a different or more customized approach. Remember to visually inspect each portal you work on and make sure that it works before moving on to the next one.
Be sure to skip user-maintained portals. They are listed at Wikipedia:WikiProject_Portals#Specific_portal_maintainers.
I've started an AWB tips page, for those of you feeling a bit overwhelmed by that power user tool. Feel free to add to it and/or improve it.
We have some very talented Lua programmers, who are pushing the limits of what we can do in gathering data from Wikipedia's various namespaces and presenting it in portals. Due to their efforts, Lua is powering the selective transclusion core of our emerging automated portal design, in the form of selected article sections that rotate content, and slideshows.
To go beyond Lua's limits, to take full advantage of Mediawiki's API, we are in the midst of adding another programming language to the resources we shall be making use of: JavaScript. The ways that JavaScript can help us edit portals to boost the power of our Lua solutions, are being explored, which will likely make the two languages synergistic if not symbiotic. Research is under way on how we can use JavaScript to make some of the portal semi-automated features fully automatically self-updating, in ways that Lua cannot. Like gathering random members from a category and inserting them into a portal's templates as parameters. Once the parameters are in place, Lua does the rest.
If you would like to get involved with design efforts, or just keep up on them, see Wikipedia talk:WikiProject Portals/Design.
Well, not at the present time, because building portals is quite time consuming. The good news is that we are working on a design that will be fully automated, or as close to that as we can get. And the new design is being implemented in the portal department's main portal creation template. This means, that not only will portals update themselves, their creation will be highly automated as well. That's the nature of templates. You put them in place, and they just... work.
What I'm getting at here, is that it would be better to wait to build lots of new portals until after the new design is completed. Because with it, instead of taking hours to create a new portal, it will likely take minutes.
That does not mean we should be idle in the meantime. The main reason most of us are here is because it became apparent that portals were largely unmaintained and had grown out-of-date. This had become so apparent that a proposal was made to delete all the portals and the portal namespace to boot. That makes our main objective in the short term to improve all the existing portals so that the community will want to keep them—forever.
Building lots of new portals comes later. Let's fix up the ones we have first. ;)
And on that note, I bid you adieu. Until next newsletter, see ya 'round the WikiProject. — The Transhumanist 12:30, 10 July 2018 (UTC)
/info/en/?search=Wikipedia:Meetup/Perth/50 - apologies for late notice - hope you are able to make it!! JarrahTree 04:28, 14 July 2018 (UTC)
We have 97 participants.
Automation makes things go faster, even portal creation. One of the components Certes made was {{ Transclude list item excerpt}}. I became curious about its possible applications.
So I worked out a portal design using it, the initial prototypes being Portal:Kyoto (without a "Selected pictures" section), and Portal:Dubai (with a "Selected pictures" section). Then I used Portal:Dubai as the basis for further portals of this type...
Why?
To see, and to show, what may become feasible via automation.
It now looks highly feasible that we could get portal construction time down to a few minutes, or maybe even down to a few seconds.
The singularity is just around the corner. :)
When using the {{ Random slideshow}} template to display pictures, be sure to use the plural tense in the section title: "Selected pictures". That's because slideshows don't show up on many mobile devices. Instead the whole set of pictures is shown, hence the section title "Selected pictures", as it fits both situations.
In case you are curious, here is a list of the portals so far that have a slideshow:
|
The intros for most of the portals up through the letter "O" have been converted, using this wikicode:
{{/box-header|Introduction|noedit=yes|}}
{{Transclude lead excerpt | {{PAGENAME}} | paragraphs=1-2 | files=1}}
{{Box-footer|[[{{PAGENAME}}|Read more...]]}}
Where the pagename didn't match the article title for the subject, the title was typed in.
Most of the portals that do not contain {{/intro}}
or {{{{FULLPGENAME}}/Intro}}
have not yet been processed.
About a thousand portals use the method of selective transclusion for the intro section. That's about two-thirds. That means we have one-third of the way to go on the intro section conversions.
So much has been happening with portals that I can't keep up with it. (That's good). Which means, more in the upcoming issue. Until then, see ya 'round the project. Sincerely, — The Transhumanist 08:45, 15 July 2018 (UTC)
I got overwhelmed IRL (in real life) during the production of issue #12. So, here is a catch-up issue, to help bring you (and me) up to speed on what is happening with portals...
By the way, we still have 97 participants. (Tell all your friends about this WikiProject, and have them join!)
One cool feature of some of the geographical portals is a panoramic picture at the top of the intro section.
Check these out:
The Portals WikiGnome squadron is busy adding panoramas to geographical portals that don't yet have one. Feel free to join in on the fun. See task details at Wikipedia:WikiProject Portals#Add a panorama or skyline to a geographic portal.
Caveat: avoid super-huge pics, as they can cause portal scripts to time-out. Please try to keep picture size down below 2 megabytes. Thank you.
Speaking of pictures...
We now have two slideshow templates. You may be familiar with {{ Random slideshow}}, in which the editor types in (or copies/pastes) a list of pictures he or she wants it to display.
Well, now we have another template, courtesy of Evad37, which accepts one or more page names instead, and displays a random image off of the listed pages. So instead of listing dozens of files by hand, you can include a title or three to be scanned automatically. It even lets you specify particular sections.
The new slideshow template is {{ Transclude files as random slideshow}}.
Here's a sample, that grabs images from a single page:
Speaking of new templates, here's another one!
Also from Evad37, we have a new component for starting section boxes, that is color configurable, and that bypasses the need for box-header subpages altogether. It is {{ Box-header colour}}.
For color support, see Web colors.
For the discussion in which this was inspired, see Wikipedia talk:WikiProject Portals/Tasks#Colour combinations for accessibility.
(In case you didn't notice, the slideshow box above uses this new template).
BTW, don't forget to close your box with {{ Box-footer}}.
The answer to this question is quite involved, and would fill this page to overflowing. Therefore, this subject, including a complete update on where we are at and where we are going with portal design, is covered at Wikipedia talk:WikiProject Portals/Design.
An AWB pass to convert intros on the portals has been completed. The pass couldn't convert them all (due to various formatting configurations, etc.).
All but about 170 portals now have introductions selectively transcluded on the base page. Not counting manually maintained portals, that leaves about 70 portals that either need their intros converted, or they need an intro.
Next, we'll be converting the categories sections!
The course of action we have been taking goes something like this, with all steps being pursued simultaeneously...
1) Design a one-page automated portal model
2) Convert existing portals to that design (except those being manually maintained)
3) Remove subpages no longer needed
4) Develop further tools to empower editors working on portals
Later, when the tools are up to the task, filling in the gaps in coverage (with new portals) will also become practical.
Probably not.
Who knows what our programmers and editors have dreamed up while I was writing this.
See ya again soon, — The Transhumanist 11:06, 18 July 2018 (UTC)
real life keeps interrupting a smooth work flow on that lot - thanks JarrahTree 03:11, 19 July 2018 (UTC)
Development of design continues, full speed ahead...
Can you say " paradigm shift"?
Now, in addition to picture slideshows, we have slideshows that can display excerpts. Portals are not just for topic tasting anymore. Now they can be made useful for surveying Wikipedia's coverage of entire subjects. This gives a deeper meaning to their name. Hmmm. "Portals"... Doorways to knowledge.
Portal:Lithuania was redesigned using excerpt slideshows. Check it out.
For those of you who cannot wait to test out these new toys...
We have not one, but three excerpt slideshow components to pick from:
{{ Transclude excerpts as random slideshow}}
{{ Transclude list item excerpts as random slideshow}}
{{ Transclude linked excerpts as random slideshow}}
{{ Portal image banner}} displays a panoramic picture the width of the page, and adjusts its size, so it stays that way even if the user changes page view size. And it accepts multiple file names, so that the picture displayed randomizes between them each time the page is visited/purged.
Give resizing the page a try:
Before:
After:
Notice how the box bottoms line up. That readjusts even if you click the slideshow buttons.
The template used for this is {{ Flex columns}}.
By the way, when you include more than one box in a column, any left over whitespace in that column is divided between them.
You may have noticed the new {{ Box-header colour}} template used above. It lets you pick the color locally (right on the same page). Before, this was handled on a subpage somewhere.
Now that we have lots of toys to play with for making cool portals...
Don't forget, that the majority of views of Wikipedia these days are from mobile devices. We need to make certain that portals display well on those. So, remember to check your work on portals in mobile view mode...
To see a portal in mobile view mode, insert a ".m" into a portal's url, after "en", like this:
https://en.m.wikipedia.org/wiki/Portal:Reptile
If you discover problems in a portal you can't fix, report them on Wikipedia talk:WikiProject Portals/Design.
Have fun. — The Transhumanist 00:58, 27 July 2018 (UTC)
Someone asked me for a reference on this.
You wouldn't happen to know the link to this statistic, would you?
Thank you, — The Transhumanist 00:39, 28 July 2018 (UTC)
|
Hello Evad37, thank you for your work reviewing New Pages!
Overall the June backlog drive was a success, reducing the last 3,000 or so to below 500. However, as expected, 90% of the patrolling was done by less than 10% of reviewers.
Since the drive closed, the backlog has begun to rise sharply again and is back up to nearly 1,400 already. Please help reduce this total and keep it from raising further by reviewing some articles each day.
Go here to remove your name if you wish to opt-out of future mailings. — Insertcleverphrasehere ( or here) 00:00, 30 July 2018 (UTC)
Template:Uses TemplateStyles/sandbox/example.css has been nominated for deletion. You are invited to comment on the discussion at the template's entry on the Templates for discussion page. {{3x|p}}ery ( talk) 00:13, 30 July 2018 (UTC)
Now that we have lots of toys to play with, it's play time!
Here are some fun activities to use our new toys on...
Would you like to travel around the world? Well, this may be the next best thing...
Here's another fun toy to play with: {{ Portal image banner}}
To see what it looks like, check out the panoramas at the tops of the following portals:
The task: There are many geography portals that lack panoramas. Please add some. Please keep the file size down below 2 megabytes, and keep in mind that you may find quality banners at commons: at less than 200K (.2 megabytes). Good search terms to include with the place name are "banner", "cityscape", "skyline", "panorama", "landscape", etc.
Related task: There are also lots of geography portals that have panoramas used as gaudy banners (with print or icons splattered across them) or that display them in some random location on the page. In many cases, those pages would be improved by displaying the panorama as a clean picture at the top of the intro section, like on the examples above. This works best with banner-like panoramas. Please fix such pages when you come across them, if you believe it would improve the look of the page.
Taller images might be better suited displayed further down the page, or in the "Selected images" section.
Note that {{ Portal image banner}} supports multiple images, and displays one at random upon the first visit, and each time the page is purged.
That is, image slideshows!
Over 200 have been installed so far. Just 1200 to go. (Be sure not to install them on portals with active maintainers, unless they want you to).
The title "Selected images" reflects the fact that not all images on Wikipedia are pictures, and encompasses maps, graphs, diagrams, sketches, paintings, pictures, and so on.
The toys we have to work with for this are:
{{ Random slideshow}}
and
{{ Transclude files as random slideshow}}
The task: Using one of the above templates directly on a portal's base page, replace static "Selected picture" sections, with a section like one of these:
The one on the left uses {{ Random slideshow}} (which accepts file names), and the one on the right uses {{ Transclude files as random slideshow}} (which accepts source pages from which the filenames are gathered).
The above section formatting is used on many of the pages you will come across, but not all. In those cases, use whatever section formatting matches the rest of the page.
Note that you may come across "Selected picture" sections done with {{ Random portal component}} templates. That template call is the entire section. Replace it with a section that matches the other sections on the page, and put the new slideshow inside that.
For example, in Portal:California, this code:
{{Random portal component|max=21|seed=27|header=Selected picture|subpage=Selected picture}}
was replaced with this code:
{{/box-header|Selected images|noedit=yes}}
{{Transclude files as random slideshow
| {{PAGENAME}}
| Culture of {{PAGENAME}}
}}
{{Box-footer}}
And the new section blended right in with the formatting of the rest of the page. Note the use of the {{PAGENAME}}
magic word. Plain article titles also work. Don't feel limited to one or two page names. But be sure to test each slideshow before installing the next one. (Or if you prefer, in batches - just don't leave them hanging). Report technical problems at the
Portal design talk page.
These sections, where unmaintained, have gone stale. That's because 1) the excerpts are static, having been manually copied and pasted, and 2) because they lack automatic addition of new entries.
They can be upgraded with:
{{ Transclude random excerpt}}
or
{{ Transclude list item excerpt}}
or
{{ Transclude linked excerpt}}
All three of these will provide excerpts that won't go stale. The latter two can provide excerpt collections that won't go stale, by providing new entries over time. The key is to select source pages or source sections that are frequently updated, such as root article sections, mainstream lists, or navigation templates.
When the above tasks are completed for the entire collection of portals (except the ones with specific maintainers), we'll be more than half-way done with the portal system upgrade.
Keep up the great work. — The Transhumanist 19:10, 30 July 2018 (UTC)
I wonder why [13] was necessary? ☆ Bri ( talk) 02:08, 1 August 2018 (UTC)
{{Wikipedia:Wikipedia Signpost/Templates/RSS description|1=Title}}
, and it was still there when it was published. If there's an existing value in the RSS description, the script won't override it. -
Evad37 [
talk 02:17, 1 August 2018 (UTC)
The Technical Barnstar | |
Thank you for all of your contributions to skin-related bugs, including the patches you've submitted! I haven't seen a patch that closed as many bugs as gerrit:442021 in quite a while :) Legoktm ( talk) 04:17, 3 August 2018 (UTC) |
Hello, may you please add the dynamic wikimap parameter into those two templates, your edits on {{ Infobox building}} are very useful and better than use location map. angys ( Talk Talk) 15:10, 12 August 2018 (UTC)
/info/en/?search=Template_talk:WikiProject_Australia - I think the default should be nla but... JarrahTree 04:44, 15 August 2018 (UTC)
Discussions are underway on the design of a portal tool (user script) that will hopefully have features for modifying portals at the click of a menu item, to make editing them easier. It might do things like change the color for you, add to a selection, add a new section, move a section, and so on.
If you'd like to be involved and suggest features for the tool, please join us at Wikipedia talk:WikiProject Portals/Design#What would you want a portal tool to be able to do?.
As new portal components are built by our Lua gurus, those components are being used to upgrade portals. Each component automates a section of a portal in a particular way.
The sections that are mostly upgraded so far are the Intro, and the Associated Wikimedia section.
The sections currently undergoing upgrade are: Selected image, Categories, and the Intro.
The Intro? Isn't that done already?
Yes, and no.
The upgrade of the excerpt in intros is mostly complete (there are about 70 non-standard portals that still need it).
Now we are doing another upgrade of intros in the form of adding a panoramic picture at the top of the intro, on portals for which such a picture is available on Commons:. Dozens of panoramas have been added so far, and they are really starting to affect the look of portals — the portals that have them look really good.
Regions are the most likely subjects to have panoramas, but a surprising number of other subjects have banner-shaped pictures too. Some examples of non-geographic portals that they have been added to are:
Speaking of pictures, several hundred Selected image sections have been upgraded to include image slideshows.
The push for automation continues, with new components under continuous testing in the field. As problems are spotted, they are reported to our programmers, who have done a fantastic job of keeping up with bug reports and fixing the relevant Lua modules fast. I am highly impressed.
Construction time on new portals is now down to as little as a minute or less. Though not in general. If you are lucky enough to spot portals that fit the profile of the new tools (their strengths), then a portal can be complete almost as soon as it is created, with the added time it takes to find and add a panorama. Source page titles are not generally standardized, and so it source pages in many cases must be entered manually. Where source page titles follow a standard naming convention, portal creation for those subjects goes quickly.
So, we still have some hurdles, but the outlook on portals is very good. New features, and many improvements to features are on the horizon. I'll be sure to report them when they become available.
What will the portal of the future look like? That is up to you!
See you on the project's talk pages.
Sincerely, — The Transhumanist 21:04, 15 August 2018 (UTC)
This issue is about portal creation...
Myself and others have been testing and experimenting with the new components in upgrading existing portals and in building new portals. They have now been applied in hundreds of portals.
The templates are ready for general use for portal creation.
They are still a bit buggy, but the only way we are going to work the rest of the bugs out is by using them and reporting the bugs as we come across them.
I look forward to seeing what new portals you create!
Be sure to report bugs at WT:WPPORTD.
The main portal creation template is {{ box portal skeleton}}.
After starting a portal using {{ box portal skeleton}}...
Check out the Did you know? section on Portal:Determinism. — The Transhumanist 02:21, 22 August 2018 (UTC)
Hello Evad37! Thank you for the magic you did at {{ Infobox building}}. :-) A quick question, if you edit a random page which uses Infobox building, you will notice that in the edit mode, when clicking preview, the map has additional zoom-in/zoom-out buttons, and also zooms in/out when scrolling over the map. Would you know if this functionality could be made available in the viewing mode as well? Maybe at least the zoom buttons? Best regards, Reh man 10:48, 24 August 2018 (UTC)
code will insert a simple interactive map ... with the ability to maximize it by either double-clicking the map or clicking the icon in the right corner. Which might mean the documentation is outdated, e.g. static maps might be needed for performance reasons... except that on test2wiki (a test site running the latest version of the software) dynamic thumbnails are shown when viewing a page, e.g. [15]. I've asked for clarification on Phabricator; See also mw:Help talk:Extension:Kartographer § Map maximizing on single click? - Evad37 [ talk 03:35, 25 August 2018 (UTC)
Regarding the upcoming tech report. Do you think the visibility of the server switch should be higher? I'm not sure if the "up to" one hour editing outage is realistic or a worst-case scenario. ☆ Bri ( talk) 16:11, 25 August 2018 (UTC)
The second issue of the Timeless newsletter is out.
The news: Themes are coming to Timeless! Your infobox and navbox templates in particular are probably going to look absolutely horrible in the new built-in night mode.
For more information, background, plans and progress updates, please see the
full issue on Meta, complete with a ridiculous list of phabricator task links, gratuitous mention of other skins, and me complaining about the current state of MediaWiki skinning in general.
If you want to move my DateCountdown widget to shared space go ahead. It could be a community tool. ☆ Bri ( talk) 04:17, 30 August 2018 (UTC)
As you know, portals are now supported by a number of new templates, which are in turn supported by some new Lua modules.
Those templates and modules are being put to the test, in the new portals that have been created since this WikiProject rebooted, plus a number of existing portals that have been revamped.
The new portals, and revamped ones, can be found at Category:Single-page portals.
Please browse the new portals at your leisure, and report any and all problems that you spot. Post bug and other portal problem reports at WT:WPPORTD. Please report bugs, quirks, awkward aspects, or anything weird or off that you notice. Compliments and suggestions are also welcome. :)
When you report a bug, please indicate the portal's name, the section that the problem appeared in, and the name of the article appearing (first) in the section with the problem. Most problems will likely be encountered in the Selected general articles" section, due to quirks in a displayed article's wikicode that the lua modules don't handle yet. Your help in spotting those is of utmost value. Thank you.
For portals that have been converted to the single-page design, we are not deleting their subpages at this time, because we are working on ways to harvest the data from those pages. For example, the Selected picture subpages include filenames and captions that would be valuable for the image slideshows. Please don't delete portal subpages, for now. They'll be slated for d-batch speedy deletion after harvesting. Thank you.
We are currently testing a feature added to {{ Transclude files as random slideshow}} that allows it to accept both sourcepages and filenames. Courtesy of Evad37. This will pave the way for harvesting files and their captions from portal subpages, for use in image slideshows.
The bulk of the work is being done by a handful of editors. But we can't do it all. We need help with spotting bugs, refining the search parameters in new/revamped portals (in the "Did you know..." and "In the news" sections), adding images to slideshows for a broader selection (they default to showing the images on the root article page but are capable of showing so much more), adding panoramic pictures at the top of the intro section of region portals (cities, counties, states, provinces, countries, continents, and other regions), to name but a few task types.
It is rewarding to be a part of the growing portal phenomenon. And you get to see its expansion and refinement up close.
Feel free to join in on the fun. ;)
Thank you, — The Transhumanist 06:50, 4 September 2018 (UTC)
Hi! I patrol Category:Templates with missing files and just wanted to quick let you know that your template is currently showing up in there due to a missing file(s) somewhere. I attempted to fix it myself, though I'm not finding what's causing the error. No worries and you're welcome to just leave it the way it is if you like, just thought I'd let you know in case it would help with testing process in some way. All the best, Katniss May the odds be ever in your favor ♥ 21:08, 3 September 2018 (UTC)
|thumb
from transcluded images, but did not take account of |thumbnail
also being a valid syntax. So [[File:Cat_playing_with_a_lizard.jpg|thumbnail|alt=Cat playing with a lizard|Cat playing with a lizard]]from Cat#Play got turned into
File:Cat_playing_with_a_lizard.jpgnail|alt=Cat playing with a lizard|Cat playing with a lizardinstead of
File:Cat_playing_with_a_lizard.jpg|alt=Cat playing with a lizard|Cat playing with a lizardThanks for letting me know, so I could investigate and fix this error. - Evad37 [ talk 02:47, 4 September 2018 (UTC)
frame
and framed
. Not sure if that applies here too.
Certes (
talk) 07:49, 4 September 2018 (UTC)
Hello, I noticed you assessed Imaqtpie as Start class. It is one of my first articles I have created, so I was wondering if you would please give me some advice on how to improve it to C class or better? I have already taken a look at Wikipedia:WikiProject_Video_games/Assessment#Quality_scale but I am still confused. Thank you. Derek M ( talk) 17:26, 6 September 2018 (UTC)
The Technical Barnstar | |
XFDcloser is just brilliant. Nothing more to say.. Galobtter ( pingó mió) 05:17, 7 September 2018 (UTC) |
I'm writing a user script.
I need to preview a page rather than save (submit).
How do you do that?
(More importantly, how do you find that information? I couldn't find it in the API) ( https://en.wikipedia.org/w/api.php)
I look forward to your replies. — The Transhumanist 23:33, 26 August 2018 (UTC)
document.editform.submit();
$('#wpPreviewWidget > input').click();
. Which then causes the page to reload, so you can't do anything with the script after that point (or at least not easily) -
Evad37 [
talk 07:04, 6 September 2018 (UTC)
<title>
that starts with "Creating", and the page has an empty edit window on it. When you Ctrl+click on that redlink, you get a tab; then, when you go to that tab, there's the same page I just described. So, there appears to be a page that exists as soon as you go there. It looks like a perfectly viable html page to me. The thing I don't understand is, why the script runs in the first instance of that page, and not the second. —
The Transhumanist 07:56, 6 September 2018 (UTC)
After I added your line for previewing the page, it worked, but each tab went into an endless loop, because the script ran again each time a new edit page was presented (which is what happens with preview). So I added a conditional so it would only continue if the page was empty, and a weird thing happened. The tabs went into an endless loop until I looked at them. Meaning they were empty until I actually went there. Bizarre. I have no idea why it is behaving that way. But, on the bright side, I'm further along with this thing than I was. Thank you.
I'll tinker around with it some more, and will let you know how far I get. — The Transhumanist 05:12, 7 September 2018 (UTC)
The problem went away after turning wikEd off. Works like a charm. Thank you for your help. — The Transhumanist 05:38, 7 September 2018 (UTC)
Hi Evad37, How difficult would it be to write a template that transcludes the short description of an article as an annotation?
The usage would be something like {{
Transclude short description|Foo}}
and should return A metasyntactic variable commonly used in template discussions
. It would mainly be useful to annotate a list of article links, so {{
Annotated link|Foo}}
would return [[Foo]] – A metasyntactic variable commonly used in template discussions
which would be useful in list articles like indexes. Part of it should be easy, as manually edited short descriptions are generally near the top of the article and use a consistent and straightforward syntax, {{short description|A metasyntactic variable commonly used in template discussions}}
, but some are embedded in infoboxes and disambiguation notice templates. Even just working with the standard short description template would be useful. Cheers, · · ·
Peter (Southwood)
(talk): 10:05, 6 September 2018 (UTC)
{{Template parameter value|Achilles|short description|1|1}}
→ Greek mythological hero -
Evad37 [
talk 05:34, 13 September 2018 (UTC)
Hey...
If you have AWB laying around, please dust it off and crank it up! ;)
We have a growing backlog!
There are now 539 portals. Of those, 51 are of the new design.
Many of the new portals are orphaned or near orphaned, and need links pointing to them:
To make a list of corresponding templates, you can use AWB's make list feature to make a list of the pages in
Category:Single-page portals. Then you copy that list to a sandbox, and replace \nPortal:
with ]]\n* [[Template:
, using
WP:wikEd. That will give you a list of templates to work on. Then you set skip in AWB to skip the ones that already have the portal link.
To make a list of corresponding root articles, make a list of portal links, and then remove "Portal:" from the links.
To make a list of category links to process, make sure you use a leading colon (:) in the category links, like this: [[:Category:Blue Öyster Cult]]
.
All new and revamped portals can be found at Category:Single-page portals.
Thank you. — The Transhumanist 20:44, 17 September 2018 (UTC)
Hello Evad37, thank you for your work reviewing New Pages!
The New Page Feed currently has 2700 unreviewed articles, up from just 500 at the start of July. For a while we were falling behind by an average of about 40 articles per day, but we have stabilised more recently. Please review some articles from the back of the queue if you can (Sort by: 'Oldest' at Special:NewPagesFeed), as we are very close to having articles older than one month.
List of other useful scripts for New Page Reviewing
|
---|
|
Go here to remove your name if you wish to opt-out of future mailings. MediaWiki message delivery ( talk) 23:11, 17 September 2018 (UTC)
The publication date for the Signpost is fast approaching, and your section seems to need some amount of work until it's publishable. Please continue working! Eddie891 Talk Work 15:10, 19 September 2018 (UTC)
next meetup thingoes for next event in perth are a real mess - and you are so good at fixing it up - 16th cancelled till following week - any chance to have a once over of all the points of mistakes etc? if you are able much appreciated. thanks JarrahTree 23:49, 19 September 2018 (UTC)
Five years! |
---|
-- Gerda Arendt ( talk) 06:53, 22 September 2018 (UTC)
Don't blink. You might miss something.
As of a few days ago, portals had doubled in about a month and a half.
Also, there were 98 incompleted portals in Category:Portals under construction. Now there are just 43.
The goals, plans, and task sections have all been updated.
Many new portals are still orphans, and need links pointing to them:
All new and revamped portals can be found at Category:Single-page portals.
This is the main list of portals.
Nearly 2,000 of the new portals need to be listed here.
They can be found at Portal talk:Contents/Portals#These are not listed yet. Instructions are included there.
Portals now have a new rating system of their own designed specifically to support portal evaluation! We were trying to use the standard assessment system for articles, but that doesn't fit portals very well.
Many thanks to Evad37, Waggers, AfroThundr3007730, SMcCandlish, Tom, BrendonTheWizard, and Pbsouthwood for their work and input on this.
The new system can be found at the top of all portal talk pages, in the WikiProject portals box. Those with "???" ratings need to be assessed, which makes up most of the older portals.
Most of the new portals were started out with an initial "Low" level of importance when their talk pages were created. Those deserving higher importance should be promoted as you come across them.
The starting point for new portals included minimal parameters and content, in the form of default values in the template(s) used for their creation.
So, for the search strings in the "Did you know..." and "In the news" sections, this was the magic word {{PAGENAME}}
, which represents the portal's name. Unfortunately, the resulting term is alway capitalized, which limits its effectiveness as a search string for anything but proper nouns. Results for those two sections can be improved, by replacing the "PAGENAME" magic word with multiple search strings, and search strings that begin with lower case letters. There is no inherent limit as to how many search parameters may be included. Lua search notation is used. The more general the subject, the more subtopic search terms you may want to include. For example, on
Portal:Avengers (comics), {{PAGENAME}}
turned up nothing. But, when more parameters were added, as in the wikicode below...
{{Transclude selected recent additions | {{PAGENAME}} | Iron Man | Spiderman | Antman | Hawkeye | The Hulk | Incredible Hulk | David Banner | Captain America | Scarlet Witch | Black Widow | Tony Stark | Nick Fury | Age of Ultron | Infinity War | months=36 | header={{Box-header colour|Did you know... }}|max=6}}
... that returned several results in the portal's DYK section.
Be sure you make the improvements to both the DYK section and the "In the news" section, as they both require the search strings.
The default starting selection for the image slideshow in most new portals is whatever images happen to be in the corresponding root article (via the PAGENAME magic word). You can improve image slideshows by adding more sourcepages and filenames as parameters in the "Selected images" section of portals.
See Template:Transclude files as random slideshow/doc for instructions.
Portals used to take about 6 hours or more to create. Now, for subjects that have particular navigation support, we've got that down to about one minute each, with even more content displayed than ever. True, that means the new portals pick you, rather than the other way around. Creating a specific portal that doesn't happen to have the requisite navigation support is still pretty time consuming. But, we are working on extending our reach beyond the low-hanging fruit.
And efforts are ongoing to keep shaving time off of the creation process. Eventually, we may get it down to seconds each.
In addition to improving automation, we're always looking for new features and improvements that we can add to portals, and there is plenty of potential to expand on the standard design so that new portals are even better right out of the starting gate. Additional designs are also possible.
On the horizon, there are many more portals waiting to be created. And we can expect to see at least a few more section types emerge. I never expected slideshows, for example, especially not for excerpts. Who knows where innovation will take us next?
Keep up the great work everyone.
Sincerely, — The Transhumanist 07:06, 23 September 2018 (UTC)
Hi Evad. Saw that you started a Technology report for September issue. Will it be possible to make it ready for copyedit soon? Say in next 24-48 hours? I'd like to publish in month of September. ☆ Bri ( talk) 14:27, 28 September 2018 (UTC)
The SPS does not appear in my pull-down menu. I had no issue last month. I jumped on another computer (different OS/ different browser) and it still doesn't appear. I had no problem last month and I cannot figure out what changed. Chris Troutman ( talk) 23:04, 30 September 2018 (UTC)
importScript('User:Evad37/SPS.js');
from your common.js and then see if it's there when you go to the newsroom, in case one of the other scripts you are using is interfering. -
Evad37 [
talk 23:53, 30 September 2018 (UTC)
Hi there. I raised an idea at Wikipedia talk:WikiProject Video games#Semi-automating cover upload? and would need someone very skilled (like you!) to implement it. Basically, it would be a upload- and edit-script that works like this:
Do you think you can create such a script? And more importantly, would you be willing to? Regards So Why 09:40, 27 September 2018 (UTC)
The Technical Barnstar | |
For your tool User:Evad37/rater.js Dreamy Jazz 🎷 talk to me | my contributions 21:16, 7 October 2018 (UTC) |
The Technical Barnstar | |
For the genius creation that is User:Evad37/Covery and the help you provide all the time. If you ever reconsider RFA, I'd be happy to nominate you. Regards So Why 12:23, 9 October 2018 (UTC) |
Whew, a lot has been happening.
A bit of defending of the portals has been needed. But, most activity recently has been directed upon maintenance and development of existing portals.
The majority of portals now use the new design, about 2400 of them, leaving around 1200 portals that still employ the old style.
Please inspect these portals, and report problems or suggest improvements at WT:WPPORTD. Thank you.
Since the last issue of this newsletter, Nineteen portals were nominated for deletion. All posted by the same person.
Two portals were deleted.
One resolved as "no consensus".
Sixteen resolved as "keep".
Links to the archived discussions are provided below:
Many thanks to those who participated in the discussions.
To watch for future MfD's, keep in mind that the Portals WikiProject is supported by automatic alerts. You can see them at: Wikipedia:WikiProject Portals#Article alerts: portals for deletion at MfD
There was also some discussion of creation criteria for portals. The result was that one of the participants in the discussion reverted the portal guidelines to the old version, which has the minimum number of articles for a portal included in there: "about 20 articles", a guideline that was in place since 2009.
Many of the portals that existed prior to April 2018 do not have that many (being limited to however many subpages the portal creator created), and therefore, these portals need to be upgraded to the new design (which automatically provides many articles for display). Using the new design, exceeding 20 articles for display is very easy.
Efforts have been underway to place links to new portals (all 2200 of them created since April).
Your help is needed. It is easy to access the page mentioned in #1, #2, & #3 from the portals themselves.
AWBers could do these tasks even faster (that's how the category pages were done), except #4...
Item #4 above pretty much has to be done by hand. (If you can find a way to speed that up, I would be very impressed). The links needing placement can be found at Portal talk:Contents/Portals#These are not listed yet. Instructions are included there.
There are still around 1200 old-style portals that have only undergone partial conversion to the new design concepts, still relying on subpages with copied/pasted excerpts that have been going stale for years, out of date (manually posted) news entries, etc.
The section currently being tackled on these is news. You can help by deleting any news section on the old-style portals that has news entries that are years old (that is the dead giveaway to a manual news section). Be sure not to delete the news sections of portals that have up-to-date news, or active maintainers. For maintainers, look at the portal's categories, and/or check the participants list at WP:WPPORT.
Eventually, conditional news sections (that appear only when news items are available for display) will be added using AWB to all portals without a news section.
News items (and even the news sections themselves) are automatically generated for portals that were created using the Basic portal start page. On those portals, there is a hidden comment at the top of the page (that you can see in the edit window), that says this:
<!-- This portal was created using subst:Basic portal start page -->
Presently, we are in the process of implementing the new design features, creating new portals with them, and installing them in existing portals.
But, what about development of new new design features?
We have a wish department.
Post your wishes at Wikipedia talk:WikiProject Portals/Design#Discussions about possible cool new features, and they might come true. Many have already, and for many of those, this is where they were posted.
A resource that has been elusive so far will be obtained eventually: categories. That is, the ability to pull category member links to populate a page.
Rather than populate portals directly with such links, it may be more beneficial to the encyclopedia to utilize them in navigation footers, because portals already have the ability to generate themselves based on those.
So, this would create a cascade effect: auto-gathering entries from categories, would enable the construction of new navigation footers, that would in turn support the development of new portals.
The cascade effect would also be felt by existing portals, as existing navigation footers could be expanded using the category harvesting methods, which would in turn expand the coverage of portals that access those navigation footers.
You can help by providing leads about any potential category harvesting methods. Please report anything you know about harvesting categories at WT:WPPORTD. Thank you.
One idea that has been floating around is the concept of a pageless portal. That is, a portal that isn't stored anywhere, instead being generated when you click on a menu item or button.
Many of the new portals were generated by a single click, and then saved via a second click.
Therefore, it seems likely that the portals of the future will employ the one-click concept.
Because of the need for customization by users, this concept would need to be augmented with a way to integrate user contributions. This could be done in at least two ways: posting an existing portal, autogenerating one from scratch if such does not yet exist, or have a special data page for user contributions that is folded into the auto-generated portal.
How soon? That is up to you. All that is needed are persons to implement it.
Keep up the good work on portals. They are improving daily. Thank you. — The Transhumanist 04:18, 12 October 2018 (UTC)
Kaya, I trying to create a template that can be used to identify each of the Noongar origins for the different spellings. that way we put a template say in quenda and show each of the regional variants in spelling names. or if there is no known word not include that group in the list. I know it'll be a quick one for you to do, I have created User:Gnangarra/sandbox/nys help with what I'd like to see. thanks in advance Gnan garra 13:30, 13 October 2018 (UTC)
Hi Evad37,
Are you perhaps interested in working on a new stub-tagging script or on a new automatic copyvio checking script? I put two requests in over at the
script requests page with some details. Feel free to decline if busy or if you think them too tedious. The copyvio one especially would be of huge benefit to the wiki. —
Insertcleverphrasehere (
or here) 22:37, 19 October 2018 (UTC)
Hi Evad37, hope all is well with you. Just wondering if you were planning to contribute to the issue 11 Technology report? ☆ Bri ( talk) 20:17, 20 October 2018 (UTC)
|
Hello Evad37, thank you for your work reviewing New Pages!
As of 21 October 2018 [update], there are 3650 unreviewed articles and the backlog now stretches back 51 days.
Go here to remove your name if you wish to opt-out of future mailings. — Insertcleverphrasehere ( or here) 20:49, 21 October 2018 (UTC)
Portals have passed the 4,000 mark.
Here's a list of portals created since the last issue
Please inspect these portals, report problems or suggest improvements at WT:WPPORTD, or develop them further (see below). Thank you.
There is still lots to do...
There are many subject gaps that need to be filled. This can be done by creating new portals, or by adding Selected article sections to existing portals. To create a new portal, simply place {{subst:Basic portal start page}}
on an empty portal page, and click "Preview". If the portal is complete, click "Save". After you try it, come share your experience and excitement at
WT:WPPORTD.
Each new portal is just a starting point. Each portal of the new design can be further developed by:
Besides the new portals, there are still about 1200 portals of the old design that need to be converted to the new design.
Many portals need to be de-orphaned, by placing links to them (in the See also section of the corresponding root articles, at the bottom of the corresponding navigation footer templates, and on the corresponding category pages).
Many of the new portals still need to be listed at Portal:Contents/Portals.
Bugs keep popping up in portals. These need to be tracked down and reported at WT:WPPORTD.
Tools are needed to make developing and maintaining portals quicker and easier.
Dreaming up new features and capabilities. Innovation needs to continue, to design the portal of tomorrow, and the portal development-maintenance-system of the future. Automation!
So, if you find yourself with a little (or a lot) of free time, pick an area (or more) above and...
...dive in! — The Transhumanist 07:04, 25 October 2018 (UTC)
P.S.: Evad, there's a bunch of new feature idea posts at WT:WPPORTD.
I see from the page history that you created Template:Maplink. I have tried a number of times to get this feature to work but have only managed to get a single point to work. I have copied one of my attempts below and would appreciate an indication of where I am doing it wrong. I do understand basic template and lua syntax but not these geodata concepts. — Frayæ ( Talk/ Spjall) 12:18, 25 October 2018 (UTC)
|frame-lat=
and |frame-long=
.
Galobtter (
pingó mió) 12:26, 25 October 2018 (UTC)|frame-width=
and |frame-height=
is something you also may want to change too.
Galobtter (
pingó mió) 12:28, 25 October 2018 (UTC)
Hi,
Do you know why some hospitals have a red boundary around their main buildings on the mapframe maps (in the infobox) wheras others do not?
ClippednPinned ( talk) 11:22, 2 November 2018 (UTC)
Give a hearty welcome to AmericanAir88, who has adopted working on portals as one of his main purposes on Wikipedia. So far, he has created the following portals:
Way to go!
Evad disappeared from Wikipedia on October 18.
He has been, and will continue to be, sorely missed.
Hopefully, he is okay, on a Caribbean cruise or something.
Portals of the old design, are slowly but surely being converted to the new single-page design.
One factor that has slowed things down is that for many sections, the section header call and section contents call are integrated into a template and buried in a lua module, locking them in on each portal. They have been that way for years.
This means that these sections can't be directly edited like the other sections on the same portal. So, search/replaces affect all the sections except those. So, upgrading headers on these portals, for example, misses the integrated sections and inadvertently results in 2 different header colors.
Before we can continue with the upgrade of these portals, the headers and section contents calls need to be restored to each portal, so that those can be edited in concert with the other sections on the portal, and worked on independently of each other.
This is underway, with a solution implemented on about 1/4 of the affected portals so far. Around 300 of them. The remaining 900 should be done within a couple weeks or so.
We now have banner-shaped pictures included in the introduction sections of 180 portals. The rarity of such pictures has made it difficult to find suitably narrow images for display across the tops of portals.
We have a solution for this, courtesy of FR30799386...
Most pictures are not banner-shaped. But, you can still use them as banners. Here's how:
{{Portal image banner|File:Blueberries .jpg |maxheight=120px |overflow=Hidden }}
Using both maxheight=120px
and overflow=Hidden
produces this:
There are now 4,140 portals, with more being created almost daily. Prior to this project's reboot, portals were created at about the rate of 80 per year. Since April of this year, we've created about 2,600 new portals, or 32.5 years' worth at the old rate.
Of those new portals, about 3/4 of them need links leading to them. Almost all of them are linked to from the category system, but they still need links in article see also sections, at the bottom of navigation templates, and on the main portals list at Portal:Contents/Portals.
Of the 1500 portals created before the reboot, about 300 have been completely converted to the new design so far. About 1100 more have been partially converted, with intros, image slideshows, and associated wikimedia sections getting the most attention.
Discussion has resumed on the portal guidelines.
See ya round the portal system! — The Transhumanist 11:42, 11 November 2018 (UTC)
Hi, this worked great but then it stopped so I deleted it and readded it later but now it wont load at all and am getting the following javascript error: index.php?title=User:Evad37/XFDcloser/v3.js&action=raw&ctype=text/javascript at line 1772: SyntaxError: Unexpected token ')'
Please advise, thanks Atlantic306 ( talk) 13:17, 8 November 2018 (UTC)
Dear Evad37, can you please see page User:Nitobus/test, and research why map number 6 (from6=moscowborders.ru/Crd/50-G.Dolgoprudny.map) does not displayed. Thank you in advance. Nitobus ( talk) 19:09, 14 November 2018 (UTC)
Chart of the New Pages Patrol backlog for the past 6 months. |
Hello Evad37,
Go here to remove your name if you wish to opt-out of future mailings. — Insertcleverphrasehere ( or here)18:37, 16 November 2018 (UTC)
Hello, Evad37. Voting in the 2018 Arbitration Committee elections is now open until 23.59 on Sunday, 3 December. All users who registered an account before Sunday, 28 October 2018, made at least 150 mainspace edits before Thursday, 1 November 2018 and are not currently blocked are eligible to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
If you wish to participate in the 2018 election, please review the candidates and submit your choices on the voting page. MediaWiki message delivery ( talk) 18:42, 19 November 2018 (UTC)
It's been a month since the last logon. If anyone knows, please let the rest of us know. — The Transhumanist 00:43, 20 November 2018 (UTC)
Hi Evad37, I hope that you're well! I was wondering if you would have time to help create a script for us over at peer review to help close reviews. It's not a particularly cumbersome process but can get quite time consuming if there are lots of reviews, and a script would be very helpful. I posted a description of what I think could happen at Wikipedia_talk:Twinkle#Feature_request_-_Peer_review and was wondering if this is something you could help out with? We'd be very thankful! -- Tom (LT) ( talk) 00:19, 19 November 2018 (UTC)
you are missed, trust all is ok - happy christmas at least!!! JarrahTree 00:13, 12 December 2018 (UTC)
Hello,
I have noticed that you marked the portal Australian roads for manual maintenance in June 2018, but this notice has not been updated in 6 months. This notice needs to be kept up to date to reflect the current status of the portal in December 2018. You can:
If you don't respond by updating the date in the notice in 2 weeks, then your name will be removed from the notice and the portal marked for automatic maintenance.
Thanks for your dedication to Portal:Australian roads. If you have questions about this message please {{ ping}} me about it. Thanks and happy editing, Dreamy Jazz 🎷 talk to me | my contributions 23:44, 13 December 2018 (UTC)
Hello Evad37,
This year's award for the Reviewer of the Year goes to Onel5969. Around on Wikipedia since 2011, their staggering number of 26,554 reviews over the past twelve months makes them, together with an additional total of 275,285 edits, one of Wikipedia's most prolific users.
See also the list of top 100 reviewers.
The backlog is now approaching 5,000, and still rising. There are around 640 holders of the NPR flag, most of whom appear to be inactive. The 10% of the reviewers who do 90% of the work could do with some support especially as some of them are now taking a well deserved break.
At #1 position, the Community Wishlist poll closed on 3 December with a resounding success for NPP, reminding the WMF and the volunteer communities just how critical NPP is to maintaining a clean encyclopedia and the need for improved tools to do it. A big 'thank you' to everyone who supported the NPP proposals. See the results.
Due to a number of changes having been made to the feed since this three-minute video was created, we have been asked by the WMF for feedback on the video with a view to getting it brought up to date to reflect the new features of the system. Please leave your comments here, particularly mentioning how helpful you find it for new reviewers.
If you wish to opt-out of future mailings, go here.
MediaWiki message delivery ( talk) 21:14, 14 December 2018 (UTC)
Welcome to the third issue of the Timeless newsletter, complete with a somewhat dubious explanation of where I've been all this time.
Somewhat dubious explanation of where I've been all this time:
I suffered a rather bad concussion in October, which knocked me pretty much completely out of commission through November, and I'm still recovering even now. One person = bus factor of one, even though it wasn't actually a bus but a very short flight of stairs.
Updates:
Comments on the RfC ( MediaWiki wiki RfC page, task) or bugs, or further reports, are always appreciated.
Until next time, hopefully with no further injuries,
Hi there all TPSs. I'm back after a longer than expected wikibreak. I'll be catching up with what I've missed over the next couple of weeks, but feel free to let me know if there's anything in particular you want me to look at. Cheers, - Evad37 [ talk 05:32, 21 December 2018 (UTC)
Hi. Recently, I discovered a passion for created and understanding user scripts on wikipedia, and am planning to create a monthly newsletter about new scripts and related projects (created by anyone, not for simply promoting my own), as well as currently pending user script requests, Wikipedia-related JavaScript tips/tricks, and other related information. This message was sent to you because you are listed as a member of the user script developers category. If you would like to subscribe to this upcoming newsletter, please go to User:DannyS712/subscribe to scripts and add yourself. If you have any questions, please reach out and talk to me。 -- DannyS712 ( talk) 05:22, 23 December 2018 (UTC)
Last issue, I mentioned there would be a flood, and so, here it is...
We now have 4,620 portals.
And the race to pass 5,000 by year's end is on...
Can we make it?
The New Year, and the 5,001st portal, await.
( New portals are created with {{subst:Basic portal start page}}
or
{{subst:bpsp}}
)
After disappearing in mid-thread, Evad37 has returned from a longer than expected wikibreak.
Be sure to welcome him back.
User:FR30799386 is working on making {{ Portal image banner}} even better by enabling it to chop the top off an image as well as the bottom.
Many pictures aren't suitable for banners because they are too tall. Therefor, User:FR30799386 added cropping to this template, so that an editor could specify part of a picture to be used rather than the whole thing.
Work has begun on upgrading Wikipedia's flagship portals (those listed at the top of the Main page).
So far, Portal:Geography, Portal:History, and Portal:Technology have been revamped. Of course, you are welcome to improve them further.
Work continues on the other five. Feel free to join in on the fun.
In place of many missing portals, there is a redirect that leads to "the next best topic", such as a parent topic.
Most of these were created before we had the tools to easily create portals (they used to take 6 hours or more to create, because it was all done manually). Rather than leave a portal link red, some editors thought it was best that those titles led somewhere.
The subjects that have sufficient coverage should have their own portals rather than a redirect to some other subject.
Unfortunately, being blue like all other live links, redirects are harder to spot than redlinks.
To spot redirects easily, you can make them all appear green.
And I'll see you next issue.
Sincerely, — The Transhumanist 08:08, 26 December 2018 (UTC)
It is now faster to build a portal than to place the links leading to it. So, I've been trying to write a link placer.
P-link stands for "portal link".
When completed, it will place links in 3 locations leading to a portal: on the corresponding category page, in the See also section of the corresponding article, and at the bottom of the corresponding navbox footer template. This will save loads of time, and should bring portal creation including link placement, down to under a minute for each portal.
I've got the "P link on category" menu item for placing the category page link working, sort of, but I had to resort to programming it to click the menu item up to 3 times instead of once, depending where you start from. I'd like it to work with one click from all of the allowed starting locations. It's a puzzle that has me stumped - working through the problem in my head or on paper with locally stored variables, I keep running into ambiguities discerning page types that I can't figure out. Once that problem is solved, I can move on to the other 2 menu items. — The Transhumanist 02:59, 26 December 2018 (UTC)
P.S.:pinging @ Certes and FR30799386:
?action=edit&plink=yes
. Then, for category edit pages, you check if the plink=yes
is in the URL: If so, you skip to the code that inserts the portal; if not, you add the menu item that when clicked will do that.mw.config.get('wgAction')
will result in "edit" for the initial edit page, and "submit" for the preview edit page -
Evad37 [
talk 08:17, 27 December 2018 (UTC)hope you had a good christmas, and will have a good new year
Dear Evad37, can you please see page User:Nitobus/test, and research why map number 6 (from6=moscowborders.ru/Crd/50-G.Dolgoprudny.map) does not displayed. Thank you in advance. Nitobus ( talk) 18:45, 26 December 2018 (UTC)
from
number
[21], but doesn't work when just in |from6=
. Which is quite weird, because there's nothing in the module code that would make |from6=
behave differently to the other positions. -
Evad37 [
talk 02:47, 27 December 2018 (UTC)
Before, we could only cut off the bottom of pics.
User:FR30799386 has pulled it off, and made the upgrade to {{ Portal image banner}}...
So, this:
Becomes this:
Here's the code for the above banner:
{{Portal image banner|File:American Falls from Canadian side in winter.jpg | [[Niagara falls]], from the Canadian side |maxheight=175px |overflow=Hidden|croptop=10}}
To see it employed in a portal, check out Portal:Niagara Falls.
We were racing against time to create 5,000 portals by the end of the year (just for the heck of it).
We made it. We've passed the 5,000 portals mark, with time to spare!
And the 5,000th portal is Portal:Major League Baseball, by Happypillsjr.
Congratulations!
The 10,000th portal mark. But...
...there is plenty else to do in addition to building new portals:
And whatever else you can dream up.
But most of all, have a...
Evad37, thank you for your contributions to the Portals Project, and have a prosperous, productive and enjoyable New Year.
Sincerely, — The Transhumanist 11:54, 30 December 2018 (UTC)
News and updates associated with user scripts from the past month (December 2018).
Hello everyone and welcome to the brand new Wikipedia Scripts++ Newsletter:
Scripts Submit your new/improved script here
|
|
Wishing you a happy new year, -- DannyS712 ( talk) 20:01, 31 December 2018 (UTC) |