MediaWiki talk:Proofreadpage header template

From Wikisource
Jump to navigation Jump to search

Year paramater[edit]

Is the reason this doesn't populate the year field in the header because we don't do that for subpages? Could we just pass a parameter from <pages /> that would trigger this behaviour? Prosody (talk) 15:52, 26 August 2011 (UTC)Reply[reply]

Not sure by any measure but it appears the year parameter is not a stand-alone entry as author or title are but a sub-part of the notes parameter and called via an if... statement. I suppose if it was a stand-alone, your logic about it coming up on sub-pages as well as the main makes sense and that is probably why it doesn't mirror the current "basic" header template's usage using the stand-alone parameter(s). -- George Orwell III (talk) 18:38, 26 August 2011 (UTC)Reply[reply]
Makes sense. I'm not sure if I'm reading the documentation right, but would it be technically possible to add something like | year = {{#if:{{{yearinheader|}}}||{{{year|}}}}} and have <pages yearinheader=1 ... /> automatically work? Prosody (talk) 15:44, 27 August 2011 (UTC)Reply[reply]
Try it. The documentation seems more like an after-thought than deliberate so I see no other way to move forward here short of trial & error. Of course you can try touching base with ThomasV first but I don't recall seeing him around much lately if at all. The changes proposed do not, to me, seem to be the kind that would affect the existing usage or application.... if doesn't work we can always revert it without all that drama. -- George Orwell III (talk) 16:52, 27 August 2011 (UTC)Reply[reply]
Can't. All MediaWiki pages require the admin bit to edit. Prosody (talk) 20:48, 27 August 2011 (UTC)Reply[reply]
Sorry for the long delay - had to go fight off rising flood waters here - Didn't mean to leave you hanging like that.

After thinking about this some and playing with the existing code, I first have to wonder if this will achieve the output I think you're looking for or not.

This header seems to be intended to replace the common {{header}} template altogether and is enabled by adding <pages ... header=1 ... />. In other words, its an either ~ or thing, otherwise you'll wind up with 2 green headers on top of each other. BTW, the year comes up in the notes field when this header is used and is pulling that "info" from the related Index: page (if it exists there). Not sure why but upon a closer look the Section = parameter is married to the current parameter rather than section like the stand-alone header template is crafted to as well. Maybe there is something more to (re)using the standard header parameters and their assigned defaults? ....not a clue here.
So again, I'm not sure you intend on strictly using this method for header generation in the mainspace or not? -- George Orwell III (talk) 08:10, 2 September 2011 (UTC)Reply[reply]
Kinda. I've been experimenting with it in the last work I made a mainspace page for (A Leaf in the Storm; A Dog of Flanders and Other Stories) and generally think that centralizing metadata on the index page will end up paying dividends in the future. We're obviously still missing a lot of parts for that (most crucially, the data about how the work ends up organized in the mainspace).
Gotcha. I went ahead and made the year paramater match its sister as a standalone like it is in the familar header template. The previous if... statemennt is now yeardate just in case it will be needed for some yet to be revealed reason down the road. As suspected, the year now also appears on the subpages as well. I'd rather leave that alone rather than introduce yet another not-so-certain nor documented parameter like your yearinheader mentioned earlier. If that's not cool - I'm sure there is a way to make year basepage-specific using an ifeq:... type statement though I'm drawing a blank on exactly what that should be at the moment. -- George Orwell III (talk) 00:34, 3 September 2011 (UTC)Reply[reply]
Looks fine. Thank you. Prosody (talk) 19:45, 3 September 2011 (UTC)Reply[reply]
Anytime. In case it matters in the future, I tried...
{{#ifeq:{{BASEPAGENAME}}|{{PAGENAME}}|{{!}} year = {{{year|}}}|}} get year not come up on sub-pages and that stopped it alright but the year parameter and value comes up as straight text and thinks it is part of the next parameter on base-pages unfortunately. I'm sure its something small to tweak but it escapes me at the moment. -- George Orwell III (talk) 22:27, 3 September 2011 (UTC)Reply[reply]
The current/section thing is odd, maybe there's a reason it is that way, but looking at the history it seems more likely it was an arbitrary decision (note that this wasn't initially a wrapper for {{header}}) and should probably be changed. Prosody (talk) 23:15, 2 September 2011 (UTC)Reply[reply]
Not so sure about that - from my limited poking around, the issue here compared to the French, German and other similar WS sites is that they use an all DIV based header template where as we still use a html TABLE based one. My guess is the resulting application here was a work-around more so than what was really intended or desired. -- George Orwell III (talk) 00:34, 3 September 2011 (UTC)Reply[reply]

Pictogram voting comment.svg Comment The year parameter is now bleeding through automatically on all subpages. Can we please work out how that occurred, and rescind that change. The year parameter should typically only show up in the root page, and not show in subpages unless asked to do so from the header tag syntax, not on every transclusion. — billinghurst sDrewth 14:03, 3 May 2021 (UTC)Reply[reply]


There is a bug with author link: Chronicles of the Crusades, The Princess of Cleves, The Peat Moor. Marc (talk) 17:59, 20 February 2012 (UTC)Reply[reply]

Translator field[edit]

Doesn't seem like the translator field in the header is getting populated, either from the Index metadata or direct arguments, though looking at it I can't guess why. Example here: The Alchemy of Happiness (Field). Prosody (talk) 05:46, 27 July 2013 (UTC)Reply[reply]

The problem seems to be with the original header template. The author and override_author portions of the template code are not mirrored exactly by the translator, editor, contributor, etc. portions and I'm guessing that is somehow why author works but translator et al. does not (when being pulled from the pages tag command line that is).
I think you'd better post the problem in Scriptorium - I have no idea nor the incentive on how to fix something like that. Its a pointless, redundant feature if there was one, imho, that promotes a fork in our practices while encouraging laziness. -- George Orwell III (talk) 06:46, 27 July 2013 (UTC)Reply[reply]
I forgot all about the "other" MediaWiki file... THIS simple change seems to have resolved the translator field "issue". -- George Orwell III (talk) 07:42, 27 July 2013 (UTC)Reply[reply]

Notes parameter in pages tag not populating?[edit]

In Cornhuskers I'm not having any luck with the notes parameter appending text to the notes field of the header. Prosody (talk) 02:30, 17 September 2013 (UTC)Reply[reply]

Doesn't happen when that extended use of <pages> is used to generate the page header (which I why I don't use it). You would need to convert it to standard header, retransclude and add your notes. — billinghurst sDrewth 11:43, 18 September 2013 (UTC)Reply[reply]
Same as previous issue directly above - just needed to be added to the "other" list (making more of a mess, of course).
Again: Death to ThomasV wherever he may be. -- George Orwell III (talk) 23:13, 18 September 2013 (UTC)Reply[reply]