cancel
Showing results for 
Search instead for 
Did you mean: 

selecting a 'comment' from search,yields unexpected behavior

fjdoyle
Champ in-the-making
Champ in-the-making
I did not submit this as a JIRA bug, because I'm not a hundred percent sure how it is intended to work.
I have a document library in a site.  In a folder ("TestFolder1" on that document library is a pdf file.  On that file's page, I add a comment "test_comment".
If I search "test_comment", the result list includes "comment-1260481949982_786".  If I click on that, it brings me to a file preview page (such as the one the comment was created on) with the Flash preview showing the text of the comment.  The breadcrumb on top shows:
LocationSmiley Very Happyocuments>TestFolder1>doc.pdf>doc.pdf discussion>Comments (each as folder icons)
If I click on the doc.pdf breadcrumb, I end up in what looks like an empty folder (the folder tree on the left shows the parent "TestFolder1" open, but there is no "doc.pdf" folder in the tree, yet the breadcrumb list still looks like that is where I am.

1.) I would think clicking on a comment in a result list would bring you to the document preview page that comment resided on.
2.) If not, I would at least think it should be easy to get to that point from the pseudo-content preview that is created for the comment.

Is this some oddity peculiar to my installation, or is no one else using comments/selecting them from search results…or did I just miss somebody else's mention of this?
3 REPLIES 3

zaizi
Champ in-the-making
Champ in-the-making
The search is done using this web script;

http://localhost:8080/share/proxy/alfresco/slingshot/search?site={sitename&term={query term}&maxResu...

In the comments in the code include;

// PENDING: how to handle comments? the document should
   //          be returned instead

Hope that answers you question.

fjdoyle
Champ in-the-making
Champ in-the-making
Actually no…I wasn't asking where the code was, I was asking whether the behavior exhibited was intended and if so, why…as it seems utterly counter intuitive and fairly useless.

mikeh
Star Contributor
Star Contributor
It's not intended, we just haven't got around to fixing it yet.

Thanks,
Mike