User talk:Zhuyifei1999/Archive 26
![]() | This 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. |
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. [1] - You can now see a list of all autoblocks on Special:AutoblockList. [2]
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. [3]
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.
Future changes
- stats.wikimedia.org will be replaced. You can see the new prototype. You can leave feedback on this change.
- 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. [4]
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. [5][6]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
19:32, 17 April 2017 (UTC)
Image without license
- Describe what it is about in a short sentence. (What does the image show?)
- State the author and the date of creation. If you made it yourself, say so explicitly. If it is from another Wikimedia user, link to the person's local user page. Best to use CommonsHelper.
- If you did not create the file yourself, state the source you got it from.
- Add a copyright tag - images without an appropriate license tag will be deleted.
- Add the image to one or more gallery pages and/or appropriate categories, so it can be found by others. To find out where an image belongs, you can use CommonsSense.
If you copied the file from another wiki, please copy all information given there and say who uploaded it to that wiki. Use CommonsHelper.
It is recommended to use Template:Information to put that information on the description page. Have a look at Template talk:Information for details of the use of this template.
You can edit the description page and change the text. Uploading a new version of the file does not change the description of the file.
Please add as much information as possible. If there is not sufficient information, the file may have to be deleted. For more information, follow the Commons:First steps guide. If you need help or have questions, please ask at the Help desk.
Thank you.This message was added automatically by MifterBot (Talk • Contribs • Owner), if you need some help about it, please read the text above again and follow the links in it, if you still need help ask at the ->Commons:Help desk in any language you like to use. --MifterBot (Talk • Contribs • Owner) 15:34, 2 May 2017 (UTC)
How to upload file
Hello. I upload the file AVG Screenshot.jpg and you nominated it for deletion. So my questions are how to upload files like these and where is my mistake ? --Nikki070 (talk) 14:31, 22 April 2017 (UTC)
- Please see Commons:Screenshots#Software --Zhuyifei1999 (talk) 14:45, 22 April 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.
Recent changes
- New filters for recent changes are now available as a beta feature on most wikis. You can turn it on in your preferences. Remaining wikis will have the new filters on 9 May. [7]
- 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. [8]
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. [9]
Changes this week
- The GuidedTour extension will be enabled on all wikis. This is a tool to explain to new users how to edit. [10]
- 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. [11]
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.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
16:40, 24 April 2017 (UTC)
common.js
I saw on the Help Desk that you offered to help others with fixing their common.js script. I was hoping to get some help with mine. --Elisfkc (talk) 16:44, 27 April 2017 (UTC)
- I cannot seem to import scripts. I am currently just replacing the import function with the original scripts (for a couple of them). --Elisfkc (talk) 16:51, 27 April 2017 (UTC)
- (Edit conflict) Loading your common.js I got
ReferenceError: getElementsByClassName is not defined
in User:Kanonkas/rollbackSummary.js, a script you imported. Since that user does not seem to be active I guess I'll have to change it for him. :/ --Zhuyifei1999 (talk) 16:54, 27 April 2017 (UTC)Done Special:Diff/242263878 --Zhuyifei1999 (talk) 17:01, 27 April 2017 (UTC)
- Ok, but I'm still having issues. My "AjaxDeleteExtraButtons" only appear occasionally and the cleanup scripts are just buttons, they don't actually run anything. --Elisfkc (talk) 17:04, 27 April 2017 (UTC)
- Ah, more errors in User:ZooFari/licensereviewer.js. Is there any reason to use that over User:Rillke/LicenseReview.js? I don't really have the interest to fix an old unmaintained script unless it serves some special purpose --Zhuyifei1999 (talk) 17:13, 27 April 2017 (UTC)
- Nope. And I think that solved everything. Thanks Elisfkc (talk) 17:19, 27 April 2017 (UTC)
- Ah, more errors in User:ZooFari/licensereviewer.js. Is there any reason to use that over User:Rillke/LicenseReview.js? I don't really have the interest to fix an old unmaintained script unless it serves some special purpose --Zhuyifei1999 (talk) 17:13, 27 April 2017 (UTC)
- Ok, but I'm still having issues. My "AjaxDeleteExtraButtons" only appear occasionally and the cleanup scripts are just buttons, they don't actually run anything. --Elisfkc (talk) 17:04, 27 April 2017 (UTC)
contact info
Dear Zhuyifei1999, Please give me your contact info such as mob. no. , skype , etc.--Zoc2 (talk) 12:02, 29 April 2017 (UTC)
- Why? You are free to email me if you have anything in private. --Zhuyifei1999 (talk) 12:14, 29 April 2017 (UTC)
No , I want to talk with you --Zoc2 (talk) 12:18, 29 April 2017 (UTC)
- Why do you think I should? --Zhuyifei1999 (talk) 13:35, 29 April 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.
Recent changes
- The content translation tool works again. It was turned off because of a database problem. [12]
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 add
mw.loader.using( 'mediawiki.util' )
block for your scripts also, or addmediawiki.util
dependency in gadget ResourceLoader section in MediaWiki:Gadgets-definition. [13][14]
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. [15]
- The
Publish changes
,Show preview
andShow 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. [16]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
19:50, 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.
Recent changes
- The content translation tool works again. It was turned off because of a database problem. [17]
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 add
mw.loader.using( 'mediawiki.util' )
block for your scripts also, or addmediawiki.util
dependency in gadget ResourceLoader section in MediaWiki:Gadgets-definition. [18][19]
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. [20]
- The
Publish changes
,Show preview
andShow 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. [21]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
19:50, 1 May 2017 (UTC)
FlickrReviewR 2 and the Trump White House & USDA
It looks like both the White House Flickr stream (https://www.flickr.com/people/148748355@N05?rb=1) and the Department of Agriculture Flickr stream (https://www.flickr.com/people/41284017@N08?rb=1) have decided to switch from using the US Government Works license on Flickr to using the normal Public Domain Mark 1.0 license. Any chance of making it so that, when FlickrReviewR 2 comes across images from these accounts, it automatically passes them like it did when the tag was US Government Work? That way, we don't crowd up Category:Flickr public domain images needing human review with these images that are clearly ok. I have already asked for Flinfo to override the normal Public Domain 1.0 tag. Elisfkc (talk) 15:50, 2 May 2017 (UTC)
- o.O... We could make a bot to replace the licenses with {{PD-POTUS}} & {{PD-USDA}}, in which case the bot will pass the image automatically (pass is used when it sees an actual PD template on the file description page), but IMHO the reviewer but should not whitelist specific accounts. (And if Flinfo decides to implement that flickr2commons transfers will work fine anyways, there wouldn't be a need for a patch to the bot; IIRC, UW prompts for a license when it sees a PDM) --Zhuyifei1999 (talk) 16:02, 2 May 2017 (UTC)
But this will still be an issue with the Flickr2Commons tool. Elisfkc (talk) 16:20, 2 May 2017 (UTC)Never mind, I get what you are saying now about it automatically passing the review. In that case, why doesn't PD-USGov-FBI do the same thing (example)? Elisfkc (talk) 16:23, 2 May 2017 (UTC)- Hmm... I thought it worked this way, but then I went to the commit history and saw this change. No idea why I did that... Will revert --Zhuyifei1999 (talk) 17:23, 2 May 2017 (UTC)
Done [22] --Zhuyifei1999 (talk) 17:30, 2 May 2017 (UTC)
Why does your bot re-upload files?
Why does Embedded Data Bot re-upload files like File:Пермский край. Нижневишерский заказник 1.jpg? This creates a lot of confusion in the Wiki Loves Earth competition and botches all our statistics. --Alexander (talk) 17:10, 4 May 2017 (UTC)
- See Commons:Bots/Requests/Embedded Data Bot. TL;DR: it contains embedded jpeg(s) which are not rendered by any image viewer and may contain malicious data. --Zhuyifei1999 (talk) 17:17, 4 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.
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 offExpand watchlist to show all changes, not just the most recent
in your watchlist preferences. You can remove problematic categories from Special:EditWatchlist/raw. [23] - 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. [24]
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
andSource editing
instead ofSwitch to visual editing
andSwitch to code editing
. This is because it was confusing when the menu said you could switch to the editor you were already using. [25] 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. [26][27]
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. [28][29]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
02:24, 9 May 2017 (UTC)
False positive reported by Embedded Data Bot
File:Uyghur flag construction.svg – it's even a valid SVG file.
Other issue are JPEGs processed by AtomJPEG (I believe this is it's home page) – AFAIR 100% of them are false positives. Example: File:The Princess of Hope.jpg. And last but not least, there are problematic photos taken using some smartphones, usually Samsung's, e.g. File:Fim do ano dia no Rio Paraná.jpg (taken using a Samsung) or File:Khairpur tamewali lake.jpg (taken using a Huawei). --jdx Re: 04:09, 9 May 2017 (UTC)
- Regarding photos processed by AtomJPEG,
jpegtran -copy all -optimize
strips some stuff from them: File:The Princess of Hope.jpg. --jdx Re: 04:21, 9 May 2017 (UTC)- File:Uyghur flag construction.svg --
</svg>
inside the comment broke the ending detection algorithm. Need a full-fledged XML parser to workaround that. - File:The Princess of Hope.jpg -- contains another JPEG file starting at position 307899,
file
showsJPEG image data, JFIF standard 1.01, aspect ratio, density 1x1, segment length 16, Exif Standard: [TIFF image data, big-endian, direntries=5, datetime=2017:03:06 18:10:35, orientation=[*0*], model=SM-G920F, manufacturer=samsung], comment: "processed by AtomJPEG 1.5.0n", baseline, precision 8, 3771x2121, frames 3
, but the JPEG is not render-able. Unless AtomJPEG is willing to give out ts source code, I have no idea what's going on. - File:Fim do ano dia no Rio Paraná.jpg -- Similar to File:Smedenpoort_Brugge.jpg, an MP4-like file concatenated. (see phab Z567)
- File:Khairpur tamewali lake.jpg -- not recognizable.
- File:Uyghur flag construction.svg --
- When jpegtran can truncate more than 50% of the data, the bot is probably gong to be suspicious anyways. --Zhuyifei1999 (talk) 06:24, 9 May 2017 (UTC)
Technical problems
I read the page you suggested about clearing the problems. I'm still not technical, but the solution I came up with was to install a clean copy of a different browser (in this case Safari) and found that everything was working. I will use Safari from now on to do Commons work. I still have no idea why the Firefox was failing, but as I don't understand any of it; and changing browsers solved the problem, I wish to thank you for trying to help and tell you it's all fixed. The only remaining problem now is to become fluid in my workflow with the new browser. Cheers! Ellin Beltz (talk) 16:40, 13 May 2017 (UTC)
- @Ellin Beltz: Oh hi. I personally like Firefox the best (and I use it all the time). Sad to see it not work :/ but glad that you got everything working anyways :) Btw: Have you tried the "new way to install VFC" I posted to COM:VP/P? It might solve the issue but I can't guarantee that. (Race conditions are weird) --Zhuyifei1999 (talk) 16:49, 13 May 2017 (UTC)
- I totally prefer Firefox. If you can figure out the problem from File:JavaScreenShotAsRequested.jpg, maybe I can keep using it. Even to my ignorant eye, "mw.util is undefined" seems like it might be the problem. That seems to cause everything else after it to be in pink. Thanks so much! Ellin Beltz (talk) 18:13, 13 May 2017 (UTC)
- @Ellin Beltz: That shares the same symptom as the race condition I mentioned on COM:VP/P last section. The fix would be: 1. get rid of that mw.util.addPortletLink in User:Ellin_Beltz/common.js 2. follow Help:VisualFileChange.js#Step_0:_How_to_Install. It worked for MichaelMaggs so hopefully it will work for you as well (if my guess on the cause is right). --Zhuyifei1999 (talk) 18:36, 13 May 2017 (UTC)
- Followed those instructions, no change. Still do not have "no permissions," "no source", "copyright violation" and/or "batch task" in Firefox. Also, are you aware that where it says "click here to autoinstall" doesn't do anything but reopen the same window? Ellin Beltz (talk) 19:01, 13 May 2017 (UTC)
- @Ellin Beltz: You missed step 1 "get rid of that mw.util.addPortletLink in User:Ellin_Beltz/common.js" :P See COM:VP/P "Enabling the gadget does not automatically resolve all the issues in common.js if you don't remove the original lines in common.js." Regarding the autoinstall link, it is built on the assumption that you don't have a JS error, as it is MediaWiki:ActivateGadget.js doing all the magic. So you need to do step 1 :P --Zhuyifei1999 (talk) 19:12, 13 May 2017 (UTC)
- You're probably going to think that I'm really stupid, but https://commons.wikimedia.org/wiki/Help:VisualFileChange.js#Step_0:_How_to_Install, says "Step 1: Insert contributor..." The batch task thing has to work first in order to get there. But I'm trying to understand what you're saying, and wonder if wiping out the entire *.js file first and then running the auto installer is what you're trying to say? I am really sorry, but your explanations are probably 100% perfect for someone who already knows what you're talking about; but for me, I am totally lost and just banging around trying to fix something. Ellin Beltz (talk) 00:02, 14 May 2017 (UTC)
- UPDATE: I got stupid/smart and just copied your *.js page. Now everything works (I hope) and I have a pile more buttons than I used to have... but the ones which vanished have returned. I hope that's ok with you? Ellin Beltz (talk) 00:08, 14 May 2017 (UTC)
- @Ellin Beltz: Yeah, wiping it out (the real thing is just to comment out / remove that mw.util.addPortletLink line) and run the autoinstall is one way. I have a ton of junk inside my common.js, and would prefer if you don't copy it. Though if you really like it that's fine. Btw:, that floater is from
importScript( 'User:Rillke/gallery-sort.js' );
. --Zhuyifei1999 (talk) 04:15, 14 May 2017 (UTC)
- @Ellin Beltz: Yeah, wiping it out (the real thing is just to comment out / remove that mw.util.addPortletLink line) and run the autoinstall is one way. I have a ton of junk inside my common.js, and would prefer if you don't copy it. Though if you really like it that's fine. Btw:, that floater is from
- UPDATE: I got stupid/smart and just copied your *.js page. Now everything works (I hope) and I have a pile more buttons than I used to have... but the ones which vanished have returned. I hope that's ok with you? Ellin Beltz (talk) 00:08, 14 May 2017 (UTC)
- You're probably going to think that I'm really stupid, but https://commons.wikimedia.org/wiki/Help:VisualFileChange.js#Step_0:_How_to_Install, says "Step 1: Insert contributor..." The batch task thing has to work first in order to get there. But I'm trying to understand what you're saying, and wonder if wiping out the entire *.js file first and then running the auto installer is what you're trying to say? I am really sorry, but your explanations are probably 100% perfect for someone who already knows what you're talking about; but for me, I am totally lost and just banging around trying to fix something. Ellin Beltz (talk) 00:02, 14 May 2017 (UTC)
- @Ellin Beltz: You missed step 1 "get rid of that mw.util.addPortletLink in User:Ellin_Beltz/common.js" :P See COM:VP/P "Enabling the gadget does not automatically resolve all the issues in common.js if you don't remove the original lines in common.js." Regarding the autoinstall link, it is built on the assumption that you don't have a JS error, as it is MediaWiki:ActivateGadget.js doing all the magic. So you need to do step 1 :P --Zhuyifei1999 (talk) 19:12, 13 May 2017 (UTC)
- Followed those instructions, no change. Still do not have "no permissions," "no source", "copyright violation" and/or "batch task" in Firefox. Also, are you aware that where it says "click here to autoinstall" doesn't do anything but reopen the same window? Ellin Beltz (talk) 19:01, 13 May 2017 (UTC)
- @Ellin Beltz: That shares the same symptom as the race condition I mentioned on COM:VP/P last section. The fix would be: 1. get rid of that mw.util.addPortletLink in User:Ellin_Beltz/common.js 2. follow Help:VisualFileChange.js#Step_0:_How_to_Install. It worked for MichaelMaggs so hopefully it will work for you as well (if my guess on the cause is right). --Zhuyifei1999 (talk) 18:36, 13 May 2017 (UTC)
- I totally prefer Firefox. If you can figure out the problem from File:JavaScreenShotAsRequested.jpg, maybe I can keep using it. Even to my ignorant eye, "mw.util is undefined" seems like it might be the problem. That seems to cause everything else after it to be in pink. Thanks so much! Ellin Beltz (talk) 18:13, 13 May 2017 (UTC)
- Please check now? I don't think there's anything remaining which is exactly identical except for whatever the installer generated (if it's the same). I've tried to mark the "paragraphs" as to what they do. Thanks. Ellin Beltz (talk) 05:00, 14 May 2017 (UTC)
- @Ellin Beltz: The installer is basically activating the gadget by editing your user preferences (MediaWiki:ActivateGadget.js, I haven't read through it yet). However, changing the text like 'vFCProfil' or 'catALotEnd' may break MediaWiki:Gadget-SettingsManager.js when cat-a-lot or vfc tries to save your gadget preferences. I'm not 100% sure since I'm not Rillke the genius, but I suggest you to change them back (i.e. for cat-a-lot preferences this is
//**** Cat-A-Lot user preferences //////////
=>//catALot///////////////////////////////////////
,////////////////////////////////////
=>////////////////////////////////////catALotEnd//
) --Zhuyifei1999 (talk)
- @Ellin Beltz: The installer is basically activating the gadget by editing your user preferences (MediaWiki:ActivateGadget.js, I haven't read through it yet). However, changing the text like 'vFCProfil' or 'catALotEnd' may break MediaWiki:Gadget-SettingsManager.js when cat-a-lot or vfc tries to save your gadget preferences. I'm not 100% sure since I'm not Rillke the genius, but I suggest you to change them back (i.e. for cat-a-lot preferences this is
@Zhuyifei, probably there should be sent a mass message to all users which have installed VFC in old style, with the suggestion to switch to gadget and/or as an alternative - an explanation how to fix possible issues with the VFC userscript. XXN, 14:05, 14 May 2017 (UTC)
- Good point. I probably won't have time next week though :/ --Zhuyifei1999 (talk) 15:08, 14 May 2017 (UTC)
Hi. Thank you for running Embedded Data Bot. Would it make sense, in cases like the subject file, for the bot to revdel the version which contains embedded data? Note, the name has changed since the bot took action. — Jeff G. ツ 15:41, 14 May 2017 (UTC)
- Those files that the bot decided to reupload should be usually harmless (they just seem to contain embedded JPEG with yet unknown reason, though these may contain steganography-coded data), but those the bot delete immediately are 100% (idk a counter example yet) abusive files (they contain embedded archive), and those that are tagged is when the bot is unsure. Though, revdel may be implemented soon, see phab:Z567. --Zhuyifei1999 (talk) 16:23, 14 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.
Recent changes
- You can now use ISBNs to automatically generate citations in the visual editor. This works on wikis that have enabled Citoid. [30]
- The Two Column Edit Conflict View is available as a beta feature on all wikis. It is a new interface for the edit conflict resolution page. [31]
Problems
- 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 addingmw.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. [32]
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. [33]
- There is no new MediaWiki version this week.
Future changes
- Administrators will soon be able to search through deleted pages. [34][35]
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. [36][37]
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. [38][39]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
21:48, 15 May 2017 (UTC)