Template:If empty is permanently protected from editing because it is a heavily used or highly visible template. Substantial changes should first be proposed and discussed here on this page. If the proposal is uncontroversial or has been discussed and is supported by consensus, editors may use {{edit protected}} to notify an administrator to make the requested edit. Usually, any contributor may edit the template's documentation to add usage notes or categories.
Any contributor may edit the template's sandbox. Functionality of the template can be checked using test cases.
This edit request has been answered. Set the |answered= parameter to no to reactivate your request.
Please merge {{If empty/sandbox}} into here. I believe User:Jackmcbarn and I have tested it quite thoroughly to ensure backwards compatibility. The only difference now is that this template is no longer limited to nine parameters and that it should run considerably faster. Also, someone may want to protect Module:If empty. —CodeHydro21:52, 23 December 2014 (UTC)[reply]
Look at the pages transcluding {{error}}s in main namespace. Most are mountain articles such as Mount Kilimanjaro, which transclude {{Infobox mountain}}. There are no actual errors in these articles, and that's why I call these "false transclusions". {{error}} should only be transcluded in these articles when the name is missing and the error message "Mountain name required" is shown at the top of the infobox. This is how I patrol for these, by looking for {{error}} transclusions. Wbm1058 (talk) 00:04, 27 December 2014 (UTC)[reply]
Thanks for pointing this out. I've rewritten the error check at {{Infobox mountain}}'s sandbox as not to use this module at all. While using {{If empty}} to produce a transclusion is clever, it's not at all a common use (based on the relatively tiny number of transclusions of {{error}} in template space). The purpose of this module is to check multiple variables... even though this module is much less expensive than the old wikitext template, it is more expensive than a simple #if call, which is what should be used to check a single empty param. While I have an idea how to make the module avoid false transfusions, I do not want to encourage this usage. —CodeHydro04:50, 27 December 2014 (UTC)[reply]
Thanks. I've applied the change to each of those templates. None are protected so doesn't really help me get template editor at all since I've no shortage of non-protected edits, but the thoughtfulness is appreciated. —CodeHydro15:17, 27 December 2014 (UTC)[reply]
@Wbm1058 and Codehydro: This is actually a bug in Module:Arguments. Once I get it fixed, this won't be a problem anymore. You don't need to "fix" any more templates that use this, as they'll all be fixed again soon. Jackmcbarn (talk) 05:00, 28 December 2014 (UTC)[reply]
@Pppery: I've removed the backwards compatibility code from the module's sandbox (which also has a never-deployed bugfix); the testcases page looks fine (other than the undefined parameters case, which is to be expected). If everything looks good to you, it can be deployed and the tracking category tagged for deletion. 「ディノ奴千?!」☎ Dinoguy100006:49, 5 May 2022 (UTC)[reply]