Page MenuHomePhabricator

No support for versioned transclusions (specific page/template revisions)
Open, LowPublicFeature

Description

At the moment, when writing about or revising templates, comparing former versions is impossible to do without resorting to screenshots. Much better would be, if we could just transclude different versions next to each other so as to be able to see their differences.

E.g. putting (figures represent sample revision numbers):

{{template#18825}}
{{template#18852}}
{{template#18995}}

…in a page, we could have older existing versions shown underneath each other, and editing progress documented, or the ground laid for a decision, which layout to finally choose for general use in the future, etc.

Of course, the same can apply to any page transclusion, not only templates. The syntax above is not meant to be final or recommended, it is chosen only for quick and simple demonstration.


Versions: All, up to at least 1.43
Severity: enhancement

Details

Reference
bz29051

Event Timeline

bzimport raised the priority of this task from to Low.Nov 21 2014, 11:37 PM
bzimport set Reference to bz29051.
bzimport added a subscriber: Unknown Object (MLST).

Use of specific versions by local ID number would not survive import/export across sites, making it very unsuitable for general usage. If something like this were considered it would probably need to be pretty explicitly unavailable in content pages.

Indeed; that is why I did not propose a more general identification.
The ids being used in permalinks to local pages that have not been
hidden are the only ones that (currently) are guaranteed to work.
They should luckily already cover a large class of pages that one
may want to be able to serve again with their unaltered historic
content, even if not with each of their old CSS.

If we want something more permanent, being constant across sites
and export/import, we need to use something like the message-id's
known from e-mail and netnews to identify revisions. Yet that would
have to be carefully considered and most likely existing revision
numbers converted which I am hesitant to propose.

Aklapper changed the subtype of this task from "Task" to "Feature Request".Feb 4 2022, 11:00 AM
Chealer renamed this task from Allow transclusion of a specific page or template version to No support for versioned transclusions (specific page/template revisions).Jul 6 2025, 8:53 PM
Chealer updated the task description. (Show Details)
Chealer awarded a token.