Menu

#7 Clicking URL refs to html in mercurial repos start download not page display.

None
closed
website (3)
2
2015-06-10
2013-10-14
Greg White
No

THIS ISSUE IS INTENDED TO BE UPDATED AS PROBLEMS ARE FOUND IN THE DOCUMENTATION.
SO, THIS ISSUE WHOULD BE TREATED AS 'UNDER CONSTRUCTION'.

Summary:
Direct URL references from the website pages to html in mercurial repos, was broken by SF's move to newSF. Rather than displaying the HTML directly from the mercurial raw-source, the source documents are now instead downloaded!

Eg all references to URLs with "raw-file", eg following, must be fixed:
http://epics-pvdata.sourceforge.net/hgweb/pvAccessJava/raw-file/tip/documentation/pvAccessJava.html

Discussion

  • Ralph Lange

    Ralph Lange - 2013-11-28

    This is only indirectly related to the SF changes.
    This is the hgweb instance that is running as part of our webspace, using repository copies inside our webspace.
    The version of hgweb is different than the older, patched version SF was using on their old repository servers.

    The docbuild area of our webspace is used for documentation being put together during a build (static and generated). This is documented in the AccessToWebSpace guide.
    As such, it contains documentation, but not other files from the source repositories.

    The correct link for your example is:
    http://epics-pvdata.sourceforge.net/docbuild/pvAccessJava/tip/documentation/pvAccessJava.html

    When changing, please change these links to relative URLs.
    This makes sure the webspace as a whole is position independent, and the links between static documents always stay within the same set of files.
    I.e., relative links in your checked-out version of pvDataWWW work as expected, and do not all point to the remote SF webspace.

    So, the correct html tag for the link mentioned above in a top level html document would be

    <a href="docbuild/pvAccessJava/tip/documentation/pvAccessJava.html">foobar</a>
    
     

    Last edit: Ralph Lange 2013-11-28
  • Ralph Lange

    Ralph Lange - 2015-06-10

    Issue is partly fixed, partly explained, partly not relevant anymore (after move to git@GitHub).

     
  • Ralph Lange

    Ralph Lange - 2015-06-10
    • status: open --> closed
    • Group: -->
     

Log in to post a comment.