User Details
- User Since
- Oct 6 2014, 9:38 PM (521 w, 4 d)
- Availability
- Available
- LDAP User
- Jackmcbarn
- MediaWiki User
- Jackmcbarn [ Global Accounts ]
Nov 4 2023
Jan 24 2021
Aug 19 2020
Aug 13 2020
Until this is implemented, https://en.wikipedia.org/wiki/User:Jackmcbarn/advancedtemplatesandbox.js can serve as a workaround.
Mar 25 2018
Oct 12 2017
Feb 21 2017
Feb 19 2017
IMO, it was a bad idea for {{int:}} to ever work on user language instead of on content/page/site language. I don't think we should extend that mistake.
Feb 6 2017
Feb 5 2017
Feb 2 2017
Jan 10 2017
That already all exists. You get it when an error makes it back to the console or wikitext without (x)pcall catching it.
Jan 7 2017
@Rical A cursory look at that module reveals that you're using "select" as a variable name in it. That's a bad idea, since it's the name of a built-in global function. It wouldn't surprise me if that were the root of the problem.
Jan 1 2017
No, since the output of the parser can't change whether or not a page exists. Basically, I don't like things that could cause paradoxes if called on themselves, or on other pages in a loop. (See also my response to T71441).
I dislike the idea of exposing through the parser any properties that can be set via the parser.
Nov 2 2016
Instead of splitting discussion, if you still think this should happen, please reopen the old issue.
Nov 1 2016
I still don't really like the idea. When is this even useful? (And my point wasn't that it's not possible at all, but that it will necessarily give the wrong answer sometimes.)
Oct 16 2016
Passing the same dataWrapper result more than once would introduce another way that T67258 could happen.
Sep 27 2016
This seems like a non sequitur. None of this is improved by being able to automatically switch by wiki ID, since the different configurations for different wiki IDs would have to be written anyway (just in a different place). And centralized modules are also totally orthogonal to this.
Sep 26 2016
I tend to agree with Anomie on this. I'm not sure this should be done.
Jun 26 2016
Done. (You do "Merge Duplicates In" from the other task.)
Jun 19 2016
Jun 16 2016
I'm pretty sure that the lack of locational context would keep enwiki from switching to this.
Jun 14 2016
Jun 9 2016
Hmm, apparently this was intentionally done by @ori in rETBLa05d0abed95481de9009050c0e0a759900708d4a. Adding him for comment.
Jun 3 2016
May 29 2016
IMO, the second method here is the right way to do this, and this isn't a bug but rather intentional behavior.
May 25 2016
May 23 2016
I still don't see anything to do here. Please give a clear, specific description of what functionality you want to be added.
May 22 2016
@Rical, you still haven't given a specific example of what you'd like to be done in Scribunto.
Rical, please don't do that.
May 14 2016
Closing since T28546, now fixed, was a better solution.
My patchset was merged. I'm not sure why gerritbot didn't post here about it.
May 8 2016
I see no reason that this has anything to do with Lua. I think my patch at https://gerrit.wikimedia.org/r/#/c/158098/ is a much better solution.
Apr 26 2016
As legoktm said, this happens because it's currently impossible to create a module redirect. Rest assured that this will never allow unauthorized users to access the block or delete buttons. (Also, my personal opinion is that suppressredirect should not be required to move modules, etc.)
Apr 6 2016
CAPTCHA isn't meant to be "Are you sure". It's meant to be "Are you a human". If you want a bigger confirmation step, please ask for something different (like typing the username of the user to nuke again).
Looking at everything that uses $wgSemiprotectedRestrictionLevels, it does look like exactly what we want. Let's do that.
That feels clunky, though, and it doesn't completely fix the problem. If page A referenced page B and page B referenced page A, you'd still get the same issue.
I really don't like all of these recent ideas to let Lua fetch information about pages that isn't known until the page is parsed.
Apr 2 2016
The problem with listing all pages transcluded on a given page is that it can't be accurate on a given page. Imagine if it were, and someone created a template called "IsTranscluded", that returned whether a given template was transcluded on a given page. Then suppose a page called {{#if:{{IsTranscluded|{{FULLPAGENAME}}|Template:Foobar}}||{{Foobar}}}}. Now the result of that will never be accurate.
In core, the formatnum and plural parser functions use it.
Mar 31 2016
All parseFormattedNumber does is call Language::parseFormattedNumber in core, so this isn't Scribunto-related at all.
Mar 28 2016
Can you make it clearer what you're asking for? I'm not sure if you want all pages that transclude a page, or all pages that are transcluded by a page.
Mar 26 2016
Mar 20 2016
Feb 24 2016
No problem, I already have it taken care of.
FYI, I didn't realize that this was taking parsoid-prod.wmflabs.org down until it happened, so a lot of the requests from it were probably from my https://en.wikipedia.org/wiki/WP:EPH script.
Feb 22 2016
Feb 1 2016
This can't be done, since the number of sections in a page isn't known until after parser functions get evaluated. Imagine a page that contained {{#ifeq:{{NUMBEROFSECTIONS:{{FULLPAGENAME}}}}|0|== Section ==}}. This would cause a paradox.
Jan 3 2016
Jan 1 2016
https://en.wikipedia.org/wiki/User:Anomie/linkclassifier.js can add the class "self-redirect" to such links (which can then be styled with CSS), though I agree this would be nice to have in core.
I proposed exposing this information from Lua in https://gerrit.wikimedia.org/r/#/c/188503/ and Tim didn't like it because changes to user groups don't have a practical way to invalidate caches of pages that use the information.
Dec 22 2015
No, for all the same reasons as T6196.
Dec 15 2015
Closing then, as there's nothing to do. It doesn't make sense to make a task a blocking task if there's no work to do for it.
Are there any features that you still need then, or can this be closed? Also, I encourage you to use callParserFunction rather than preprocess.
Dec 11 2015
Dec 7 2015
For relatively-named submodules, do this:
local submodule = require(mw.getCurrentFrame():getTitle() .. '/submodule')
For versioning, either keep a version constant in the code, or use frame:callParserFunction with REVISIONTIMESTAMP. For ISO 8601 dates, call mw.getContentLanguage():formatDate('c', theDate).
Dec 4 2015
I remain unconvinced that the old situation is better than it is now. It shouldn't be that hard to add the ability to filter this data if it's wanted that badly.
Nov 27 2015
Nov 18 2015
EDIT: Anomie beat me to it.
Nov 4 2015
When you performed your undo, you only undid one of two pending changes, so your revision wasn't automatically accepted. (The second pending change was this one.) As a reviewer, you could have accepted it yourself anyway by checking the "Accept this version (includes ## pending change(s))" box before saving, or just like any other pending change after saving. Unless I'm missing something else, there doesn't seem to be anything wrong here.
Oct 29 2015
I don't really see a need to add a built-in for something that it's trivial to write a module for.
Sep 30 2015
I like this idea a lot. Making it work like Special:WhatLinksHere (for example) is probably the best way to go here.
There's no 500-page limit as far as I can see, and on both en.wikisource and www.wikisource, I wouldn't exactly say it's "flooded" until you start getting into occurrences with only 1 or 2 transclusions. (The one thing I would like to fix is that transclusions of stock messages really shouldn't count.)
Sep 24 2015
For clarification, that change was merged a while ago, so this is already possible.
Sep 23 2015
I think {{ns:0}} is good enough.