Last modified: 2006-07-12 21:23:12 UTC
While building a software manual in MediaWiki it would be nice to be able to tag
specific versions of pages (the history) with certain software release version
numbers, most likely using categories that persist beyond revisions. Ie:
- Create page 'Main', tag with category 'R1.0'
- Create page 'Cats and Dogs', tag with category 'R1.0'
- Update page 'Main'
- Update page 'Main', tag with category 'R1.1' (and remove 'R1.0')
- Create page 'Home', tag with category 'R1.1'
It would probably be necessary to differentiate between these special version
categories and standard categories. Some way of grouping these categories should
be used to prevent 'R1.0' and 'R1.1' being on the same version of a page,
although 'R1.0' could co-exist with 'User Reference' for example which might be
on all revisions of the 'Main' page.
While browsing pages, if they have this special version category, the user's
session should remember the current category. When visiting other pages the Wiki
should keep within that category. Ie:
- User visits 'Home' in above example, this might link to the 'Cats and Dogs'
page. When C&D is visited we will get that tagged with 'R1.0' as there is no
higher version, however, then moving to 'Main' should bring in the version
tagged with 'R1.1'.
- User then hits a link to 'R1.0' of 'Main' and this is explicitally stored in
the session as that is the category user is interested in. User will be unable
to see page 'Main' as there is no version on or before 'R1.0' however they can
still visit 'Cats and Dogs'.
This would be particularly useful if implemented with branching of document
history (when one may want to edit 'R1.0' of 'Main' for example, without
distroying the 'R1.1' version.
Appologies if this is already possible, but it does not seem so. Any other
suggestions as to how to yeild the same result?
*** This bug has been marked as a duplicate of 4288 ***
If I publish a new revision of an article about the Model A Ford
we have a very different issue than publishing a separate article for fixing
a Ford Focus. We start out with a subject like Ford and then we fork
articles about the different cars. We also fork for different languages.
If we tag revisions of the Model A Ford article or revisions of the Ford
corporation article then
we have a duplicate of bug 4288.
However the issue of forking an article into different articles is a different
This is now often done with something in perenthesis Model A Ford (Movie), Model
A Ford (Song) or Model A Ford (Car).
Now if we want to tag the forks with something more useful then this bug is not
a duplicate of bug 4288.