| Bug #36014 | "MySQL 6.0 Reference Manual" points to 5.1 manual | ||
|---|---|---|---|
| Submitted: | 12 Apr 2008 9:08 | Modified: | 16 Oct 2009 16:14 |
| Reporter: | Olaf van der Spek (Basic Quality Contributor) | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
| Version: | OS: | Any | |
| Assigned to: | Stefan Hinz | CPU Architecture: | Any |
| Tags: | qc | ||
[12 Apr 2008 9:08]
Olaf van der Spek
[12 Apr 2008 9:09]
Olaf van der Spek
Tags += qc;
[12 Apr 2008 9:22]
Peter Laursen
I think they all do! Also 5.0, 3/4.0/4.1 don't go anywhere!
[12 Apr 2008 9:33]
Valeriy Kravchuk
Yes, they all do. But you are looking at news about 5.1.x, http://dev.mysql.com/doc/refman/5.1/en/news-5-1-x.html, so it may be even reasonable (although looks misleading :). Why 4.1 Manual should have a page on 5.1.x news? Anyway, let documentation team check it.
[14 Apr 2008 5:15]
Stefan Hinz
This was filed as Web request "Change link to point to 6.0 Manual" and will be fixed by our Web team.
[12 Aug 2008 12:31]
Jon Stephens
Since this appears to be fixed and was not a Docs bug but rather an issue with the site, I've closed this bug.
[12 Aug 2008 15:41]
Olaf van der Spek
It doesn't seem to be fixed. 3.23/4.0/4.1, 5.0 and 6.0 still point to 5.1...
[12 Aug 2008 18:09]
Valeriy Kravchuk
This is NOT fixed yet, indeed.
[16 Oct 2009 14:34]
MC Brown
The problem here is that the links on the left to switch between manuals assume that the ID used for the current page is the same in each manual. This is fine for something like 'optimization', which exists with that ID in all manuals and can therefore be easily guessed for every manual version just by replacing the corresponding manual version and ID within the link. Clicking on the corresponding manual links on this page will take you to the page for the corresponding version. However, for pages that are version specific, like the pages that provide the changelog information, these contain a page ID which is unique for the version of the reference manual currently being viewed. The web interface doesn't know (and is incapable of knowing) that this is the case, so it generates the HTML link anyway, and then ultimately redirects you to back to the manual where it exists. Hence why all links seem to click back to the manual. There are two issues here: 1) Adding exceptions of this nature into the system is not impossible, but is probably impractical, since there are many many sub-versions (5.1.31, 5.1.32), and we would have to provide an alternative for each item. 2) Even if we added an exception in these cases where the page doesn't exist (either because it's a feature or reorganized chapter, or a version specific page), the behavior of such an occurrence is not easy to identify. If I'm on the page for 5.1.31 changelog and I click on the 'MySQL Reference Manual 5.0', where am I expecting to go? There isn't an equivalent page (for obvious reasons). Should I go to the home of the 5.0 manual? The root of the news section? How about if I click on a page for a feature that only exists in 5.1, and not 5.0. What page should I go to? There are no easy answers to this question. The other alternative is remove the link to other manuals entirely when we know it doesn't exist in the other version, but this then breaks navigation completely in terms of visiting the other manuals. There is no quick fix, or even medium term fix, for this problem at the moment, even if the problems of where would link to could be fixed. At the present time this bug cannot be fixed within the limits of the existing infrastructure and layout, and there is no reasonable workaround or alternative that will eliminate or solve the problem. I have, however, logged the problem and it will be considered as part of other improvements and changes to the way we currently build and publish the documentation.
[16 Oct 2009 16:14]
Olaf van der Spek
> The other alternative is remove the link to other manuals entirely when we know it doesn't exist in the other version, but this then breaks navigation completely in terms of visiting the other manuals. I don't understand this part. If the link target doesn't exist and the link redirects back to where you came from, removing the link doesn't seem like a bad idea.
