Template talk:Infobox venue

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

New "Major Events" section under tenants[edit]

a new section where major events such as world cups, olympics ect can be listed? Creeperlover1000 (talk) 01:09, 23 October 2022 (UTC)[reply]

That should be avoid! Events are not tenants, talk about miss information!! Govvy (talk) 21:58, 27 April 2023 (UTC)[reply]
Miss Information? Is that a Silicon Valley beauty contest? But seriously, this is a good idea, as many major events are regularly held in certain venues, but wouldn't be classed as "tenants" per se. BilCat (talk) 08:23, 28 April 2023 (UTC)[reply]
Then shouldn't that be a separate field and element altogether. If you goto Old Trafford, it is currently sitting in the Tenant field. Govvy (talk) 08:30, 28 April 2023 (UTC)[reply]
That's why the suggestion is to make it a separate section. Instead of a knee-jerk reaction maybe actually read the post? oknazevad (talk) 15:26, 28 April 2023 (UTC)[reply]

Edit request 19 January 2023[edit]

| image = {{#invoke:InfoboxImage [...] |upright=1 [...] | header48 = [...] {{#invoke:Check for unknown parameters [...] | logo_size | main contractors
+
| image = {{#invoke:InfoboxImage [...] |upright={{{logo_upright|1}} [...] | header48 = [...] {{#invoke:Check for unknown parameters [...] | logo_size | logo_upright | main contractors

Add a parameter named logo_upright in the {{#invoke:InfoboxImage}} for the logo image. Per MOS:IMGSIZE, this would allow editors to resize the logo image in a way that respects readers' preferences for image thumbnail size. Accordingly, add logo_upright to the {{#invoke:Check for unknown parameters}} table at the bottom of the template to avoid an erroneous message in an edit preview. This change has been tested with the sandbox, and works functionally. — AFC Vixen 🦊 08:05, 19 January 2023 (UTC)[reply]

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

Tenant field again[edit]

Description on the main page should read, if the stadium owner and operator are same as the tenant, then the tenant field shouldn't be needed. It effectively an N/A argument. And should be thus. Still bizarre that people are using it incorrectly. Govvy (talk) 22:00, 27 April 2023 (UTC)[reply]

And owner and operator field should be defined as stackable and not a single use field. You can have multiple owners, operators over time. Govvy (talk) 22:02, 27 April 2023 (UTC)[reply]
Not again. I thought we buried this argument years ago? BilCat (talk) 22:05, 27 April 2023 (UTC)[reply]
Morning BilCat All I am saying is the language could be improved Parameters (Explanation) cells on the table. Govvy (talk) 08:18, 28 April 2023 (UTC)[reply]
The tenant parameter is for the team itself, not the ownership. BilCat (talk) 08:29, 28 April 2023 (UTC)[reply]

Edit request 19 March 2024[edit]

| label17 = Record attendance
+
| label17 = Record attendance
with nbsp
Location
  • Cnr Eden Blvd & Smith Rd
  • Southend-on-Sea, England
Public transit Havenoak–23rd Street
Record attendance76,920 (South Africa v Germany)
without nbsp
Location
  • Cnr Eden Blvd & Smith Rd
  • Southend-on-Sea, England
Public transit Havenoak–23rd Street
Record attendance76,920 (South Africa v Germany)

The non-breaking space used in the "Record attendance" label restricts the width of the infobox's entire data column when the row is made active by a |record_attendance= input. This is especially detrimental in cases where the additional space taken up by this non-breaking label is sorely needed to better fit data in the infobox. No other label in this template with a similarly lengthy name has a non-breaking space, such as | label15 = Executive suites, | label37 = Construction cost, and | label43 = General contractor, so I'm confused as to why this specific label has one. Examples of how the data is presented with and without the non-breaking space in Record attendance's name are presented on the right. — AFC Vixen 🦊 13:27, 19 March 2024 (UTC)[reply]

 Done — Martin (MSGJ · talk) 13:30, 19 March 2024 (UTC)[reply]