Results 1 to 3 of 3

Thread: URLs in comments area

  1. #1

    URLs in comments area

    Ever since the major upgrade to Trove was made, any Trove URLs I use in the comments sections of articles no longer work.

    The clickable part of each URL stops at "http://nla.gov.au/nla", with the rest of the URL becoming just plain text.

    E.g.:
    http://trove.nla.gov.au/newspaper/article/76689562
    http://trove.nla.gov.au/newspaper/article/225623763
    http://trove.nla.gov.au/newspaper/article/4832307

    Oddly enough, links to URLs outside of Trove can work without a problem.
    E.g.: http://trove.nla.gov.au/newspaper/article/12879021
    http://trove.nla.gov.au/newspaper/article/146225826

    Unfortunately, the comments section doesn't give access to the source code, so I can't edit the URLs.
    I tried adding HTML link codes to the URLs, but the Trove software still cut off the links at "http://nla.gov.au/nla". (What the ???)
    e.g. http://trove.nla.gov.au/newspaper/article/130702623
    http://trove.nla.gov.au/newspaper/article/31666434
    -- If I click to edit the comment, my HTML link coding is still there - but the Trove software is disabling it somehow.

    Prior to the major upgrade, the URLs worked fine.
    I had expected that this was just a teething problem which would be fixed soon after the upgrade had been put in place, but no such luck.
    (Or maybe the problem had somehow not been noticed?)

    Is it possible that this problem will be fixed?
    If it is fixed, would the "fix" correct the past problematic URLs?

  2. #2
    Prolific poster
    Join Date
    Feb 2011
    Posts
    336
    I know this problem has been reported to Trove staff, as I reported it over six months ago. However, there is a way around the problem in the interim.

    Using one of your example comments (at http://trove.nla.gov.au/newspaper/article/130702623), where you will have entered the following in the text of a Comment - and this is also what you will see when you try to edit the Comment:
    See also: The Queanbeyan Age and Queanbeyan Observer (NSW : 1915 - 1927), 29 June 1915, p. 2, http://nla.gov.au/nla.news-article31666434
    The Comment text above has resulted in the following Comment being created, with a faulty link:
    InstituteOfAustralianCulture
    a year ago (Feb 20, 2016 7:42 PM)
    See also: The Queanbeyan Age and Queanbeyan Observer (NSW : 1915 - 1927), 29 June 1915, p. 2, http://nla.gov.au/nla.news-article31666434

    Having looked at various Comments with links I have noticed that the generated links are failing at the first full stop (.), or the first pipe character (|), following the last forward slash (/).
    So links that do not have a full stop or pipe character after the last forward slash do in fact function correctly in a Comment.

    An example of a faulty non-Trove web address with a full stop (.) following the last forward slash (/):
    http://nla.gov.au/nla.news-article4201483 - with the faulty link shown as http://bpadula.tripod.com/walksdiary/index.html
    An example of a faulty web address with a pipe character (|) following the last forward slash (/):
    http://nla.gov.au/nla.news-article28029365


    I also notice that Comments with links that existed prior to the major Trove upgrade also have the same problem, but when you go to edit one of these earlier Comments you do in fact see the source code for the link. If your example Comment had been made prior to the major upgrade the contents of the Comment when editing it would look like this:
    See also: The Queanbeyan Age and Queanbeyan Observer (NSW : 1915 - 1927), 29 June 1915, p. 2,
    <a href="http://nla.gov.au/nla.news-article31666434">http://nla.gov.au/nla.news-article31666434</a>
    Using the source code format from the Comment above gives us a way around the problem. The bit following "href=" gives the actual link and the second part gives the text of the link as it is to appear in the finished comment. If you replace this second part with something like "Follow this link" instead of a web address, as follows:
    See also: The Queanbeyan Age and Queanbeyan Observer (NSW : 1915 - 1927), 29 June 1915, p. 2,
    <a href="http://nla.gov.au/nla.news-article31666434">Follow this link</a>
    ...... then voila, it works !! The Comment will appear as follows with a working link:
    See also: The Queanbeyan Age and Queanbeyan Observer (NSW : 1915 - 1927), 29 June 1915, p. 2, Follow this link

    So it appears the faulty links are not caused by the actual link provided but the text that is displayed for the link, i.e. when it is the same as the web address itself (and contains a full stop following the last forward slash).

    I am guessing that this bug is an unintended consequence of code that was designed to create valid links from Comment text that contains web addresses with an end of sentence full stop immediately afterwards.
    Last edited by Spearth; 09-07-2017 at 06:24 PM. Reason: Corrections to get links to appear correctly in this post

  3. #3
    Prolific poster
    Join Date
    Feb 2011
    Posts
    336
    There also appears to be a problem with email addresses included in Comments.

    Often the part of an email address after the @ character appears as a blue link, but often it does not. There seems to be no rhyme nor reason to the difference, in fact exactly the same email address can appear both ways in different Comments.

    I actually saw one case where someone had entered the email address with a # character, instead of the @ character, and that part after the character was shown as a blue link.

    When I tried creating a new Comment with an email address then it would not appear as a link at all.

    There is obviously something messed up here.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •