User talk:JJMC89/Archives/2017/January
![]() | 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. |
2015: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2016: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2017: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2018: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2019: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2020: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2021: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2022: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec 2023: Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec |
Happy New Year, JJMC89!
JJMC89,
Have a prosperous, productive and enjoyable New Year, and thanks for your contributions to Wikipedia.
SA 13 Bro (talk) 12:30, 1 January 2017 (UTC)
Send New Year cheer by adding {{subst:Happy New Year fireworks}} to user talk pages.
AFD for Bernhard Rosenberg
I am not a registered user and cannot complete the page, but I listed reasons on the article's talk page and on TALK:AFD about why this article should not exist. Could you please go through the process for me. 129.98.153.147 (talk) 23:54, 4 January 2017 (UTC)
- Thanks so much. 2604:2000:1304:402F:C8B1:F3F5:CF4:CE95 (talk) 05:20, 5 January 2017 (UTC)
A thank you post
I appreciate your help with the go templates I created today. Thank you. --Wesalius (talk) 20:44, 5 January 2017 (UTC)
I'm not sure you made the right call here. I wouldn't want this to be used as a precedent for blocking users when, in my opinion, there is not a clear consensus to disallow the name. Beeblebrox (talk) 02:20, 6 January 2017 (UTC)
- @Beeblebrox: I've change the close to just note that the account appears to be abandoned. If you feel that is insufficient, feel free to revert my close entirely. — JJMC89 03:31, 6 January 2017 (UTC)
- Looks good to me, thanks for reconsidering. Beeblebrox (talk) 04:05, 6 January 2017 (UTC)
Coordinate conversion problem
Hi, sorry for late report of problem but I am catching-up from the Christmas break. In this change the bot appears to have left in the parameters |coordinates format=
, |coordinates display=
and |iso region=
in the Infobox. It also appears to have changed the display option away from that which is specified in the |coordinates display=
parameter and completely ignored the |iso region=
parameter which is missing from the {{coord}} template. Regards
Keith D (talk) 22:51, 6 January 2017 (UTC)
- The configuration had underscores instead of spaces in the parameter names (fixed), so they were completely ignored. I will work through the ones with issues and correct them. — JJMC89 00:21, 7 January 2017 (UTC)
- Thanks for quick response. Keith D (talk) 01:50, 7 January 2017 (UTC)
- Done. If you see any outstanding issues, please let me know. — JJMC89 04:39, 7 January 2017 (UTC)
- Thanks for quick response. Keith D (talk) 01:50, 7 January 2017 (UTC)
Mass reverts
Please hold up on these and let's talk? Paine Ellsworth u/c 02:41, 8 January 2017 (UTC)
- Sure. All the ones that I reverted pointed to non-existent talk pages. Without reverting or creating the target pages, they would be deleted. — JJMC89 02:46, 8 January 2017 (UTC)
- Thank you! When I looked at your first revert, it has been placed back into Category:Unsynchronized talk page redirects. Talk page redirects should target the talk pages of their subject pages' targets. I'm trying to empty that category. If that means targeting a non-existent talk page, then the talk page redirect should be deleted. If any of your other reverts have unsynchronized the talk page redirects, could you please self revert? Paine Ellsworth u/c 02:54, 8 January 2017 (UTC)
- I think they all did, so I've reverted them all. — JJMC89 03:13, 8 January 2017 (UTC)
- Again, thank you! Paine Ellsworth u/c 03:17, 8 January 2017 (UTC)
- I think they all did, so I've reverted them all. — JJMC89 03:13, 8 January 2017 (UTC)
- Thank you! When I looked at your first revert, it has been placed back into Category:Unsynchronized talk page redirects. Talk page redirects should target the talk pages of their subject pages' targets. I'm trying to empty that category. If that means targeting a non-existent talk page, then the talk page redirect should be deleted. If any of your other reverts have unsynchronized the talk page redirects, could you please self revert? Paine Ellsworth u/c 02:54, 8 January 2017 (UTC)
Bot problem
In this edt your bot correctly changes lat/long to {{coord}}, in {{infobox country}}, but sets the type to city instead of the obvious and more appropriate country. I’ve corrected that particular instance of it but don’t know if there’s a wider issue.--JohnBlackburnewordsdeeds 23:20, 8 January 2017 (UTC)
- @JohnBlackburne: The coordinates are for the country's capital, not the country itself. — JJMC89 23:32, 8 January 2017 (UTC)
- Ah, you are right. I was confusing them with the coordinates that appear at the top of the article, as I assumed that’s what they did, as the 'coordinates' in 'infobox country'. I had not noticed the ones associated with the capital. Still seems odd it works like that, but I follow it now.--JohnBlackburnewordsdeeds 00:00, 9 January 2017 (UTC)
Checkuser template change
Hey, apparently your change impacted a script I use. The script puts a strike through a user's name if the user is blocked. It's still working in other places, e.g., my watchlist, but at SPI it doesn't work on the checkuser template. If you can fix the template so the strike-through works again and it doesn't ping the user, great. Otherwise, the strike-through is more important to me than eliminating the notification. Thanks.--Bbb23 (talk) 15:42, 8 January 2017 (UTC)
- @Bbb23: The change prevents pinging and the strikethrough. (They both work based on a wikilink to the userpage.) The talk and contribs links in the template should still have the strikethrough though. If those links having strikethrough is not sufficient, I will revert the change. — JJMC89 18:41, 8 January 2017 (UTC)
- I noticed the talk and contribs links strike-throughs. It's not as prominent (I often move quickly), though, and it's (a) different from what I'm used to and (b) different from the other pages. Let me think on it a bit, and I'll let you know. Thanks for all your help.--Bbb23 (talk) 18:45, 8 January 2017 (UTC)
- Hi again. I've decided I prefer it the way it was. Please revert your change. Sorry for all the trouble.--Bbb23 (talk) 00:15, 9 January 2017 (UTC)
- Undone No worries, Bbb23. — JJMC89 00:20, 9 January 2017 (UTC)
- Hi again. I've decided I prefer it the way it was. Please revert your change. Sorry for all the trouble.--Bbb23 (talk) 00:15, 9 January 2017 (UTC)
- I noticed the talk and contribs links strike-throughs. It's not as prominent (I often move quickly), though, and it's (a) different from what I'm used to and (b) different from the other pages. Let me think on it a bit, and I'll let you know. Thanks for all your help.--Bbb23 (talk) 18:45, 8 January 2017 (UTC)
CFB North Bay Page
Good day. I'm replying to your question about copyright of the photograph of the F.3 flying boat, on the Red River, Manitoba, in October 1920. The image is from the Canadian federal government (specifically the Department of National Defence archives), therefore in accordance with the Canadian 50 year rule on government photographs the image no longer has a copyright, is in the public domain. Thanks. 22WHERO (talk) 19:46, 17 January 2017 (UTC)
- @22WHERO: Could you point to where I asked about the photo's copyright? I haven't edited CFB North Bay (edit | talk | history | links | watch | logs) or your talk page. — JJMC89 20:06, 17 January 2017 (UTC)
- My bad. It was another address. I'd transcribed your address from your revision of the page's update on 3:03 12 Jan 2017 and the address of the intended recipient, who sent the query to me, on the same notepad. I'll ensure to pay better attention in the future. Cheers. 22WHERO (talk) 20:26, 17 January 2017 (UTC)
Geobox
I added support for |coordinates=
, |capital_coordinates=
, |highest_coordinates=
, |lowest_coordinates=
, |source_coordinates=
, |source1_coordinates=
, |source2_coordinates=
, |source_confluence_coordinates=
, |management_coordinates=
, and |government_coordinates=
to {{geobox}} (search the geobox code for coord= to find them all). the core code is in {{geobox2 coor}} which is called by {{geobox}}. when converting transclusions to the new format, |display=inline,title
should be added to the coordinates passed through |coordinates=
, if it exists, otherwise added to |mouth_coordinates=
, otherwise added to |capital_coordinates=
. however, if |coordinates_no_title=
is non-empty, then |display=inline,title
should be added to none of them. the {{geobox2 coor}} template uses {{geobox2 coor type}} to determine the region: and type: for the coordinates. I may need to tweak the insert code in {{geobox2 coor}} if there is a problem with how the default and override works. let me know if you see any problems. Frietjes (talk) 15:47, 20 January 2017 (UTC)
Template:Infobox Municipality PT
You just took the latd/longd parameters out of Template:Infobox Municipality PT, but the articles have not been converted yet. Did you mean to edit Template:Infobox Municipality BR instead? – Jonesey95 (talk) 05:36, 25 January 2017 (UTC)
- Yes, I did. Reverted for now. Thanks, Jonesey95! — JJMC89 05:43, 25 January 2017 (UTC)
- No trouble. You, Frietjes, and I have made a pretty good team on this coordinates project, cleaning up each other's edits and keeping things moving. – Jonesey95 (talk) 06:11, 25 January 2017 (UTC)
Minor bot error in coord template
Sorry to be the bearer of bad news. Take a look at this output from the bot. type:region:IT_type:city(24230)
is not right. I think I see how it happened, but regardless, it's an error. I don't know how many edits made it through like this, but there is an error report of all coord syntax errors available. I'll try to make you a list from that report. – Jonesey95 (talk) 06:01, 26 January 2017 (UTC)
- Here's a list, sorted in a way that made sense to me. I imagine you have the tools to do text processing on this list, but if not, let me know if you want the list of articles in a different way. I removed a bunch of articles from the report to make this list, narrowing down to only the "too many colons" errors. I suspect that all, or nearly all, of the errors are the result of the bot's edits, based on the type of error and the types of articles. – Jonesey95 (talk) 06:06, 26 January 2017 (UTC)
- I noticed that. It is due to
|coodinates_type=
being mapped to {{geobox coor}}'s|9=
instead of|type=
, as the name suggests. ({{geobox coor/sandbox.*}}
's|type=
addstype:
.|coordinates_parameters=
would have been a better name.) I still need to fix some of the bot configs after double checking the infoboxes. () I'll write a script or bot to fix the effected pages and maybe some of the other problems in that report. — JJMC89 17:17, 26 January 2017 (UTC)- Sounds good. The very low number of complaints we have received so far is evidence that the bot is doing great work. The minor problems have typically been quirks in the individual templates that we needed to adjust or account for, rather than problems with the bot. Keep it up.
- It will be nice to get these settlement articles behind us, but I think we have at least another month of bot edits before we are done (max 10,000 edits per day on something over 200,000 articles, I think). – Jonesey95 (talk) 20:22, 26 January 2017 (UTC)
- I noticed that. It is due to
Afc List
Hey, So Mainspace edits are the only ones counted? Best Regards Shawrix (talk) 09:27, 28 January 2017 (UTC)
- Yes. — JJMC89 09:28, 28 January 2017 (UTC)
- Thanks for the information. I'll keep that in mind. Shawrix (talk) 09:32, 28 January 2017 (UTC)
- But I couldn't edit the page before 500 total edits, does that indicate something? sorry for the talkback. Shawrix (talk) 09:35, 28 January 2017 (UTC)
- It means that you are WP:EXTENDEDCONFIRMED (able to edit WP:ECP pages), which is not related to AfC qualifications. — JJMC89 09:42, 28 January 2017 (UTC)
The Original Barnstar | |
Thanks for all the info! Shawrix (talk) 10:33, 28 January 2017 (UTC) |
Thank you!
Hello JJMC89 (talk), thanks for editing the Denver Broncos' colors at Template:NFLPrimaryColor and Template:NFLTertiaryColorRaw for me! I really appreciate it! Charlesaaronthompson (talk) 00:22, 29 January 2017 (UTC)
Thanks for fixing my broken links. I had just noticed them when you beat me to it. Meters (talk) 01:11, 29 January 2017 (UTC)
- No problem. You beat me to filing the report. — JJMC89 01:17, 29 January 2017 (UTC)
Your BRFA
Your BRFA, Wikipedia:Bots/Requests for approval/JJMC89 bot 8 has been approved. Happy editing, — xaosflux Talk 04:55, 29 January 2017 (UTC)
Small bot issue
Not a big problem but on Turgon, Charente, Chemillé-Melay and Bussac-Forêt the bot introduced errors, as {{coord}} seems a little stricter about coordinates than bare values when there's no leading zero in a decimal value less than one. It might be something you could add to the bot, as a further check. I imagine it could happen again with locations close to the Greenwich Meridian.--JohnBlackburnewordsdeeds 17:26, 29 January 2017 (UTC)
- @Frietjes and Jc86035: Could you take a look at Module:Coordinates and/or Module:Location map and adjust to allow for no leading 0 before a decimal place. Location map gives a Lua error when the leading 0 is missing (example). — JJMC89 21:12, 29 January 2017 (UTC)
- It looks like the problem lies in Module:Coordinates (or in the coord2text thereof), based on this test in my sandbox. I hacked the module's sandbox with possibly unintended side effects, and it was able to extract numbers for me. – Jonesey95 (talk) 23:21, 29 January 2017 (UTC)
- I was almost right just above. The coord2text function is replicated in Location map. Here's the result of me implementing the same coord2text hack in the Location map sandbox. – Jonesey95 (talk) 23:33, 29 January 2017 (UTC)
- Jonesey95, I simplified the expressions in the sandbox, now they say "any sequence of digits and decimal points followed by the degree marker". I believe the '%.' means a literal . instead of any character in lua patterns, but '\.' probably works too if it was working for you. if we have something that works now, I think we can go forward and update the main modules. note that I added the same function to geobox map, but I believe those are the only modules. Frietjes (talk) 15:02, 30 January 2017 (UTC)
- I told you mine was a hack. I don't know Lua. So who will be bold enough to move this fix to the main template? I find it hard to believe that Module:Coordinates is only template-protected, which means it is not safe from dummies like me. – Jonesey95 (talk) 16:08, 30 January 2017 (UTC)
- @Jonesey95 and Frietjes: I've merged the change into both modules. — JJMC89 16:40, 30 January 2017 (UTC)
- I told you mine was a hack. I don't know Lua. So who will be bold enough to move this fix to the main template? I find it hard to believe that Module:Coordinates is only template-protected, which means it is not safe from dummies like me. – Jonesey95 (talk) 16:08, 30 January 2017 (UTC)
- Jonesey95, I simplified the expressions in the sandbox, now they say "any sequence of digits and decimal points followed by the degree marker". I believe the '%.' means a literal . instead of any character in lua patterns, but '\.' probably works too if it was working for you. if we have something that works now, I think we can go forward and update the main modules. note that I added the same function to geobox map, but I believe those are the only modules. Frietjes (talk) 15:02, 30 January 2017 (UTC)
- I was almost right just above. The coord2text function is replicated in Location map. Here's the result of me implementing the same coord2text hack in the Location map sandbox. – Jonesey95 (talk) 23:33, 29 January 2017 (UTC)
- It looks like the problem lies in Module:Coordinates (or in the coord2text thereof), based on this test in my sandbox. I hacked the module's sandbox with possibly unintended side effects, and it was able to extract numbers for me. – Jonesey95 (talk) 23:21, 29 January 2017 (UTC)