Wikipedia talk:Lua

From Wikipedia, the free encyclopedia
  (Redirected from Wikipedia:Lua requests)
Jump to navigation Jump to search
 WP:Lua
Project
 WT:Lua
Project talk
 Help
 
 To do
 
 Resources
en: m: mw: external
 

Request Lua module for removing/striping leading zeros[edit]

Hello there! I am not familiar with Lua, but I would like to invoke a module for Template:SEHK to remove all leading zeros. This is needed as the template uses the numerical stock code inputted and replaces the value inside the stock exchange URL. The problem is that SEHK tickers are often reported in the English media with leading zeros (making it up to 4 digits, such as "0001" rather than just "1") The current stock website does not support leading zeros, hence redirecting to an error site. I was wondering if anyone here experienced with Lua can help with this issue? It has been affecting a wide range of Hong Kong stock exchange-listed articles. Cheers –Wefk423 (talk) 18:49, 26 July 2018 (UTC)

It's easy enough to write a module to use the Lua function tonumber(), but it's probably simpler to use the magic word {{#expr: }}. For example, {{#expr:0001}} gives 1. HTH --RexxS (talk) 19:09, 26 July 2018 (UTC)
Expr seems really reasonable considering the other alternative of Module:String#Replace (finding regex 00+ and replacing with nothing). Template:Trim exists. Expr emits an NAN if the input is bad, no? --Izno (talk) 19:26, 26 July 2018 (UTC)
Thanks for the suggestion. I have added the magic word {{#expr: }} to the template to resolve the error webpage issue for now. But I do think that such module (with usage tutorial) can be created as other templates might also need to strip leading zeros. It seems like a fast and easy way, especially for users who don't know how to use magic words. –Wefk423 (talk) 19:35, 26 July 2018 (UTC)
(edit conflict) It throws an error for me: {{#expr:ABCD}}Expression error: Unrecognized word "abcd".
If you want to control the errors, then a Lua module starts to become attractive:
p = {}
p.stripzeros = function(frame)
	x = tonumber(frame.args[1])
	if x then
		return x
	else
		return "whatever you want to indicate NaN"
	end
end
return p
Usage: {{#invoke:Modulename |stripzeros |number-goes-here}}HTH. --RexxS (talk) 19:40, 26 July 2018 (UTC)
Thank you so much for the great suggestion on customizing the error message by using this Lua module. It is currently live at Module:Leading zeros and has also been implemented in Template:SEHK. Way much better than the red bold message which will look terrible in a infobox. When inputting a non-numeric value, it will now appear as "SEHK: Incorrect". How do you think? Cheers! –Wefk423 (talk) 00:21, 27 July 2018 (UTC)
@Wefk423: That seems to do the job for you. If you re-use the module in other applications, you can trap the error word "Incorrect" with an {{#ifeq: }} test in the template, which will allow you to take different actions when the input is not a number.
One other thing (in your documentation): I would encourage everyone not to use <br> to separate items in a list (see MOS:NOBR. Using {{ubl}}, especially in an infobox, is much better because it creates a real list that is much more useful for screen readers. Cheers --RexxS (talk) 09:33, 27 July 2018 (UTC)
@RexxS: I'm sorry I don't really catch that. Which documentation are you refering to? I don't seem to find any list. Nevermind, I found it! I've edited the documentation of the template here. Thanks and cheers –Wefk423 (talk) 16:32, 27 July 2018 (UTC)
  • Another way to strip leading 0's in a string: {{#invoke:String|match|000123450|^0+(.*)}} -- Matroc (talk) 08:31, 12 September 2018 (UTC)
and of course, the original suggestion by RexxS, using #expr is still valid, and prolly the simplest... handling errors is no biggy - just enclose in #iferror, like so (presuming the thing you want to strip is in param 1):{{#iferror:{{#expr:{{{1}}} }}| <your "non-numeric" error message here> | {{#expr:{{{1}}} }} }} - peace - קיפודנחש (aka kipod) (talk) 15:26, 12 September 2018 (UTC)

Module:Leading zeros has been nominated for deletion. {{3x|p}}ery (talk) 14:09, 8 October 2018 (UTC)

Improving Template:Code[edit]

I'm wondering if it's feasible to re-do {{code}}, a wrapper for <syntaxhighlight>, in such a way that some parameter, perhaps |filter=y, could pre-filter and convert some of the input before it reaches the underlying <syntaxhighlight> process. [Inserting a code snippet for example purposes below: <span>.]

  • The issue: Sometimes it is not desirable to feed this template something literal. E.g., if you do {{code|lang=html|1=<span style="color: purple;">}} (without the closing tag for the span), then anyone using the edit-mode wikimarkup syntax highlighter by Remember_the_dot, available at Special:Preferences#mw-prefsection-gadgets and thus our most frequently used highlighter, will have their syntax highlighting in the editing window boogered by what Remember_the_dot's syntax highlighter sees as a real open and not-yet-closed <span> rather than as template content. [If you use that highlighter, and are reading this in edit mode, you should see this effect now, caused by the snippet I inserted before this bullet list. Most of my entire post should have a pink background as unclosed code content when it really is not.]
    • And one cannot escape this with &lt; to encode the exmaple span's leading < symbol; all input received by <syntaxhighlight> is treated as a literal.
    • This also makes it impossible to do something like {{code|lang=html|1=<span '''style'''="color: purple;">}} to emphasize something in the markup.
  • The idea: Use Lua and a table of entities and of select wikimarkup to pre-filter (and possibly post-filter) the content before (and maybe after) it hits <syntaxhighlight>:
    • Pre-filter so that things like < can be escaped in the visible wikitext with &lt;, converted to <, then passed to the parser function.
    • Possibly also tokenize a few things like ''...'' and '''...''' markup so they can be operated on after the fact:
    • Post-filter to de-tokenize those bits and actually perform their intent. Ideally this would also include <var>...</var> so that variables within code can be marked up as such (lack of ability to do that is a serious flaw in <syntaxhighlight>).

 — SMcCandlish ¢ 😼  22:12, 1 August 2018 (UTC)

@SMcCandlish: Unfortunately, post-filtering is impossible as the output from <syntaxhighlight> is not exposed to lua other than as an opaque strip marker. Pre-filtering could be done trivially using Module:String and/or Module:MultiReplace without creating a new lua module. {{3x|p}}ery (talk) 11:31, 18 September 2018 (UTC)
Correction: Post-filtering is not technically impossible, only impossible to do without relying heavily on undocumented implementation details of the SyntaxHighlight extension, which seems like it's not a good idea to do for such a heavily used template. {{3x|p}}ery (talk) 22:22, 18 September 2018 (UTC)
I should have known better than to call something impossible. {{3x|p}}ery (talk) 22:25, 18 September 2018 (UTC)
@Pppery: Well, what I suggested was that "some parameter, perhaps |filter=y, could pre-filter", so it sounds like you're telling me that the problem I'm reporting is in fact easily fixable.  — SMcCandlish ¢ 😼  11:10, 8 November 2018 (UTC)

Can Lua be used to parse a section of one page, change the contents and be transcluded on another page?[edit]

Hi there. I'm not familiar with Lua at all, so please forgive me if this sounds obvious. I recently noticed that {{WPVG announcements}} is manually updated by a number of dedicated editors to reflect changes from WP:GAN#VG, which basically means translating the values from the {{GANentry}} templates at WP:GAN#VG to the {{ganl}} templates used in {{WPVG announcements}}. Would it be possible for a Lua script to parse the content of the former section, reassign the values to a different template and display those for inclusion in the announcements-template? That way, editors wouldn't have to manually update the template anymore and it'd be always up-to-date. Regards SoWhy 07:44, 10 September 2018 (UTC)

Although Lua can read the content of a page using the getContent() method from the title library and can write text to a page, Lua scripts are run when a page is rendered, so somebody would have to trigger the script by previewing an edit or something similar to do the update. The kind of job you're envisaging is most commonly done by a bot, often running a Python script. I recommend putting in a request at Wikipedia:Bot requests where you can get feedback and suggestions on how best to get the results you want. --RexxS (talk) 18:21, 10 September 2018 (UTC)
You could probably also do something like this by managing a JSON file or a Lua table, but that's not very wiki-textish. --Izno (talk) 19:04, 10 September 2018 (UTC)
wiki syntax now allows segment transclusing, (explained in Help:Labeled section transclusion and probably in other places also). you could use this to create labeled section in the "source" page, and pass the transclusions are parameters to a template that would then do the conversions. this would make the source page a bit more cumbersome to edit, introducing all the "section begin/section end" tags, but i think it can do what you want. the "conversion template" can use scribunto, or not - it may not be necessary if the conversion code is simple enough. i believe that doing so will solve the issue RexxS mentioned: changes to the "source" page should be reflected automagically in the target page. peace - קיפודנחש (aka kipod) (talk) 21:29, 10 September 2018 (UTC)
@קיפודנחש: Unfortunately, since WP:GAN is managed by a bot, making changes to it is not possible because it will likely break the bot. Since the bot already updates that page, I thought these updates could be translated to {{WPVG announcements}} as described. The latter template is used on tens of thousands of talk pages (any talk that uses {{WPVG}} in fact), so I assumed the template will be updated often anyway. I'll ask whether a bot could do it instead. Thanks for the replies! Regards SoWhy 09:00, 11 September 2018 (UTC)

───────────────────────── @SoWhy: Incorrect. What is requested here is possible, and in fact relatively easy to implement: I implemented it in Template:WPVG announcements/sandbox. In exactly the same way as pages update when the pages they transclude update, the list will automatically update whenever new good articles are nominated. {{3x|p}}ery (talk) 23:02, 17 September 2018 (UTC)

@Pppery: Wow, nice work. Thanks! I'll ask if someone has objections to implementing this at WT:VG. Regards SoWhy 06:58, 18 September 2018 (UTC)

Lua error[edit]

Hello everyone, Who can tell me how can i fix this error at ckbwiki? Tap the red text, you will see something. Thank you.ئارام بکر (talk) 21:07, 19 September 2018 (UTC)

One of lang:formatDate( 'U', nil, true ) or inputTime in:
local timeDiff = lang:formatDate( 'U', nil, true ) - inputTime
is a string and needs to be a number. You might try, as a first fix:
local timeDiff = tonumber(lang:formatDate( 'U', nil, true )) - tonumber(inputTime)
But, were I you, I would translate your local wiki language date/time inputs to their English equivalents before doing any operation on those date/time values and then at the end translate the English result back to your local language. My experience is that Lua and formatDate() don't handle non-English language date names and non-western digits well. Internationalization isn't as easy as one might wish it were.
Trappist the monk (talk) 21:49, 19 September 2018 (UTC)

Help with calling String.replace[edit]

Hello, I'm new to Lua and trying to create a module (Module:Sandbox/Gonnym/Episode disambiguation description) that takes an article title and returns a formatted style depending on how the article title is written. However, I'm not able to get one String function to work - String.replace - it's not even getting colored green like the other functions I'm using. What I'm trying to do with it, is what Template:PAGENAMEBASE does. I would really appreciate any help (and any other comments) on this. Thank you. --Gonnym (talk) 13:18, 20 September 2018 (UTC)

review the documentation on string.match()
Trappist the monk (talk) 14:16, 20 September 2018 (UTC)

Timeout on specific settings[edit]

I'm in the process of creating a module that can take either 3 or 4 params and produces a short description with those params. When I give it the first 3 params (episode, season and tv series) it works. I've checked it with around 20 calls running on the same page and they all worked fine. When I give it all 4 params (which includes the 4th "yes" param) it times out. I tried debugging it and sent the 3 params again, but made the system act as if the 4th one was sent (just set it manually to true) and it worked for the first 2 calls and timed-out for the others. So code-wise there isn't an error crashing it and the code isn't really long or complex, so I pretty much ran out of ideas what is causing this. Would appreciate if anyone could have a look at it - Module:Sandbox/Gonnym/Episode short discription (ignore the typo in title). --Gonnym (talk) 13:59, 22 September 2018 (UTC)

line 37; function calls itself.
Trappist the monk (talk) 14:42, 22 September 2018 (UTC)
Thanks Trappist! --Gonnym (talk) 16:50, 22 September 2018 (UTC)
Ok, I fixed it and it worked for a while but I'm getting this timeout again. If I enter the 3 value option of "23|1|somename" I it works, but if I add the 4th param it fails. So {{User:Gonnym/sandbox/Test|23|1|Lost}} works, while {{User:Gonnym/sandbox/Test|23|1|Lost|y}} doesn't. --Gonnym (talk) 17:34, 22 September 2018 (UTC)
the solution is at lines 33 & 35.
Trappist the monk (talk) 18:01, 22 September 2018 (UTC)
Thanks again! No idea why that would cause a timeout though. Redundant? probably, but it didn't seem breaking. --Gonnym (talk) 18:12, 22 September 2018 (UTC)
when first episode is 23 and second episode is 24 the number of interest is 4. you were testing number < 4 and number > 4 but not testing number == 4. the if-then-else tests, not knowing what to do with 4, just kept the while looping round and round and round ...
Trappist the monk (talk) 18:49, 22 September 2018 (UTC)
Totally missed that I forgot to do >=4, thanks again! --Gonnym (talk) 19:55, 22 September 2018 (UTC)

Accessing a page's short description (inside infobox) from another page[edit]

Hello again. I was trying to access the short description information from an article that uses an auto-generated short description created inside the infobox template used on that page, and use that on a different page. So, "Page A" uses "Template:Infobox x" that has code that generates a short description with Template:Short description. In "Page B", I want to access that data. I tried using Template:Extract short description to access that data, which does indeed work, however, that has a side-effect that since it transcludes the page, it also adds things that should not be there, such as FA/GA ratings and warnings such as Warning: Display title <article name> was ignored since it is not equivalent to the page's actual title. There might be other issues that also come from this. Since this method does not work, I was wondering if anyone can think of another way to access it. --Gonnym (talk) 21:29, 26 September 2018 (UTC)

If you know the name of the article you might use a variant of this:
=string.match (mw.title.new ('Abraham Lincoln'):getContent(), '{{ *short +description *| *([^}]+) *}}')
For the article Abraham Lincoln, the above, executed from the debug console returns:
16th President of the United States
But, caveat here, too many uses of this kind of trick in a single article will cause Lua timeouts.
Trappist the monk (talk) 21:51, 26 September 2018 (UTC)
That would still be regarded as a transclusion. Using getContent for a couple of small uses might be ok but it's not viable for routine use. Using it on Abraham Lincoln worked easily because that article has {{short description}} in the wikitext. Using it at Athens which auto-generates the description would be a lot more challenging. Johnuniq (talk) 01:34, 27 September 2018 (UTC)
I'm thinking maybe there is way to make it work with a workaround with Template:Template parameter value, by adding a silent field to an infobox template and calling it, but so far I couldn't get it to work. Not sure how to pass the short description data to that field. --Gonnym (talk) 06:42, 27 September 2018 (UTC)

───────At Athens the infobox generates "City in Central Greece, Greece" as the short description. Previewing the following extract from the infobox is enough to reproduce that.

{{Infobox settlement
| settlement_type      = [[Cities of Greece|City]]
| subdivision_type     = Country
| subdivision_name     = [[Greece]]
| subdivision_type1    = [[Geographic regions of Greece|Geographic region]]
| subdivision_name1    = [[Central Greece]]
| subdivision_type2    = [[Administrative regions of Greece|Administrative region]]
| subdivision_name2    = [[Attica (region)|Attica]]
| subdivision_type3    = [[Regional units of Greece|Regional unit]]
| subdivision_name3    = [[Central Athens (regional unit)|Central Athens]]
}}

There is no parameter with the description so {{Template parameter value}} cannot help. You would need to reproduce the calculations performed by {{Infobox settlement}}—calculations that might be changed at any time and which would not apply for other infoboxes. Alternatively, you would need to expand the infobox then somehow extract the description from the resulting mess. In principle that would be easy because the wanted text appears in:

<div class="shortdescription nomobile noexcerpt noprint searchaux" style="display:none">City in Central Greece, Greece</div>

What is the purpose? There is no viable way to do the required complex operations in a manner that would be reasonable for generating text in another article. Johnuniq (talk) 07:34, 27 September 2018 (UTC)

I know that there currently is no parameter with the description. What I'm asking is if after the the description was generated on the first line at {{Infobox settlement}}, can it then be added to a new |description = param (which won't visually show up in the infobox), and then be accessed with {{Template parameter value}}? (currently testing this it seems it's not possible as I'm getting the error Lua error in Module:Template_parameter_value at line 43: bad argument #1 to 'gsub' (string expected, got nil).) --Gonnym (talk) 10:02, 27 September 2018 (UTC)
Clearly a bug exists in Module:Template parameter value. Pinging the module's author.
|short_description={{Short description/test}} is inside {{infobox}} which is inside {{Infobox television episode/sandbox}}. Module:Template parameter value uses the same trick that I suggested with my Abraham Lincoln example: it read's the article's wiki source. If you can't see |short_description={{Short description/test}} in the article wiki source, then Module:Template parameter value won't be able to see it either.
So how about this. Extract the infobox template from the article source (not necessarily an easy task because of nested templates – left as an exercise for the reader). Then call the syntaxhighlight parser function with the infobox wikitext as the argument:
{{#invoke:Sandbox/trappist the monk/tag|tag|{{Infobox television episode/sandbox
| title          = test
| series =
| season         = 5
| series_no      = 
| multi_episodes = y
| episode        = 
}}}}
which returns:
<div class="shortdescription nomobile noexcerpt noprint searchaux" style="display:none">A television episode</div>[[Category:project pages with short description]]<table class="infobox vevent" style="width:22em"><tr><th colspan="2" class="summary" style="text-align:center;font-size:125%;font-weight:bold;font-weight: normal; background: #CCCCFF; padding: 0.25em 1em; line-height: normal;">"'''test'''"</th></tr><tr><th scope="row" style="white-space: nowrap">Episode <abbr    title="numbers">nos.</abbr></th><td>Season&nbsp;5<br /></td></tr></table>
from which you can get your short description.
Trappist the monk (talk) 12:45, 27 September 2018 (UTC)
To be honest, I'd suggest using JavaScript rather than Lua at present for this sort of job because it can access the API to read the generated descriptions directly. That avoids all of the messing about.
Looking forward, I know there are obvious security concerns for Scribunto, but I think it might be worth making a case for asking for the API (or part of it, maybe 'read-only') to be exposed to Scribunto, so we could read something like https://en.wikipedia.org/w/api.php?action=query&prop=description&titles=Alan_Turing as a Lua object. That would make a lot of jobs much more feasible if we could make a proper case for it. --RexxS (talk) 13:53, 27 September 2018 (UTC)
That does indeed make it much more easier. Is it possible for JavaScript and a Lua module to pass data to one another? Is there some sort of documentation I can read that someone can point me to? I don't know JS but maybe I'll be able to understand how to make it work. --Gonnym (talk) 14:16, 27 September 2018 (UTC)
Javascript runs on the reader's browser, does it not? So whatever js script you might write has to somehow be made available to every reader who reads any page that would need that js script which means, I think, that the js script must be made part of whatever js MediaWiki includes with every page rendering.
I do not know of any connection between Lua and js – they operate at different times; Lua modules are processed (by the MediaWiki servers) when you save or refresh a page, js is processed (by your browser) when you view the rendered (cached) page.
Trappist the monk (talk) 14:54, 27 September 2018 (UTC)
If a user needs to install something then that isn't a viable idea, so its back to try and find the pattern to find the infobox in the article text. --Gonnym (talk) 15:29, 27 September 2018 (UTC)
I believe the idea is to put it in MediaWiki:Common.js which is loaded for all pages. Frietjes (talk) 16:01, 27 September 2018 (UTC)
If you know the name of the infobox (ibox_name) then once you have the Wikisource (content):
local ibox_start = string.find (content, '{{%s*' .. ibox_name)</code>		-- find the start of {{Infobox ...; ibox_name is a pattern that accepts various legit spacing and capitalization ...
local ibox_text = string.match (content, '%b{}', ibox_start)				-- ibox_start points to first { of the infobox template
Trappist the monk (talk) 16:37, 27 September 2018 (UTC)
Did we solve the transcluding issue with "mw.title.new ('Abraham Lincoln'):getContent()" or was there another way to get the wikisource that I missed? --Gonnym (talk) 17:12, 27 September 2018 (UTC)
Perhaps. You will notice that I added a {{DISPLAYTITLE}} directive to your User:Gonnym/sandbox/tests2. Here, we fetch the {{Infobox television episode/sandbox}} template from your test page's wiki source, stir, and pour out this:
{{#invoke:Sandbox/trappist the monk/tag2|tag|User:Gonnym/sandbox/tests2}}
Script error: No such module "Sandbox/trappist the monk/tag2".
From that you can get the short description. I do not get any display title warning messages when I preview this page.
Trappist the monk (talk) 18:25, 27 September 2018 (UTC)
I tried it with an article from my previous tests which I got an error with before and I still get it with this code - The End (Lost). It currently does not have a short description (but not sure that has any impact on the error). Might have to do with articles that are disambiguated. --Gonnym (talk) 08:16, 28 September 2018 (UTC)
What did you try? What were the steps? What error did you get? Where can I see this error without my having to do the sleuthing work to noodle it out?
Trappist the monk (talk) 08:45, 28 September 2018 (UTC)
Sorry for being unclear. I just changed the article name to the title I mentioned {{#invoke:Sandbox/trappist the monk/tag2|tag|The End (Lost)}} and the error being the one previously stated Warning: Display title "User:Gonnym/sandbox/tests2" was ignored since it is not equivalent to the page's actual title. --Gonnym (talk) 09:56, 28 September 2018 (UTC) Seems I had unused code that caused that. Bug not part of your code. --Gonnym (talk) 09:58, 28 September 2018 (UTC)
I've ran into an issue. The output from your code encloses the tag in <pre></pre> which causes the pattern to fail to match. If I remove the tag it works. I'm assuming this somehow causes the code to stop treating it as plain text. I tried using string.replace to replace the "pre" tag, but that didn't work. Any ideas? (pattern template can be found {User:Gonnym/sandbox/tests1) --Gonnym (talk) 11:31, 28 September 2018 (UTC)
I've tweaked tag2 so that it returns the shortdescription text:
{{#invoke:Sandbox/trappist the monk/tag2|tag|User:Gonnym/sandbox/tests2}}
Script error: No such module "Sandbox/trappist the monk/tag2".
Trappist the monk (talk) 13:22, 28 September 2018 (UTC)
As always, you are a star! Thank you very much! :) --Gonnym (talk) 15:53, 28 September 2018 (UTC)

I've now noticed that the output of {{#invoke:Sandbox/trappist the monk/tag2|tag|User:Gonnym/sandbox/tests2}} is incorrect (it shows on that page "4th episode of the fifth season of lost", while the result from the invoke shows "A television episode"). It's showing the default description in case there is no data filled in the infobox. Maybe using | short_description = {{Short description/test}} in the infobox didn't work? --Gonnym (talk) 23:00, 28 September 2018 (UTC)

These parameters are getting to tag2:
| title = test | series = lost | season = 5 | series_no = | multi_episodes = | episode = 4
but aren't coming out of frame:expandTemplate(). Probably just need to massage the parameters a bit before passing them to frame:expandTemplate(). I'll do some experimenting tomorrow.
Trappist the monk (talk) 00:52, 29 September 2018 (UTC)
{{#invoke:Sandbox/trappist the monk/tag2|extract_short_description|User:Gonnym/sandbox/tests2|infobox television episode/sandbox}}Script error: No such module "Sandbox/trappist the monk/tag2".
Trappist the monk (talk) 11:28, 29 September 2018 (UTC)
Amazing! Thanks again! --Gonnym (talk) 11:31, 29 September 2018 (UTC)
On my sandbox page I have an {{infobox television episode/sandbox}} that has |series={{lang|de|lost}}. I did that because editors will assign templated values to infobox parameters:
{{#invoke:Sandbox/trappist the monk/tag2|extract_short_description|User:trappist the monk/sandbox|infobox television episode/sandbox}}Script error: No such module "Sandbox/trappist the monk/tag2".
Float your mouse-pointer over lost in the rendering above and you should get a 'German language text' tooltip. Editors will also wikilink infobox parameters. If I write |episode=[[44]] in the infobox, I get 'An episode of the forty-fifth season of lost'. I don't know what the rules are (if there are any) for short description text, but if wiki markup and templated data are acceptable then perhaps your module should accept wikilinked values for |episode=, |season=, and |series_no=? Or, perhaps, the infobox and its documentation should be modified to prohibit wikilinking of these parameters.
|short_description={{Short description/test}} in {{infobox television episode/sandbox}} is not required, right?
Trappist the monk (talk) 12:15, 29 September 2018 (UTC)
Per Wikipedia:Short description#Content, nothing in the description should be linked. Per the specific MoS guidelines in my case, those entries should also not be wikilinked. I'm ok with them failing as that means someone will fix a much larger issue first, but good find. I want to see how exactly it fails so nothing breaks. And yes, that isn't needed if your code doesn't use it. That was me trying to find a way to access the data. --Gonnym (talk) 12:25, 29 September 2018 (UTC)
Well, doubled-checked and one param can actually be wikilinked and pipped, so thanks for raising that issue! --Gonnym (talk) 16:55, 29 September 2018 (UTC)

Overhead from a generally unused code path[edit]

Wikisaurus has added a "subst only" code path for generating the list of parameters from a template to the Russian version of Module:Check for unknown parameters (see the generate function in ru:Модуль:Check for unknown parameters). I added this to Module:Check for unknown parameters/sandbox, which seems fine since it's an entirely different code path. but, then I started wondering if there is any significant overhead from having this rarely used code path in the module? would it be better to put it in "Module:Check for unknown parameters/generate" or is there no substantial difference in terms of overhead? thank you. Frietjes (talk) 12:47, 27 September 2018 (UTC)

Beyond the amount of time and resources required to read the extra 844 bytes that you added to the module, I would be surprised if there were any noticeable execution time difference between a 1000 iterations of the live module vs the sandbox module. That is an experiment that you can try; use the parser profiling data for comparison.
Trappist the monk (talk) 13:34, 27 September 2018 (UTC)

Overload Template:Bicolor (Commons)[edit]

Can someone please convert c:Template:Bicolor into a module? PS: I mean this would be a perfect reason for conversion. The idea of optimizing is also to omit ifexists with an existing color table. User: Perhelion 11:15, 5 October 2018 (UTC)

This is being discussed at c:Template talk:Bicolor. No good method. Johnuniq (talk) 00:42, 6 October 2018 (UTC)
@Johnuniq what do you mean? The discussion comes from here...
 Done User: Perhelion 18:05, 10 October 2018 (UTC)
I suspect that John meant that all of the solutions available suffer from some issue, such as expensive calls or size of rendered text, that makes them less than ideal in his (and in my) opinion. We have a solution of sorts, but I'm not 100% satisfied with it. Cheers --RexxS (talk) 18:43, 10 October 2018 (UTC)
That's right although my "no good method" comment was before I had seen your clever solution. I think a bot would be needed to handle more combinations. Johnuniq (talk) 02:55, 11 October 2018 (UTC)

Pages where template include size is exceeded[edit]

to remove Émerson Leão from Category:Pages where template include size is exceeded I created {{navboxes top}} and {{navboxes bottom}}. the implementation is definitely a hack, but could be improved by adding new functionality to Module:navbox. I don't think the problem is being caused by the tracking because {{navboxes/sandbox}} has no appended tracking and shows the same issue in preview. does anyone have any other ideas for addressing the problem, or is the top/bottom approach the only way? Frietjes (talk) 15:48, 11 October 2018 (UTC)

Fix the root problem, which is Sports Navboxes in general? :) --Izno (talk) 16:50, 11 October 2018 (UTC)
Frietjes may remember {{Football manager history}} which I refactored to use Module:Football manager history two years ago. Some preliminary discussion was here. I remember some other discussion was pretty indifferent about the module because quite a few participants felt that the enormous navboxes were way over the top and should be removed rather than fixed. The module drastically reduces the template expansion size because it processes everything once only. In the old system, nested template calls meant that each resulting line was counted three or four times because it was passed from template to template. Possibly the same approach would fix templates like {{Brazil squad 1970 FIFA World Cup}} which uses {{National squad}} which uses {{navbox}}. It might be straight forward based on the existing module, or looking at the details might show a bunch of work would be needed. Johnuniq (talk) 06:57, 12 October 2018 (UTC)
Johnuniq, good suggestion. that fixed the problem for United States men's national soccer team, but did not fix Émerson Leão and Belgium national football team. unless there is another one that can be reduced in size, I am considering refactoring Template:Navboxes to use {{#invoke:navboxes|top}} and {{#invoke:navboxes|bottom}}. the hack in Module:navboxes could be improved, but this would fix the problem for those two articles (and probably many others). Frietjes (talk) 15:06, 12 October 2018 (UTC)

Module:Infobox[edit]

I'm trying to understand Module:Infobox and see if the code there allows another infobox module to send it values and for it to return the required sub-infobox, but since it lacks in documentation, I can't seem to figure this out (it seems me that it doesn't support what I want). What I'm looking for is something similar to what fr.wiki has with fr:Module: Infobox. If anyone can help me figure this out, would really appreciate this. --Gonnym (talk) 13:04, 23 October 2018 (UTC)

Are you talking about embedding one infobox inside another?
Trappist the monk (talk) 13:12, 23 October 2018 (UTC)
No. What I'm trying to do (which is available in the french version) is to create a very small infobox module (in terms of code) which only lists the parameters it gets from a user (fr:Module:Infobox/Tapis persan), which then sends it to the main module (Module:Infobox), which it is responsible for actually building it. Basically eliminating all the code currently in the infobox templates. --Gonnym (talk) 13:19, 23 October 2018 (UTC)
As we currently have far more active editors familiar with template syntax than with Lua code, is it a good idea at present to shift so much of the development and maintenance of infoboxes onto a much smaller group? --RexxS (talk) 13:59, 23 October 2018 (UTC)
That is neither my call nor my intention, but I also don't believe that not testing better options just because not enough people can add to it, is correct either. Also, the french example I've linked to seems much easier to code than any infobox I've seen, including the need to keep that awful numbering system which forces you to change so many lines, if you need to add a new row somewhere at the top. --Gonnym (talk) 14:13, 23 October 2018 (UTC)
You may find User:Frietjes/infoboxgap.js useful in dealing with that awful numbering system. --RexxS (talk) 14:39, 23 October 2018 (UTC)
@Gonnym: As far as I'm aware the module is currently inaccessible from other Lua modules (the p.infobox function only accepts values from a frame object), although Mr. Stradivarius might be able to say otherwise. You might want to fiddle a bit with the p.infobox function in a sandbox to see how it'll let you input data from another module.
Parts of enwiki also have a weird thing for discouraging any more Lua modules than absolutely necessary because most editors can only read wikicode and therefore can't debug modules, although I do think the frwiki approach would have benefits for some templates like {{Singles}} (which already uses its own Lua module). Jc86035 (talk) 15:21, 24 October 2018 (UTC)
@Jc86035: I don't believe it will let me, but no harm in playing a bit with it. Also, I don't understand how anyone can read this code Template:Infobox album (the part before the actual start of the infobox code) and even more think that it's easier to read than Lua. --Gonnym (talk) 18:10, 24 October 2018 (UTC)
@Gonnym: My fault, because I wrote that part of the template. Most of the reason it's so complicated is because I was trying to replace and format about seven different templates' parameters by allowing their replacement through template substitution (example) and for some reason I thought it would be a good idea to do the formatting with parser functions and Module:String. If you take out the part between |prev_title= and |$flags=override (the part that formats the parameters) then it starts to look a little more like it was written by a normal sensible person. Jc86035 (talk) 18:18, 24 October 2018 (UTC)

───────────────────────── It's generally not too difficult to make Scribunto functions available to other modules. If you want to make p.somefunc(frame) available in a simple form, you can check what is used from the frame object, say frame.args.param1 and frame.args.param2, then amend the function definition be to something like function p._somefunc(param1, param2), and use param1 and param2 in place of frame.args.param1 and frame.args.param2 within the function. Finally write

function p.somefunct(frame)
    return p._somefunc(frame.args.param1, frame.args.param2)
end

to recreate the function that uses the frame object for use with #invoke. The _somefunc(param1, param2) will be available from require("Modulename")

There are alternative ways, for example passing a single table of parameters instead of each one individually (useful when there are lots of parameters), but the general principle is the same. --RexxS (talk) 22:05, 24 October 2018 (UTC)

Yes, that will work with a bit of moving around the meat of that function into the _function, but from what I can tell from the code, the infobox is eventually still waiting for values in the form of how an infobox template keeps them, and not in an easy to code FR style. --Gonnym (talk) 22:19, 24 October 2018 (UTC)

Navbox with collapsible groups[edit]

can someone help me debug Module:Navbox with collapsible groups which is being called through Template:Navbox with collapsible groups/sandbox? in particular, see Template:Navbox with collapsible groups/testcases. for debugging, I have appended the values of the 'sargs' which are used to build the subgroups, and I appended the values of 'targs' which is passed through Navbox._navbox to build the final result. the values for the sargs and the targs look great, but the actual navbox output has the academics group repeated 4 times :( I have never seen this pathology before. thank you! Frietjes (talk) 16:27, 24 October 2018 (UTC)

update, this edit appears to fix the problem. so, going through the template interface for the child boxes, instead of going through the module interface. I think it would be better to go through the module interface, and I have no idea why that doesn't work. Frietjes (talk) 21:05, 24 October 2018 (UTC)
I started looking at this but then I saw you were still working on it. Please post again if there is something specific I could look at. Johnuniq (talk) 04:15, 25 October 2018 (UTC)
Johnuniq, I found the problem in Module:Navbox, listnums was being initialized globally, but not emptied at the top of _navbox(), so each time you call the _navbox() it just appends more lists to listnums. it looks like this fixes the problem. I don't see any other entry points into the module, other than p.navbox(frame) and p._navbox(navboxArgs) so it looks like it is safe to initialize listnums at the top of p._navbox(navboxArgs) instead. Frietjes (talk) 13:20, 25 October 2018 (UTC)
That looks good. I vaguely remember some oddities about the module from the time I jumped into it. I would prefer to get rid of those effectively global variables at the top of the module but the refactoring effort might not be worth it. Johnuniq (talk) 09:33, 26 October 2018 (UTC)

teach Module:Graph some new tricks[edit]

background (long story - safe to skip): back in 2013, i created Module:Chart, to display bar and pie charts.

my motivation was mainly to make adding charts easier: the various charting templates that existed were limited (e.g., pie chart had max of 6 slices), none support "stacked" bar charts, and more importantly, they all used cumbersome (IMO) and inconvenient way of passing parameters: instead of, e.g., delimited list of numbers for each series, you had to pass a separate parameter for each data point, with different convention for each template. (there's a whole slew of other charts, using the "timeline" extension - those are even more difficult to use, and produce ugly charts, IMO).

(irrelevant, but interesting tidbit): this module uses an arcane and esoteric feature of html to display pie charts (which i copied from the brilliant template that already existed), exploiting the "border" element, giving it width and colors, and using the fact that 2 sides of html "border" are connected with a "bevel": by separately controlling the width of each side, you control the angle of the bevel, then you color one of the sides with he desired color, leave the other transparent, repeat for each segment of the pie, stacked on top of each other, do it separately for each of the 4 quarters of the axis system, and finish it all by covering the whole jumble with a circle, having transparent interior and white exterior. bizarre to the point perversion, and at the same time brilliant. the most amazing thing about it is the fact that it actually works...

relevant part

anywhoo, several years later, the "graph" extension was introduced (mw:Extension:Graph), and some time later, User:Mps created Module:Graph (maybe elsewhere (dewiki?), and imported to enwiki - not sure). some time after that, Template:Graph:Chart was created. at this point, my 2013 "chart" module became obsolete, but people are still using it.

so here is (finally) my actual request: there are some legit requests on Module talk:Chart, to which i usually respond "you should use the new stuff". the latest such request, asked for horizontal bar chart, which neither module supports. i have no doubt the "graph" extension can easily do it, but unfortunately, Module:Graph does not provide horizontal bar charts. can someone pick the challenge, and teach this module to draw horizontal bar charts? and, maybe, while you are at it, also teach it to do scatter chart?

peace - קיפודנחש (aka kipod) (talk) 16:55, 25 October 2018 (UTC)

Module error on Syrian Civil War map[edit]

I've noted what seems to be a strange bug on the module maps at Talk:Cities and towns during the Syrian Civil War#Some sort of module error causing extra marks. If someone who has more experience with module programming and such could take a look, that'd be great. (This was originally posted on VPT, but someone pointed out in an unrelated section that this is usually where Module questions are asked.) Thanks, ansh666 21:22, 4 November 2018 (UTC)

The above was posted at 00:45, 6 November 2018 and it looks as if the issue has been resolved according to the latest at the above talk link. Johnuniq (talk) 02:43, 6 November 2018 (UTC)

How do you look up which pages are directly calling given module?[edit]

I am looking for ways of tracking which pages directly call some module, in case I am altering the module interface. For example I have some Module:X intended to be accessed through Template:X and I would like to check if any other templates, modules or other pages call it. Special:WhatLinksHere with namespace filter is great but it is swamped by 'indirect calls through template. One can compare Special:WhatLinksHere for Module:X and Template:X and look for the differences, but that also mostly has pages which are there for unexplained reason. I only want to find pages with "{{#invoke:X|Y" so maybe I should write SQL query to look for that in page text? Or is there an easier way? --Jarekt (talk) 17:39, 7 November 2018 (UTC)

Enter insource:"invoke:X" in the search box. Click "Everything" to find results in all namespaces. PrimeHunter (talk) 17:52, 7 November 2018 (UTC)
(edit conflict) @Jarekt: If I go to Special:Search, then pick the namespaces and search for something like insource:/invoke:\s*WikidataIB/, I can find the pages that invoke WikidataIB. You'll probably be able to adapt that for what you need. Cheers --RexxS (talk) 18:04, 7 November 2018 (UTC)
insource:/.../ is an expensive regex search which shouldn't be used alone per mw:Help:CirrusSearch#Insource. A normal insource: search works fine here unless the module name often occurs after the word "invoke" in normal English text. PrimeHunter (talk) 18:16, 7 November 2018 (UTC)
As you don't know whether there are space characters between "invoke:" and the module name, your search will miss those. You need a regex to find all of them in one search. As usual, the documentation on mediawiki is a long way from realistic, and these sort of simple searches execute rapidly without problems.
If you feel you have to use a search domain to use the regex on, then something like insource:"WikidataIB" insource:/invoke:\s*WikidataIB/ will do the job almost instantly. --RexxS (talk) 19:11, 7 November 2018 (UTC)
I prefer to limit it to "hastemplate:"Module:X" insource:/invoke:\s*X/". --Izno (talk) 19:13, 7 November 2018 (UTC)
insource:"invoke:X" also finds cases with spaces and it's simple. PrimeHunter (talk) 00:21, 8 November 2018 (UTC)
You're absolutely right and I was wrong: your search works. The colon character is treated as greyspace, so of course it will also match invoke X, etc. But as you say, that's almost certainly not going to be a common expression in prose (unless you write a module called "BRD"). Cheers --RexxS (talk) 01:40, 8 November 2018 (UTC)

Thanks all for your help! --Jarekt (talk) 19:27, 7 November 2018 (UTC)

Knowing if being called from a disambiguation page[edit]

If a template/module needs to know if it is being invoked from a disambiguation page (without user input), is searching the page for the {{Disambiguation}} template (and redirects) the way to go, or is there another way? --Gonnym (talk) 23:54, 7 November 2018 (UTC)

It's pretty ugly, but searching the page content is all that's possible, I think. That's what I did at c:Module:Countries in function getRedirectTarget. It seems to be pretty fast. It was pointed out to me that I missed a few infrequently used redirects/templates but I thought targeting the main ones was good enough. Johnuniq (talk) 00:09, 8 November 2018 (UTC)
Thanks for the answer and for the code reference! --Gonnym (talk) 12:12, 8 November 2018 (UTC)
Doesn't mw.title.getCurrentTitle().isRedirect give you that answer?
Trappist the monk (talk) 13:05, 8 November 2018 (UTC)
Tested it out and no. It makes sense as redirect is not the same as disambiguation I guess. --Gonnym (talk) 13:33, 8 November 2018 (UTC)
Doh! brain fart. nevermind.
Trappist the monk (talk) 14:06, 8 November 2018 (UTC)
Wikipedia does know which pages are disambiguation pages though. It doesn't look like there is a method exposed in the Lua api but that would be a pretty reasonable request for Phabricator. --Izno (talk) 17:38, 8 November 2018 (UTC)

How can one track module dependencies[edit]

I am wandering is there some way of tracking module dependencies. Let me give an example, on commons we have c:Module:Fallback which according to Special:MostTranscludedPages is used on 44M pages, including many other modules like my c:Module:Artwork or RexxS' c:Module:WikidataIB. c:Module:Fallback implements mostly retired language fallback mechanism and should not be part of many of other Modules, so I am curious how those dependencies sneak in. Is there some tool or approach to track it down? --Jarekt (talk) 21:40, 8 November 2018 (UTC)

You might try this kind of search in the module namespace:
insource:/require *\( *["']module:fallback["']/i[1]
Trappist the monk (talk) 12:32, 9 November 2018 (UTC)
@Jarekt: Following up from PrimeHunter's tip above, searching for insource:"require module fallback" finds them plus a couple of extras like module:fallback/sandbox. There are few enough of those to manually pick the ones that interest you. --RexxS (talk) 13:37, 9 November 2018 (UTC)
c:Module:Fallback is used by couple abandon and unused modules and by subtemplates of c:Module:Wikidata (used on 2M pages), so 44M uses is a mistery as I can not find templates that use it either. --Jarekt (talk) 03:58, 18 November 2018 (UTC)

Validating date parameter is in a Template:Start date[edit]

I have a template which the documentation asks for the date parameter to be in a {{Start date}} template. The template code is in the template namespace and is not a module. I'm trying to add a tracking cat to it in the situations where the date is not in that format. I've tried using {{Str sub find}} and also invoking String.find directly, but can't get this to work. This fails either because of the "|" character, which I can escape in the static target value with {{!}}, but I'm not sure how to handle the user-entered value; or it fails because of the template itself. Alternatively, if there is a better option, I'm open to that as well.

Example code:

  • {{#if: {{str sub find|1={{start date|1993|02|24}}|2={{start date|}} }} | Substring is found | Substring is not found }} -> Substring is not found --Gonnym (talk) 10:34, 12 November 2018 (UTC)
I don't know if this would help (I have not investigated your issue), but {{extract}} can parse dates. Problem: It checks the date for validity and people often make mistakes such as 31 April so the result might cause clutter.
  • {{extract|show=format}} → error
  • {{extract|2001|2|28|show=format}} → dmy
  • {{extract|Feb 28, 2001|show=format}} → mdy
  • {{extract|2001|2|29|show=format}} → error
Johnuniq (talk) 22:10, 12 November 2018 (UTC)
This might work, but I'm running into issues with it:
  • {{start date|1993|02|24}} → February 24, 1993 (1993-02-24)
  • {{extract|1993|02|24|show=mdy}} → February 24, 1993
  • {{extract|{{start date|1993|02|24}}|show=mdy}} → Error: Need valid date
Any idea? This might be because {{Start date}} "also includes duplicate, machine-readable date (or date-time) in the ISO date format (which is hidden by CSS), for use inside other templates (or table rows) which emit microformats". --Gonnym (talk) 12:18, 13 November 2018 (UTC)
Also, I'm not sure this would really solve my issue, as it will accept correctly formatted dates, but not those using the template, which is a requirement. --Gonnym (talk) 12:22, 13 November 2018 (UTC)
Your problem rests on the fact that the parser will expand the template {{Start date}} before passing its value to your template. Perhaps something like this will be usable:
  • {{Posnq | {{start date|2018|November|30}} | bday dtstart published updated }} → 75
  • {{Posnq | 30 November 2018 | bday dtstart published updated }}
  • {{Posnq | {{start date|2018|November|31}} | bday dtstart published updated }} → 75
  • {{Posnq | 31 November 2018 | bday dtstart published updated }}
That accepts invalid dates as well, but still discriminates between having a template that has those microformats and one that doesn't. Obviously, you pass {{{date|}}} as the first parameter. --RexxS (talk) 14:24, 13 November 2018 (UTC)
Just to help check: Let's say you were looking for the parameter |airdate= in Template:Infobox television episode. You could search all articles on:
  • insource:"Infobox television episode" insource:"airdate" to find 9,240 occurrences; then on:
  • insource:"Infobox television episode" insource:"airdate" insource:/| *airdate *= *\{\{[Ss]tart date/ to find 3,775 that have the {{start date}} template; and on:
  • insource:"Infobox television episode" insource:"airdate" insource:/| *airdate *= *[^{ ]/ to find 5,674 that don't have a template.
  • insource:"Infobox television episode" insource:"airdate" insource:/| *airdate *= *[1-9A-Za-z]/ shows 5,648 articles. --RexxS (talk) 16:14, 13 November 2018 (UTC)
I always like to point out that insource:"name of template" is more fragile compared to hastemplate:"Infobox television episode", which catches all transclusions (some 120 through pass-through templates in this case). (I think I did that recently with you--just a friendly reminder.) It's also less expensive for the search in the event you have multiple templates with a single core template (as with the citation module for example). (I think it's marginally less expensive than an insource search even without regex but I could be wrong about that.) --Izno (talk) 17:18, 13 November 2018 (UTC)
Thanks for the reminder, Izno. I never spend enough time optimising searches and suchlike, and I'd be astonished if hastemplate: wasn't more efficient and less expensive than insource: when looking for templates. Cheers, --RexxS (talk) 23:07, 13 November 2018 (UTC)

@RexxS: - I've used your code and it works and I've also found another template that does it. However, {{posnq}} will fail if any text is placed before {{Start date}} (which technically is good, but not the way I'd like to catch "abnormal" additions, as that will include other cases) so hard-codding the result to "75" is a bit fragile here.

  • {{str find0}}: {{#ifexpr: {{str find0| {{start date|1993|02|24}} | dtstart }} != -1 | Substring is found | Substring is not found }} → Substring is found
  • {{str find0}}: {{#ifexpr: {{str find0| First released: {{start date|1993|02|24}} | dtstart }} != -1 | Substring is found | Substring is not found }} → Substring is found
  • {{posnq}} ok: {{#ifexpr: {{Posnq| {{start date|1993|02|24}} | bday dtstart published updated }} = 75 | Substring is found | Substring is not found }} → Substring is found
  • {{posnq}} fail: {{#ifexpr: {{Posnq| First released: {{start date|1993|02|24}} | bday dtstart published updated }} = 75 | Substring is found | Substring is not found }} → Substring is not found

I'm pretty sure if the template was in lua, this whole process would have been easier and cleaner. --Gonnym (talk) 10:29, 14 November 2018 (UTC)

@Gonnym: Template:Posnq is designed to return nothing if no match is found, so you only need to use an #if to test (since #if treats nothing as false and anything else as true):
  • {{#if: {{Posnq | {{start date|1993|02|24}} | bday dtstart published updated }} | | [[:Category:Parameter not using Start date template]] }}
  • {{#if: {{Posnq | 24 February 1993 | bday dtstart published updated }} | | [[:Category:Parameter not using Start date template]] }}Category:Parameter not using Start date template
All you need to do is add:
  • {{#if: {{Posnq | {{{airdate|}}} | bday dtstart published updated }} | | [[Category:Parameter not using Start date template]] }}
to the template in its tracking category section. --RexxS (talk) 14:40, 14 November 2018 (UTC)
Thanks RexxS, works great! --Gonnym (talk) 10:48, 18 November 2018 (UTC)

Lua "Beta" template[edit]

What is the template to say in Lua documentation: "This module is beta status/quality"? (alpha, etc). -DePiep (talk) 12:35, 17 November 2018 (UTC)

Found: {{Module rating}} - DePiep (talk) 12:41, 17 November 2018 (UTC)

Mystery script errors on Wikidata[edit]

Wikidata has 4K pages with d:Category:Pages_with_script_errors. Pages like d:Talk:Q100 where I can see the error details in html ( in <script> but not on the page itself. How do we debug such cases? --Jarekt (talk) 04:09, 18 November 2018 (UTC)

That is a really weird one. The error (translated from the HTML source) is:
Lua error: bad argument #1 to 'getAllStatements' (string expected, got nil).
in function "error"
libraryUtil.lua:11: in function "checkType"
mw.wikibase.lua:151: ?
(tail call): ?
Module:Wikidata:581: in function "getClaims"
Module:Wikidata/utils:44: ?
(tail call): ?
mw.lua:511: ?
Something is going wrong during the expansion of {{Item documentation}}. Interestingly, editing d:Talk:Q100 shows its contents is {{Item documentation}} and previewing the edit (without changing anything) shows d:Category:Pages with script errors at the bottom. However, replacing the contents with {{Item documentation|Q100}} and previewing shows there is no error category. Near the bottom of the preview page is "Lua logs" with some mumbo jumbo that I suspect is internal to mw.wikibase although I can't find it. Previewing {{Item documentation|Q5}} shows a much longer log corresponding to the longer tree of "parent classes". The "1>=10" stuff might be a log of a binary search? Or a sort? I don't have time to look more at the moment. If someone doesn't crack it soon, a developer might be needed. Johnuniq (talk) 06:44, 18 November 2018 (UTC)
Hmm. I put a temporary test in d:Module:Wikidata (preview only) and confirmed that everything works at line 581 which is the fail point in the error above. That is, entity and property are always strings. That makes me think that a developer is needed. Johnuniq (talk) 06:55, 18 November 2018 (UTC)
@Jarekt: I think I fixed the problem with an edit at d:Template:Item documentation. Try refreshing or purging affected pages and the errors might go away. Johnuniq (talk) 10:10, 18 November 2018 (UTC)
Johnuniq Thanks a lot for looking into it. I spent a while scrathing my head trying to figure it out. The number of pages in d:Category:Pages with script errors is now 448, down from 4k. So your elagant fix of the template worked. --Jarekt (talk) 02:54, 19 November 2018 (UTC)

Module request[edit]

I request that the code at Module:Sandbox/BrandonXLF/2 should be moved to Module:Module link. The purpose of this module is to create modules links. It is planned to be used on {{ml}}, {{mli}}, {{mlix}} and {{mlx}}. The advantage of the module is the error message (can be helpful) and it let's you use as many parameters are you need. BrandonXLF (t@lk) 18:36, 25 November 2018 (UTC)

@BrandonXLF:  Done, although to my knowledge you should have been able to do this yourself (bar some technical error). Jc86035 (talk) 16:21, 5 December 2018 (UTC)

Ordinal numbers[edit]

Hi. I want to add a function to the Dates module on Azerbaijani Wikipedia to create categories automatically. They are mandatory because of the Azerbaijani grammar. Formula will be year+ordinal number suffix, the word "ildə" which means "in year" and the rest will be dependents.

The ordinal suffixes are, 0-cı (not mandatory), 1-ci, 2-ci, 3-cü, 4-cü, 5-ci, 6-cı, 7-ci, 8-ci, 9-cu, 10-cu (the last digits are repeated), 20-ci, 30-cu, 40-cı, 50-ci, 60-cı, 70-ci, 80-ci, 90-cı, 100-cü... (hundreds are -cü), 1000-ci (thousands are -ci).

For the catogories they would be like Category:2018-ci ildə vəfat edənlər, Category:1976-cı ildə vəfat edənlər, Category:1900-cü ildə yarananlar.

Please help if interested. Thank you!--Toghrul Rahimli (talk) 11:21, 5 December 2018 (UTC)

@Toghrul Rahimli: If I've understood properly, here are some tests using Module:Sandbox/RexxS/Ordinal:
  • 1000-ci
  • 1900-cü
  • 1910-cu
  • 1920-ci
  • 1930-cu
  • 1940-cı
  • 1950-ci
  • 1960-cı
  • 1970-ci
  • 1980-ci
  • 1990-cı
  • 1991-ci
  • 1992-ci
  • 1993-cü
  • 1994-cü
  • 1995-ci
  • 1996-cı
  • 1997-ci
  • 1998-ci
  • 1999-cu
  • 2000-ci
Are those correct? You can use the local function in your own module. Obviously you can add on "Category:", " ildə", and the rest of the wording as needed. --RexxS (talk) 15:26, 5 December 2018 (UTC)

@RexxS: this was the exact function i tried to create, but failed obviously. I tested a lot of different numbers, it works how it should. Thank you for sparing your time and helping!--Toghrul Rahimli (talk) 17:05, 5 December 2018 (UTC)

@RexxS: excuse me, i faced a little bit of a trouble. Could you help me? I want to integrate inYear parameter to the ordinal one.

function inYear( year )
    if ( year >= 0 ) then
        return '' .. year .. ''
    else
        return '' .. ( 0 - year) .. 'e.ə.'
    end
end

Categories part:

    if categoryNamePrefix then
        if ( nd ~= nil and nm ~= nil) then
            datePart = datePart .. '[[Kateqoriya:' .. nd .. ' ' .. genitivusMonthes2[nm] .. ' ' .. categoryNamePrefix .. ']]'
        end
        if ( ny ~= nil) then
            datePart = datePart .. '[[Kateqoriya:' .. inYear( ny ) .. ' ildə ' .. categoryNamePrefix .. ']]'
        end
    end

The result is obvious, 2018 ildə vəfat edənlər. Or i would be happy if you took a look at the module, and an example of an article is Corc Herbert Uoker Buş and the module is Dates.

@Toghrul Rahimli: I'm sorry, but I don't understand enough about how the Azerbaijani language works to see what is wrong with Corc Herbert Uoker Buş. Can you explain in simple terms what output you need and what output you are getting? --RexxS (talk) 01:04, 7 December 2018 (UTC)
@RexxS: The problem is the category. I implemented wikidata on the templates, and trying to adapt modules to our language. On the article you will see the red categories, they are not how they should be. For example, it shouldn't be 1924 ildə doğulanlar, it should be 1924-cü ildə doğulanlar which means people born in 1924. You created the algorithm for the suffixes. The main purpose of that was to implement them into categories, but i failed. This is the string in which the ordinal system will be implemented:
            datePart = datePart .. '[[Kateqoriya:' .. inYear( ny ) .. ' ildə ' .. categoryNamePrefix .. ']]'

By the way, b.e.ə means means BC, which is shown in the module. Cheers!--Toghrul Rahimli (talk) 05:39, 7 December 2018 (UTC)

@Toghrul Rahimli: I've amended az:Module:Dates so that it returns the ordinal instead of the cardinal for the year in the InYear function, but I don't see any change on az:Corc Herbert Uoker Buş. That might be a caching issue, so I looked at some others: az:Mustafa Kamal Atatürk and az:Əli Xamenei both seem to have correct categories, but my translation skills are not sufficient to get much further. Could you look at some articles that you know use the Dates module and see if they are right now, please? P.S. I'm not sure I have put the "b.e.ə" in the right place, could you check that as well, please? Cheers --RexxS (talk) 16:43, 7 December 2018 (UTC)
@RexxS: thank you for your edit on the module. The categories in some other articles are correct, because they are not added by the module, but a template. For example, if you remove
{{doğum tarixi və yaşı|1939|7|17}}
(which means date of birth and age), you will see the data will be filled by wikidata, and its category will be shown incorrectly (the year one). It means, the problem directly comes from the last string which is highlighted in my previous reply. if Kateqoriya: .. inYear( ny ) .. ildə .. categoryNamePrefix .. would be changed into a correct one, they will work perfectly. Cheers!--Toghrul Rahimli (talk) 06:32, 8 December 2018 (UTC)
@Toghrul Rahimli: The problem was that the function inYear() needed to be local to the Module:Dates, otherwise somewhere else another version of the function was being used which only returned the year. I've fixed that and now it's correctly using the ordinal function and the categories on az:Corc Herbert Uoker Buş are blue-linked. Would you check some other articles to make sure it's working properly, please? It especially needs to check someone with a date "b.e.ə" so that we know it's in the right place. Cheers --RexxS (talk) 12:29, 8 December 2018 (UTC)
@RexxS: I checked it, it's working how it should be now. Made a minor edit for e.ə so this is correct now. Thank you for your help, it contributed to Azwiki a lot. Cheers!--Toghrul Rahimli (talk) 13:03, 8 December 2018 (UTC)
nitpick: in the code
local function ordinal(number)
	local suffix
	if number % 1000 == 0 then
		suffix = "ci"
	elseif number %100 == 0 then
		suffix = "cü"
	elseif number %10 == 0 then
		local rem = number % 100
		suffix = suffixes[rem]
	end
	if not suffix then
		rem = number %10
		suffix = suffixes[rem]
	end
	return number .. "-" .. suffix
end
note that the scope of "local rem" does not span all the way to its 2nd appearance (so it becomes global at this point). personally, i prefer the and/or logic when writing lua, like so - i find it more readable. not everyone agrees...
local function ordinal(number)
	local suffix =
	    number % 1000 == 0 and "ci"
	    or number %100 == 0 and "cü"
	    or number %10 == 0  and suffixes[number % 100] -- the condition number %10 == 0 is not really needed, but is left for clarity
	    or suffixes[number % 10]
	    or '' -- safety. should never happen
	return number .. "-" .. suffix
end
peace - קיפודנחש (aka kipod) (talk) 21:50, 11 December 2018 (UTC)
Thanks for spotting the scope problem with the second rem. Had I taken the time, I would have simplified to:
local function ordinal(number)
	local suffix
	if number % 1000 == 0 then
		suffix = "ci"
	elseif number %100 == 0 then
		suffix = "cü"
	elseif number %10 == 0 then
		suffix = suffixes[number % 100]
	else
		suffix = suffixes[number %10] or ""
	end
	return number .. "-" .. suffix
end
While we're nit-picking, I think you'll find that the condition number %10 == 0 actually is necessary, otherwise 1910, 1920, 1930, etc. would all have the same suffix, which is incorrect. Cheers --RexxS (talk) 01:44, 12 December 2018 (UTC)
i don't see it. for 1910, mod 100 will return 10, and for 1930 it will be 30, which are different entries in the table. for 1934, mod 100 returns 34, which is nil, equivalent to false, in the table, so the boolean shortcut falls through to the mod 10 line, even without the "%10==0" condition. peace - קיפודנחש (aka kipod) (talk) 06:57, 13 December 2018 (UTC)
Yes, you're right! I misinterpreted what you meant, assuming you were implying that the whole line or number %10 == 0 and suffixes[number % 100] was redundant. I can see you were saying one could replace that line with just or suffixes[number % 100]. Cheers --RexxS (talk) 00:31, 14 December 2018 (UTC)

List of parameters as one parameter[edit]

I have a general design/coding question which I hope someone here could shed some light on. I've seen several table modules which work in the style of 1 module for the table-header and 1 module for the table-rows with corresponding templates. I was wondering, is there a way for a template to accept a list of parameters as one parameter? So for example, instead of calling the table-row template for each row and passing it the parameters |a=, |b= and |c=, have a |row= parameter that gets the row parameters |a=, |b= and |c=? --Gonnym (talk) 08:05, 13 December 2018 (UTC)

It's not possible to do exactly what you suggest—you can't bundle parameters a=one, b=two, c=three together except by a redesign. I rewrote {{Football manager history}} because it used separate templates for the header, footer, and each row with the result that the crazy navboxes seen, for example here generated more than 2 megabytes of "Post‐expand include size". The template now calls Module:Football manager history to do all the work. The module has to parse each row to extract the implied row parameters. That can be messy and fragile although it has worked well in this reasonably simple case. Another example of a module doing a bunch of work to parse data is Module:Val/units which uses a giant text string to define required units, one per line, rather than a traditional Lua table. It turns out that parsing a giant string can be more efficient than using nested tables, and can be easier for editing the wikitext which was the motivation for Val. If you have a specific example I'll have a look. Johnuniq (talk) 08:44, 13 December 2018 (UTC)
Gonnym, Template:Routemap uses a similar approach, and Module:TemplatePar sends in the entire list of parameters as an "=" delimited list. so, it really depends on what you know about the values of |a=, |b= and |c=. for example, if you know they will never contain a "/" then you could use that as a delimiter, for example see Module:Sports rbr table. Frietjes (talk) 12:24, 13 December 2018 (UTC)

New parameter for Module:Article history[edit]

I proposed adding a parameter to Template:Article history (which merely invokes Module:Article history). There was no support or opposition to it after the requisite amount of time, and it was a relatively minor edit, so I would have gone ahead and implemented it myself. However, I do not know Lua. Could someone who does assist with this task (described at the template's talk page), which involves: (1) creating a new parameter and (2) tweaking the target of one of the wikilinks displayed by the template? Thanks in advance. Ergo Sum 02:53, 14 December 2018 (UTC)

Requested move 16 December 2018[edit]

– Centralize personal lua modules under Module:Sandbox {{3x|p}}ery (talk) 23:27, 16 December 2018 (UTC)

(Module:Sandbox/Angr pukhlya and Module:Sandbox/Shah Jahan Ishaq already exist, so the modules that I would otherwise move there are given a ? target. ) {{3x|p}}ery (talk) 23:27, 16 December 2018 (UTC)

  • Pinging @Angr pukhlya, Lotje, MjolnirPants, RexxS, and Shah Jahan Ishaq:. {{3x|p}}ery (talk) 23:29, 16 December 2018 (UTC)
    • There's also a number of pages under Module:Module:Sandbox/* and Module:User:* , so not everything is under Module:Sandbox/* , but yes, it's good to move those listed from where they currently are. -- WOSlinker (talk) 23:45, 16 December 2018 (UTC)
      • What should be done about naming conflicts (the cases I marked with a ?)? {{3x|p}}ery (talk) 23:48, 16 December 2018 (UTC)
  • Oppose Sandboxes are useful for testing and trying out content. It makes sense for modules that are tests to be subfolders of Module:Sandbox. However, when it comes to other content, a registered user has their own userspace for essays, demos, etc. in addition to their user sandboxes for development work, but there is no user-modulespace. I'm quite happy to do development work in a subfolder of Module:Sandbox, but for completed projects and mature code, there is no user space where they can reside. I see reason why Module:Username should not serve that purpose for a user's completed work. What benefit is there in moving them? All that happens is that there going to be conflicts between Module:Username and Module:Sandbox/Username when the user already makes use of these titles for different purposes. In my case, I use Module:Sandbox/RexxS as a demonstration for students of Google Code-In, not as repository for completed work, which I use Module:RexxS to store. --RexxS (talk) 00:46, 17 December 2018 (UTC)