Template talk:Version

Codes for version type

Can somebody explain how they came about? I can't make sense of them and have to consult the help every time. KPu3uC B Poccuu (talk) 08:15, 21 January 2026 (UTC)

@KPu3uC B Poccuu: o=old; c=current; p=preview. --Redrose64 🌹 (talk) 21:01, 26 January 2026 (UTC)

@KPu3uC B Poccuu: o=old, no longer maintained; co=old, still maintained; c=current; cp=current preview; p=planned future version. See Template:Version § Table cells. Guy Harris (talk) 07:46, 27 January 2026 (UTC)

@KPu3uC B Poccuu: And presumably "c" stands for "current", "o" stands for "old", "co" stands for "well, it's old, but it's still being kept up to date, so I guess it's current in some sense", "p" stands for "preview" if it's combined with "c" and stands for "planned" if it's not combined with "c". Not entirely obvious, but so it goes. Suggest a better set of names here on the talk page for discussion if you want; from a quick look at the source to the template it appears that it could be changed to accept the new names as well as accepting the old names for backwards compatibility. Guy Harris (talk) 08:05, 29 January 2026 (UTC)

Uh, does it accept unabbreviated words? I can do with those, thanks. If not, that's what I'd like. KPu3uC B Poccuu (talk) 08:09, 29 January 2026 (UTC)

@KPu3uC B Poccuu: does it accept unabbreviated words? No. It appears to match only the abbreviations.

If not, that's what I'd like. Again, from a quick look at the source, it could be made to, for example, support both "o" and "old" (or whatever unabbreviated word you'd like) for old versions, by having two separate entries, one for "o" and one for "old". Guy Harris (talk) 11:32, 29 January 2026 (UTC)

This template was imported from the German Wikipedia, the codes read as follows:

• o – old version
• co – current older version
• c – current version
• cp – current preliminary version
• p – prospective version

--Vanger (talk) 12:26, 19 April 2026 (UTC)

Bad class names

This template's HTML uses very short class names like "l". Needless to say, this is a bad idea, as class names should attempt to be unique and somewhat descriptive. Opencooper (talk) 02:17, 29 March 2026 (UTC)

@Opencooper: Presumably you refer to attributes such as these:

• class="templateVersion l {{#ifeq: {{{orientation|}}} | vertical | version-legend-vertical | version-legend }}"
• class="templateVersion lv version-legend-vertical"
• class="templateVersion co swatch-unsupported"
• class="templateVersion co swatch-maintained"
• class="templateVersion c swatch-latest"
• class="templateVersion cp swatch-preview"
• class="templateVersion p swatch-future"

I would say that it's a misunderstanding on the part of Jesus Presley (talk · contribs) as to how class names work: probably they did not realise that a class="..." attribute contains a space-separated list of class names, therefore a class name cannot contain a space. They should probably have been templateVersion-l etc. However, I'm not altering them until we can track down all the places that these class names are used. --Redrose64 🌹 (talk) 18:40, 29 March 2026 (UTC)

Yes, thanks for making it clearer. Your suggested hyphenated alternative would work. I looked through styles.css, and nothing there is targeting these class names. A search shows that the templateVersion class isn't being specified in any user CSS/JS. Opencooper (talk) 22:06, 29 March 2026 (UTC)

Time to remove the Accessibility dispute template?

Is it time to remove the Accessibility dispute template? I do not think "version information conveyed by background color has no text alternative" is valid anymore considering versions now have tags. Leonard LMT (talk) 20:43, 6 May 2026 (UTC)