Open main menu

Wikimedia Commons β

User talk:1Veertje

Notice Please be aware that the only reason I'm at the top of the list of administrators is because the list is ordered alphabetically.
Please consider the Help Desk first

Commons Conference projectEdit

Hello

I'm writing you as one of the most active Commons users right now. Since a while now, the idea of a dedicated Commons conference has been floating around. But since the last Wikimania concrete steps have been taken to actually make it happen next year. If you're interested in participation or maybe willing to help organize the first ever Commons Conference, I invite you to check out the project page and leave your comments; or just show your support for the idea, by signing up.

Cheers,

--Touzrimounir (talk) 20:07, 6 September 2017 (UTC)

Rijksmuseum TwentheEdit

Hoi Vera, op de website van Rijksmuseum Twenthe zijn wel wat aardige schilderijen te vinden die in het publiek domein zijn, zie [1] en [2]. Ze gebruiken memorix, zie bijvoorbeeld https://collectie.rijksmuseumtwenthe.nl/zoeken-in-de-collectie/detail/id/66b193f1-f56d-5f86-94fa-c587e5b5670b . Kan jij zien of de download link hetzelfde geeft als jouw tooltje? Wellicht zin om deze afbeeldingen naar Commons te uploaden? Ik ga de schilderijen denk ik binnenkort aan Wikidata toevoegen. Multichill (talk) 19:49, 18 September 2017 (UTC)

Hey, ja het RMT maakt ook gebruik van de Memorix Maior en dus met m'n scriptje in de max resolutie gedownload worden. Mijn scriptje gaat op zoek naar de link van de thumbnail.

Daarmee wordt er uit de API opgehaald wat de dimensies van de grootste versie kan worden opgehaald en de tegels van die versie aan elkaar kunnen worden geplakt:

for ($row=0; $row < $layer['rows']; $row++) { 
		for ($col=0; $col < $layer['cols']; $col++) { 
		 $url = 'http://images.memorix.nl/'.$institution.'/getpic/'.$id.'/';
			$url .= $layer['starttile']+$row*$layer['cols']+$col.'.jpg';
			$tile = imagecreatefromjpeg($url);
			imagecopy($image, $tile, $col * $tilewidth, $row * $tileheight, 0, 0, $tilewidth, $tileheight);
		}
	}

PHP is niet de handigste taal als je dit voor een hele groep afbeeldingen wil doen. In het verleden heb ik dit wel gedaan voor iMacros een macro te schrijven die het PHP scriptje voerde. Java zou beter zijn. Niet alleen voor dit, maar User:Hannolans heeft ook nog data op de plank liggen die ik van het nationaal fotomuseum waar hij de foto's die PD zijn uit zou gaan filteren.--Vera (talk) 13:47, 19 September 2017 (UTC)

Gebeurt het trouwens wel eens dat we eerst een set in commons plaatsen voorzien van de kant-en-klare thumbnails en daarna een botje draaien op commons om de highres toe te voegen? --Hannolans (talk) 13:55, 19 September 2017 (UTC)
Nee. Is ook niet direct makkelelijk automatisch te detecteren wanneer dat gebeurt.--Vera (talk) 14:11, 19 September 2017 (UTC)

File:Edit-a-thon-Haagse-Monumenten-02-Motion-Blur-Effect.pngEdit

Beste Vera,

Leuk je weer eens tegen te komen. Je Dememorixer blijft vreselijk handig! Wilde je het volgende laten weten, als je het al niet wist. Een Peruaan, Jsmura van Wiki loves monuments geloof ik, vond het leuk om vervormde foto's van edit-a-thons op te laden, zoals deze van jou en dan de auteursvermelding niet aan te passen. Heb net om verwijdering gevraagd voor een soortgelijke foto "van mij". Vriendelijke groet, Hansmuller (talk) 07:56, 19 September 2017 (UTC)

Hey, tja in principe kan je dit doen met werk dat een vrije licentie heeft, al kan men zich afvragen wat de het educatieve doeleind is van een afbeelding die een en al motion blur is. --Vera (talk) 13:51, 19 September 2017 (UTC)

Foto'sEdit

Hallo Vera, ik zie een aantal monumenten foto's die nog niet in de WLM2017 categorie staan. Is dit een bewuste keuze, of zal ik deze toevoegen? groetjes, Rudolphous (talk) 18:52, 1 October 2017 (UTC)

De foto's van Texel moest ik nog taggen en categorizeren. Dat heb jij al gedaan, en nu heb ik ze ook voor WLM nog even getagged. --Vera (talk) 20:02, 2 October 2017 (UTC)
Hierbij nog een lijstje foto's waarbij het monumentnummer mist. Ook kan het zijn dat het geen monumenten zijn. In dat geval staat de foto onterecht in de wlm categorie. [3] groeten, Rudolphous (talk) 13:59, 4 October 2017 (UTC)
Ik heb het recht gezet. Wist je trouwens dat je de coördinaten uit een categorie of pagina kan projecteren op OSM of Google Maps? Met {{GeoGroup}} kan je de links daarvoor aan een pagina toevoegen. Zelf heb ik ook een simpel formulier een keer gemaakt om het ook los te kunnen gebruiken. Zie bijvoorbeeld mijn foto's van maart 2015. Met Google MyMaps kan je een geëxporteert KML besetand aan je Google Drive toevoegen. Kaarten die je daar maakt kan je op je smart phone weer naar boven halen zoals ik bij Wiki Takes Leiden deed. --Vera (talk) 20:01, 4 October 2017 (UTC)
Hoi 1veertje, handig allemaal, dank daarvoor :-) Hierbij de map van WLM nederland 2017: [4]. Kennelijk heeft afgelopen jaar niemand de moeite genomen om foto's in zeeland te maken. Rudolphous (talk) 20:44, 4 October 2017 (UTC)

Beschrijving bij categoryEdit

Hallo 1Veertje, de beschrijving is nogal verwarrend. Kan je dit aanpassen en de respectievelijke links aanbrengen? :) Lotje (talk) 11:16, 6 October 2017 (UTC)

Ik bedoel te zeggen wat er staat: Er is een plaatsje wat Stroe heeft met een straat Stroeërweg waar een boerderij aan nr 39 is in zowel Gelderland als Noord-Holland. Wat ik me kan herinneren had ik al RCE afbeeldingen van de ene Stroe naar de andere Stroe verplaatst dus die lijken ook niet te weten in welke provincie hun fotograaf bezig is geweest. --Vera (talk) 13:15, 6 October 2017 (UTC)
De beschrijving heb ik aangepast zoals ik bedoelde. :) Lotje (talk) 13:33, 6 October 2017 (UTC)

File:Informateur zalm-hres.jpgEdit

  File:Informateur zalm-hres.jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue.
Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!


Afrikaans | العربية | Български | বাংলা | Беларуская (тарашкевіца)‎ | Català | Čeština | Dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | עברית | Magyar | Bahasa Indonesia | Íslenska | Italiano | 日本語 | 한국어 | Македонски | മലയാളം | Plattdüütsch | Nederlands | Norsk nynorsk | Norsk bokmål | Occitan | Polski | Português | Português do Brasil | Română | Русский | Slovenčina | Slovenščina | Shqip | Српски / srpski | Svenska | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Jan Arkesteijn (talk) 21:31, 25 October 2017 (UTC)

File:Informateur zalm-hres (cropped).jpgEdit

  File:Informateur zalm-hres (cropped).jpg has been listed at Commons:Deletion requests so that the community can discuss whether it should be kept or not. We would appreciate it if you could go to voice your opinion about this at its entry.

If you created this file, please note that the fact that it has been proposed for deletion does not necessarily mean that we do not value your kind contribution. It simply means that one person believes that there is some specific problem with it, such as a copyright issue.
Please remember to respond to and – if appropriate – contradict the arguments supporting deletion. Arguments which focus on the nominator will not affect the result of the nomination. Thank you!


Afrikaans | العربية | Български | বাংলা | Беларуская (тарашкевіца)‎ | Català | Čeština | Dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Esperanto | Español | Eesti | فارسی | Suomi | Français | Galego | עברית | Magyar | Bahasa Indonesia | Íslenska | Italiano | 日本語 | 한국어 | Македонски | മലയാളം | Plattdüütsch | Nederlands | Norsk nynorsk | Norsk bokmål | Occitan | Polski | Português | Português do Brasil | Română | Русский | Slovenčina | Slovenščina | Shqip | Српски / srpski | Svenska | Türkçe | українська | Tiếng Việt | 中文 | 中文(简体)‎ | 中文(繁體)‎ | +/−

Jan Arkesteijn (talk) 21:32, 25 October 2017 (UTC)

Video en still Carola SchoutenEdit

Dag Vera. Ik heb zojuist in de beschrijvingen van File:Kamerlid Carola Schouten over het aanvragen van een Kamerdebat.webm en het daarvan afgeleide File:Carola Schouten 2016.jpg toegevoegd dat 2016 het jaar van uploaden is (op YouTube nl.). Het is zeker niet het jaar van de opname. Ik vermoed dat dat 2012 is, want sinds ergens in 2013 draagt ze geen bril meer. Zie ook de sterke gelijkenis met File:Carola Schouten 2012.jpg. In de categorieën van de video dient daarom denk ik ook nog iets aangepast worden alsmede in de bestandsnaam van de still. Groetjes, Apdency (talk) 17:31, 27 October 2017 (UTC)

de website die bij deze filmpjes hoorde heeft de mp4 bestanden gelinkt. In de metadata van die videos is een betere datum waarschijnlijk te vinden. Daar zal ik later ff naar kijken. Vera (talk) 17:48, 27 October 2017 (UTC)
Ik heb in ieder geval bij het filmpje de categorie over video's uit 2016 weggehaald. De still kan een naam met het jaartal 2012 krijgen, of een naam zonder jaartal, als we het niet exact weten. Groet, Apdency (talk) 20:29, 7 November 2017 (UTC)
De mp4's op de website hadden geen metadata in de bestanden ingesloten. De persafdeling van de tweede kamer zal ik even mailen. Vera (talk) 20:31, 7 November 2017 (UTC)

UploadfilmpjeEdit

Dag Vera. Deze week ben ik weer eens bezig om mensen die een foto naar Commons willen uploaden uit te leggen hoe dat gaat. Het is erg lastig om dit uit te leggen aan gebruikers die nooit eerder te maken hebben gehad met licenties en uploaden. Ten einde raad heb ik maar een YouTube link gestuurd https://www.youtube.com/watch?v=FbqmA2iR5kE. Het lijkt me handig als zo 'n soort filmpje (in het Nederlands) beschikbaar komt voor onervaren gebruikers. Of bestaat er al zoiets? 'k Leg de suggestie hier even neer, maar de vraag moet waarschijnlijk ergens anders neergelegd worden. Met vriendelijke groet, Tulp8 (talk) 18:05, 30 October 2017 (UTC)

Hey, Ja Wikimedia Nederland heeft een aantal van dit soort films geproduceerd. Zie deze bijvoorbeeld Vera (talk) 18:09, 30 October 2017 (UTC)
Dat had ik al gehoopt. Zelfs als behoorlijk ervaren gebruiker was ik niet van het bestaan van dit filmpje op de hoogte. Zou dit niet wat prominenter onder de aandacht van nieuwe gebruikers moeten worden gebracht? Tulp8 (talk) 12:09, 31 October 2017 (UTC)
Wikimedia Nederland zit in de precaire situatie dat ze er voor zijn om de Wikimedia gemeenschap te ondersteunen, niet om zich met de inhoud van de Wikimedia projecten te bemoeien. Heb je zelf een voorstel waar nieuwe gebruikers deze filmpjes tegen zouden kunnen komen? Op Wikimedia Commons hier heb je ook nog het probleem dat het moeilijk te zien is welke nieuwe gebruiker uit Nederland komt. Vera (talk) 12:50, 31 October 2017 (UTC)
'k Dacht aan hier boven de gele balk met bijvoorbeeld de linktekst: "Nederlandstalig uploadfilmpje". Tulp8 (talk) 12:58, 31 October 2017 (UTC)

Zoiets zou in de kroeg besloten moeten worden Vera (talk) 21:49, 7 November 2017 (UTC)

File:Stephen Law voice en 160731 205357.oggEdit

The Big Bad Wolfowitz (talk) 17:11, 4 November 2017 (UTC)

Categorie formatie 2017Edit

De bestanden in Category:Dutch general elections 2017 coalition negotiations zijn toegevoegd aan Commons:Deletion requests/Dutch general elections 2017 coalition negotiations zodat de gemeenschap kan bespreken of die behouden moeten worden of niet. We zouden het op prijs stellen als u uw mening hierover daar uit. Als u het bestand heeft gemaakt, bedenk u dan dat een verwijderverzoek niet betekent dat het bestand wordt verwijderd of dat we als gemeenschap uw bijdragen niet waarderen. Het betekent dat een gebruiker denkt dat er een specifiek probleem mee is, zoals bijvoorbeeld met de auteursrechten. Als het bestand ter verwijdering is voorgedragen omdat er een beter bestand beschikbaar is, bedenk u dan dat hoewel het bestand verwijderd zou kunnen worden, uw harde werk (dat we echt enorm waarderen) voortleeft in een nieuw bestand. Vat het verwijderverzoek in alle gevallen niet persoonlijk op. Zo is het ook niet bedoeld. Dank u!

Wel jammer 1veertje, maar ik denk dat het niet in orde is, vandaar deze massa nominatie. Met overigens hartelijke groet, Elly (talk) 20:08, 4 November 2017 (UTC)

it's OK. Ken je visualFileChange.js? Daarmee kan je gemakkelijk alle afbeeldingen in een categorie nomineren / bewerken in een batch Vera (talk) 21:50, 7 November 2017 (UTC)
Dank je, ja daar heb ik het inderdaad mee gedaan. Heel handig! Groet, Elly (talk) 14:56, 13 November 2017 (UTC)
Ik heb een handjevol tips verzameld mocht je geïnteresseerd zijn. --Vera (talk) 15:05, 13 November 2017 (UTC)

Category:Winding towers in NederlaandEdit

Hallo, 1Veertje, vreemde benaming voor Nederland. De vraag is, maak ik een [[Category:Winding towers in the Netherlands]] aan. :) Lotje (talk) 07:41, 13 November 2017 (UTC)

Ik heb het rechtgezet met Category:Winding towers in the Netherlands. --Vera (talk) 09:13, 13 November 2017 (UTC)
Bedankt! Lotje (talk) 10:17, 13 November 2017 (UTC)

Category:Poetry slamEdit

Hallo 1Veertje, er bestaat een Poetryslam pagina hier (dus het in het Nederlands), zou het niet eenvoudiger en minder verwarrend zijn deze leeg te halen en de link naar Poetry slam te maken in de Category:Poetry slam ? Lotje (talk) 10:39, 13 November 2017 (UTC)

Met {{Move}} kan je dit soort naamswijzigingen aanvragen. --Vera (talk) 10:54, 13 November 2017 (UTC)

Category:PalmeselEdit

Hallo 1Veertje, only me again! Kan dit worden opgelost in het Engels hier? :) Lotje (talk) 17:09, 13 November 2017 (UTC)

File tagging File:RN7 Logo.jpgEdit

Беларуская (тарашкевіца)‎ | Català | Čeština | Dansk | Deutsch | Deutsch (Sie-Form)‎ | Ελληνικά | English | Español | فارسی | Suomi | Français | Galego | עברית | Hrvatski | Magyar | Հայերեն | Italiano | 日本語 | 한국어 | Lietuvių | Македонски | മലയാളം | Plattdüütsch | Nederlands | Norsk bokmål | Polski | Português | Română | Русский | Sicilianu | Slovenčina | Slovenščina | Svenska | Türkçe | Українська | اردو | Tiếng Việt | 中文(简体)‎ | 中文(繁體)‎ | +/−
 
This media may be deleted.
Thanks for uploading File:RN7 Logo.jpg. This media is missing permission information. A source is given, but there is no proof that the author or copyright holder agreed to license the file under the given license. Please provide a link to an appropriate webpage with license information, or send an email with copy of a written permission to OTRS (permissions-commons@wikimedia.org). This also applies if you are the author yourself.

Please see this page for more information on how to confirm permission, and Commons:Permission if you would like to understand why we ask for permission when uploading work that is not your own.

Unless the permission information is given, the image may be deleted after seven days. Thank you.

MoiraMoira (talk) 16:08, 14 November 2017 (UTC)

Wiki Loves Monuments 2017 in the United States – Results!Edit

  This user participated in Wiki Loves Monuments 2017.

Want to show your participation in Wiki Loves Monuments 2017? Add {{User Wiki Loves Monuments 2017}} to your userpage!

Thank you for contributing to Wiki Loves Monuments 2017 in the United States during the month of October! The United States contest saw over 1,400 people (the most of any nation this year) contribute over 8,000 great photos of cultural and historic sites from all over the United States and its territories. Hundreds of these photos are already being used to illustrate pages on various Wikimedia projects.

We're excited to announce that our national judging process has concluded, and that we have selected the winners of Wiki Loves Monuments 2017 in the United States! These photos are recognized for their photographic quality, artistic merit, and their encyclopedic value as illustrations of unique historical sites. We were amazed by all of the uploads, and regret only being able to formally recognize the top 10. That being said – congratulations to our national winners and their amazing shots! Our 10 winners will be sent to the international Wiki Loves Monuments jury, who will then select the winners of the international contest. If you're interested in seeing the winners of the other national contests, you may do so at Wiki Loves Monuments 2017 winners.

If you would like to view all the photos submitted for the U.S. this year, you may do so here.

Finally, we have also created a feedback form for all U.S. participants to fill out. The survey is optional and anonymous, and only takes a minute or two – we hope to use the feedback to organize better events in the future!

A quick thank you to our national jury, as well as Commons editors who have helped categorize and place photos for the event. And finally, thank you for participating in Wiki Loves Monuments and helping to preserve our history through photography - we hope to see you again for future Commons photography events!

~Kevin Payravi & Nikikana, from Wiki Loves Monuments in the United States (16:26, 15 November 2017 (UTC))

File:Ondernemer van het jaar 2017.webmEdit

 
File:Ondernemer van het jaar 2017.webm has been marked as a possible copyright violation. Wikimedia Commons only accepts free content—that is, images and other media files that can be used by anyone, for any purpose. Traditional copyright law does not grant these freedoms, and unless noted otherwise, everything you find on the web is copyrighted and not permitted here. For details on what is acceptable, please read Commons:Licensing. You may also find Commons:Copyright rules useful, or you can ask questions about Commons policies at the Commons:Help desk.

The file you added has been deleted. If you believe that the deletion was not in accordance with policy, you may request undeletion.

Wikimedia Commons takes copyright violations very seriously and persistent violators will be blocked from editing.


Afrikaans | العربية | Asturianu | Azərbaycanca | Беларуская (тарашкевіца)‎ | Български | বাংলা‎ | Català | Čeština | Dansk | Deutsch | Deutsch (Sie-Form)‎ | Zazaki | Ελληνικά | English | Español | فارسی | Suomi | Français | Galego | עברית | Magyar | Հայերեն | Bahasa Indonesia | Italiano | 日本語 | 한국어 | Luxembourgish | Македонски | മലയാളം | Bahasa Melayu | Malti | မြန်မာဘာသာ | Plattdüütsch | Nederlands | Norsk nynorsk | Norsk bokmål | Polski | Português | Português do Brasil | Română | Русский | Slovenčina | Slovenščina | Svenska | ไทย | Türkçe | Українська | Tiếng Việt | 中文(简体)‎ | 中文(繁體)‎ | +/−

EugeneZelenko (talk) 14:57, 22 November 2017 (UTC)

1VeertjeBotEdit

Hello, I blocked 1VeertjeBot because it is not approved. It is also causing a huge backlog of patrolled edits. Best --Steinsplitter (talk) 12:51, 23 November 2017 (UTC)

Steinsplitter would you be ok with me deblocking my bot account for a bit so I can correct the "Videos of YYYY by country" categories I created? As Auntof6 pointed out I forgot to add "country" to the {{Metacat}}. --Vera (talk) 12:11, 26 November 2017 (UTC)
Nevermind, I see they already fixed it. --Vera (talk) 12:13, 26 November 2017 (UTC)
Ok :-). I have seen you filed a "request or botflag" thanks. --Steinsplitter (talk) 12:15, 26 November 2017 (UTC)

Metacategories created by 1VeertjeBotEdit

Hi, 1Veertje. Your bot has been creating metacategories with incomplete {{metacat}} template coding. That template needs a parameter to indicate the sorting criterion. For example, the template on Category:Videos of 1959 by country should be {{metacat|country}}. Please be sure to include the parameter when you or your bot create a metacategory. Thanks. --Auntof6 (talk) 04:01, 24 November 2017 (UTC)

Ah, sorry about that. Will try to keep that in mind in the future.--Vera (talk) 12:04, 24 November 2017 (UTC)

User:1VeertjeBotEdit

Congratulations! It has bot status now. --EugeneZelenko (talk) 14:44, 1 December 2017 (UTC)

  --Vera (talk) 14:48, 1 December 2017 (UTC)

deletion of image File:Patty pan from lalbagh 2285.JPGEdit

Hi, You have notified me on the image deletion File:Patty pan from lalbagh 2285.JPG. I would like to know about the deletion request entry and discussion about this. --Rameshng (talk) 01:58, 16 December 2017 (UTC)

Your photograph was a photograph of a photograph of Pattypan. That makes it not entirely your work to license but a derivative work. At the time it was a speedy deletion request since it was an open and shot case.--Vera (talk) 11:06, 17 December 2017 (UTC)


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 28 new jshint issues -- the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 63 character 15: Duplicate key 'author'. - Evidence: author: 'author',
  2. ISSUE: line 219 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  3. ISSUE: line 225 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  4. ISSUE: line 230 character 14: Unnecessary semicolon. - Evidence: };
  5. ISSUE: line 337 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  6. ISSUE: line 340 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  7. ISSUE: line 425 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  8. ISSUE: line 468 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  9. ISSUE: line 476 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  10. ISSUE: line 477 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  11. ISSUE: line 478 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  12. ISSUE: line 490 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  13. ISSUE: line 610 character 6: Missing semicolon. - Evidence: }
  14. ISSUE: line 632 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  15. ISSUE: line 970 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  16. ISSUE: line 994 character 20: 'i' is already defined. - Evidence: for (var i = details.length - 1; i >= 0; i--) {
  17. ISSUE: line 1053 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  18. ISSUE: line 1056 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  19. ISSUE: line 1059 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  20. ISSUE: line 1062 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  21. ISSUE: line 1065 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  22. ISSUE: line 1068 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  23. ISSUE: line 1071 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  24. ISSUE: line 1074 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  25. ISSUE: line 1077 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  26. ISSUE: line 1080 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  27. ISSUE: line 1083 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  28. ISSUE: line 1086 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  29. ISSUE: line 1089 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  30. ISSUE: line 1092 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  31. ISSUE: line 1095 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  32. ISSUE: line 1105 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  33. ISSUE: line 1108 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  34. ISSUE: line 1111 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  35. ISSUE: line 1114 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  36. ISSUE: line 1117 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  37. ISSUE: line 1120 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  38. ISSUE: line 1123 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  39. ISSUE: line 1126 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  40. ISSUE: line 1129 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  41. ISSUE: line 1135 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  42. ISSUE: line 1145 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  43. ISSUE: line 1151 character 9: Unreachable 'break' after 'return'. - Evidence: break;
  44. ISSUE: line 1154 character 9: Unreachable 'break' after 'return'. - Evidence: break;

Your CommonsMaintenanceBot (talk) at 16:13, 23 December 2017 (UTC).


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 424 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  7. ISSUE: line 467 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  8. ISSUE: line 475 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  9. ISSUE: line 476 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  10. ISSUE: line 477 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  11. ISSUE: line 489 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  12. ISSUE: line 609 character 6: Missing semicolon. - Evidence: }
  13. ISSUE: line 631 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  14. ISSUE: line 969 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  15. ISSUE: line 993 character 20: 'i' is already defined. - Evidence: for (var i = details.length - 1; i >= 0; i--) {
  16. ISSUE: line 1142 character 16: 'i' is already defined. - Evidence: for (var i = deviders.length - 1; i >= 0; i--) {

Your CommonsMaintenanceBot (talk) at 19:18, 23 December 2017 (UTC).

Dememorixer CategoryEdit

Dear 1Veertje, I sometimes use your useful Dememorixer. There is a [[Category:Dememorixer]], but that Category is used to identify images that could be "upgraded" with the Dememorixer. Is there also a category that identifies images that have been upgraded by the Dememorixer? Vysotsky (talk) 14:12, 24 December 2017 (UTC)


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue -- the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 424 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  7. ISSUE: line 467 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  8. ISSUE: line 475 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  9. ISSUE: line 476 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  10. ISSUE: line 477 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  11. ISSUE: line 489 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  12. ISSUE: line 609 character 6: Missing semicolon. - Evidence: }
  13. ISSUE: line 631 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  14. ISSUE: line 944 character 48: Missing semicolon. - Evidence: var title, date, object_history, source description, artist, lang, langParam, medium, dimensions, institution, notes, accession_number, quote, selection, work, publisher;
  15. ISSUE: line 970 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  16. ISSUE: line 994 character 20: 'i' is already defined. - Evidence: for (var i = details.length - 1; i >= 0; i--) {

Your CommonsMaintenanceBot (talk) at 22:05, 24 December 2017 (UTC).


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new esprima issue -- the page's status is now having ERRORS. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ERROR: Cannot parse line 944 column 43: Unexpected identifier

Your CommonsMaintenanceBot (talk) at 22:05, 24 December 2017 (UTC).


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 11 new jshint issues -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 424 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  7. ISSUE: line 467 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  8. ISSUE: line 475 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  9. ISSUE: line 476 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  10. ISSUE: line 477 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  11. ISSUE: line 489 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  12. ISSUE: line 609 character 6: Missing semicolon. - Evidence: }
  13. ISSUE: line 631 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  14. ISSUE: line 970 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  15. ISSUE: line 994 character 20: 'i' is already defined. - Evidence: for (var i = details.length - 1; i >= 0; i--) {
  16. ISSUE: line 1158 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1158 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1158 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  19. ISSUE: line 1158 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  20. ISSUE: line 1161 character 35: Missing semicolon. - Evidence: matches = regex.exec(date)
  21. ISSUE: line 1168 character 35: Missing semicolon. - Evidence: matches = regex.exec(date)
  22. ISSUE: line 1174 character 35: Missing semicolon. - Evidence: matches = regex.exec(date)
  23. ISSUE: line 1178 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  24. ISSUE: line 1178 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  25. ISSUE: line 1180 character 35: Missing semicolon. - Evidence: matches = regex.exec(date)
  26. ISSUE: line 1184 character 67: Missing semicolon. - Evidence: var unknown = ['Entstehungszeit unbekannt', 's.d.', 'unknown']

Your CommonsMaintenanceBot (talk) at 09:42, 25 December 2017 (UTC).

Recent VFC edits to make BBC Your Paintings fixEdit

1Veertje, thanks for your recent use of the VFC tool to fix a bunch of BBC Your Paintings links. I happened to notice that one of these VFC edits (see this edit to File:Unknown painter - Brig 'Jane Williamson' Entering the Bay of Naples.jpg) produced a malformed result. You may wish to do a quick review of the other files you edited with VFC in the same edit run to see if any more need a similar fix. Thanks again. —RP88 (talk) 00:12, 29 December 2017 (UTC)

it seems that links that didn't work before now do, AND vice versa. That's not quite what I had expected. First need to get some sleep though. There doesn't seem to be a pattern to which links fall in either category 🙀 Vera (talk) 02:05, 29 December 2017 (UTC)
btw, I've made a bookmarklet for ArtUK.org that puts all the meta data on their site in an {{artwork}} template. Vera (talk) 10:00, 29 December 2017 (UTC)


Code issues in User:1Veertje/ArworkRef-test.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef-test.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 18 new jshint issues -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 219 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 225 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 230 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 337 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 340 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 425 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  7. ISSUE: line 468 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  8. ISSUE: line 476 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  9. ISSUE: line 477 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  10. ISSUE: line 478 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  11. ISSUE: line 490 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  12. ISSUE: line 632 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  13. ISSUE: line 971 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  14. ISSUE: line 1160 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  15. ISSUE: line 1160 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  16. ISSUE: line 1160 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1160 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1180 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  19. ISSUE: line 1180 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');

Your CommonsMaintenanceBot (talk) at 16:05, 31 December 2017 (UTC).


Code issues in User:1Veertje/ArworkRef-test.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef-test.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 20 new jshint issues -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 13 character 2: Missing semicolon. - Evidence: a// v. 2017-11-10; en.wikipedia.org/wiki/User:V111P/js/WebRef
  2. ISSUE: line 231 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  3. ISSUE: line 237 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  4. ISSUE: line 242 character 14: Unnecessary semicolon. - Evidence: };
  5. ISSUE: line 349 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  6. ISSUE: line 352 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  7. ISSUE: line 437 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  8. ISSUE: line 480 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  9. ISSUE: line 488 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  10. ISSUE: line 489 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  11. ISSUE: line 490 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  12. ISSUE: line 502 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  13. ISSUE: line 644 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  14. ISSUE: line 983 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  15. ISSUE: line 1172 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  16. ISSUE: line 1172 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1172 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1172 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  19. ISSUE: line 1192 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  20. ISSUE: line 1192 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  21. ISSUE: line 1432 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  22. ISSUE: line 1438 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  23. ISSUE: line 1443 character 14: Unnecessary semicolon. - Evidence: };
  24. ISSUE: line 1550 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  25. ISSUE: line 1553 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  26. ISSUE: line 1638 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  27. ISSUE: line 1681 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  28. ISSUE: line 1689 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  29. ISSUE: line 1690 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  30. ISSUE: line 1691 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  31. ISSUE: line 1703 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  32. ISSUE: line 1845 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  33. ISSUE: line 2184 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  34. ISSUE: line 2373 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  35. ISSUE: line 2373 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  36. ISSUE: line 2373 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  37. ISSUE: line 2373 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  38. ISSUE: line 2393 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  39. ISSUE: line 2393 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');

Your CommonsMaintenanceBot (talk) at 16:13, 31 December 2017 (UTC).

AhemEdit

Hello. Just to let you know about this edit which removed a tag. I’ve fixed it. Green Giant (talk) 10:51, 2 January 2018 (UTC)

that's what you get when contributing to the Wikimedia projects: you do it right a hundred times and nobody remarks on your contributions. Do it wrong once and it gets noticed. Vera (talk) 13:22, 2 January 2018 (UTC)


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 416 character 35: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(\([A-Za-z ]+\))');
  7. ISSUE: line 416 character 47: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(\([A-Za-z ]+\))');
  8. ISSUE: line 443 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  9. ISSUE: line 486 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  10. ISSUE: line 494 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  11. ISSUE: line 495 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  12. ISSUE: line 496 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  13. ISSUE: line 508 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  14. ISSUE: line 650 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  15. ISSUE: line 989 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  16. ISSUE: line 1191 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1191 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1191 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  19. ISSUE: line 1191 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  20. ISSUE: line 1211 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  21. ISSUE: line 1211 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');

Your CommonsMaintenanceBot (talk) at 14:34, 2 January 2018 (UTC).


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 444 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  7. ISSUE: line 487 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  8. ISSUE: line 495 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  9. ISSUE: line 496 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  10. ISSUE: line 497 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  11. ISSUE: line 509 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  12. ISSUE: line 651 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  13. ISSUE: line 990 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  14. ISSUE: line 1192 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  15. ISSUE: line 1192 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  16. ISSUE: line 1192 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1192 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1212 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  19. ISSUE: line 1212 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  20. ISSUE: line 1222 character 46: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(.+?)(1[0-9])(th)?(C\.|C|Century)?');

Your CommonsMaintenanceBot (talk) at 15:47, 2 January 2018 (UTC).


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 444 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  7. ISSUE: line 487 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  8. ISSUE: line 495 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  9. ISSUE: line 496 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  10. ISSUE: line 497 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  11. ISSUE: line 509 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  12. ISSUE: line 651 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  13. ISSUE: line 990 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  14. ISSUE: line 1192 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  15. ISSUE: line 1192 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  16. ISSUE: line 1192 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1192 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1212 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  19. ISSUE: line 1212 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  20. ISSUE: line 1222 character 48: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(.+?)(1[0-9])(th)? ?(C\.|C|Century)?');

Your CommonsMaintenanceBot (talk) at 09:43, 3 January 2018 (UTC).


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 447 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  7. ISSUE: line 490 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  8. ISSUE: line 498 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  9. ISSUE: line 499 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  10. ISSUE: line 500 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  11. ISSUE: line 512 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  12. ISSUE: line 654 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  13. ISSUE: line 993 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  14. ISSUE: line 1183 character 35: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('([0-9\.,]+)');
  15. ISSUE: line 1195 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  16. ISSUE: line 1195 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1195 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1195 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  19. ISSUE: line 1215 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  20. ISSUE: line 1215 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  21. ISSUE: line 1225 character 74: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(.*)([^0-9]|^)(1[0-9])(\b|th)( ([cC]entury|[Cc])\.?)?(.*)?');

Your CommonsMaintenanceBot (talk) at 19:30, 7 January 2018 (UTC).


Code issues in User:1Veertje/common.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/common.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 70 character 1522: Bad or unnecessary escaping. - Evidence: window.vFC_Profiles = {"last executed (auto-saved)":{"editInputs":{"mdDeleteReason":"","mdEditSummary":"","mdReplacePermission":false,"mdDeleteHeading":"Files in [[:Category:Images from Art UK]] ","mdTalkNote":"Yours sincerely,","mdRRegEx1":true,"mdRVar1":true,"mdMatchText1":"/http:\\/\\/www\\.bbc\\.co\\.uk\\/arts\\/yourpaintings\\/paintings\\/(.+)/","mdReplaceText1":"{{BBCYourPaintings|$1}}","mdRRegEx2":false,"mdRVar2":true,"mdMatchText2":"","mdReplaceText2":"","selPreserve":"secure","alsoPreserve":""},"action":"c_replace","objectMembers":{"queryParams":{"target":"Category:Images from Art UK","cmdir":"asc","cmsort":"sortkey","cmstartsortkey":"","cmcontinue":"file|434841524c455320544f574e5348454e44204146544552205245594e4f4c44532e4a5047|49890231"},"startInput":{"mode":"Category","modeCat":true,"modeUser":false,"modePage":false,"modeSearch":false,"target":"Category:Images from Art UK","loadThumbs":true,"loadWikitext":true,"startDate":"","startFile":""}},"proceedAt":{"vals":["file|434841524c455320464f535445522042415248414d2042592048454e525920545245464652592044554e4e20313836302e4a5047|35172884","file|434841524c455320544f574e5348454e44204146544552205245594e4f4c44532e4a5047|49890231"],"setVals":["cmcontinue"]},"time":"2017-12-28T23:02:08.690Z"},"putting dimensions into size template":{"editInputs":{"mdDeleteReason":"","mdEditSummary":"putting dimensions into size template","mdReplacePermission":false,"mdDeleteHeading":"","mdTalkNote":"Yours sincerely,","mdRRegEx1":true,"mdRVar1":true,"mdMatchText1":"/\|dimensions ?= ?([0-9.]+) ?x ?([0-9.]+) ?(m|cm|mm|mi|in|ft|yd)/g","mdReplaceText1":"|dimensions = {{Size|unit = $3|width=$1 |height = $2}}","mdRRegEx2":false,"mdRVar2":true,"mdMatchText2":"","mdReplaceText2":"","selPreserve":"secure","alsoPreserve":""},"action":"c_replace","objectMembers":{"queryParams":{"target":"1Veertje","ledir":"older","lecontinue":"20180109110525|251304245"},"startInput":{"mode":"User","modeCat":false,"modeUser":true,"modePage":false,"modeSearch":false,"target":"1Veertje","loadThumbs":true,"loadWikitext":true,"startDate":"","startFile":""}},"proceedAt":{"vals":["20180109112124|251307548","20180109110525|251304245"],"setVals":["lecontinue"]},"time":"2018-01-10T16:15:32.778Z"}};

Your CommonsMaintenanceBot (talk) at 16:22, 10 January 2018 (UTC).


Code issues in User:1Veertje/ArworkRef-test.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef-test.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 447 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  7. ISSUE: line 490 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  8. ISSUE: line 498 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  9. ISSUE: line 499 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  10. ISSUE: line 500 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  11. ISSUE: line 512 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  12. ISSUE: line 654 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  13. ISSUE: line 993 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  14. ISSUE: line 1183 character 35: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('([0-9\.,]+)');
  15. ISSUE: line 1195 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  16. ISSUE: line 1195 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1195 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1195 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  19. ISSUE: line 1215 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  20. ISSUE: line 1215 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  21. ISSUE: line 1225 character 74: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(.*)([^0-9]|^)(1[0-9])(\b|th)( ([cC]entury|[Cc])\.?)?(.*)?');

Your CommonsMaintenanceBot (talk) at 14:24, 13 January 2018 (UTC).


Code issues in User:1Veertje/ArworkRef-test.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef-test.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 1 new jshint issue -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 458 character 12: Missing semicolon. - Evidence: "}"
  7. ISSUE: line 484 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  8. ISSUE: line 527 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  9. ISSUE: line 535 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  10. ISSUE: line 536 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  11. ISSUE: line 537 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  12. ISSUE: line 549 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  13. ISSUE: line 691 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  14. ISSUE: line 1030 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  15. ISSUE: line 1220 character 35: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('([0-9\.,]+)');
  16. ISSUE: line 1232 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  17. ISSUE: line 1232 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  18. ISSUE: line 1232 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  19. ISSUE: line 1232 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  20. ISSUE: line 1252 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  21. ISSUE: line 1252 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  22. ISSUE: line 1268 character 74: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(.*)([^0-9]|^)(1[0-9])(\b|th)( ([cC]entury|[Cc])\.?)?(.*)?');

Your CommonsMaintenanceBot (talk) at 15:29, 13 January 2018 (UTC).


Code issues in User:1Veertje/ArworkRef-test.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef-test.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 2 new jshint issues -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 458 character 12: Missing semicolon. - Evidence: "}"
  7. ISSUE: line 479 character 85: Missing semicolon. - Evidence: institution = institution + "|Institution:"+institution.split('The ')[1]
  8. ISSUE: line 508 character 12: Missing semicolon. - Evidence: "}"
  9. ISSUE: line 536 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  10. ISSUE: line 579 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  11. ISSUE: line 587 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  12. ISSUE: line 588 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  13. ISSUE: line 589 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  14. ISSUE: line 601 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  15. ISSUE: line 743 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  16. ISSUE: line 1082 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  17. ISSUE: line 1272 character 35: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('([0-9\.,]+)');
  18. ISSUE: line 1284 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  19. ISSUE: line 1284 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  20. ISSUE: line 1284 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  21. ISSUE: line 1284 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  22. ISSUE: line 1304 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  23. ISSUE: line 1304 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  24. ISSUE: line 1320 character 74: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(.*)([^0-9]|^)(1[0-9])(\b|th)( ([cC]entury|[Cc])\.?)?(.*)?');

Your CommonsMaintenanceBot (talk) at 21:50, 13 January 2018 (UTC).


Code issues in User:1Veertje/ArworkRef.jsEdit

Hi 1Veertje, I am a bored bot (this is kind of a computer program) that is watching the recent changes and tapping buttons like I did now.

Curious about the reason? Possibly not but I will tell you anyway:

  1. You edited User:1Veertje/ArworkRef.js. Glad to see you coding in javascript! Have you ever considered becoming a MediaWiki hacker?
  2. Though, that change appears to introduce 3 new jshint issues -- the page's status is now having warnings. Note that invalid or ambiguous code often has unwanted side effects like breaking other tools for you. If you cannot find out how to fix it, I suggest blanking the page for now.
  3. To help you understanding where the issues are, I have aggregated a report here and now. If you have questions, don't hesitate to ask users experienced in javascript writing for help. But do not ask the bot's operators (chronically overwrought) unless you suspect an error of mine. If you prefer not getting spammed by me, you can opt-out reports by adding {{ValidationOptOut|type=all}} to your user page. Good luck at Wikimedia Commons and happy hacking!
  1. ISSUE: line 218 character 43: Expected a conditional expression and instead saw an assignment. - Evidence: if (node = node.firstChild) do {
  2. ISSUE: line 224 character 49: Expected a conditional expression and instead saw an assignment. - Evidence: } while (node = node.nextSibling);
  3. ISSUE: line 229 character 14: Unnecessary semicolon. - Evidence: };
  4. ISSUE: line 336 character 33: ['lang'] is better written in dot notation. - Evidence: var lang = htmlEl[0]['lang'] || htmlEl[0]['xml:lang'];
  5. ISSUE: line 339 character 20: ['title'] is better written in dot notation. - Evidence: metaContent['title'] = document.title;
  6. ISSUE: line 457 character 12: Missing semicolon. - Evidence: "}"
  7. ISSUE: line 477 character 85: Missing semicolon. - Evidence: institution = institution + "|Institution:"+institution.split('The ')[1]
  8. ISSUE: line 505 character 12: Missing semicolon. - Evidence: "}"
  9. ISSUE: line 531 character 51: Use '===' to compare with ''. - Evidence: if (t.accessDate && t.dateFormatRetrieved == '')
  10. ISSUE: line 574 character 47: Missing semicolon. - Evidence: authorParamNames.push(t.first + n)
  11. ISSUE: line 582 character 20: 'n' is already defined. - Evidence: for (var n = 0; n <= 9; n++)
  12. ISSUE: line 583 character 53: Use '===' to compare with '0'. - Evidence: names += (val.match(strt + t.first + (n == 0 ? '' : n) + end) || ['', ''])[1] + ' '
  13. ISSUE: line 584 character 62: Use '===' to compare with '0'. - Evidence: + trimCollapse((val.match(strt + t.last + (n == 0 ? '' : n) + end) || ['', ''])[1]).replace(/ /g, '_') + ',';
  14. ISSUE: line 596 character 28: 'n' is already defined. - Evidence: for (var n = 0; n < authorParamNames.length; n++)
  15. ISSUE: line 738 character 87: ['copyFailed'] is better written in dot notation. - Evidence: if (copyFailed) this.parentNode.insertBefore(dom.textNode(msgs['copyFailed']), this.nextSibling);
  16. ISSUE: line 1077 character 40: Use '===' to compare with '0'. - Evidence: if (siteLang.search(/^en-US/i) == 0) siteLang = 'en-US';
  17. ISSUE: line 1268 character 35: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('([0-9\.,]+)');
  18. ISSUE: line 1280 character 33: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  19. ISSUE: line 1280 character 40: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  20. ISSUE: line 1280 character 65: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  21. ISSUE: line 1280 character 72: Bad or unnecessary escaping. - Evidence: var regex = new RegExp('(ca\.|um|c\.)? ?(1[0-9]{3}) ?. ?(ca\.|um|c\.)? ?(1[0-9]{3})');
  22. ISSUE: line 1300 character 29: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  23. ISSUE: line 1300 character 36: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(ca\.|um|c\.) ?(1[0-9]{3})');
  24. ISSUE: line 1316 character 74: Bad or unnecessary escaping. - Evidence: regex = new RegExp('(.*)([^0-9]|^)(1[0-9])(\b|th)( ([cC]entury|[Cc])\.?)?(.*)?');

Your CommonsMaintenanceBot (talk) at 22:20, 13 January 2018 (UTC).

Return to the user page of "1Veertje".