-
Suggestion
-
Resolution: Answered
NOTE: This suggestion is for Confluence Cloud. Using Confluence Server? See the corresponding suggestion.
The Gliffy Plugin for Confluence stores diagram data as XML Attachments to pages.
If a customer searches for content, and a Gliffy document is a search result, when the user clicks on the search result they get the un-rendered XML of a Gliffy document.
Ideally, we'd like the customer to be provided a link which points to a page which renders the diagram in a user friendly manner.
If there was a way to hook into the links that are generated for search results, we could populate that link such that the diagram is rendered correctly for the user.
This is a customer request.
- is related to
-
- Closed
-
- Gathering Interest
- relates to
-
- Gathering Interest
[AI-695] Define custom links for search results
True, this is a workaround. However, it's difficult to explain this to my users, as it's different behavior compared to all other search results.
Any plans to make a better workaround (read: solution 
)?
There is a workaround – you can navigate to the Confluence page that contains a Gliffy diagram by clicking the small gray text below the diagram search result.
Mike
Gliffy Engineer
Gregory Frazier
added a comment - This is a major issue for us and its causing us many problems. Please fix this!
Gregory Frazier
added a comment - This is a major issue for us and its causing us many problems. Please fix this! 
Charlie Hayes
added a comment - This issue is affecting many members of our team. This obviously isn't resolved, why mark it resolved? If anything give it a low priority.
Charlie Hayes
added a comment - This issue is affecting many members of our team. This obviously isn't resolved, why mark it resolved? If anything give it a low priority. We would really like to have a solution to this behavior. Our users get confused when they get a xml page as search result instead of the page with the Gliffy diagram. Any chance that this ticket will be re-opened?
Bob Kennedy
added a comment - So one day my customers can see Gliffy's the next they get garbage? Removing functionality without telling us is just bad. In the future some notice in release notes for an upgrade would be helpful.
Bob Kennedy
added a comment - So one day my customers can see Gliffy's the next they get garbage? Removing functionality without telling us is just bad. In the future some notice in release notes for an upgrade would be helpful. Thank you for raising this issue. While we can see how this feature would be useful, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request now.
Thanks again for your idea.
Bill Arconati,
Confluence Group Product Manager
We're still investigating this, but it appears that Atlassian have stopped using the SearchResultRenderer hook points in Confluence 5.2+. Older versions render results properly. No changes were made on our end which would have broken this functionality. Confusingly, the SearchResultRenderer interface is still public in 5.2+, but it doesn't appear to be used by Confluence. Here's the doc: https://docs.atlassian.com/atlassian-confluence/5.4.4/com/atlassian/confluence/plugin/SearchResultRenderer.html
Mike Cialowicz
Gliffy Engineer
Since your "A whole new search, Stop looking, start finding." update (https://www.atlassian.com/en/software/confluence/whats-new/confluence-improved-search) our users have trouble opening gliffy-diagrams on our intranet. Since we have organization-charts done with gliffy this is a big pain. . I would expect the search results link to “viewlargediagram.action” for gliffy. IMO also other documents could be handled better with a preview.
See https://jira.atlassian.com/browse/CONF-36691 as well.