Article · Wikipedia archive · Last revised Jul 11, 2026

User talk:Zackmann08

Last revised
Jul 11, 2026
Read time
≈ 15 min
Length
3,556 w
Citations
Source
User:Zackmann08 User talk:Zackmann08 User:Zackmann08/Awards User:Zackmann08/Contacts User:Zackmann08/Notes User:Zackmann08/Templates User:Zackmann08/Wikipedia Bookmarks User:Zackmann08/sandbox
User Talk Awards Contacts Notes Templates/Tools Bookmarks My Sandbox

1,076,437+This user has made more than 1,076,437 contributions to Wikipedia.
This user is one of the 18 most active English Wikipedians of all time.

Simplify infobox code?

Hi, Zackmann. I noticed your edits to Infobox valley may be overly complex. The new code is

| image2      = {{#invoke:Location map|infobox_pushpin_map
   | pushpin_map = {{if empty|{{{map|}}}|{{{pushpin_map|}}}}}
   | pushpin_relief = {{if empty|{{{relief|}}}|{{{pushpin_relief|}}}|1}}
   | pushpin_label = {{if empty|{{{label|}}}|{{{pushpin_label|}}}|{{{name|}}} }}
   | pushpin_label_position = {{if empty|{{{label_position|}}}|{{{pushpin_label_position|}}}}}
   | coordinates = {{if empty|{{{coords|}}}|{{{coordinates|}}}}} 
}}

However, infobox_pushpin_map() calls getArgs() from Module:Arguments. By default, the frame argument is taken before the parent argument. This means you shouldn't need to pass in, e.g., |pushpin_map=. I think it is sufficient to have:

| image2      = {{#invoke:Location map|infobox_pushpin_map
   | pushpin_map = {{{map|}}}
   | pushpin_relief = {{if empty|{{{relief|}}}|{{{pushpin_relief|}}}|1}}
   | pushpin_label = {{if empty|{{{label|}}}|{{{pushpin_label|}}}|{{{name|}}} }}
   | pushpin_label_position = {{{label_position|}}}
   | coordinates = {{{coords|}}}
}}

because if the passed argument is empty, getArgs() will look to see if there is a non-empty parameter passed to Template:Infobox valley with the same name. You may wish to test this out in the sandbox. — hike395 (talk) 04:37, 2 July 2026 (UTC)[reply]

That is super good to know! I will test that out now. To be clear, the code is only temporary while the clean is underway... Pretty soon it will look MUCH cleaner, see this diff comparing the sandbox. But I really appreciate you pointing this out. Going to play around with it right now.
Also, if you have any suggestions for improvements to the new infobox_pushpin_map method, PLEASE share them. Either here directly or on the talk page for the module. Really looking for any feedback on it. Zackmann (Talk to me/What I been doing) 04:40, 2 July 2026 (UTC)[reply]
This will save me some time... Though now I have to make sure not to overlook things in my AddCheckForDeprecatedParameters which automatically pulls parameters from {{if empty}} statements... May stick to the same method I'm using for my own sanity, but in any event, I greatly appreciate you showing me this! Super good to know. Zackmann (Talk to me/What I been doing) 04:45, 2 July 2026 (UTC)[reply]

I've been getting pings from your edits at User:Zackmann08/sandbox. It's not surprising those don't work. User:Zackmann08/sandbox2 calls |pushpin_relief= which is always set to 1 (hence is always non-empty). Thus getArgs() never falls back to looking at how User:Zackmann08/sandbox sets |pushpin_relief=. — hike395 (talk) 04:57, 2 July 2026 (UTC)[reply]

AHHH!!! That makes total sense. I seem to remember that with Module:Infobox mapframe you can do that sort of logic where you set a default value (say for |mapframe-marker=car) in the Infobox but it can still be overridden in the transclusions. Guessing that uses different logic? Zackmann (Talk to me/What I been doing) 05:00, 2 July 2026 (UTC)[reply]
For example, don't get why Special:Diff/1362142173/1362143820 works then... As I said, I'm guessing that the logic for Infobox mapframe is just different? Zackmann (Talk to me/What I been doing) 05:03, 2 July 2026 (UTC)[reply]

It's the same logic (in Module:Arguments) --- to trigger it, User:Zackmann08/sandbox2 would have to be something like

{{Infobox
| image2  = {{#invoke:Location map|infobox_pushpin_map
   | pushpin_map = {{{map|}}}
   | pushpin_relief = {{{flooby_nooby|}}}
}}}}

and then User:Zackmann08/sandbox could either have

{{User:Zackmann08/sandbox2
| coordinates = {{coords|1|N|1|W}}
| pushpin_map = Africa
| pushpin_relief = 0
| mapframe = yes
| mapframe-marker = airport
}}

or

{{User:Zackmann08/sandbox2
| coordinates = {{coords|1|N|1|W}}
| pushpin_map = Africa
| flooby_nooby = 0
| mapframe = yes
| mapframe-marker = airport
}}

Note that the getArgs code doesn't let you specify a non-empty default argument (like "1"). It just lets you wire up an alternative argument without having to use {{if empty}}. If you want a default argument in the outer template, you still need {{if empty}} in User:Zackmann08/sandbox2:

{{Infobox
| image2  = {{#invoke:Location map|infobox_pushpin_map
   | pushpin_map = {{{map|}}}
   | pushpin_relief = {{if empty|{{{flooby_nooby|}}}|{{{pushpin_relief|}}}|1}}
}}}}

which is why I only changed two of the {{if empty}} in my original suggestion. — hike395 (talk) 12:56, 2 July 2026 (UTC)[reply]

Mahfiruz Hatun

Hi there, there is some issue In the article in Mahfiruz hatun, it shows that she died in 1610/1612. But prince Bayezid ( her son ) birth year was 1612, her another son prince hussein birth year was 1614-15, prince suleiman 1615. Her daughters princes geverhan, princess zeynep their birth year also indicates that Mahfiruz didn't died in 1610 or 1612. And eyup centre was the place where she was buried. The article shows that it was built by Osman the young in 1618. But before this version of "Mahfiruz hatun" article there was a link of eyup centre. Where they declared that it was built by Mahfiruz. Also about the name. Mahfiruz hatun was also known as Mahfiruz sultan. Source is Turkish Wikipedia, Ibrahim pecevi books. But it's also removed. As it's semi protected page. Edit war would be a bad thing. One user already got warning for that issue but still the war was going in last two days. So, I want to show it in ur concern. Have a good day. Habib hu 123 (talk) 12:29, 2 July 2026 (UTC)[reply]

Edit summaries

Hello, your recent JWB edits have a broken link in the edit summary, which you should probably fix. ([1]) a wondrous raven (talk) 17:43, 2 July 2026 (UTC)[reply]

Facepalm Facepalm THANK YOU!!!! Zackmann (Talk to me/What I been doing) 17:45, 2 July 2026 (UTC)[reply]

converts with hyphens

Hi, User:Zackmann08. Your recent infobox cleanups have introduced 3 area errors (I fixed one, have left the other two for now).

When it said something like "300-acre" you retained the hyphen, confusing the template.

Example: https://en.wikipedia.org/w/index.php?title=Fort_Dupont_Park&diff=1362560670&oldid=1355151685&variant=en

I think you edit by script a lot, so I figure bringing this to your attention beats silently cleaning up behind you.. though it does give me something to do! Polunbus (talk) 21:26, 4 July 2026 (UTC)[reply]

Well shit. That sucks. Really appreciate you catching these! Sorry about that. Zackmann (Talk to me/What I been doing) 23:22, 4 July 2026 (UTC)[reply]

Template:Infobox sailboat specifications

The deprecation code you did at [2] is completed, but that 2025 seems to not represent your current (better) style of underscores, so you might want to revisit it :) Gonnym (talk) 06:32, 5 July 2026 (UTC)[reply]

Oh for sure! It is on the loooonnngggg list! Zackmann (Talk to me/What I been doing) 15:03, 5 July 2026 (UTC)[reply]

Subst url template

Hi, I wanted to let you know that your User:Zackmann08/subst url template/script appeared to cause a few CS1 errors in reference 6 of Andasibe-Mantadia National Park. I'm not experienced in this sort of thing, but it may be because the url in question is dead. I went ahead and fixed the errors and added an archived copy. BlaqWiedow (talk) 02:21, 6 July 2026 (UTC)[reply]

That is so odd. I have no idea how that error slipped through. Really appreciate you both fixing it AND taking the time to notify me of the issue. Thank you! Zackmann (Talk to me/What I been doing) 02:41, 6 July 2026 (UTC)[reply]

Hobson's Choice (1920 film)

Why was Hobson's Choice (1920 film) reverted:? I just added an film infobox. Savolya (talk) 13:16, 6 July 2026 (UTC)[reply]

My edit summary clearly explained the issue as did the numerous warnings that have been placed on your talk page and that you have ignored. Zackmann (Talk to me/What I been doing) 15:53, 6 July 2026 (UTC)[reply]

Please slow down

I've noticed that you are doing a massive cleanup of many infobox templates. While that is very admirable, I think you need to slow down and be more careful. More specifically:

  1. You're putting a notice of cleanup on the Talk pages of the templates, then immediately removing parameters from articles. This is not giving enough time for any editors to object. As we've discussed before, I think you should wait the typical 7 days after giving notice before applying a broad fix to many articles. Editors could get angry that their voices are not being heard.
  2. I notice that you're applying some stylistic differences when you apply the cleanup, but those stylistic differences are not being described on the Talk page. I only noticed them when I went in the cleanup the code. For example, you have been setting |pushpin_relief=1 as default on {{Infobox park}} and {{Infobox forest}}, and have removed |default_width= and |max_width= from both of those infoboxes. There was no indication at either the Talk page or the edit summary of those style tweaks. When you do these massive deprecated parameter cleanups, I would strongly encourage you to stick to only the removal, and leave stylistic tweaks to a separate edit.

Thanks for all of your work! — hike395 (talk) 03:36, 7 July 2026 (UTC)[reply]

As always, I greatly appreciate your feedback. Always learn something from you.
  1. I think we need to remember that I am not "removing" anything... I am renaming parameters. I will again note that in cases where information is actually being removed from pages, those discussions take much longer ({{Infobox settlement}}, {{Infobox sportsperson}} and {{Infobox person}} all come to mind). Uncontroversial renaming of parameters to conform to MOS:INFOBOXNAME and other aspects of MOS I do not feel require 7 days of waiting for people to object to something that is stated in the MOS. That being said... I do think there are some cases where I have gotten overzealous. A return to focusing on JUST one thing at a time might be better. I do want you to understand, the double edged sword I have been faced with. I have had other editors actually take me to ANI for doing multiple passes on the same Infobox and crowding their watchlist with useless edits (direct quote). So I absolutely want to listen to your concerns, but at the same time, worry about pissing off people on the other side. No matter what, someone is always going to be unhappy. That being said, as always, I greatly appreciate your approach of coming here to seek discussion.
  2. The relief map was an oversight and a mistake. Appreciate you changing those back. While I have no objection to restoring the default width and max width code, you should be aware that what you restored, does not actually work or do anything... See Special:Permalink/1362950794 and Special:Diff/1362950650/1362950748. You will have to add those to the Module code around Module:Location_map#L-529... Which I have no objection to, but don't see a need for... Happy to help you there if you need it but frankly you are better with Lua code than I...
Again, thanks for the message! Not being passive aggressive or anything. I genuinely value your feedback. Looked over some of the fixes you did to some of the updates I made... I didn't know that {{If first display both}} was a thing. Will be adding that in the future. Also, if you want to look over the Infoboxes I have updated, the full list is at User:Zackmann08/pp.
Thanks! -- Zackmann (Talk to me/What I been doing) 04:20, 7 July 2026 (UTC)[reply]
You're making a good point that you're not removing functionality. When I look at WP:TPECON, the closest analogy I can see is The addition of new parameters, if they'll significantly change the template's usage or display. This includes adding numbered parameters as aliases for named parameters, adding additional numbered parameters to ones already in use under "Changes that require at least some discussion, or at least several days passing with no one commenting on your proposal". It's not exactly the same. I don't think this is Replacement of deprecated code or templates used within a given template, provided said deprecation is based on a prior consensus, because it changes the interface to the template.
I can't find the ANI notice about you crowding someone's watchlist. Yes, your edits are lighting up my watchlist, but it's easy to fix. I simply add "hide non-minor edits" to as a temporary extra filter and *boom*, problem solved. Not sure why this would require an admin.
There is code in Module:Location map to hanndle |default_width= and |max_width=: I checked before adding my comment. If it doesn't work, there may be a bug somewhere. I will take a closer look. Thanks for testing! — hike395 (talk) 11:53, 7 July 2026 (UTC)[reply]

There is a design flaw in the infobox_pushpin_map() as written: when the new code was added, it only handles parameters that are meant to be editor-specified (like |pushpin_mark_size=). It currently cannot handle "hidden" parameters (like |float= or |default_width=) that were never meant to be parameters of the outer infobox --- those are currently ignored. As written, those hidden parameters have to be fixed as constants (e.g., |float=center). There may be a way to hack around this problem, let me investigate. — hike395 (talk) 12:33, 7 July 2026 (UTC)[reply]

Fixed I made a kludge in infobox_pushpin_map() where I call getArgs() twice, once with frameOnly=true, once without. This allows us to grab |float=, |default_width=, etc. only from the actual module invocation, not exposing them as outer infobox parameters.
Unfortunately, there doesn't seem to be any test code for infobox_pushpin_map(), so I tested it in {{Infobox forest/sandbox}}.
I am a bit worried about parameters like |image_overlay=. Those may be currently used in infoboxes, but are now silently thrown away. — hike395 (talk) 13:10, 7 July 2026 (UTC)[reply]
Sorry just getting back online. Thanks for all your work on this. Question for ya though, since this new functionality is designed to just be used in the Infobox, is there a scenario where you would ever want |float= or |border= to be set as anything other than 'center' and 'infobox'? Those I intentionally hardcoded... The default and max widths I overlooked and love your solution there. Zackmann (Talk to me/What I been doing) 15:08, 7 July 2026 (UTC)[reply]
Hike just to follow up on a few other points.
  • Re the ANI and watchlist... I 100000% agree with your take, I'm just telling you the issues I've run into in the past and why I was doing things the way I was. Your point about hiding minor edits is completely valid and I agree. People are just.... difficult sometimes. That being said, you and I are in agreement. This DOES NOT require admin intervention, just saying I got taken to ANI because of it. Facepalm Facepalm
  • Re the |image_overlay=, I have so far done something like 75,000 pages as part of this cleanup and I have so far found a grand total of FOUR pages using an alternative image for the pushpin map. All four were using Israel's relief map, the exact one that could simply be obtained by using |pushpin_relief=1. For these, my workflow is such that any uses of alternative image will pop as unknown parameters in a way that gets my attention so I have to manually go in and fix them. If I find even one case where a legit alt map is being used, I will re-evaluate adding that functionality. Thus far, just haven't found the need to do so but no reason it cannot be added later if needed. When I finally get to {{Infobox settlement}}, that will be the real test. So we shall see!
Zackmann (Talk to me/What I been doing) 16:00, 7 July 2026 (UTC)[reply]

Infobox artwork

following your update to statue of Alan Turing, Bletchley Park, I thought "what on earth use is a pushpin map of Buckinghamshire? We need a mapframe zoomed at about 15 or 16 to show where it is in the park!" But mapframe is not supported in this infobox . Somebody forgot outdoor sculpture.

Would you add it to your long "to do" list, please? 𝕁𝕄𝔽 (talk) 19:59, 7 July 2026 (UTC)[reply]

It is supported... Zackmann (Talk to me/What I been doing) 20:00, 7 July 2026 (UTC)[reply]
i did mapframe-zoom= instead of mapframe_zoom= . My apoligies. 𝕁𝕄𝔽 (talk) 20:13, 7 July 2026 (UTC)[reply]
|mapframe-zoom= is correct (for now). But I bet you forgot to first set |mapframe=yes... Zackmann (Talk to me/What I been doing) 20:15, 7 July 2026 (UTC)[reply]
Also, don't be sorry, JUST DO IT RIGHT NEXT TIME! Zackmann (Talk to me/What I been doing) 20:16, 7 July 2026 (UTC)[reply]
No, didn't forget maprframe= , just kneejerked to this error message
  • Preview warning: Page using Template:Infobox artwork with unknown parameter "mapfrarme-zoom"'
either way...
  • 'Preview warning: Page using Template:Infobox artwork with unknown parameter "mapfrarme_zoom"'
Am I being especially dim? 𝕁𝕄𝔽 (talk) 20:30, 7 July 2026 (UTC)[reply]
read that again... SLOWLY... mapfrarme_zoom... Zackmann (Talk to me/What I been doing) 20:32, 7 July 2026 (UTC)[reply]
JMF you are not spelling the word "mapframe" correctly... You have spelled it "maprframe" and "mapfrarme"... Zackmann (Talk to me/What I been doing) 20:35, 7 July 2026 (UTC)[reply]
"Should have gone to Specsavers"
I don't even have the rn=m (RN=M) excuse. 𝕁𝕄𝔽 (talk) 20:38, 7 July 2026 (UTC)[reply]

Uh-oh...

Something's broken, friend; see here. What parameters are you removing/renaming? I'm glad to clean up (I'm seeing maybe 9 of these errors), but I can't tell what should go/stay. Jessicapierce (talk) 03:02, 8 July 2026 (UTC)[reply]

Facepalm Facepalm GRRRRRRRR. Aborting... Can you revert the errors? I borked something. As usual, thank you. Zackmann (Talk to me/What I been doing) 03:05, 8 July 2026 (UTC)[reply]
The GOAL was to merge the location parameters onto one line. Got on a roll and got complacent. Obviously logic wasn't as sound as I thought it was. Thanks for saving my behind as usual. Zackmann (Talk to me/What I been doing) 03:11, 8 July 2026 (UTC)[reply]
Ha, no worries, I got your back. It really was only ten or so, among your bazillion fixes. I bookmarked everything and will set them right. It's kind of fun - these are articles I never would have visited otherwise, so now I get to read about sedimentary rock! :) Jessicapierce (talk) 14:56, 8 July 2026 (UTC)[reply]
HA!! Well glad you appreciate it. Zackmann (Talk to me/What I been doing) 14:58, 8 July 2026 (UTC)[reply]
Got em! Jessicapierce (talk) 16:03, 8 July 2026 (UTC)[reply]

Personal attack

Hi I have been personaly attacked for giving my opinion per source. What should I do? Panam2014 (talk) 22:25, 8 July 2026 (UTC)[reply]

I would recommend WP:ANI. Zackmann (Talk to me/What I been doing) 01:51, 9 July 2026 (UTC)[reply]

Speedy deletion declined: Rodney Chapman

Hello Zackmann08. I am just letting you know that I declined the speedy deletion of Rodney Chapman, a page you tagged for speedy deletion, because of the following concern: Winning the first European Truck Racing Championship is a cresdible claim of importance. Use WP:AFD. Thank you. Whpq (talk) 22:00, 10 July 2026 (UTC)[reply]

Less gravedancing, please

Thanks. SarekOfVulcan (talk) 02:03, 11 July 2026 (UTC)[reply]

I know you're right. Just felt it was warranted given what a jerk they were being, and given that I was responding to their calling me a fucking clown. In any case, won't be going back to their talk page. Zackmann (Talk to me/What I been doing) 02:05, 11 July 2026 (UTC)[reply]

dcw2003

Dcw2003 (talk)dcw2003 You do not need to respond. But if you choose to, please be mindful that I have been reading your warnings and using Preview. Respectfully, I have been using Preview regularly and not ignoring your warnings. Your warning to Lauren Silver came while I was still writing to the Lauren Silver stub. The medaltemplates field had to be changed to medal_templates to fix the problem that was cited in the warning when I hit Preview. I didn't have time to read your message prior, as I was still working on Lauren Silver when I received your first message Please accept my apologies.

I've used Preview many times, and written around 15 water polo stubs since your last warning. You don't have to answer this response, but if you do I prefer you use patience and reflection. I've used the Preview key each time I've written additional text to the last 15 stubs, particularly if I make any changes to the infobox fields. I'm sorry they caused you disruption. Changing the infobox to sportsperson changes the medaltemplates field to require medal_templates with the underbar. Other than that, I've created very very few stubs that had parameter issues in the last three weeks, none that I didn't fix immediately, I believe. But I suppose I could be wrong.

Please consider this. I always add field parameters to stubs, because they frequently have few or none. I add college_team and coach, because they always lack these fields. I often have to add the position field and then fill it in as well. Sorry for the disruption. I'm not trying to cause you extra work. I did not delete your message on Lauren Silver, or was unaware that I had. If I had ignored your warning, I would not have known to fix the parameters as I did. I've done many stubs in the last two weeks, and tried to use the Preview key each time.