This is an archive of past discussions with User:Davidbuddy9. 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.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Some older web browsers will not be able to use JavaScript on Wikimedia wikis from this week. If you have an old web browser on your computer you can upgrade to a newer version. [2]
New filters for Recent changes will come to Wikidata and Persian, Russian, Turkish and French Wikipedia on 11 April. The schedule has been changed to fix the user intent prediction filters for some wikis. User intent prediction means the filter tries to make it easier for editors to determine if the edit was made in good faith or not. Other wikis will get it later. [3]
The list of special characters in the wikitext editor and the visual editor will now have a group of Canadian Aboriginal characters. [4]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 11 April. It will be on non-Wikipedia wikis and some Wikipedias from 12 April. It will be on all wikis from 13 April (calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 11 April at 19:00 (UTC). See how to join.
Future changes
Because of a data centre test you will be able to read but not edit the wikis for 20 to 30 minutes on 19 April and 3 May. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. You can read more about this.
RevisionSlider will change how you move between revisions. This will be available on the test wiki from 11 April. It will come to other wikis later if users like the change. You can test it and give feedback.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
You can add ?safemode=1 to the end of the URL on Wikimedia wikis to disable your personal CSS and JavaScript. Example: https://en.wikipedia.org/wiki/Literature?safemode=1. This means you can test if a problem is because of your user scripts or gadgets without uninstalling them. [5]
The Wikiversity and Wikinews logos are now shown directly from the configuration and not from [[File:Wiki.png]]. If you want to change logo or have an anniversary logo, see how to request a configuration change. This is how it already works for other projects. They can request logo changes the same way. [7]
Problems
Because of a data centre test you will be able to read but not edit the wikis for 20 to 30 minutes on 19 April. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. You can read more about this. This will also happen on 3 May.
Changes this week
There is no new Mediawiki version this week. This is because of the data centre test.
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 18 April at 19:00 (UTC). See how to join.
Page Previews will be turned on for logged-out users on a large number of wikis in May. It could be postponed and happen later. Page Previews shows readers a short part of a linked article when they rest their mouse pointer on the link. This is to help them understand what it is about without leaving the article they are reading. Page Previews used to be called Hovercards. Users who have tested the feature can give feedback. [8]
From next week, user scripts using very old deprecated wikibits functions will show errors. These functions have not worked since 2013. You should fix or disable broken scripts. You can see examples of how to upgrade scripts. [9][10]
The fourth fiscal quarter began the first of this month, and Collaboration Team has begun work on our new quarterly goals. In the coming months, we'll be working to release the New Filters for Edit Review beta on all wikis and then to improve the beta as much as possible based on user feedback. On that score, we're planning a round of user interviews on the new tools in May to get detailed information about usability and usefulness. If you've tried the new features and have thoughts, please share them with us in any language.
Our other focus right now is to look at what changes will be needed to spread the new filtering interface to other review pages, especially Watchlist. We're also exploring how to incorporate the tools we didn't include in the new interface in this round, like the Tag Filters, time-frame selector and Namespace filter.
New Filters for Edit review are now available on Polish, Portuguese, Persian, Russian and Turkish Wikipedias as a Beta feature. French Wikipedia and Mediawikiwiki have the filters as a Beta feature too, but without the quality and intent filters. [11]
Special:RecentChangesLinked now displays a message when no results are found for a given combination of filters. [12]
Problems
Polish Wikipedia is experiencing an issue with predictions (quality and intent filters using ORES). The different predictions are in conflict. An edit can be considered as "good" and "bad" at the same time, and the filter levels are somewhat redundant. We have formulated a plan to address this and are working on a fix, which is deployed progressively on Polish Wikipedia. [13]
The issue on Polish Wikipedia is shared by a few other wikis: Dutch, Czech and Hebrew, and Wikidata. The deployment for those wikis has been postponed to Tuesday, May 9. Wikis without this predictions problem have been deployed or will be deployed with no change on the schedule. [14]
Interestingly, the "problem" with those wikis is that they perform better than we anticipated. Once the fix is in place, the tools will work with particular simplicity on these wikis.
Future changes
English Wikipedia and all wikis without ORES prediction services will get the New Filters for Edit review on Monday, April 24. [15]
All remaining wikis will get the New Filters for Edit review on Tuesday, May 9. [16]
Wikidata edits will be added as a type of change on New Filters for Edit review. [17]
Saturday, April 1 concluded the 2016-2017 GA Cup. 64 reviews were completed by our finalists. Although the backlog increased by 42 over the reviewing period instead of declining, the increase suggests that the contest is encouraging editors to nominate articles for review.
Congratulations to Shearonink, who is the winner of the Cup, finishing with 672 points! Once again, just as in last round, this is more than the point totals for all the other competitors combined! It was a close race for second place between Krishna Chaitanya Velaga, who achieved 164 points, and Sturmvogel_66, who earned 150. Though Sturmvogel_66 reviewed one more article than Krishna Chaitanya Velaga, Krishna Chaitanya Velaga managed to earn 14 points more due to reviewing older articles. Our two wildcard competitors, Kees08 and Chris troutman, came in fourth and fifth, respectively.
There were some bumps in the competition this time: The sign-up deadline and the first round were both extended due to fewer competitors signing up then was planned for. And there were delays in tallying points and getting out the newsletter. The judges apologize for this latter difficulty. Lastly, mid-way through the competition we bid farewell to Zwerg Nase, who stepped down from their position as judge due to other commitments. Information about the Final can be found here.
Thank you to all of our competitors, and congrats to our winners!
To subscribe or unsubscribe to future GA Cup newsletters, please add or remove your name to our mailing list. If you are a participant still competing, you will be on the mailing list no matter what as this is the easiest way to communicate between all participants.
21:16, 10 April 2017 (UTC)
Wikidata weekly summary #257
Here's your quick overview of what has been happening around Wikidata over the last week.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
When administrators, bureaucrats and stewards make a user a member of a user group they can now set an expiry date. A user group is for example "administrators" or "bots". This means that they can give someone user rights for a limited time. This is similar to how blocks and page protections can be limited in time. Special:UserRights will have new options for this. You can read more about user groups.[22]
Problems
Since the data centre test last week the content translation tool has been disabled. This is because of a database problem. It will be back as soon as the problem has been solved. [23]
Changes this week
The GuidedTour extension will be enabled on all wikis. This is a tool to explain to new users how to edit. [24]
Wiktionary will handle interlanguage links in a new way. The Cognate extension will automatically link pages with the same title between Wiktionaries. For this to work all old interlanguage links have to be removed. You can read more about this. [25]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 25 April. It will be on non-Wikipedia wikis and some Wikipedias from 26 April. It will be on all wikis from 27 April (calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 25 April at 19:00 (UTC). See how to join.
The second round of the competition has now closed, with just under 100 points being required to qualify for round 3. YellowEvan just scraped into the next round with 98 points but we have to say goodbye to the thirty or so competitors who didn't achieve this threshold; thank you for the useful contributions you have made to the Cup and Wikipedia. Our top scorers in round 2 were:
Cas Liber, led the field with five featured articles, four on birds and one on astronomy, and a total score of 2049, half of which came from bonus points.
1989 was in second place with 826 points, 466 of which were bonus points. 1989 has claimed points mostly relating to anime and Japanese-related articles.
Peacemaker67 took third place with two FAs, one GA and seven GARs, mostly on naval vessels or military personnel, scoring 543 points.
Other contestants who scored over 400 points were Freikorp, Carbrera, and Czar. Of course all these points are now wiped out and the 32 remaining contestants start again from zero in round 3.
Vivvt submitted the largest number of DYKs (30), and MBlaze Lightning achieved 13 articles at ITN. Carbrera claimed for 11 GAs and Argento Surfer performed the most GARs, having reviewed 11. So far we have achieved 38 featured articles and a splendid 132 good articles. Commendably, 279 GARs have been achieved so far, more than double the number of GAs.
So, on to the third round. Remember that any content promoted after the end of round 2 but before the start of round 3 can be claimed in round 3. Remember too that you must claim your points within 10 days of "earning" them. Invitations for collaborative writing efforts or any other discussion of potentially interesting work is always welcome on the WikiCup talk page. Remember, if two or more WikiCup competitors have done significant work on an article, all can claim points equally.
If you are concerned that your nomination—whether it is at good article nominations, a featured process, or anywhere else—will not receive the necessary reviews, please list it on Wikipedia:WikiCup/Reviews. If you want to help out with the WikiCup, please do your bit to help keep down the review backlogs! Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages or by email. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove yourself from Wikipedia:WikiCup/Newsletter/Send. Godot13, Sturmvogel 66 and Cwmhiraeth13:16, 1 May 2017 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Scripts using very old deprecated wikibits functions show errors. These functions have not worked since 2013. You should fix or disable broken scripts. You can see examples of how to upgrade scripts. This is the same thing as Tech News wrote about in issue 2017/16. You need to addmw.loader.using( 'mediawiki.util' ) block for your scripts also, or add mediawiki.util dependency in gadget ResourceLoader section in MediaWiki:Gadgets-definition. [27][28]
Problems
Because of a data centre test you will be able to read but not edit the wikis for 20 to 30 minutes on 3 May. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. You can read more about this.
Changes this week
There is no new MediaWiki version this week. This is because of the data centre test.
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 2 May at 19:00 (UTC). See how to join.
Future changes
All Wikimedia wikis will have cookie blocks from May 8. This is an extension to the autoblock system so when a user is blocked, the next time they visit the wiki a cookie will be set. This means that even if the user switches accounts and to a new IP address the cookie will block them again. [29]
The Publish changes, Show preview and Show changes buttons will look slightly different. This is to fit with the OOUI look. Users can test scripts, gadgets and so on to see if they work with the new interface by adding &ooui=1 to the URL. [30]
Worked more on support for lexicographical data (specifically support for lexicographic category and statements on forms)
Dealt with issues after the deployment of automatic interwiki links for Wiktionary
Worked on constraint violation user script based on your feedback (improving messages to make it more understandable, layout, etc)
Add support for the following new language codes for monolingual text properties: brx, chn, cop, gez, quc, kjh, nr (will become available in a few days)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Problems
Some users have a problem with the watchlist. Some changes in categories make the watchlist a blank page. The developers are working on this. Until this is fixed you can try some things that have helped other editors if you have this problem. You can turn on Hide categorization of pages in your watchlist preferences. You can turn off Expand watchlist to show all changes, not just the most recent in your watchlist preferences. You can remove problematic categories from Special:EditWatchlist/raw. [31]
There was a problem with the visual editor for several days. You could not save edits that triggered a CAPTCHA. This would for example be when a new user added external links in references. This was fixed on 2 May. [32]
Changes this week
When you edit you can switch between the visual editor and the wikitext editor. This works if the wiki you edit has the visual editor. The menu will now say Visual editing and Source editing instead of Switch to visual editing and Switch to code editing. This is because it was confusing when the menu said you could switch to the editor you were already using. [33]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 May. It will be on non-Wikipedia wikis and some Wikipedias from 10 May. It will be on all wikis from 11 May (calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 9 May at 19:00 (UTC). See how to join.
Future changes
You will be able to get a notification when a page you created is connected to a Wikidata item. This will come to Wikivoyage on 9 May. If there are no problems it will come to most Wikipedias on 30 May. It will come to other projects and English, French and German Wikipedia later in the summer. It will be opt-in for existing users and opt-out for new users. [34][35]
Markup that looks like code for language variants might need to be fixed. If -{ is used in transclusions or web addresses it has to be escaped appropriately. You can use -<nowiki/>{ for transclusions and %2D{ in web addresses. A transclusion could for example be when you use -{ in a template: {{1x| sad :-{ face }}. This is because of some code fixes to the preprocessor and affects all wikis. [36][37]
Did you know that you can review your changes visually?
When you are finished editing the page, type your edit summary and then choose "Review your changes".
In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
Click the toggle button to switch between visual and wikitext diffs.
The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history.
You can read and help translate the user guide, which has more information about how to use the visual editor.
A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#mw-prefsection-betafeatures to enable the ⧼Visualeditor-preference-newwikitexteditor-label⧽.
A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [38]
You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [40]
The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [41]
The Categories item has been moved to the top of the Page options menu (from clicking on the icon) for quicker access. [42] There is also now a "Templates used on this page" feature there. [43]
You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [44]
Tables can be set as collapsed or un-collapsed. [45]
The Special character menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [46]
A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [47]
There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K on a PC or Command+K on a Mac. [48]
Future changes
The VisualEditor team is working with the Community Tech team on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [49]
The kind of button used to Show preview, Show changes, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [50]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
You can now use ISBNs to automatically generate citations in the visual editor. This works on wikis that have enabled Citoid. [52]
The mediawiki.util library does not load automatically any more. Your Special:MyPage/common.js may use it. If you have technical problems that started a couple of weeks ago you can try adding mw.loader.using('mediawiki.util').done(function(){ as the first line in the file and }); as a last one. Tech News wrote about this in the 2017/18 issue. [54]
Changes this week
The RevisionSlider extension will be a default feature on all wikis. RevisionSlider is an easier way to move between changes in the page history. It has been a default feature on German, Arabic and Hebrew Wikipedia and a beta feature on all wikis. You will be able to turn it off in your preferences. [55]
There is no new MediaWiki version this week.
Future changes
Administrators will soon be able to search through deleted pages. [56][57]
Markup that looks like code for language variants might need to be fixed. Tech News wrote about this last week. If -{ is used in transclusions or web addresses it has to be escaped appropriately. You can use -<nowiki/>{ for transclusions and %2D{ in web addresses. This is because of some code fixes to the preprocessor and affects all wikis. You can now see the full list of wikis with this problem and help fix them to avoid that things break later this month. You might find false positives. You can read more about what to fix. [58][59]
Older unreported changes
Your Meta user page is shown on all wikis where you don't have a local user page. You can now add the magic word __NOGLOBAL__ to your Meta user page to stop this. [60][61]
