Page MenuHomePhabricator

Support crosswiki template inclusion (transclusion => interwiki templates, etc.)
Open, LowPublic

Tokens
"Love" token, awarded by robkam."Like" token, awarded by Liuxinyu970226."Love" token, awarded by ahmad."Like" token, awarded by ResMar."Like" token, awarded by Yurik."Love" token, awarded by Qgil."Like" token, awarded by Kanzat."Like" token, awarded by Ricordisamoa."Like" token, awarded by Kozuch."Like" token, awarded by Nemo_bis."Love" token, awarded by DiegoQueiroz."Love" token, awarded by He7d3r.
Assigned To
None
Authored By
bzimport, Jan 10 2006

Description

Author: Wiki.Melancholie

Description:
It should be possible to include templates that are stored on
Commons. Just like we can do with images! This would be for
centralized templates. Examples would be:

  1. Templates for interwiki links (interlanguage links); this

would make the interlang bot activity almost unnecessary.

  1. Templates with current information like software versions,

etc.

There is much more application range, of course. This would
help reducing redundancy! Currently all the work that is the
same in every wiki has to be done xxx-times. With template
inclusion from Commons enabled we only have to do that once.
The template names could be in English, or in the language of
the creator (who comes first...).

Best regards, Melancholie


Version: unspecified
Severity: enhancement
URL: http://strategy.wikimedia.org/wiki/Proposal:Data.wikimedia.org
See Also:
T58388: Pre-packaged templates for new MediaWiki installs

Details

Reference
bz4547

Related Objects

Event Timeline

There are a very large number of changes, so older changes are hidden. Show Older Changes
Kanzat added a subscriber: Kanzat.Apr 26 2015, 2:34 PM

This feature would be extremely useful in wikipedia! Most of templates in wikipedia are translated from other language (mostly, from English) and after some time, they just become outdated. There must be one place, where templates can be stored with easy translation tools (like "Translate" extension).

This task is here for 10 years! Does it really have "high" priority? There is even noone assigned to it.

This task is here for 10 years! Does it really have "high" priority? There is even noone assigned to it.

It's high priority because it's the first thing one should do when starting work on this MediaWiki core component i.e. templates. However, nobody has been working in this area for a while.

Qgil awarded a token.Apr 27 2015, 10:45 AM
TTO added a subscriber: TTO.May 9 2015, 1:11 PM
ResMar added a subscriber: ResMar.EditedJun 12 2015, 2:51 PM

This task is imho perhaps the most important piece of independent development that could be performed at this point. I'm thinking in particular about the new Graph extension, the rolling-out of which is bound to result, over time, in hundreds of different Lua wrappers on all the hundreds of different Wikipedias. Surely it would be better and more expedient to have one set of commonly agreed-upon and styled wrappers hosted on Meta accessible to all?

This could also give Meta more of a purpose, of course, but this is something that's been discussed again, and again, and again...

Nonetheless recent events have made this task ever more critical. I'm guessing from the history here that the 'iwtransclusion' branch is at this point abandonware?

(I am aware that the scope of this bug is technically templates only, but Lua has long since made templates and their core modules inseparable)

TTO added a comment.Jun 12 2015, 11:57 PM

Nonetheless recent events have made this task ever more critical. I'm guessing from the history here that the 'iwtransclusion' branch is at this point abandonware?

Not necessarily. It was originally merged into core during the SVN days, when code review happened after merging. In this case, there were enough flaws that the code was deemed unsuitable for the impending release of MediaWiki 1.19, so it had to be reverted. However, the last few comments at https://www.mediawiki.org/wiki/Special:Code/MediaWiki/95396 are quite optimistic, so I wouldn't write it off completely.

Stryn added a subscriber: Stryn.Jul 6 2015, 2:49 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptJul 18 2015, 5:00 PM
Huntster removed a subscriber: Huntster.Jul 18 2015, 8:18 PM

This feature would be extremely useful in wikipedia! Most of templates in wikipedia are translated from other language (mostly, from English) and after some time, they just become outdated. There must be one place, where templates can be stored with easy translation tools (like "Translate" extension).

Maybe than we can store templates in other project and import them to our projects. Templates are always a big mess. Even youd like to share them between different languages, you have allways to figure out, of which components such template consist, to import all its components and customize them to your language. Maybe having that on a separate project like mediawiki.org would ease their usage.

I suggest that the best approach would be to have all templates stored on Meta with individual languages' translations stored as subpages using Meta's translation facilities. As here, for example. There could be a new template transclusion prefix ({{iw:Template}} for instance) which returns the appropriate translation subpage based on the language settings of the current wiki.

A stopgap solution would be writing a script running off of labs that would propagate changes in a master template to all child templates across the wikis once per day, or perhaps once per hour, or however often that could be done.

robkam added a comment.EditedJul 31 2015, 4:37 PM

It looks like the WMF preferred method for achieving this is via Shadow namespaces. See T91162

However it's done this is long overdue but I can't find any indication that it's going to happen.

It looks like the WMF preferred method for achieving this is via Shadow namespaces. See T91162

Not really, if you look at ACTION there.

Qgil added a comment.Jul 31 2015, 9:34 PM

Regardless of the method, mediawiki.org would fit better as source repository than Meta. Commons is for media, mediawiki.org is for software, and templates are software. This makes even more sense if third party MediaWikis can pull those templates remotely, just like they can pull now images from Commons.

Well... that is/will be a little confusing because we also have the request T59336: Make metawiki the central OAuth wiki.

-jem- added a subscriber: -jem-.Aug 10 2015, 4:42 PM
ResMar added a comment.EditedAug 28 2015, 3:27 PM

See also T3126.

Jay8g added a subscriber: Jay8g.Sep 4 2015, 2:00 AM
In T6547#1362094, @TTO wrote:

Nonetheless recent events have made this task ever more critical. I'm guessing from the history here that the 'iwtransclusion' branch is at this point abandonware?

Not necessarily. It was originally merged into core during the SVN days, when code review happened after merging. In this case, there were enough flaws that the code was deemed unsuitable for the impending release of MediaWiki 1.19, so it had to be reverted. However, the last few comments at https://www.mediawiki.org/wiki/Special:Code/MediaWiki/95396 are quite optimistic, so I wouldn't write it off completely.

Its probably bitrotted beyond belief at this point. It would probably have to be mostly rewritten in order to keep up with changes in core since it was written.

TTO added a comment.EditedSep 4 2015, 7:42 AM

My point was that the approach and ideas in that code could still be very useful today for anyone who was going to go ahead and reimplement this.

In T6547#1605539, @TTO wrote:

My point was that the approach and ideas in that code could still be very useful today for anyone who was going to go ahead and reimplement this.

Oh certainly. I just don't want anyone to get the wrong impression that all they have to do is just fix a couple lines and hit the submit button. There's quite a bit of work to be done.

Liuxinyu970226 set Security to None.Dec 7 2015, 7:19 AM
Liuxinyu970226 added a subscriber: Liuxinyu970226.
Meno25 removed a subscriber: Meno25.Feb 22 2016, 7:12 PM
ResMar removed a subscriber: ResMar.Apr 15 2016, 1:38 PM
Krinkle removed a subscriber: Krinkle.Apr 16 2016, 12:43 AM
ahmad added a subscriber: ahmad.
MKar added a subscriber: MKar.May 21 2016, 4:21 AM
Qgil moved this task from To triage to Team radar on the Developer-Advocacy board.
robkam awarded a token.Dec 9 2017, 7:56 PM
gpaumier removed a subscriber: gpaumier.Jul 18 2018, 5:57 PM

@Nemo_bis

It's high priority because it's the first thing one should do when starting work on this MediaWiki core component i.e. templates. However, nobody has been working in this area for a while.

Do you have evidence that there are Gerrit patches to fix this problem, if not, then I don't think that this can be a reason to keep High priority for more than a decade.

This task was authored in 2006, now its 2019. This seems like a never ending process. Any comments on status and roadmap, or should this task be closed as rejected?

I would like watchlists to be allowed in templates. A watchlist for English Wikipedia. A watchlist for Meta. A watchlist for Mediawiki.org

And I want to be able to stack those watchlists on one crosswiki set of show/hide watchlists on one page. A page like this:

Wikipedia:Dashboard:
https://en.wikipedia.org/wiki/Wikipedia:Dashboard

Jony added a subscriber: Jony.Sep 14 2019, 2:11 AM
DannyS712 lowered the priority of this task from High to Low.Sep 14 2019, 2:21 AM
DannyS712 added a subscriber: DannyS712.

Reflect actual priority for developers - I support this, but its been sitting here for so long its clearly not "high priority"

DannyS712 moved this task from Backlog to Transclusions on the Crosswiki board.Sep 14 2019, 2:24 AM
Elitre removed a subscriber: Elitre.Sep 16 2019, 9:38 AM
Qgil removed a subscriber: Qgil.Sun, Nov 17, 9:47 AM