Apache OpenOffice (AOO) Bugzilla – Issue 2201
broken link for the last month!
Last modified: 2003-12-06 14:52:32 UTC
the above URL is linked to from this page: http://www.openoffice.org/dev_docs/source/download.html ...and it has broken for at least a month, since I last tried it! The error message says something about "local-access-only" in the URL Not Found The requested URL /local-access-only/www/www/dev_docs/source/release_notes_638c.html was not found on this server. Apache/1.3.19 Server at localhost Port 80
OK maybe it hasn't been a month if 638c only came out around 10-13, but it's been a few weeks since I first heard about 638c and found that broken link. I have just now for the first time successfully found a link to the release notes... from the download page.
not sure what you want me to do.... as it happens, the release notes are certainly available from the download page, but also from the 638c page: by each build. closing issue. louis
Sorry, my second comment must have been confusing. When I said it worked from the "Download" page, I meant this one: http://www.openoffice.org/dev_docs/source/build_638c/build638c.html#binaries ...which has a link to: http://www.openoffice.org/dev_docs/source/build_638c/release_notes_638c.html ...which works GREAT! So HERE is the problem. From the URL I first mentioned: http://www.openoffice.org/dev_docs/source/download.html The link entitled "Release Notes" is broken. This is the second link from the left on the third bulleted item (right after the link to "Features"): http://www.openoffice.org/dev_docs/source/release_notes_638c.html So from comparing the two URLS pointing to the file "release_notes_638c.html" it would seem to me that the "build_638c" directory is missing from the broken URL. The "URL" field in this issue report now points to the page which HAS the broken link, rather than the broken page. I suppose that makes more sense. Sorry for any confusion.
fixed.
As agreed by Louis I will close these resolved fixed support-owned issues now. If you have trouble with that, please re-open the issue.