Template talk:Infobox constituency

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Documentation[edit]

It would be nice if documentation could be written for this infobox. It's pretty tough to figure out what's required to make the infobox work. I've started it, but don't know enough about the underlying code to be able to progress this. Schwede66 18:21, 2 August 2013 (UTC)[reply]

Pushpin map[edit]

: Help needed from template editor / admin. I recommend using pushpin map with coordinates for this template and have amended the related doc. Can you please help in implementing the same? Thanks, Arun Kumar SINGH (Talk) 07:25, 2 August 2015 (UTC)[reply]

I have reverted the change to the documentation for now; we shouldn't have a documentation disagree with the underlying tempate. Constituencies are rather unlikely to be so small that a pushpin map is of any use. Take for example New Territories East (constituency) - where would you put the pin? That one is hardly the only example; I couldn't find ones where a pushpin map would be a significant advantage. What's the benefit? Huon (talk) 13:08, 2 August 2015 (UTC)[reply]

Navigation between constituencies[edit]

I would like to add links at the top of the infobox to previous and next constituencies with arrows same as we have links to previous and next year elections in Template:Infobox election to make the navigation easier from constituency to constituency from within the infobox. Sheriff | ☎ 911 | 15:39, 21 May 2018 (UTC)[reply]

Choice of infobox on articles about constituencies[edit]

 – Pointer to relevant discussion elsewhere.

Please see this discussion and follow-up RfC concerning the relative merits of {{infobox constituency}} and {{infobox settlement}}. --Redrose64 🌹 (talk) 07:13, 4 July 2018 (UTC)[reply]

Deprecated syntax[edit]

This template's current form causes things based on it to apparently need to use deprecated syntax; for example, Infobox Ghana constituency uses the syntax [[File:{{{Map1}}}|frameless|upright=0.7|]]|{{#if:{{{Map1|}}}|[[File:{{{Map1}}}.png|frameless|upright=0.7|]] to get the map to display right. How can this template be used to get all those parameters right and get the syntax to be modern? DemonDays64 (talk) 00:17, 22 December 2019 (UTC)[reply]

Your first link goes back to an older version of this talk page. --Redrose64 🌹 (talk) 09:04, 22 December 2019 (UTC)[reply]
@Redrose64: oops! Fixed. DemonDays64 (talk) 15:45, 22 December 2019 (UTC)[reply]

Template-protected edit request on 3 July 2020[edit]

I'd like to request the index of the 'Created from' field to be swapped with the 'Replaced by' field so that the entries appear chronologically when both field are populated. The lines to edit are:

|label18 = Replaced by
|data18  = {{{next|}}}

|label19 = Created from
|data19  = {{{previous|}}}

The indices for 'Created from' would be changed to 18 and 'Replaced by' to 19. -- AquaDTRS (talk) 06:08, 3 July 2020 (UTC)[reply]

 Not done: please make your requested changes to the template's sandbox first; see WP:TESTCASES. Please don't paste code blobs into the talk page, we need to be able to test directly. --Redrose64 🌹 (talk) 11:33, 3 July 2020 (UTC)[reply]
Understood. I have made the change to the sandbox. -- AquaDTRS (talk) 17:16, 3 July 2020 (UTC)[reply]
Have a look at Template:Infobox constituency/testcases, specifically the Abingdon entry at the bottom. Does this exhibit the desired changes? --Redrose64 🌹 (talk) 18:18, 3 July 2020 (UTC)[reply]
Yes -- AquaDTRS (talk) 18:28, 3 July 2020 (UTC)[reply]
OK then,  Done --Redrose64 🌹 (talk) 18:40, 3 July 2020 (UTC)[reply]

Edit request: vary towns label[edit]

I would like the option to vary the towns label, similarly to how district and region can varied. I'm developing the infoboxes for constituencies to the Irish House of Commons, and as some were rotten boroughs, with barely any population (see, e.g. Harristown, Naas South, the term Major settlements is a bit misleading or overstating matters. I've tested this at the sandbox. Iveagh Gardens (talk) 18:08, 4 January 2023 (UTC)[reply]

 Done * Pppery * it has begun... 15:33, 5 January 2023 (UTC)[reply]

Edit request 18 January 2023[edit]

Requesting a minor typographical edit to make the first letter of the word "constituency" in the subheader lowercase if it is not the first word in the statement. Also resolves the inconsistency between when |constituency_link = is specified and when it isn't.

Current line 13:

|subheader2 = {{#if:{{{abolished|}}}|Former|}} {{if empty|{{{constituency_type||}}}|{{{type<includeonly>|</includeonly>}}} {{#if:{{{constituency_link|}}}|[[{{{constituency_link}}}|constituency]]|Constituency}}}}{{#if:{{{parl_name|}}}|<br />for the {{{parl_name}}} }}

New line 13 (tested in sandbox):

|subheader2 = {{ucfirst: {{#if:{{{abolished|}}}|Former|}} {{if empty|{{{constituency_type||}}}|{{{type<includeonly>|</includeonly>}}} {{#if:{{{constituency_link|}}}|[[{{{constituency_link}}}|constituency]]|constituency}}}}{{#if:{{{parl_name|}}}|<br />for the {{{parl_name}}} }} }}

Pizza1016 (talk | contribs) 08:41, 18 January 2023 (UTC)[reply]

 Completed. P.I. Ellsworth , ed. put'r there 23:18, 18 January 2023 (UTC)[reply]

constituency_type parameter error message[edit]

I am seeing an error message in the edit box saying that "constituency_type" is an unknown parameter (see Berlin-Mitte (electoral district) for example). I have checked the source coding and the parameter is still there so I'm not sure what the issue is. Obi2canibe (talk) 16:37, 20 February 2023 (UTC)[reply]

@Obi2canibe: This edit should fix it. --Redrose64 🌹 (talk) 21:01, 20 February 2023 (UTC)[reply]

Template-protected edit request on 13 November 2023[edit]

Please make the following change so that we don’t display such foolish captions as Location of Mount Roskill within {{{region}}}:

|caption3 = {{#if:{{{map3|}}}|Location of {{{map_entity}}} within {{{region}}}|{{{caption3|}}}}}
+
|caption3 = {{#if:{{{map3|}}}|Location of {{{map_entity}}}{{#if:{{{region|}}}| within {{{region}}}}}|{{{caption3|}}}}}

— HTGS (talk) 04:57, 13 November 2023 (UTC)[reply]

This sounds uncontroversial, but it looks like map3 is not the only place where a similar construct is used (map2 for instance). Could you set up the change(s) you'd like in the sandbox so it's clear exactly what needs to be changed? Happymelon 10:29, 13 November 2023 (UTC)[reply]
Sandbox ready now. I have similar concerns about {{{map_entity}}} displaying even if blank, so I made one similar change, but I can't tell exactly what the exact purpose of that parameter is, and it’s probably not as trivial/uncontroversial to do more. — HTGS (talk) 20:53, 13 November 2023 (UTC)[reply]
@Happy-melon, if you please! — HTGS (talk) 03:59, 16 November 2023 (UTC)[reply]
I have added a new test case that displays the failure to check for what are currently required parameters in all four maps. Also, the four maps take different types of input (one adds "Constituency.svg", two add ".svg", and one takes the value by itself). How has this template been around for so long, and used in 5,000 pages, in such a state? – Jonesey95 (talk) 18:49, 17 November 2023 (UTC)[reply]
 Done Anyone is welcome to fix (or request be fixed) the additional bugs Jonesey95 found, but those shouldn't block this request. * Pppery * it has begun... 02:21, 19 November 2023 (UTC)[reply]

Location of <map_entity>within <region>: missing space between <map_entity> and "within"[edit]

If you look at the infobox in, for example, this page, you'll see that there's no space between "Rangitata" (the name of the entity) and the word "within". You can also see the same thing in the illustration examples (under "Full Blank Template") in the Template:Infobox_constituency page itself (in two out of three occurrences of "within"). I suspect this is easy to fix, but I don't know where/how to fix it.PatricKiwi (talk) 02:24, 7 December 2023 (UTC)[reply]