Protection
Per WP:AA, I have reprotected this template. It is not to be unprotected for ANY reason. Non-admins wishing to edit the template for ANY reason are to post their proposed change(s) on this talk page and wait for an admin who understands the template code to review the change for bugs and implement the change themselves. A piece of code this complex that has such huge effects if broken demands sane code-review processes before changes are merged. To facilitate testing and code review, I will shortly create sandbox and testcases pages, similar to what is found on Wikipedia, so that code can be tested in a controlled environment without causing disruption.
With regard to the edit that was reverted immediately prior to the reprotection, that change, which sanctioned by consensus, immediately broke every single use of DISPLAYTITLE in the mainspace. Such disruption is unacceptable. There is no rush, repeat, no rush to implement the CT. That edit is not to be reverted until every single instance of DISPLAYTITLE has been removed from the mainspace. The new parameters approved at the Mofference still work when explicitly used, and the reversion does not change that. Parentheses not being smaller is not "broken"; lack of italicization is broken. There is no need to fix the former until it won't cause problems with the latter. —MJ— War Room 00:29, July 24, 2014 (UTC)
Update needed to exists function
When someone has a second, can you update the exists funciton in Module:Eras? It needs be be changed from this:
local function exists(page)
local success, title = pcall(mw.title.new, page)
return success and title and title.exists or false
end
To this:
local function exists(page)
local success, pageExists = pcall(function ()
return mw.title.new(page).exists
end)
return success and pageExists
end
This is because in later versions of Scribunto, creating title objects is no longer expensive, but accessing the exists property of title objects is still expensive. This probably won't actually affect any pages, as Eras is usually the first thing on the page, but it's better to be safe than sorry. — Mr. Stradivarius ♪ talk ♪ 09:36, August 13, 2015 (UTC)
Also, I've just noticed that Eras:renderProtectionIcon needs to be changed for the same reason. You need to change this:
function Eras:renderProtectionIcon(data)
if not data.protectionAction then
return self:renderIcon(data)
end
local protectionLevel = self.title.protectionLevels[data.protectionAction]
protectionLevel = protectionLevel and protectionLevel[1]
if protectionLevel and protectionLevel == data.protectionLevel then
return self:renderIcon(data)
else
self.hasIncorrectProtectionIcon = true
end
end
To this:
function Eras:renderProtectionIcon(data)
if not data.protectionAction then
return self:renderIcon(data)
end
local success, protectionLevel = pcall(function ()
local ret = self.title.protectionLevels[data.protectionAction]
return ret and ret[1]
end)
if success and protectionLevel and protectionLevel == data.protectionLevel then
return self:renderIcon(data)
else
self.hasIncorrectProtectionIcon = true
end
end
Best — Mr. Stradivarius ♪ talk ♪ 09:51, August 13, 2015 (UTC)
- Actually, ignore that. I've just realised that the module is semi-protected, not fully protected, so I've done it myself. — Mr. Stradivarius ♪ talk ♪ 10:02, August 13, 2015 (UTC)
- Nice, I think, but for some reason I can't see eras icons at all now (using monobook). I don't know if anyone else has this problem, but I thought I'd let you know.--Dionne Jinn (Something to say?) 12:53, August 13, 2015 (UTC)
Porting
Sorry, I don't know if this belongs here, but I can't get the Template to work on my own wiki. The tabs work, just not the small icons. I've copied Tl|Eraicon and {{Top}}, as well as the Wikia.css module and the Eras.css module. What am I missing? NoahR9 (talk) 04:46, April 9, 2016 (UTC)
Should there be an Infinities/Non-Canon tab?
I mean, think about it, there are plenty of stories set in the Star Wars Universe that don't - or didn't - fit into the Legends continuity (for example that Indiana Jones one), and to me it makes sense to have a section about this rather than just tag it on to something it doesn't belong to. I suppose it could be argued that there's not enough material to merit such an addition, but I think the n- and d-class entries on the Holocron Continuity Database speak for themselves. Go look for yourselves, and then draw your own unbiased, well-thought-out decision.
Just one more thing I think will vindicate my suggestion, a direct quote from the canon page:
- N' is Non-Canon. What-if stories (such as stories published under the Infinities label) and anything else directly and irreconcilably contradicted by higher canon ends up here. N is the only level that is not considered canon by Lucasfilm. Information cut from canon, deleted scenes, or from canceled Star Wars works falls into this category as well, unless another canonical work references it and it is declared canon.
How does it do that?
Hey guys! I am working on a project for Bible Wiki, trying to get certain icons to be displayed where you guys have your icons displayed. We want to use your idea here to do it. But we do not know how you guys managed to get it where it at. Could someone explain it to me? Thanks in advance,
- It use a combination of Module:Eras, CSS, and JavaScript. I've imported it to another wiki before. NoahR9
Chat with me! 21:32, December 27, 2016 (UTC)
- Could you perhaps be a little more specific about it? I am interested in how the coding places it where it is located on a page, whether it the coding be Lua or JS. 14:22, January 3, 2017 (UTC)
updates to usage instructions
The usage instructions need some updates.
- The
hide=parameter is not documented at all. - The Canon/Legends specifications section mentions /Canon extensions but not /Legends ones. Today, the latter are far more common, and the former only temporary.
- This section should probably mention that
type=legendsis unnecessary if a publishing era from the next section is specified.
Thank you. Asithol (talk) 23:29, July 17, 2017 (UTC)
- Third bullet point has been implemented... I'm honestly not sure how, or if,
hideeven works? Logically it would hide the Eras from showing up but I can't seem to replicate that. As for the second bullet point, I'm a bit unclear on what you mean by that. 1358 (Talk) 22:34, July 20, 2017 (UTC)- From what I can tell,
hide=1omits the CANON and LEGENDS tabs from the top of the article. This would be used, for instance, if articles Shrdlu and Shrdlu/Legends both existed—and thus would link to each other via those tabs by default—but are not the same thing in canon and Legends and therefore should not be linked to each other. It might be worthwhile to confirm this with whoever implemented this feature, though, and get better instructions. For instance, I am not sure if the=1is required, or what other values can be put there and what they might do. Asithol (talk) 02:35, August 2, 2017 (UTC) - Sorry my second point was well-nigh incomprehensible. To clarify: look, for example, at the current instructions for the
legends=parameter, which say, in part, "defaults to subtracting '/Canon' from the current page name." This phrasing made sense in the days when all canon articles had "/Canon" in their page names and Legends articles were unadorned. Today, it is far likelier that the canon article will be unadorned and the Legends article will end with "/Legends"—any exception to this is temporary, as it means the /Canon article is new and has not been moved into its permanent home yet. So phrasing the instructions this way, today, covers the less likely case and omits the majority of cases. A more current wording might be:
- From what I can tell,
legends- page name of the Legends article for the subject; defaults to "PAGENAME/Legends" (unless the current article ends with "/Canon", in which case this is subtracted)canon- page name of the canon article for the subject; defaults to subtracting "/Legends" from the current page name (unless this name lacks this suffix, in which case "/Canon" is added)
- This is just a suggestion, to be improved as you see fit. Additionally, as above, it would be prudent to check in with whoever maintains the template code to make sure all those details are correct, and see if they overlook any subtleties. Asithol (talk) 03:30, August 2, 2017 (UTC)
Mercury
I don't know how it works in the app, but as there exists the template of Eras-mobile, I believe it's no longer needed in the mobile skin. All it does is making an article look worse. @Mustafar29「talk」(he/him/his/hisself) 15:38, July 14, 2018 (UTC)
Categories
I know there's already a category called Star Wars media by canonicity but could we change the Eras template so the so the pages listed under the canon and legends categories are listed under canon and legends in the other categories that make up those pages (i.e. Canon Males to Legends Males, Canon Females to Legends Females) and so on?--Rgilbert27 (talk) 20:18, December 8, 2018 (UTC)
- You mean basically splitting our category tree into a Legends and Canon fork? That's a much bigger discussion than simply modifying the Eras template. 1358 (Talk) 20:20, December 8, 2018 (UTC)
- Still that's something we can discuss so can we discuss here or do we have to move it to a forum?--Rgilbert27 (talk) 03:13, December 9, 2018 (UTC)
Usage update
It looks like the usage instructions needs an update - for example, it looks like it now includes NOTOC functionality. Corellian PremierThe Force will be with you always 00:48, July 28, 2019 (UTC)
- NOTOC in Eras isn't codified in the LG yet (I've been meaning to propose that in the CT/Mofference for ages now) so I'll avoid adding it before that happens. 1358 (Talk) 10:08, July 28, 2019 (UTC)
- The usage instructions merely document what the template can do. Even if policy (LG or any other) doesn't mandate how NOTOC should be specified, the usage instructions should document how it can be via this template. Policy and documentation are separate things. Asithol (talk) 02:49, August 27, 2019 (UTC)
Unlicensed banner
Would it be possible to create a new specification for articles that derive from unlicensed Star Wars Legends sources? It would display an "unlicensed" banner with the yellow Legends background (sort of like "ncl"). If possible, it would be wonderful if a bot could then add it to articles with the {{Unlicensed}} template. —DKS MaXoO (talk) 03:30, 22 November 2024 (UTC)
- I think this should be rather discussed as an SH, as unlicensed content is still regarded as an "unstable" part of Wookieepedia that need to be re-examined seriously. NanoLuukeCloning Facility 09:55, 22 November 2024 (UTC)
Unnecessary wanted pages
Second suggestion today...or more likely a technical thing. I'm not sure if this has been discussed before, but I have noticed this long ago - the module itself creates an unnecessary bunch or rather tons of wanted pages. Examples:
Dates - just one example and this applies to any date page:
Other pages
- Special:WhatLinksHere/Darth_Vader_(2020)_1/Canon
- Special:WhatLinksHere/Darth_Vader_(2020)_1/Legends
- Special:WhatLinksHere/Star_Wars:_Episode_I_The_Phantom_Menace/Canon
- Special:WhatLinksHere/Star_Wars:_Episode_I_The_Phantom_Menace/Legends
- Special:WhatLinksHere/Tensu Run/Canon (a canon-only character that will obviously never have a Legends counterpart)
- Special:WhatLinksHere/Tensu Run/Legends (same here)
and so on.
I've also noticed there are no extra pages requested with the templates using {{Top}}, example - Special:WhatLinksHere/Template:Star_Wars/Canon
I do acknowledge the following:
- Luckily, the number of the wanted pages created by the module is still limited.
- Comment: But having about 730 extra wanted pages for dates only?
- There will never come a time when Wookieepedia runs out of the wanted pages, so at least we will never see only the incorrectly wanted pages on Special:WantedPages.
Still - could there be a way to somehow tweak this module to stop it from automatically creating wanted pages or is it the way it operates and is it something we have to adapt to? Could there be a solution (such as a blacklist page) that doesn't break the way the module works? --Orgus Ordo (talk) 10:49, 22 November 2024 (UTC)
- It's intentional, yes, because the technical implementation of checking whether a page exists in Lua causes a page reference in terms of WantedPages. I can suppress the checking for real-world articles, but it's not possible to do anything about them for canon/Legends pages. Cade
Calrayn 16:34, 24 November 2024 (UTC)
- Thank you for your reply and more than extensive answer. So I imagine in an alternative universe we could just have the unnecessary wanted pages created as redirects to the real ones, to get rid of the extra stuff. I've just looked at how many pages use, for example, the general comic book template and realized there around 5500-5600 extra non-existing pages based on the comic issues only (with /Canon and /Legends counterparts wanted) --Orgus Ordo (talk) 14:02, 27 November 2024 (UTC)
- Update: I believe they are gone now. Thank you for this great job of implementing this change. At least the real world topics will be free of this subpage anomaly. --Orgus Ordo (talk) 18:20, 27 November 2024 (UTC)
Using this template on other wiki
Hello dear Wookieepedia editors, I came here to ask you if I could use the {{Top}} template on a wiki I partake in editing, w:c:HypixelSkyblock, I would like to use its tabs as it could be useful in countless of pages on our wiki, but I would first like the blessing to use code someone else wrote.