| Summary: | [Webapp] Wrong doc path when a page is referenced twice | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Samuel Wu <samuelwu> | ||||||||||
| Component: | User Assistance | Assignee: | Chris Goldthorpe <cgold> | ||||||||||
| Status: | RESOLVED FIXED | QA Contact: | |||||||||||
| Severity: | normal | ||||||||||||
| Priority: | P3 | CC: | cgold | ||||||||||
| Version: | 3.2.1 | ||||||||||||
| Target Milestone: | 3.8 M2 | ||||||||||||
| Hardware: | PC | ||||||||||||
| OS: | Windows XP | ||||||||||||
| Whiteboard: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Samuel Wu
Created attachment 183622 [details]
Screen capture of the problem
Any update on this one? This is not so easy to fix - it would require putting more information in the TOC which would have a small performance impact for all users. What is the circumstance which causes a document to be in more than one TOC - can you work around the problem by making one of the references be a link from a page rather than a link in the TOC file? There are a couple of editors and language parsers in our product. The help contains a category for editors and another one for parsers. A help page on customizing a parser for a specific editor is shared under both categories. We can create a page which lists all the customization choices, but we do prefer that these topics are listed as the toc items since it's consistent to the rest part of the help. Created attachment 202463 [details]
Patch version 1
Here is the initial version of the patch. Note that this causes 3 Junit tests in TocFragmentServiceTest to fail because they are checking the result of calling the TocFragmentServlet and that result has now changed.
Created attachment 202557 [details]
Patch for tests
The tests were failing because the test was checking for the values of hrefs in topics. Those hrefs now have an addition parameter representing the position of the element in the toc tree.
Targeting 3.8M2 Created attachment 202826 [details]
Patch as committed
This patch has been committed to master.
This is now fixed. |